How the WebSphere Adapter for Siebel Business Applications works

WebSphere® Adapter for Siebel Business Applications connects to Siebel applications by making calls to the Siebel native interfaces and passing data to and receiving data from the Siebel application. The adapter supports Siebel business services only in this release.

The adapter models Siebel business service method calls as business objects. Outbound event processing consists of the following steps:
  1. A business object representing the Siebel method call is passed from the JCA client application to the adapter using the common client interface (CCI) record. The CCI record is an instance of the CCI implementation that enables the interaction between the J2EE application and the adapter, and then to the Siebel back-end system. This record generates and sets the business object.
  2. The adapter extracts the elements from the business object and, using the metadata information from the business object, recognizes the Siebel interface to use.
  3. The adapter converts the business object data to the appropriate Siebel method call.
  4. The adapter executes the method on the designated Siebel business service.

For inbound processing, the adapter models the integration objects as business objects. You select the business service name that processes the required integration object. For example, you select EAI Siebel Adapter if you plan to use an integration object based on a Siebel business object or you select Siebel Account if you plan to use Account Interface as the integration object for your inbound processing.

For outbound processing, Event Method is not used and should be left blank when the service type is outbound. This is used by the adapter for inbound processing alone to retrieve the integration object; this should be the business service method name that does the retrieval.

Inbound processing consists of the following steps:
  1. The adapter polls the event component at regular intervals.
  2. If an event is found, the integration object represented by the event is retrieved.
  3. The appropriate verb is set and dispatched to the registered endpoints.

Terms of use |

Last updated: Sun Mar 12 11:38:27 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)