The naming convention for business objects representing Siebel business services are the same for both inbound and outbound processing.
Business object naming format | Description |
---|---|
Prefix | The Prefix property value is prefixed
to the names of the WebSphere business objects generated against the following:
|
Business Service Name | The business service for the business object. |
Integration Object | The underlying integration object for the Siebel message container business object. |
Integration Component | The underlying Integration component for the Siebel Message container business object. |
Outbound
<Prefix><Business Service Name><Method Name><Names of all the integration objects
selected for the Input and InputOutput arguments>
<Prefix><Business Service Name><Method Name><Names of all the integration objects
selected for the output arguments>
<Prefix><Business Service Name><Method Name>
<Top Level business object Name> + BG.
Examples
IBMEAISiebelAdapterInsertAccountInterfaceBusinessAddressInterface
IBMEAISiebelAdapterInsertAccountInterfaceBusinessAddressInterfaceBG
‘IO’ + <Name of Integration Object> + ‘IC’ + <Name of integration component>
As an example, the Account Interface integration object with the integration component Account has the business object name, IOAccountInterfaceICAccount.
Inbound
Since the objects are generated only for integration components, the naming convention for inbound objects follows the one used for outbound objects generated against integration components. However, there is a business graph generated too.