WebSphere Message Brokers
File: csba_busobjstruc_bs
Writer: Karen Cameron

Concept topic

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

Business object structure

The following business object structures show a method with the same integration object as the input and output, an inbound event business object based on the account interface integration object, and a method with a different integration object as the input and output.

A method with the same integration object as the input and output

The following naming conventions apply to the diagrams showing methods, inputs, and outputs.
  • <Prefix> - Prefix as stated in enterprise metadata discovery (EMD)
  • <BSN> - The business service name for the business object
  • <Method> - The method the business object was generated against
  • <IO> - The underlying integration object is chosen to be used in the method

The following diagram represents a method with the same integration object being used as input and output.

Figure 1. A method with the same integration object as the input and output

An inbound business object based on the account interface integration object

The top-level object of the business structure contains metadata information that states the business service for which the business object corresponds. The business graph contains top-level verbs which are used during event notification as an emit event which is based on the verb. The verbs currently supported are Create, Update, and Delete.

The following diagram represents a business object for an inbound event. The top-level data represents both input and output arguments with the Siebel message as a container. This same business object can be used for both request and response to and from the adapter to interact with the underlying Siebel enterprise information system (EIS). This means that the same business object type that you send in as a request is returned as the result of the execution.

The Siebel message is a wrapper similar to the wrapper the Siebel EIS uses to wrap integration objects (IO) and their respective fields and components within business services, as shown below.

Figure 2. An event business object based on the account interface IO

A method with a different integration object as the input and output

The following diagram corresponds to a custom business service with a different integration object as the method’s input and output.

Figure 3. A method with the same integration object as the input and output
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:26

csba_busobjstruc_bs This topic's URL is: