cancel
Showing results for 
Search instead for 
Did you mean: 

WSDL for AdapterMessageMonitoringVi web service

adityavempati
Participant
0 Kudos

Hi There,

I tried to get the message count of an interface which is in Adapter Engine by calling AdapterMessageMonitoringVi webservice via WSNavigator.

Could anyone help me in getting the wsdls (request and response) of this webservice and the URL to call it. So that I can import it in SOAP UI tool and play around.


References: http://scn.sap.com/community/pi-and-soa-middleware/blog/2015/01/22/reading-messages-from-pi-system


Regards,

Aditya Vempati

Accepted Solutions (0)

Answers (2)

Answers (2)

iaki_vila
Active Contributor
0 Kudos

Hi Aditya,

With the URL http://host:50000/AdapterMessageMonitoring/basic?wsdl, i can get the methods,

have you get any exception?

Regards.

adityavempati
Participant
0 Kudos

Hi Inaki Vila,

I got the wsdl and I imported it in SOAP UI. But, when I tried to test getMessageList.. I am getting an error in the response (mentioned above).. Could you please suggest..

Regards,

Aditya Vempati

former_member184720
Active Contributor
0 Kudos

Below URL should work. Remove spaces after "/"

http:// host:port/ AdapterMessageMonitoring/ basic?wsdl=binding&style=document

adityavempati
Participant
0 Kudos

Thanks Hareesh.


I was able to get the wsdl from that URL. Now, I imported it into the SOAP UI. To call that webservice.. what should I set the endpoint URL as?

Regards,

Aditya Vempati

former_member183908
Active Contributor
0 Kudos

once you load the WSDL into SOAP UI by creating new project automatically all the methods and target URL will be loaded.double click on the method and provide username and password and invoke the webservice.

Thanks

adityavempati
Participant
0 Kudos

But Pavan, no URL is loaded here..Just the operations are loaded..

former_member183908
Active Contributor
0 Kudos

Menu-->File-->New SOAPUI Project--->Browse the WSDL from your location,refer below screen shot

Its working for me.I hope you saved your WSDL file name with .wsdl extension

Thanks

adityavempati
Participant
0 Kudos

Hi Pavan,

Earlier I tried taking wsdl from / AdapterMessageMonitoring/ basic?wsdl=binding&style=document

URL wasn't formed for it.

This worked: / AdapterMessageMonitoring/ basic?wsdl&mode=ws_policy&style=document

Now, when I trigger the call for getIntegrationFlows I got the response.

But, when I trigger the call for getMessageList, I get the below fault message in response:

Deserializing fails. Nested message: XML Deserialization Error. Empty node passed to deserializer [com.sap.engine.services.webservices.jaxrpc.encoding.primitive.DateTimeSD] which is not acceptable..

Below is the request message:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:AdapterMessageMonitoringVi" xmlns:urn1="urn:com.sap.aii.mdt.server.adapterframework.ws" xmlns:urn2="urn:com.sap.aii.mdt.api.data" xmlns:lang="urn:java/lang">

   <soapenv:Header/>

   <soapenv:Body>

      <urn:getMessageList>

         <urn:filter>

            <!--Optional:-->

            <urn1:applicationComponent></urn1:applicationComponent>

            <urn1:archive>false</urn1:archive>

            <!--Optional:-->

            <urn1:connectionName></urn1:connectionName>

            <!--Optional:-->

            <urn1:correlationID></urn1:correlationID>

            <urn1:dateType>0</urn1:dateType>

            <!--Optional:-->

            <urn1:direction></urn1:direction>

            <!--Optional:-->

            <urn1:errorCategory></urn1:errorCategory>

            <!--Optional:-->

            <urn1:errorCode></urn1:errorCode>

            <!--Optional:-->

            <urn1:fromTime>2015-06-28T13:10:13.751+01:00</urn1:fromTime>

            <!--Optional:-->

            <urn1:interface>

               <!--Optional:-->

               <urn2:name>EmployeeNotificationToMYCAPP_Async_Inb</urn2:name>

               <!--Optional:-->

               <urn2:namespace></urn2:namespace>

            </urn1:interface>

            <!--Optional:-->

            <urn1:messageFormat></urn1:messageFormat>

            <!--Optional:-->

            <urn1:messageIDs>

               <!--Zero or more repetitions:-->

               <lang:String></lang:String>

            </urn1:messageIDs>

            <!--Optional:-->

            <urn1:messageType></urn1:messageType>

            <urn1:nodeId>0</urn1:nodeId>

            <urn1:onlyFaultyMessages>false</urn1:onlyFaultyMessages>

            <!--Optional:-->

            <urn1:persistUntil></urn1:persistUntil>

            <!--Optional:-->

            <urn1:protocol></urn1:protocol>

            <!--Optional:-->

            <urn1:qualityOfService></urn1:qualityOfService>

            <!--Optional:-->

            <urn1:receiverInterface>

               <!--Optional:-->

               <urn2:name></urn2:name>

               <!--Optional:-->

               <urn2:namespace></urn2:namespace>

            </urn1:receiverInterface>

            <!--Optional:-->

            <urn1:receiverName></urn1:receiverName>

            <!--Optional:-->

            <urn1:receiverParty>

               <!--Optional:-->

               <urn2:agency></urn2:agency>

               <!--Optional:-->

               <urn2:name></urn2:name>

               <!--Optional:-->

               <urn2:schema></urn2:schema>

            </urn1:receiverParty>

            <!--Optional:-->

            <urn1:referenceIDs>

               <!--Zero or more repetitions:-->

               <lang:String></lang:String>

            </urn1:referenceIDs>

            <urn1:retries>0</urn1:retries>

            <urn1:retryInterval>0</urn1:retryInterval>

            <!--Optional:-->

            <urn1:scheduleTime></urn1:scheduleTime>

            <!--Optional:-->

            <urn1:senderInterface>

               <!--Optional:-->

               <urn2:name></urn2:name>

               <!--Optional:-->

               <urn2:namespace></urn2:namespace>

            </urn1:senderInterface>

            <!--Optional:-->

            <urn1:senderName></urn1:senderName>

            <!--Optional:-->

            <urn1:senderParty>

               <!--Optional:-->

               <urn2:agency></urn2:agency>

               <!--Optional:-->

               <urn2:name></urn2:name>

               <!--Optional:-->

               <urn2:schema></urn2:schema>

            </urn1:senderParty>

            <!--Optional:-->

            <urn1:sequenceID></urn1:sequenceID>

            <!--Optional:-->

            <urn1:serializationContext></urn1:serializationContext>

            <!--Optional:-->

            <urn1:serviceDefinition></urn1:serviceDefinition>

            <!--Optional:-->

            <urn1:softwareComponent></urn1:softwareComponent>

            <!--Optional:-->

            <urn1:status></urn1:status>

            <!--Optional:-->

            <urn1:statuses>

               <!--Zero or more repetitions:-->

               <lang:String></lang:String>

            </urn1:statuses>

            <urn1:timesFailed></urn1:timesFailed>

            <!--Optional:-->

            <urn1:toTime>2015-06-29T13:10:57.881+01:00</urn1:toTime>

            <!--Optional:-->

            <urn1:transport></urn1:transport>

            <!--Optional:-->

            <urn1:validUntil></urn1:validUntil>

            <urn1:wasEdited>false</urn1:wasEdited>

         </urn:filter>

         <!--Optional:-->

         <urn:maxMessages>9</urn:maxMessages>

      </urn:getMessageList>

   </soapenv:Body>

