Business object naming convention for business components includes
the concatenation of several words for both outbound and inbound events.
All business object names have the following format for outbound and inbound
operations:
<Prefix><BO><Business Object Name><BC><Business Component
Name>
- Prefix An optional prefix, which is placed at the start of the
business object name.
- Business object Name The Siebel business object name under which
the Siebel business components are grouped.
- Business component The Siebel business component name.
Note: The Siebel business object and component names are stripped of all non-alpha-numeric
characters before being added to the WebSphere business integration business
object name. If the resultant names have uniqueness issues, a counter will
be suffixed to the names. For example, if two WBI business objects have the
name SiebelBOAccountBCBusinessAddress, the names are suffixed with the counter
to get unique values, for example, SiebelBOAccountBCAddress1 and SiebelBOAccountBCAddress2.
Currently, the special character (non-alpha-numeric) in the name is replaced
with "U"+"its Unicode number".
A business graph is generated for the top-level business object. The business
graph name has the following format:
<Prefix><BO><Business Object Name><BC><Business Component Name> + BG
To support the RetrieveAll operation, a container business object is generated.
The complex type within the container object will be the top-level business
graph. The container business object has the following format:
<Prefix><BO><Business Object Name><BC><Business Component Name> + Container
The business object generated for the Exists operation has the following
format:
<SiebelExistsResult.xsd>
This fixed name is always used for the return WebSphere business integration
business object of the Exists operation. The business object generated for
the Exists operation contains one Boolean attribute showing the return status.
A business graph is not generated for the corresponding ExistsResult business
object because there is no need for one.
Terms of use |
Last updated: Thu 12 Oct 2006 03:37:03
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)