Connection from DP to SAP PI 7.11 via SOAP/https failed

[Former Member]

Hello Guys,

we have a problem with connection from DP to SAP PI via SOAP/https.

DP send a request and get a timeout. timeout is 2 or 3 minutes.

DP and SAP PI authentificated with certificates.

Our Problems:

DP get now failure code

in commnication channel monitoring in RWB from SAP PI I see no entry, no error

in java default trace I see no error.

What could be the Problem? What must we configure for https communication via SOAP Adapter?

Which Log get me some information?

Thanks and regards

Martin

[Former Member]

Martin,

DP send a request and get a timeout. timeout is 2 or 3 minutes.
DP get now failure code

Have you tried sending the request to PI using any external tool like SOAPUI? What is the failure code that you get?

in commnication channel monitoring in RWB from SAP PI I see no entry, no error
in java default trace I see no error.

Yes, the request is not "entering" PI, so no logs will be there. The logs will be at the sending system side, so check there.

Regards,

Neetesh

[Former Member]

Have you tried sending the request to PI using any external tool like SOAPUI? What is the failure code that you get?

Yes I have. But the client with soapUI stand in another network zone.

Yes, the request is not "entering" PI, so no logs will be there. The logs will be at the sending system side, so check there.

The sender system get only a timeout and no error message. It looks like, that the sender could authenticated with certificate. But than no message come through the communication channel.

I look up to the default java trace, ICM trace and no error is to see.

timeout = 2 minutes

What can I do?

thanks and regards Martin

[Former Member]

Martin,

I guess the problem lies with the firewall. Please talk to network folks, they might be able to give you further trace / logs on the SOAP request call.

Regards,

Neetesh

[Former Member]

Hi Neetesh,

sorry I forgot. We had tested the firewall. package go from DP to PI and also back.

I also see in the default Java trace, that DP login is ok. But no message and no error is to see.

regards Martin

[Former Member]

Hello Martin,

Please make sure all the configurations and settings for certificates is properly done.

Refer:-

http://help.sap.com/SAPhelp_nw70/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm

What is the calling URL? It should be in this format - http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

Try calling the above URL using SOAPUI etc, just to verify that you can reach PI.

Regards,

Neetesh

[Former Member]

Hi Neetesh,

I have check all, but it resolved not my problem.

I will describe my scenario again:

scenario:

syncronous request from system A over DataPower ->SAP PI to SAP system.

communication DataPower to PI: SOAP over https

DataPower located in other network zone.

port is activated in firewall.

called URL from DataPower:

https://<host>:5<instance number>01/XISOAPAdapter/MessageServlet?

channel=:<business system>:<interface>

Problem:

authentication looks like ok. No error in ICM Trace, in default java

trace login from DataPower IP-adress ok.

but no message is to see in the communication channel.

no message in the adapter engine, no message in the integration engine

DataPower get a timeout. (Timeout 2 minutes)

we find no error, but also no message

What could be the error? And where find I some information in SAP PI.

Thanks and regards

Martin

[Former Member]

Hello Martin,

we find no error, but also no message

The messages just can't disappear. It's hard for me to believe that your source system is getting back an acknowledgment for successful delivery, even if the message has not been delivered to PI.

Please check the following:-

1. Any proxy server is being used? Ask the network guys for the logs to verify if firewall server received the message.

2. Use TCP Gateway. Get the trace and analyze it.

3. Ask the web service guys how they have designed the acknowledgment of message delivery? Look for logs once again.

Regards,

Neetesh