Posts Tagged ‘Siebel EAI’

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

 

 

Siebel – Data Exchange Scenarios

 

Following are the four possible data exchange scenarios:

Additional processing may include following two cases:

  1. Transforming the data at Siebel end due to difference in data structure of exchanged information
  2. Routing incoming XML to desired process based on its content.

 

Method NameRepresents the methods available in various Siebel EAI business services. Please refer the snapshot below for an example of methods exposed by EAI File Transport business service.