GeeKs Blogging @ dotCOM

Siebel – EAI JMS Transport

by Vikas Luthra

---

Hi All,

After being a mere spectator and a regular visitor of GeeksBlogging@dotCOM for last one month, here is my first post.

In this JMS Transport series I’ll be covering following topics:-

What are Transports?
Different Methods available for Transports
Java Business Service
EAI JMS Transport and Server Setup for Inbound Receiver
How to setup local client for using EAI JMS Transport
How to connect to an MQ server using EAI JMS Transport

Before proceeding with EAI JMS Transport following concepts should be understood:-

EAI Transports
Java Business Service (Next Post)

EAI Transports:-

Transports are the means of exchanging data between different applications. w.r.t Siebel we can say that, the transports are used to send\receive data between Siebel application and other external application (say any other legacy application). This exchange of data is achieved using the API’s like EAI JMS Transport, EAI MQSeries Server Transport, provided by Siebel to connect to different communication protocols like MQSeries from IBM, MSMQ from Microsoft, HTTP etc.

Transports support bidirectional exchange of messages. As each Transport adapter is having a business service record in Siebel so these can be invoked using script, workflow process, the similar way any other business service is invoked.

Transports can invoke other workflows as well, for e.g. in case of inbound integration you have to specify what to do with the incoming message, whether to dispatch it to a workflow or some custom business service or Dispatch Rules etc. So for this you can specify the name of the business service/workflow in the Data Handling subsystem (covered in later topics)

Another flexibility provided by these transports is that in future if the technologies are changed (say you upgraded your external application from Java based technology to some other web based technology), the existing workflows\logic can be reused with minimum modifications by just changing the transport adapter. For e.g , if earlier EAI JMS Transport was used, now after up gradation you can switch to EAI HTTP Transport.

Each Transport requires a different set up\configurations, like JMS transports requires JVM installation and different jar files on the Siebel server machine. Similarly MQ transport requires the MQ server installation etc.

Different transports available are:-
EAI MQSeries Server Transport
EAI MSMQ Transport
EAI HTTP Transport
EAI JMS Transport
EAI File Transport

That’s All Folks
Any Comments\feedbacks\discussions are welcome.

Related posts:

1. Siebel – SIA BC Utility Service – Invoke BC Method I had discussed about the vanilla Business Service, “SIA BC...
2. Siebel – EAI Siebel Adapter – Looping Multiple Records This is a follow-up post on the post, Siebel –...
3. Siebel – SIA BC Utility Service – Loop multiple records This is a vanilla business service which provides an extensive...
4. Siebel – ActivateField() split wide open In Siebel, we generally tend to use the fields on...
5. Siebel – EnableServiceArgTracing – Logging Messages Hi, We have already discussed at quite a length the...
6. Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...
7. Siebel – SIS OM PMT Service There are lots of vanilla business services available in Siebel...