How the Adapter for Siebel Business Applications works

This topic describes how the Adapter for Siebel Business Applications works.

The WebSphere Adapter for Siebel Business Applications connects to Siebel applications running on application servers. It does so by making calls to the Siebel native interfaces and passing data to and from the Siebel application. The adapter supports Siebel integration interfaces.

The adapter models Siebel function calls as business objects. Outbound event processing consists of the following steps:
  1. A business object representing the Siebel function call is passed from the JCA client application to the adapter via the CCI record. The CCI record, which is an instance of the Common Client Interface implementation, enables the interaction from the J2EE application to the adapter, and then to the Siebel backend 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 function call.
  4. The adapter then executes the function on the destinated Siebel Business Application system.

For inbound processing, the adapter spawns listener threads to the Siebel application. Whenever an event occurs in Siebel, the event is pushed to the adapter via the event listeners. The adapter can track and recover events in case of abrupt termination using the data source for persisting the event state in an event recovery table.

Note that the adapter supports container managed sign-on and basic authentication. It does not support re-authentication.

The following diagram illustrates how the adapter communicates with the Siebel application for inbound and outbound processing. Diagram needed.

Parent topic: Product overview