Copying and reusing Project components

Design Center uses internal keys to identify the different components used in the Design Center Projects. This applies to all Design Center components represented by files:

•	Platform (*.dcplatform)

•	Physical Platform layer (*.dcphyspf)

•	Runtime configuration (*.dcruntime)

•	Physical runtime configuration layer (*.dcphysrt)

•	Message configuration (*.dcmessage)

•	Process (*.dcprocess)

•	Resource (*.dcres)

•	Resource set (*.dcrset)

This means all Design Center Project files must have unique keys. If several files have the same key, Design Center cannot identify which file to use where.

Copying components

If you copy/paste component files on disk, the keys are copied as well. This means the original file and the copy will have the same key, and Design Center cannot tell them apart. This will most likely lead to failure when you try to run the StreamServer application after exporting and deploying the Design Center Project.

If you want to copy a component in a Design Center Project, and use it in the same Project or in another Project that has any relations to the original Project, you must make sure the original component and the copy have unique keys. If you do it the right way, Design Center will generate new unique keys for the new components.

In this section

•	Copying Events

•	Copying Processes

•	Sharing Processes

•	Copying Message configurations

•	Sharing Message configurations

•	Copying resources

•	Sharing resources

•	Performing a sanity check