Siebel – EnableServiceArgTracing – Logging Messages
Hi,
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.
Siebel – Enable Detailed Logging – Local
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.