</soapenv:Envelope>

Same values are provided in WSNavigator and I got a proper response there. Unable to get in SOAP UI.

Regards,

Aditya Vempati

adityavempati
Participant
0 Kudos

Hi Pavan,

Are you able to test getMessageList?

Regards,

Aditya Vempati

iaki_vila
Active Contributor
0 Kudos

Hi Aitya,

I've just retrieved the same error than you. I've just found that you must set some parameters mandatory. With this call i get a response:


<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <SOAP-ENV:Header>

  </SOAP-ENV:Header>

  <SOAP-ENV:Body>

    <pns:getMessageList xmlns:pns="urn:AdapterMessageMonitoringVi">

      <yq1:filter xmlns:yq1="urn:AdapterMessageMonitoringVi" xmlns:pns="urn:com.sap.aii.mdt.server.adapterframework.ws">

        <pns:archive>false</pns:archive>

        <pns:dateType>0</pns:dateType>

        <pns:nodeId>0</pns:nodeId>

        <pns:onlyFaultyMessages>false</pns:onlyFaultyMessages>

        <pns:retries>0</pns:retries>

        <pns:retryInterval>0</pns:retryInterval>

        <pns:timesFailed>0</pns:timesFailed>

        <pns:wasEdited>false</pns:wasEdited>

      </yq1:filter>

    </pns:getMessageList>

  </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

You can omit the values but not the tags.

Regards.

adityavempati
Participant
0 Kudos

Thanks for the response Iñaki Vila

I believe that you were able to get this request from WSNavigator - XML Content.

I tried triggering this request last day and I got a response.

Now, what I am looking for is a wsdl which can be imported into SOAP UI and no changes done.

Just provide input values, trigger the call and the response should be received. Hope you understood what I am trying to say.

I am trying to build an interface in PI which can give me a response containing the mesages count. But, before doing it I would like to test this service in SOAP UI.

Could you help me with this.

Regards,

Aditya Vempati

iaki_vila
Active Contributor
0 Kudos

Hi Aditya,

You are right, i've just take the call from wsnavigator to SOAPui. I think if you are planning to construct a PI scenario with this call, you can generate easily the XSDs from the XMLs (Free Online XSD/XML Schema Generator From XML - FreeFormatter.com). Later, you will can test from SOAPui your PI scenario. Right now, you can test from SOAPui, i know that you have to take into account some restrictions, but i don't know what benefit you will have if you get the wsdl now if you goes to construct a new interface. I think the only way is to get the XSDs and contruct the WSDL manually, you can start with another WSDL that you have got in another scenarios yours.

Regards.

adityavempati
Participant
0 Kudos

Hi,


I managed to transform the input request from SOAP UI as to the one in the WSNavigator by writing a Java module.


Regards,

Aditya Vempati

iaki_vila
Active Contributor
0 Kudos

Hi Aditya,

If you have solved your issue please close the thread according this

, in this way you will can more scn member in the future.

Regards.

p_k3
Participant
0 Kudos

Hi Aditya,

Can you pleae let me know how you have managed to query the webservice. My NWDS is not able to generate the stubs.

Also, can you paste the java module client program that you have written?

cheers, PK