on 11-17-2015 1:32 PM
Dear All,
Quadrem is 3rd party portal for receiving and sending purchase orders messages. We are able to send the PO messages from PI to Quadrem through SOAP receiver channel. But PI is not able to receive the PO response from Quadrem. We have SOAP sender channel in PI for receiving the messages from Quadrem.
While trying to send PO response message from Quadrem to PI, it is getting failed in Quadrem portal itself (we cannot see anything in SOAP sender channel in PI). It errors out in Quadrem portal with this error: connection closed by remote host.
The interface was running successfully earlier, past 1 week we are facing this issue.
Does anyone has pointers to fix the issue? Please share your valuable feedback.
Regards,
Ankit
Hi All,
Issue was in the Web Dispatcher.
Restarted the Sapwebdispatcher with command line only for WEB5Q.
One service was getting stopped automatically in one of the dispatcher where the PIQ message usually strikes.
TRACE levels were also changed for the services in Webdispatcher.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Can someone help me in what are the topic should i covered in SAP MM configuration.
M very new to it.
Regards
Idrees
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear All,
We have checked the web dispatcher logs. Once the message is sent from Quadrem to SAP, we can see hits on the firewall and the traffic is reaching web dispatcher.
But in the web dispatcher logs, we see the below log with status 500
QUADRAM - "POST /XISOAPAdapter/MessageServlet HTTP/1.1" 500
Does anyone know why through the web dispatcher, it is not going to PI systm?
Thanks,
Ankit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ankit,
But in the web dispatcher logs, we see the below log with status 500
QUADRAM - "POST /XISOAPAdapter/MessageServlet HTTP/1.1" 500
May be they are not calling the full URL like below.
Make sure they are using complete URL in their side when they calling your service.
You can also check in PI system for these type of errors in below directory(HTTP trace file)
/usr/sap/PID/DVEBMGS00/j2ee/cluster/server0/log/system/httpaccess
Regards,
Praveen.
Hello Praveen,
They are calling the full URL as per the convention. As the messages are not reaching PI, so the logs will not be available in PI directory:
/usr/sap/PID/DVEBMGS00/j2ee/cluster/server0/log/system/httpaccess
Recently on Quadrem side, they have changed certificate algorithm from SHA1 to SHA256. They already provided to us the new certificates and we have deployed them in PI. Hence, we are able to send the messages successfully to Quadrem.
Similarly, they have our client public certificate installed in their Quadrem system in order to send the messages from their Quadrem system to PI. I see that our public certificate is SHA1 based. Could it be a problem? Do we need to convert our public certificate from SHA1 to SHA2 and share it with the Quadrem team or it does not matter?
Thanks,
Ankit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Chaitanya for the reply.
The issue is not with the SOAP receiver (as we are able to send the messages to them). When Quadrem is trying to send the message, it is getting failed in their portal itself (no logs in SOAP sender channel as it is not able to make up to SAP PI).
Though any configuration has not changed, do we need to still ask portal team to import WSDL?
Regards,
Ankit
Hi Ankit,
What error getting in portal ? Ask them to send.
We can test inbound interfaces ( portal to SAP PI ) also in soap ui. We can send messages same as like third parties so that we can figure out the actual error..
No need to do any settings for certificate change in soap sender channel.
Regards,
Chaitanya.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
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.