on 06-20-2016 6:41 PM
Dear Expert,
We are facing an issue with HTTP_AAE Receiver communication Channel.
The interface is like Proxy to HTTP Scenario and SAP PI version 7.4 Dual Stack.
while sending data from SAP the data will reached to SAP PI/Po and all pipeline steps completed in Moni messages.
But facing problem in HTTP_AAE Receiver communication Channel. SAP PI is internal server and HTTP Application(3rd party application) is outer Network.
By using this we are sending the attachments and data. but in receiver communication Channel we are getting Problem.
Error Log:
Regards,
Kiran Polani
Hello Kiran,
The error states that the Status Code is not correct. Basically PI expects a HTTP 200.
The request is being rejected by your Target System.
To resolve this issue I would suggest you use the HTTP_AAE Tracing Parameter as suggested by SAP in this note 2157425 - New Feature: Client side HTTP Tracing for HTTP_AAE adapter
Add Parameter TraceHTTP with value Plain in your receiver HTTP_AAE Adapter Module.
This will then dump the entire raw HTTP message to the Logs in .../server#/log/pi_http directory
This will make sure you can monitor the request and response and then work with your 3rd Party team on the resolution.
Do note this feature is supported only PI 7.31 Sp14 and greater, PI 7.4 SP 9 and greater.
Regards
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kiran,
To solve your issue you have to check certain things step by step.
telnet host name of third party 443, eg, telnet xxxx.com 443
This should result Connected to telnet xxxx.com , if there is no network or port issue, else work with your network team to open the HTTPS port 443 if its not open.
Please follow the above steps, and let me know if still you have issue.
Thanks,
Farhan
Hello Kiran,
definitely HTTP 3xx errors indicate that the destination content was moved. But sometimes it happens because of port forwarding. Please check align with receiver the current HTTP server settings. We had an issue in the past when receiver had forwarded the requests to port 443 over port 80.
Best regards,
Vadym
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.