Integration Of Third Party Appication With Siebel

I have seen developers discussing different ways to integrate third party applications with Siebel. Hope this nicely elaborated article will help you understanding this better.

I have asked industry experts to share their ideas on to this and now publishing responses with you. More ideas are open. Lets discuss this and provide your expert suggestion in comment section.

Responses of industry expert:

Read what Joan Martí Peraire says about intgrating siebel with third party appication.

In order to integrate Siebel with external application, what I can share, from my own experience, is that there are two options that can be easily carried out without any problem:

Option A: Using synchronous workflow that retrieve xml file that contains process information.

You should create integration objects within the Siebel repository to provide the definition of the mapping between the fields in the xml and Siebel.

Add a Sub Process step to invoke an EAI XML Converter(using this integration object created as a Input Argument – IntObjectName)
Business Service Name: EAI XML Converter
Business Service Method: XMLDocToIntObjHier

In Addition, add another Sub Process step to invoke an EAI Siebel Adapter Upsert (When a Workflow Process has a Business Object then a Siebel Operation Upsert step defined will upsert the record in the Primary Buisiness Component.)
Business Service Name: EAI Siebel Adapter
Business Service Method: Upsert

(*) For queues we need an external system/middleware.

Option B: Data load via EIM

EIM batch jobs are used for bulk data load. EIM are background batch jobs (not real time jobs).

In this case it’s required:

1. Previous Thread : PL/SQL can be used in order to delete previous records in EIM table.

delete from siebel.eim_EXAMPLE
where if_row_batch_num = LOT_NUMBER;

2. Preparing the EIM Tables : This section provides assistance in loading the EIM tables with data used to control insertion of rows from Siebel base tables.

insert into siebel.eim_EXAMPLE (
/* This value in combination with the nonempty contents of if_row_batch_num must yield a unique value. */
/* Set this to an identifying number for all EIM table rows to be processed as a batch.*/
/* In each row to be deleted, set this column to FOR_INSERT to indicate that the row has not been inserted. */
/*Add Required Fields to be informed*/

3. Finally, execute EIM through Server Manager, using a sentence such as:

set ExecuteEIM =”Run task for component EIM with config=C:\sea704\EXAMPLE.ifb”

%SRVRMGR%srvrmgr /g %SERVER% /e % SERVER % /u %USER% /p %PASSWORD% /s %EIMSERVER% /c %ExecuteEIM% /o %BASE%\Log.LOG

Feel free to contact Joan Martí Peraire for any information/query on above article:

4 comments on “Integration Of Third Party Appication With Siebel”

  1. Ajay Godbole Reply

    Another Option is to use Inbound WebServices which will use the same steps from Option A.

    You can import the WSDL in Tools to create External Integration Objects.

    In the workflow process, the Initial step will be to define a Mapping in the DataMap Editor to map between the External and Internal Integration Objects. Rest of the workflow steps remain the same.

  2. Narayan Patro Reply

    I would emphasize on Joan Martí Peraire’s words wherein the high level category is Real time and Batch load. Both are ways of integrating Siebel with third party applications.
    Siebel provides a lot of ways for real – time interfaces to work. All one have to do is judge the requirements alongwith scalability option and adopt one or more ways to accomplish the same. I have outlined the different real time integrations supported:
    Data Sharing Integrations include EBC and VBC configurations.
    Data replicating integrations include the following:
    1. Peer to Peer integration using HTTP
    2. Web Services / ASI
    3. Queue Based Transport (MSMQ, IBM MQ and JMS)
    4. COM Based Integration (DLL) — Tightly coupled interfaces.
    5. Java Based Integration (uses Java Class from external application and EAI Java Business Service to integrate)
    6. File Based real time integration — This approach is a bit different from the batch load done via EIM. In this approach, files can be placed on a local filesystem or a ftp server from which an RCR can pick the file and pass it onto a workflow or BS for further processing.

    Again all these integrations support synchronous or asynchronous mode exception being Queue based which only supports asynchronous mode. However you can achieve near real-time integration using Queue based system.

  3. Piyush Reply

    There are few points I would like to add from my exp.

    While integrating siebel with external application, we use Web services, queues or batch integrations.

    1. Web Services: They are the fastest method of integrating external applications. Pros are like no extra setup needed, data can travel via internet.But they have their cons like, limitation of data to be sent (vary from 1-4MB), retry mechanism needed in case of failure.
    Web services can be real time as well as background jobs.

    2. Queues: In queues we can send more data as compared to web services. No retry mechanism in needed incase of queues. In this way queues are more reilable. But for queues we need extra h/w as well as s/w setup at siebel as well as external system/middleware

    3. EIM: EIM batch jobs are used for bulk data load. EIM are background batch jobs. they are not real time jobs.


  4. Naresh Reply

    There is another way of integrating 3rd party applications with Siebel.
    Symbolic URLs, these will act as direct link of 3rd party applications into siebel, by allowing access to that application from siebel within.

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!