on 07-08-2012 9:48 AM
Hi Experts,
I would like to share one intersting situation at client side where I need your inputs.
We have developed SOAP to file scenario in PI 7.1 as per functional inputs.
We have tested this scenario and after testing delivered webservice to client.
Now the point is, client having two different system (.net based and Java based).
In .net based system they are able to consume webservice and everything is working fine.
But same Java based system , we are giving them same webservice and they are not able to consume and it is NOT hitting to PI.
We have tested this many times. It is showing – 400 BAD REQUEST error. Client’s feedback is there is problem with webservice and PI system.
What you suggest ? What should be alternative approach?
Thanks.
>What you suggest ? What should be alternative approach?
My approach would be like this. You have already created webservice and generated service definition and in turn provided WSDL to the sender systems (both Java and .Net). To check whether the service works or not, use SOAPUI or XMLSPY and test your web service. If that works, Problem is at sender side. Since it is already working in one system (say .net) , I think the problem is at the web service client implementation logic in the java system. Your job is to provide WSDL to the sender system. The java team has to convert wsdl2java to generate webservice client proxy objects. Please ask them whether they have any error in wsdl2java conversion. If there are no errors, you dont need to worry at PI side. It is their side issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anshul,
I agree with Baskar. Probably ask the .Net team to share the code logic with JAVA team for a quick comparison.
Regards
Hemant Chahal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.