The business object naming convention includes the concatenation of several words for both outbound and inbound events.
The naming convention for the business objects includes the concatenation of several words which include:
Outbound
The top-level business object name has the following format:
<Prefix><Business Service Name><Method Name><Names of all the integration objects selected for the Input and InputOutput complex type 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 complex type arguments>
If there are no complex arguments in the method, the name format 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:
Examples
When using the prefix, IBM®, you generate a business object for the EAI Siebel 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.
For the outbound objects generated against integration components, the following naming convention applies: ‘IO’ + <Name of Integration Object> + ‘IC’ + <Name of integration component>.
As an example, the Account Interface integration object 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.
Last updated: Sun Mar 12 11:38:28 2006
(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)