Archive for the ‘Enterprise Application Integration (EAI)’ Category

Integration Components

Integration Components (ICs) are the building blocks of Integration Objects. As IO is mapped to BO, in the same fashion, IC is mapped to corresponding BC.

  • One or more IC constitutes the integration object.
  • At least one IC will be primary corresponding to primary business component of the business object.
  • There would be zero or more child IC with respect to child business components in the business object.
  • Each MVG in business component is exposed as a child IC under the integration object.

Integration components have following Integration Component Keys (ICK):

  • User Keys – Set of fields to determine the records uniquely
  • Status Keys – To store the Siebel Row ID and operation status for insert, update or delete scenarios

On creating the integration objects through Siebel Wizard:

  • Calculated Fields at the business component are imported automatically as inactive fields in Integration Component.
  • For any unneeded field, mark it as Inactive. Never delete a field from Integration component as it will be added again when Business Object is upgraded.

Integration Objects – Types

There are two types of Integration Objects as follow:

1. Internal IO

  1. Describes structure of data being read or written to Siebel application
  2. Represents a subset of Siebel Business Object


2. External IO

  1. Describes of structure of data being exchanged between Siebel application and External application
  2. Is required in two scenarios:
    • External application is unable to handle data in Siebel format
    • Additional manipulation is required before saving the received data at Siebel end


Integration Objects


Integration Objects (IO) defines the structure of data to be exchanged between Siebel application and external system. IO represents hierarchical data structures.

IO also used as templates to create memory-resident instances for data processing by business services.

IO consists of Integration Components (IC). One of them is marked as Primary IC. IC further consists of Integration Component Fields (ICF).




Siebel EAI – Prebuilt Business Services

  • Accessing data in Siebel Application
    • EAI Siebel Adapter
  • Formatting the data
    • EAI XML Converter
  • Transporting data to external applications
    • EAI File Transport
    • EAI HTTP Transport
    • EAI MQSeries Server Transport
  • Transforming data between Siebel and external application data structures
    • EAI Data Transformation Engine
  • Processing messages based on content (i.e. same format but different content)
    • EAI Dispatch Service

Siebel EAI – Four basic Steps

Siebel integration involves following four basic steps:

1.     Access Data

  1. For inbound integration, Siebel will receive and save data
  2. For outbound integration, Siebel will retrieve and send data


2.     Convert Data

  1. Siebel stores data in tables.
  2. But to transport data, it is converted into more convenient format.
  3. Popular industry standard is XML format


3.     Sending Data

  1. Prepared data is sent over some specific channel – it can be HTTP protocol or any other industry standard transport


4.     Transforming Data

  1. Siebel uses tables as its data structure
  2. External application may use any other data structures to store their data
  3. On exchange of information between two systems having different data structure, it is required to transform the data and then save it.


Send Scenario


Receive Scenario