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

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.



Siebel EAI – Data Transport Strategies

Siebel EAI toolkit provides following four options to transport/transfer data between Siebel system and any third party system:

 File Transport

  • Data is written is files by one system.
  • This file is placed over other system.


  • Data is transferred over HTTP protocol
  • This requires a web server to receive data

 Queue-based Transport

  • By using 3rd party messaging software/middlware
  • For example, Java Message Service, Microsoft MSMQ.


  • Logic to transport data is implemented as DLL file
  • Then by using EAI DLL Transport business service logic can be used.


Siebel EAI – Integration Strategies

 Siebel architecture has three layers – Data layer, Business layer and UI layer. Similarly, Siebel EAI allows integration options at all the above three layers.

Integration at Siebel Data Layer 

  • Data transfer takes place between Siebel database and External system database.
  • In this case, Business logic is bypassed. Hence an overhead to validate data before insertion.
  • Implemented via EIM Loads

Integration at Siebel Business Layer

  • Data transfer take place between Siebel Object Manager and third party system.
  • This integration is implemented by Siebel EAI toolkit (including business services, EAI component, Siebel tools etc).
  • Such Integration can further be segregated in two parts:
  • Closely Coupled
  • It is required to understand the programming language, data structure and relationship at other end.
  • Implemented via VBC or EBC
  • Loosely Coupled
    • It is based on standard consumable services.
    • Implemented via Web services, Industry Standard Transports or Oracle AIA

    Integration at Siebel UI Layer

    • Both data and functionality of a system is transferred to other.
    • For instance, external application or webpage is directly displayed in Siebel view.
    • Or Siebel view is displayed in any third party system
    • Implemented via Symbolic URL and SWE APIs.

    Siebel EAI – Types of Integration Architecture

    Following are three types of integration architecture supported by Siebel:

     1)    Peer Structure

    • Refers to a set of systems interacting with each other.
    • Bilateral message exchange between each pair of systems.
    • Same view of information for all the systems in the structure.

     2)    Consumer Services

    • Siebel explicitly access any third party system or provide access to any third party system to the information held by it.
    • View of information may not be same for all the systems involved.
    • For example, Siebel generate BI Reports through BI Publisher server through outbound web services


    3)    Alternate UI

    • This architecture allows transporting functionality with the data
    • That means Siebel may embedded web page in its view.
    • Or third party system can access Siebel views and utilize Siebel functionality as well.
    • For example, Siebel and MS Outlook integration.