EAI Siebel Adapter finds its usage in almost all integration scenarios and business process automation. However, at times we hit upon limitations on its usage as Business Requirements become complex.
There is a bug which you must have encountered while using EAI Siebel Adapter BS. I will explain the issue with an example and a solution to resolve the issue…
We discussed about fetching the values from the active view in my post yesterday.
However, I also felt that it was a very crude way of doing it. We can only get the information we need, by writing a small script for it. Moreover, the information was very limited.
Siebel is POWERFUL! Now, need I even say that? And, in all its beauty and glory is the vanilla functionality. I keep coming across something new and novel everyday, and wondering, what percentage of 1% of Siebel do I now understand?!!
Here is another such Business Service that I came across the other day, “FINS Teller UI Navigation”. It has the following methods (my uncalled personal analysis is mentioned herewith):
RefreshRecord() does not work in all cases, does it?
This is a very common requirement I have seen in almost all Siebel EAI implementations. We have data flowing IN and OUT of the Siebel CRM system. It is updated in the Database alright, but, how do we update the user on the UI. I am assuming a quick data interchange in Real-time using a VBC or a Web Service or something similar. Whenever we update the Database using a Workflow or a script here, the UI will not refresh automatically, and though the process would end successfully (I hope it does), the user would never come to know about the successful updation until he manually does a Query + Go on the Applet, or uses the famed Alt+Enter Hotkey.
This is a follow-up post on the post, Siebel – Looping Multiple Records – III. We are looking at possibly more conventional methods to loop through multiple records in Siebel, than the SIA BC Utility Service.
We will make use of EAI Siebel Adapter’s QueryPage method to achieve the same. Knowledge of Siebel Workflow processes is essential to understanding this post.
The QueryPage method allows us to input an additional parameter, NumOutputObjects, to define the number of records that we want to output. Why not set this value to ’1′?
Following is an outline of the Dummy Workflow I used to achieve this.
Looping through multiple records is a requirement we come across multiple times in almost all Siebel Implementations. And, I can’t recall how many times I have seen dirty scripts to achieve the objective.
I call this Part III, as we have already covered this before on GeeksBlogging@dotCOM, in the articles,
Siebel – Looping multiple records – Query and Process
Siebel – SIA BC Utility Service – Loop multiple records
Somebody recently asked me if there is a way that we can force the user to Logoff from the current session, under some specific conditions. My simple research in Siebel Tools and around it brought up the following alternatives.
Vanilla Business Service Methods:
1) BS Name = LS Medical Product Issue Service
Method = Logoff
I can bet that for anybody who has worked on Siebel EAI, ‘EAI Siebel Adapter’ is not an Alien term. This post is about EAI Siebel Adapter’s Query method.
How to restrict the number of Child records returned in Siebel adapter’s Query.
Scenario – Order and related Order Line Items
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
“Extracting values from a tag deep down in the Hierarchy.” How many times have you come across this problem, and how many times have you wished that Siebel has an OOB method to help you extract these values?
Well, here it is. The “FINS Industry XML Query Service” in Siebel does just that. I am covering this here because of lack of documentation on the same by Oracle, and the immense use that this can be put to. This BS can save you a lot of headache of writing custom scripts to parse the entire XML Hierarchy in Siebel eScript, which can be a real pain in the neck.
This blog post will target the detailed usage of the BS, “FINS Industry XML Query Service” in Siebel CRM. This BS can be used directly in a Siebel Workflow, since this is vanilla. No scripting is needed which is as per the recommendations of Siebel Best Practices.
We have already discussed at quite a length the logging methods, the most prominent of these being the usage of vanilla Siebel EAI Queues. You can read about the entire series through the following links:
A meeting with Siebel EAI
Siebel – EAI Queue
Siebel – EAI Queue – Usage
Siebel – EAI Queue – a Critique’
I recently came across another vanilla method (EnableServiceArgTracing) to log the messages. Using this, the various Siebel logs can be created, and the Input and the Output messages to some of the Business Services can be written in XML format to a file. These XML files would appear as Siebel Dump files with a “.dmp” extension. These can be read off any standard text reading tool like Notepad, Editplus, Notepad++, etc. This process works with EAI Siebel Adapter and EAI Dispatcher business services.
Very often we come across scenarios wherein the process is not really clear through the interface exposed to us. We generally need to go into detailed logs at various levels to understand the internal process, and as to which all parameters are flowing at each step in the flow. The server level settings are different. I will cover here, as to how we can enable or disable detailed logging of Siebel processes in our Dedicated, Local or Sample environments. We can use it to understand complex Siebel processes in detail, for eg. eConfigurator and ePricer related flows.
After introduction of party model, the table structure (as far as EIM is concerned) have changed tremendously. The largest data model change involves the Party model, which I think is basis of post siebel 7 releases. Accounts, Organizations, Internal Divisions, Contacts, Employees, Positions, and Households are all party entities and are the logical extension table of S_PARTY and they all have the corresponding entry in S_PARTY base table and the data is brought into the business components through an implicit join (PLEASE NOTE THEY ARE NOT EXPLICIT JOINS).