WebSphere Message Brokers
File: csba_busobjsnamingconv_bs
Writer: Karen Cameron

Concept topic

This build: July 31, 2007 21:40:25

Business object naming convention for business objects representing Siebel business services

The naming convention for business objects representing Siebel business services are the same for both inbound and outbound processing.

The naming convention for the business objects includes the concatenation of several words, as seen in the following table:
Table 1. Business object naming formats and descriptions
Business object naming format Description
Prefix
The Prefix property value is prefixed to the names of the WebSphere business objects generated against the following:
  • Siebel business objects and components, for both inbound and outbound processing.
  • Siebel Business services, outbound processing only.
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

The integration object, top-level business object, has the following naming convention:
<Prefix><Business Service Name><Method Name><Names of all the integration objects 
selected for the Input and InputOutput arguments>
If there are no Input or InputOutput arguments, the names of all the output arguments used in the concatenation have the following format:
<Prefix><Business Service Name><Method Name><Names of all the integration objects 
selected for the output arguments>
If there are no complex arguments in the method, the naming convention has the following format:
<Prefix><Business Service Name><Method Name>
The business graph names, for the top-level business objects generated against the business service methods, have the following format:
<Top Level business object Name> + BG.

Examples

When using the prefix, IBM, you generate a business object for the Siebel EAI Adapter and insert method, and then choose the Account Interface and Business Address Interface integration objects against an Input and InputOutput method argument. The corresponding business object generated is:
IBMEAISiebelAdapterInsertAccountInterfaceBusinessAddressInterface
This gets created for the choices mentioned above. The business graph name is:
 IBMEAISiebelAdapterInsertAccountInterfaceBusinessAddressInterfaceBG
The integration-component level for the outbound objects generated against integration components, have the following naming convention:
‘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.

The business graph has the suffix, BG, added to the business object name, for example, IOAccountInterfaceICAccountBG.
Note: The Prefix property value is never used for the inbound service type.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:40:25

csba_busobjsnamingconv_bs This topic's URL is: