Message not found in Message Monitoring

[former_member228170]

Hi Experts,

We are sending a message from PI 7.3 system SOAP Adapter XI 3.0 Protocol to PI 7.4 System which is on HEC. Packets will be sent to 7.4 system that is on HEC through LOAD BALANCER which is connected to WEB DISPATCHER.  In PI 7.4 system, we are using SOAP Adapter with XI 3.0 Protocol as Sender Channel. We are able to send Message successfully to PI 7.4 System. We are also able to see a hit in PI 7.4 system in Logs and Traces(NWA) but we are not able to see anything in Message Monitoring in PI 7.4. Please suggest as to why we are not able to see any message in Message Monitoring. Please find the screenshot of the log(NWA).

Regards,

Karthik

[engswee · Accepted solution]

Hi Karthik

Can you provide screenshot of

i) message/audit log of message in sender system (PI 7.3)

ii) communication channel log of sender SOAP channel in receiver system (PI 7.4)

By the way, is there any particular reason why you are going for XI 3.0 protocol for the SOAP channel? Is there any requirement to transfer some dynamic header values or retain the message ID across systems? If not, then using SOAP 1.1 protocol would be more straightforward to configure.

If you want to use XI 3.0 protocol, you need to ensure that the sender and receiver systems have the same name across both PI systems. For example:-

ICO in PI 7.3 system:-

Sender system = BC_A

Receiver system = BC_B

Both BC_A and BC_B needs to be available in PI 7.4 system, because XI 3.0 transfers the routing information and expects an ICO which has the same sender/receiver system. Otherwise, it will not be able to find the sender agreement binding.

Regards

Eng Swee

[engswee · Accepted solution]

Just to add on to this:-

Refer the following thread on troubleshooting an PI-PI connection over SOAP (XI 3.0 protocol)

You need to set the appropriate header mapping in the ICO of your sender system, and use virtual receiver in the ICO of your receiver system.

Eventually the OP also summarized the configuration require for the issue in the following blog:

[former_member228170 · Accepted solution]

Hi Eng Swee Yeoh,

Ya we had maintained Header Mapping correctly at both sides and we were using XI Protocol at both sides. We suspected a network issue as we were trying to connect to PI on HEC but after a Cache Refresh on PI 7.3 system, we got the issue at PI 7.3 (Sender system) and we were able to resolve it with the help of the discussion ( URL for PO while migrating XI channel ) which you have shared.

Thanks and regards,

Karthik

[iaki_vila]

Hi Karthik,

If you are talking about adapter level please check this blog because you need to activate it:

If you are talking about ABAP engine in a dual stack system, check this link:

Regards.

[former_member186851]

Hello Karthik,

Check in the channel monitoring Logs.

And since your external web service I believe you should change the protocol to HTTP instead of XI 3.0.

[former_member228170]

Hi Raghu,

We are using Transport Protocol as HTTP and Message Protocol as XI3.0 in SOAP Adapters at both the PI systems.

Regards,

Karthik