Outbound Web Service- Problems & Solutions

 All right now let’s get on to the different problems and their solutions that I faced while working on this Outbound Web Service. Most of the problems that I faced were when I tried to use workflows.

 Error:

——————————————

Argument ‘SiebelMessage’ in step ‘Set Child Type’ is not correctly initialized or does not return valid data.(SBL-BPR-00107)

——————————————-

Reason/Solution:

I faced this error when I tried to pass a property set from a custom business service  (BS to change header) to the workflow and then after a bit of research I came across this SR which basically tells that to receive and hierarchical output from a Business Service to a Workflow our output argument on Business Service should have same name as Root Element of the hierarchy.

 For example in this case we were trying to return the hierarchy with root element as GetGeoIPSoapIn:parameters and in workflow I had named the output argument as ‘SiebelMessage’ which resulted in above mentioned error. Once I change the output argument name to GetGeoIPSoapIn:parameters in workflow it started working fine.

 I faced the same error when I tried to change the Type of Siebel Message to GetGeoIPSoapIn:parameters with help of PRM ANI Utility Service using SetChildType method as, this method suppose to provide output as ‘SiebelMessage’

 Error:

——————————————-

HTTP Request error during ‘Submitting Data SendHTTP request’: ‘Status code – 503′(SBL-EAI-04117)

——————————————-

Reason/Solution:

I got this error quite a few times while testing web service. If you are familiar with HTTP status codes then you will have not problem in understanding this error but if you are not then you can have pretty hard time in finding the root cause of this error.

 HTTP Status – 503 means timeout which means that the web service is not responding. If the web service at webservicex.net is too busy then you can receive this error.