The most difficult error that I fixed during this web service implementation was when there was no error.
Confused ???

 Let me make it simple. After fixing the errors mentioned in previous post my workflow executed successfully but web service returned below mentioned error response
 —————
“Error Occurred.Please ensure you enter proper IP address or try again later”
—————

 I was not able to find what could be wrong as I couldn’t see what SOAP request was going out. Normal logging techniques such as Environmental Variable, Spool, Workflow debugging don’t log EAI Requests or Responses.

 After a bit of research I found an SR on Metalink that tells you how you can enable log to capture every bit information about Siebel operations that involve EAI. Follow the steps given below to enable EAI Logs for dedicated client

•  Open your client CFG file
• Add the following lines in your cfg file after [Siebel] Section
  [EAISubsys]
  EnableServiceArgTracing = TRUE
• Save your CFG file

You are done!!!

 Don’t forget to enable logs for dedicated client after this. Once you do that you start seeing *.dmp (as shown below) files in the directory where your logs are being generated.

These dmp files will have the exact SOAP Request (OutboundDispatcher_output_args_xx.dmp) and SOAP Response returned by Web Service (OutboundDispatcher_input_args_xx.dmp). From now on if you even query using EAI Siebel Adapter business service you will see dmp files showing you exactly the input that was given to EAI Siebel Adapter BS and the output you received.

Just one more post remaining in this series where I will try to answer your questions or doubts. So if you have any questions, don’t wait ask today. I will try to answer them to best of my ability.

 Enjoy!!!