Integration Of Third Party Appication With Siebel — Continued

Discussion on Integrating siebel with other application has attracted experts from industries. Below published articles has been shared by siebel EAI champions in our website and linkedin group. Hope this will help you.

Sanjiv  [CEO at Khanna Consulting] has participated in this discussion, Lets read his contribution

 It is a very broad topic considering the various permutations and combinations. I can almost write a book on this topic. The discussion can be devided into 2 topics. First would on various ways to connect to Siebel and second one would be the various ways to read/manipulate data. In terms of connections

following are some of the popular options:

1. COM Objects
2. HTTP Adapters
3. Siebel Web Services
4. Messaging Services
5. Custom Business Services
6. Direct database connection

There are many more options available that are not so popular. In reality the options depend on the technogies adopted by the company.

After you connect to Siebel, there are many options available to process the data depending on the direction of data movement. Some of the most popular

options are:

1. Integration Objects
2. Custom Business Services (Scripting)
3. Business Objects
4. EIM

Not all options are available with all the connections.

My preference is Integration Object. I have build generic products that enhance Siebel capabilities allowing users to easily get data in and out of Siebel

with very little development. These technologies can also be used for reporting and data movement within Siebel

Lets read what Narayan Patro has to say on this.

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.

Piyush has added points to this discussion as per his vast experience in siebel integration

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.


Siebel Oracle CRM Expert Group

Read more on our linkedin group.

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

  1. Krishna Reply

    trying to develop web service to bring product data from erp system into siebel app. Using SWI Product Import bs and corresponding IOs (SWI Admin ISS Product Definition, SWIProductIntegrationIO). Product part works fine. Have added Product Eligibility Buscomp as child to Product. Have added IC in above two IOs.Tested with SOAP UI. Web service accepts data for Product eligibility but it’s not creating records. It’s not throwing error either. Did any of you worked on this kind of requirement?
    share thoughts?

    thanks in advance.

  2. Daniel Rodriguez Reply

    Hi Krishna. Sometimes the solution that we use is make a simple workflow for insert / update records (using the EAI Siebel Adapter and a Internal Integration Object). Then we publish this workflow like a Inbound Web Service. If you want, I can explain step by step the solution.
    Hope that help you. Regards.
    Daniel Rodriguez

Leave A Reply

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

error: Content is protected !!