A Design Object is uniquely identified by the name and namespace and is assigned to one software component. You can create different design objects to perform various functions and few are mandate objects and others are optional in an integration scenario. Most common design objects include process integration scenario, message types, data types, mappings, etc.
The following table defines common design objects, their functions and use in a scenario −
|Integration scenarios||No||It is used to bundle all necessary design objects|
|Message types||Yes||It is used to encapsulate data types|
|Data types||Yes||It is used to describe structure of data to be exchanged|
|Service Interfaces||Yes||It encapsulates message types and parameters|
|Mapping||No||Mapping of message|
|Integration processes||No||It defines ccBPM workflows|
These Design Objects are often represented in the form of hierarchy.