GeeKs Blogging @ dotCOM

Siebel – EAI Queue

by Nitin Jain

---

Okay, what are you thinking about? Is it Middlewares in EAI with their queue managers and queues? No, those are not the ones I am talking about. Every EAI professional knows about those.

Siebel provides an Out of the Box Message Logging mechanism for Siebel EAI messages. This is done through a Siebel feature called ‘EAI Queue’ which I would be discussing in detail in this article.

I have tried to provide a basic idea about message interchange in EAI in my last post. You can read it by clicking here.

Let’s consider a typical EAI scenario wherein we are exchanging data between two different systems. Assume the format of message interchange to be XML.
Point to point contacts risk losing the data, or overheads in case the other system is down. Generally, the robust and stable Middlewares are used as a solution to this problem, one of them being the IBM MQ Series. However, sitting at Siebel end, we always need to have a Logging mechanism which will log all the inbound and outbound messages in Siebel. Generally, this always calls for a lot of overhead in every implementation if you go in for a custom approach. Custom tables, BCs, BOs, Applets, Access controls of these logs, Business Services to log and see, testing, defect fixing, etc. need to be created and maintained.

This is a perfect scenario for usage of EAI Queue feature. To view this in action, navigate to the screen Administration – Integration -> EAI Queue. Please note that you may need special licenses to have this feature enabled in your installation.

In this screen, you would see all Siebel queues listed in the top applet. Some of the vanilla queues you can see and test out on Sample DB installation are:

tRFC Outbound to SAP
tRFC Inbound from SAP
HA Upgrade Receiver Log Queue
S2S Outbound Sub-Process Log Queue
and many more..

In the bottom applet, you would see all the messages which have been placed corresponding to the record in the top applet. Every record stored here will have a new record corresponding to it. Following message details are stored:

Sequence #
Reference Id
Status
Queued Timestamp
Comments
Attachment Name
Message File Size

As you can see, this covers most of the functionality that you would ever come across to log messages. This is a complete OOB feature which would eliminate large scale customizations, and thus, would save large scale project time and resources to a great extent. If need be, we can always go in for some customizations to this to suit the corresponding project requirements.

We have discovered and viewed the details of Siebel’s own EAI Queues in this article. In my next post, I will cover the usage of this feature in Siebel as to how it can be incorporated in your Siebel architecture in your implementation.

Related posts:

1. Siebel – EAI Queue – a Critique’ I had introduced the Siebel EAI Queue and its usage...
2. Siebel – EAI Queue – Usage I had introduced the concept of Siebel EAI Queues in...
3. Siebel – EnableServiceArgTracing – Logging Messages Hi, We have already discussed at quite a length the...
4. Siebel – SIA BC Utility Service – Loop multiple records This is a vanilla business service which provides an extensive...
5. Siebel – Symbolic Strings – Usage Symbolic Strings appear directly in Siebel Tools’ Object Explorer, an...
6. Siebel – Refresh Applet retaining existing context RefreshRecord() does not work in all cases, does it? This...
7. Siebel – EAI Siebel Adapter – Looping Multiple Records This is a follow-up post on the post, Siebel –...