IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Siebel Business Applications > Overview of WebSphere Adapter for Siebel Business Applications > Technical overview

Inbound processing

WebSphere Adapter for Siebel Business Applications supports asynchronous inbound processing. The adapter polls the Siebel applications at specified intervals for events. When the adapter detects an event, it converts the event data into a business object and sends it to the component.

The following illustration shows the inbound processing flow for WebSphere Adapter for Siebel.

When the adapter detects an event for Siebel event business components or integration components, it processes it by retrieving the updated data and converting it into a business object. Then, the adapter sends the business object to the event business component.

For example, if an event business component (an account) is updated, an event trigger adds an event record to the event business component. The adapter then polls the event business component, retrieves the event record, and processes it.

When the adapter finds an event for a Siebel event business component, it is processed as follows:

  1. The adapter retrieves the event information from the Siebel event business component.
  2. It retrieves the corresponding event business component instance hierarchy.
  3. It populates the associated WebSphere business object or business graph (if it was generated) with the values it retrieves from the event business component.
  4. It sends a notification to each registered application.

Before inbound processing can occur, a Siebel event business component must be created in the Siebel application (IBM2 for Siebel version 7.x and IBM_EVENT for Siebel version 8) and its name specified against the corresponding property in the adapter activation specification.

Technical overview