SAP PI/PO : Read messages IDs on PO system in single stack Java

[former_member623506]

Hello,

I would like to read messages IDs on my PO system from ECC system.

There is a webservice called AdapterMessageMonitoringVi which can be used to retrieve XI message remotely as described on https://blogs.sap.com/2015/01/22/reading-messages-from-pi-system/

I followed this blog too for calling the webservice from ABAP : https://blogs.sap.com/2013/06/06/create-an-sap-web-service-consumer-calling-external-web-service-fro...

I would like to call this Webservice from my ECC system but i've got an error for the response.

So, i created the service consumer with the WSDL : http://<host>:<port>/AdapterMessageMonitoring/basic?wsdl

I configured the logical port on SOAMANAGER :

When i try to test the proxy(F8) :

On SRT_UTIL :

In addition, when i try the same request on SOAPUI tool, it works perfectly.

Did i miss something with my configuration on ECC ?

Thanks in advance.

[former_member623506 · Accepted solution]

Hi

Problem resolved ! 🙂

For using the webservice AdapterMessageMonitoringVi the sap blog mentioned to use the WSDL : http://<host>:<port>/AdapterMessageMonitoring/basic?wsdl&mode=ws_policy&style=document

But i couldn't use this URL (error on the suffix "ws_policy") to create my service consumer. So, i used the URL without suffix : http://<host>:<port>/AdapterMessageMonitoring/basic?wsdl

In SRT trace, i got a response with an other XML format => This is due to the URL i used.

So i regenerate my service consumer with this URL :

http://<host>:<port>/AdapterMessageMonitoring/basic?wsdl&style=document (I let the suffixe "style=document)

[JaySchwendemann · Accepted solution]

Thanks for letting us know how you solved that. That's the spirit

[former_member623506]

Hi,

Thanks for your answer, i will try to trace my webservice.

In addition, when i try it into a program and debug it, i've got an error when the CALL TRANSFORMATION XML -> ABAP is called.

[JaySchwendemann]

I think your are not getting back an XML response, at least not the one your consumer proxy expects.

I would increase / start tracing in SRT so you might see the payload you are getting back. I could imagine some authentication error or other faults that result in an Non-XML response or an XML in another format.

Generally your approach seems legit

Cheers

Jens