Troubleshooting and verification:Dedicated clientIf you are using a dedicated client to perform the outbound web service call, please:1. Right click the icon used to call the dedicated client and select properties.2. In the properties window, target section Identify the .CFG file used. e.g: C:\Siebel\8.1\Client_1\bin\ENU\uagent.cfg3. Edit the CFG in notepad and add to the bottom of the file :

[EAISubsys]EnableServiceArgTracing = TRUE4. Save and close the CFG file.5. Close the dedicated client.6. Right click My Computer and select properties.Then advanced tab and environment variables.Add the variables:Environment variable nameValue

SIEBEL_LOG_EVENTS5

SIEBEL_LOG_DIRC:\TEMP (or any valid directory)

7. Restart the dedicated client and make the call to the outbound web service.8. Review the %SIEBEL_LOG_DIR%\OutboundDispatcher_output_args_0.dmpThis file contains the SOAP Request sent by Siebel and can be opened in any text editor.9. Review the %SIEBEL_LOG_DIR%\siebel.log file for errorsThin ClientIf you are using a thin client to perform the outbound web service call, please:1. At the siebel server machine, please open an MS-DOS command prompt (or a unix shell if applicable).2. Navigate to the siebelserver root directory.3. Cd siebsrvr4. Cd bin5. Call the server manger command line and notice the parameters :(Type srvrmgr and hit ENTER)6. Call it again with the correct parameters.The command will look similar to this :srvrmgr /g /e /s -u sadmin -p sadmin7. Once logged in, turn up log for the specific Object Manager you use :

change evtloglvl %=5 for comp change param enableserviceargtracing=true for comp 8. Review the siebsrvr\bin\OutboundDispatcher_output_args_0.dmp file.This file contains the SOAP Request sent by Siebel and can be opened in any text editor.Notice it is generated at the BIN directory.9. Review the component log, generated under siebsrvr/log (windows) or siebsrvr/enterprises//log (unix) for errors.Note: stands for the alias of the component actually running the call to the proxy business service.It can be an user interface object manager, like SCCObjMgr_enu for call center.Or it can also be a workflow component, like WFProcMgr.It all depends on how you designed your solution and where the actual call to the proxy business service will run.Using Siebel Service Argument Tracing To Capture the SOAP Message and for Troubleshooting

Within the Siebel Web Services framework, there are existing and new component events that you can enable that help you troubleshoot problems and capture the Simple Object Access Protocal (SOAP) messages exchanged.For a list of web services specific component events, see Integration Platform Technologies: Siebel EAI (Vol 2) > Web Services > Enabling Web Services Tracing.By enabling the WebSvcOutboundArgTrc (Web Service Outbound Argument Tracing) and WebSvcInboundArgTrc (Web Service Inbound Argument Tracing) events, you can capture the inbound and outbound SOAP messages generated.

Testing with a Dedicated Siebel Client

You can enable the events by modifying your client .cfg file and starting your Siebel client with logging enabled. For the dedicated client, add the following entries to your client's .cfg file:[EAISubsys]EnableServiceArgTracing = TRUEThen start your Siebel Client or Siebel Tools client with the environment variables SIEBEL_LOG_EVENTS=ALL and SIEBEL_LOG_DIR= set.

Testing with a Siebel Thin Client and for Siebel Server That Your Web Service Provided

You need to enable the events on the client's object manager such as the SCCObjMgr_enu for Call Center and the EAIObjmgr for the web service provider. In srvrmgr, the commands are:change param enableserviceargtracing=true for comp eaiobjmgr_enuchange evtloglvl %=5 for comp eaiobjmgr_enuNOTE: You may choose to enable additional component events, such as the EAI Siebel Adapter or EAISiebAdpt. By using the % wildcard, you can enable all commands that start with WebSvc.

Logs Generated

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_.dmpOutboundDispatcher_output_args_.dmpThe outut_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_.dmpInboundDispatcher_output_args_.dmpThe 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.

Sample SOAP Messages

This is a sample SOAP request for the SiebelContact ASI:

01/01/1950 00:00:00 support@siebel.com Siebel Support Technical 8002140400

true

This is a sample SOAP response:

42-4NZB7

This is a SOAP response with an error:

SOAP-ENV:ServerService Method arguments property set has no children, should have one child of type 'SiebelMessage'(SBL-EAI-04022)

Service Method arguments property set has no children, should have one child of type 'SiebelMessage'(SBL-EAI-04022)

In the above case, the error message is returned from the the Siebel Contact ASI business service on the web services provider because the input data was incomplete. The corresponding inbound SOAP message from the above example shows that incomplete input arguments were provided. There is only a value for the StatusObject argument and no Contact data.

true

The reason the message was incomplete is because the input arguments supplied to the web service proxy business service were wrong. So as a result the proxy business service did not know how to generate the expected input arguments for the web service.