on 01-04-2016 4:09 AM
Hi All:
I have the folowing problem with async ECC Proxy->SOAP integration:
System is sending messages correctly and the status is ok in RWB - but the 3rd parti system could not get message. And I tried use the SOAP UI to send the same message to the 3rd party, it can get the msg correctly.
Below are the audit log in RWB:
2016-01-04 11:06:31 Success Message successfully received by messaging system. Profile: XI URL: http://zzxis:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2016-01-04 11:06:31 Success Message successfully put into the queue.
2016-01-04 11:06:31 Success The message was successfully retrieved from the receive queue.
2016-01-04 11:06:31 Success The message status set to DLNG.
2016-01-04 11:06:31 Success Delivering to channel: CC_SOAP_BUYERCODE_AS
2016-01-04 11:06:31 Success MP: Entering module processor
2016-01-04 11:06:31 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2016-01-04 11:06:31 Success SOAP: request message entering the adapter with user J2EE_GUEST
2016-01-04 11:06:31 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2016-01-04 11:06:32 Success MP: Leaving module processor
2016-01-04 11:06:32 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
2016-01-04 11:06:32 Success The message status set to DLVD.
2016-01-04 11:06:32 Success SOAP: completed the processing
2016-01-04 11:06:32 Success SOAP: sending a delivery ack ...
2016-01-04 11:06:32 Success SOAP: sent a delivery ack
How could I check and fix this .
Highly appreciate for any inputs on this. Thanks
Hi Song Li
If you are on at least PI 7.31 SP09, I'd suggest you try to add the TraceHTTP parameter in your receiver SOAP channel to see what happens during the SOAP call. That might give you more insight into the issue.
Another alternative is to use XPI Inspector to trace the call too.
Try these and if you still cannot resolve the issue, please post additional details from the TraceHTTP log or XPI inspector so that it can be analysed further.
Rgds
Eng Swee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Solved by XSL mapping to replace the namespace.
In fact the soap message has arrived into the 3rd party. But the namespace is incorrect.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.