Last Login: June 23, 2022 11:54 AM CEST Switch to Cloud Support Abhishek (Available) (0) Contact Us Help

 
Dashboard Knowledge Service Requests Patches & Updates Community

Give Feedback...
Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.

How to enable detailed logging for tracing and troubleshooting Siebel EAI and UCM issues (Doc ID 1929084.2) To Bottom

Dedicated Web Client EAI Object Manager,

Resetting Web
Client & (Application WfProcMgr & MQSeriesReceiver,
Introduction Logging Services Troubleshooting
Siebel Object WfProcBatchMgr JMSReceiver,
Level Integration
Tools Manager) UCMBatchProcess
Search This Document Print

Tracing on the Siebel Dedicated Client and Siebel Tools

If you are trying to trace details for a problem when using a Siebel Dedicated Client application or Siebel Tools, then perform these step:

1. Navigate to the dedicated client machine.

2. On the machine's desktop > select the {My Computer} icon > right-click > Properties.

a. In the System Properties dialog box > select the {Advanced} tab > click on the {Environment Variables} button.

b. In the Environment Variables dialog box > click on the {New} button from the System Variables section.

c. In the New System Variable dialog box, enter:

Variable name: SIEBEL_LOG_EVENTS

Variable value: 5

Note: Level 5 provides the maximum tracing, this level is advised for debugging problems and other operations/navigations performed by using the
dedicated client.

d. Click {OK} to close out the New System Variable dialog box.

e. Click {OK} to close out the Environment Variables dialog box.

f. Click {OK} to close out the System Properties dialog box.

The above environment variable setting applies to both Siebel Dedicated Client and Siebel Tools.

3. Modify the client cfg file by adding this section:

[EAISubsys]

EnableServiceArgTracing = TRUE

This parameter will produce Inbound*.dmp and Outbound*.dmp files which are generated for Siebel web service processing. This parameter setting only
applies to the Siebel Dedicated Client cfg file here, as that is where the web service execution occurs on. This parameter does not apply to Siebel Tools
since Web Services will not and do not run on the Siebel Tools application.

4. Launch the Siebel Tools or Siebel dedicated client application using the programs shortcut.

5. Perform the test case to reproduce the issue depending on what the problem is.

a. If the test case involves executing a workflow process, execute the workflow process through the Siebel Client Business Service Simulator View or
through the runtime event invocation.

b. If the test case involves navigating through screens/views/applets to create/update data and/or click a button which triggers some event and invokes
some Workflow or Business Service, please proceed forward with those steps.

c. If the test case involves using Siebel Tools to debug some custom script or to simulate a workflow process, then use Siebel Tools to perform the test
case.

6. Once the workflow or test execution has performed to a point where error or incorrect behaviour has occurred or the problem has been reproduced,
close out any error message prompts/dialog boxes. Close out the Siebel dedicated client application.

7. On the machine, launch the Windows Explorer, navigate to the respective location/directory to retrieve the log files:

a. If you launch Siebel Dedicated Client standalone from the command line or program shortcuts, then the log file for it would be in
SIEBEL_CLIENT_HOME\log\siebel.log file.

b. If you launch Siebel Dedicated Client from within Siebel Tools such as using F5, or debugging a custom business service script, or simulating a Workflow
Process from Siebel Tools, then the log files would be located in:

- Siebel Tools log file would be in SIEBEL_TOOLS_HOME\log\siebdev.log file [Back To Top]

 - Siebel Dedicated Client log file (invoked from Siebel Tools), would be in SIEBEL_TOOLS_HOME\log\siebel.log file

8. Review the siebdev.log or siebel.log file to the point of the error message and then traverse upwards in the log file to find out what queries/operations
the workflow or application was performing right before the error occurred.

9. Files to collect and provide:

a. Object Manager log file: Provide the siebel.log file for the Siebel Dedicated Client execution details; or siebdev.log if the issue is for troubleshooting
problems within Siebel Tools.

b. SOAP request/response *.dmp files: If web services are involved, then also provide any *.dmp files generated, note the following about the dmp files:

- On the web service consumer application, you should these file created by the WebService dispatcher when you run your application invoking the web
service:

OutboundDispatcher_input_args_<pid>.dmp
OutboundDispatcher_output_args_<pid>.dmp

The output_args log shows your SOAP request and the input_args log shows the SOAP response. The SOAP response may be a SOAP fault message or
empty file if your SOAP request was not valid.

- On the server, if your request is successfully received and processed, you will see these two additional logs:

InboundDispatcher_input_args_<pid>.dmp
InboundDispatcher_output_args_<pid>.dmp

The input_args log shows the inbound SOAP request received and the output_args log shows the SOAP response sent out. The SOAP response may be a
SOAP fault message if your inbound request was not valid.

c. WSDL file: For web service scenarios, please also provide the WSDL file for the Web Service being invoked.

d. Workflow Process export: If there are custom workflow processes being invoked/involved, please export out the workflow processes into .xml file and
provide the .xml files.

e. Business Service export: If there are custom business service scripts being invoked/involved, please archive out the business service into a .sif file and
and provide the .sif files.

f. Screenshots: At times, it may also be beneficial to take/include screenshots showing various views, applets, buttons, errors, record data/values, etc.
Please include the screenshots if possible and appropriate.

g. Put all files into a folder named accordingly and zip up the folder into one zip file.

h. Then, upload/attach the zip file to the respective Siebel Service Request.

10. Reset the logging afterwards:

Once problem reproduction/testing is completed, or the issue is resolved, or you no longer need to detailed logging level in place for the time being, reset
the logging level on Dedicated Client by:

a. Setting the environment variable back to 1:

Variable name: SIEBEL_LOG_EVENTS

Variable value: 1

b. Modify the client cfg file by setting the parameter to FALSE:

[EAISubsys]

EnableServiceArgTracing = FALSE

c. Close out the Dedicated Client and restart it again.

REFERENCES

<>
Didn't find what you are looking for? Ask in Community...

Related
Products

Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM > Siebel EAI > General
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM > Siebel Workflow > Other
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM > System Admin > Data Quality
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Universal Customer Master > Universal Customer Master > Inbound Web Services
Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM > Client Functionality > Data Quality

Keywords
BATCH MANAGER; COMPONENT; DMP; EAI OBJECT MANAGER; ENABLESERVICEARGTRACING; ERROR MESSAGE; LOG FILE; LOG LEVEL; PROCESS EXECUTION; SOAPUI; SQL LOG; SQL
TRACING; TRACE; WORKFLOW; XML [Back To Top]