on 07-30-2012 11:26 PM
Hi,
I am working on a scenario where we send the messages from Biztalk to PI to SAP.
Earlier we were testing our interface in PI7.0 and the testing was successful, but when we tried to route our interface through upgraded PI7.3 system, the messages are getting failed at the Adapter engine with the attached error and the messages are not moved to PI.
Kindly provide your valuable inputs as why the interface is working in old PI and not in the upgraded version.
SOAP Sender Channel settings:
Transport Protocol: HTTP
Message Protocol: SOAP1.1
Adapter Engine: Central Adapter Engine
Quality of Service: Exactly Once
Regards,
Sat
Can you try using nosoap=true in the SOAP URL from Biztalk to PI, if dynamic configurations does not play significant role in your scenario.
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/3555240bea31c3e10000000a42189d/content.htm
3. Define Conversion Parameters --> point 1
- praveen
Message was edited by: Praveen Gujjeti
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From the error screenshot it looks like the dynamic configuration related to <BtsActionMapping> is causing the issue.
Can you compare the dynamic configuration in 7.0 and 7.3 see what is different? That should give you a clue as to what is different between 7.1 and 7.3. You can then act accordingly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Nageshwar point seems right. There are some differences in dynamic configurations method call usage between Pi 7.0 and later versions. Please refer the wiki and see the step 5.
http://wiki.sdn.sap.com/wiki/display/XI/Using+PI+7.1+API+for+Java+mapping
Hope that helps.
>>There are some differences in dynamic configurations method call usage between Pi 7.0 and later versions.
Bhaskar, I do not think retrieving dynamic headers during java mapping is related to the question asked. The issue is message parsing is failing in Adapter engine before it can push the message to Integration Engine.
>Earlier we were testing our interface in PI7.0 and the testing was successful, but when we tried to route our interface through upgraded PI7.3 system, the messages are getting failed at the Adapter engine with the attached error and the messages are not moved to PI.
After Pi server upgrade, endpoint location, port might be different. Please check the URL for this soap service and send the mesg accordingly. Otherwise generate the WSDL from the upgraded PI server and use SOAPUI or XMLSPY and test the interface first. You can also find endpoint location in wsdl and use them for testing. Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
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.