PeopleSoft and SOAP - Testing Using Event Tester

As an exercise to see if PeopleSoft can absorb a SOAP xml, we have created a message definition, a node and have the code ready for testing. From here, we can test the code to for the desired output using Event Tester.

To do so, Navigate to PeopleTools -> Integration Broker -> Utilities -> Event Tester

Select the message name as "SOAPTSTMSG", the event as "On Request". Use the XML provided below in the "Input Message" section, click on "Execute Event". If you have followed the instructions correctly, you would get the output as shown below

Event Tester does not actually use the Node settings which we have created and hence it would be worth using the delivered PSFT Tool, SendMaster to test our code.

Navigate to the PT8.46 folder and invoke Send Master. Set the following properties correctly:-

1) Server URL:- This should point to your integration gateway URL as

http://<Integration Gateway>/PSIGW/HttpListeningConnector?From=SOAPTEST&MessageName=SOAPTSTMSG

Here, we are passing the node name and message name.

2) Headers:-

Put this as

Content-type: text/xml; charset=UTF8
SOAPMethodName:#ProcessNumbers

3) Under Input information, pass the SOAP XML and hit POST. The output will be available in Send Master "Output Information" window. A sample output screenshot is provided below

If you get errors like:-

<?xml version="1.0"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">     <SOAP-ENV:Body>         <SOAP-ENV:Fault>             <faultcode>SOAP-ENV:Server</faultcode>             <faultstring>null</faultstring>             <detail>                 <IBResponse type="error">                     <DefaultTitle>Integration Broker Response</DefaultTitle>                     <StatusCode>20</StatusCode>                     <MessageSet>158</MessageSet>                     <MessageID>10403</MessageID>                     <DefaultMessage>A request must supply either a RequestorNode or a DistinquishedName</DefaultMessage>                     <MessageParameters>                         <Parameter>RequestorNode or DistinquishedName</Parameter>                     </MessageParameters>                 </IBResponse>             </detail>         </SOAP-ENV:Fault>     </SOAP-ENV:Body> </SOAP-ENV:Envelope>

or

<?xml version="1.0"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">     <SOAP-ENV:Body>         <SOAP-ENV:Fault>             <faultcode>SOAP-ENV:Server</faultcode>             <faultstring>null</faultstring>             <detail>                 <IBResponse type="error">                     <DefaultTitle>Integration Broker Response</DefaultTitle>                     <StatusCode>20</StatusCode>                     <MessageSet>158</MessageSet>                     <MessageID>506</MessageID>                     <DefaultMessage>Destination node does not match the local node.</DefaultMessage>                     <MessageParameters/>                 </IBResponse>             </detail>         </SOAP-ENV:Fault>     </SOAP-ENV:Body> </SOAP-ENV:Envelope>

or

<?xml version="1.0"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">     <SOAP-ENV:Body>         <SOAP-ENV:Fault>             <faultcode>SOAP-ENV:Server</faultcode>             <faultstring>null</faultstring>             <detail>                 <IBResponse type="error">                     <DefaultTitle>Integration Broker Response</DefaultTitle>                     <StatusCode>20</StatusCode>                     <MessageSet>158</MessageSet>                     <MessageID>510</MessageID>                     <DefaultMessage>Unable to find the requesting node %1 in the message node able.</DefaultMessage>                     <MessageParameters>                         <Parameter>VP1</Parameter>                     </MessageParameters>                 </IBResponse>             </detail>         </SOAP-ENV:Fault>     </SOAP-ENV:Body> </SOAP-ENV:Envelope>

Make sure that you do the following:-

1) Ensure that the URL is correct.
2) Ensure that the input XML is correct.
3) Ensure that the header information is correct.

If all these things are fine, then check the node configuration. The configuration might be incorrect.