Forum Discussion

dratliff's avatar
dratliff
Occasional Contributor
4 years ago

HTTP Request for PeopleSoft

Hello Everyone,   I am trying to create a test using ReadyAPI 2.8.0 to send a HTTP Request to a HttpListeningConnector in Peoplesoft.  I have tried to follow what was provided by PeopleSoft and als...
  • dratliff's avatar
    dratliff
    4 years ago

    Hello Rich,

     

    What a wild ride.  I figured it out, still more work to do, but the initial test has been successful.

     

    There are 2 portions of it.  In soap UI, the request can be formulated externally in some type of editor and then cut-n-pasted into the pane below the parameters.  Sometimes that pane has to be expanded.  That allowed for the message tests I had to be placed inside.  After talking with our developers for the PeopleSoft implementation, I realized the destination node was wrong.  I changed that, added an XML payload in the data section and was able to get a success.  

     

    Payload Data

    The trick with the payload was to use the XML but it had to have the field definitions preceding the actual data payload.  Once I started working with it, it become much easier.  

    I also wrote some C# code to also test this.  I still have a small component to finish but the initial testing works as expected.

     

    Thank you for you help and I hope I wrote enough here to help someone else that might be struggling with this problem.  

     

    Key takeaways:  Check syntax of To:/From: and provide field definitions before the field data.

     

    Cheers!

     

    Dave

dratliff's avatar
dratliff
Occasional Contributor

Hello Rich,

 

Thank you for the response.  Yes, it is extremely strange but a 2xx status is provided regardless by the HttpListeningConnector in PeopleSoft.  

 

I guess what I need is a specific way to create the header and body content for the message.  Or if anyone in this group has had the same problem with trying to communicate with PeopleSoft using the HTTP Request.  I am going through the code from a consultant that wrote the initial interface and it is fairly straightforward but in order to demonstrate and document the process I'd really like to use Soap UI.  

 

Any insight is greatly appreciated.  

 

Thank you,

 

Dave.

richie's avatar
richie
Community Hero
4 years ago
dratliff

Hey Dave, yep describing exactly what you need to do is pretty straight forward, but im gonna need some details.

Can you submit the request in Postman and provide the full RAW details of the request please?

When i say the full RAW details i mean the full URL, the method, the payload, the authentication type (but dont provide the actual username or password) and especially the headers parameters please?

If you provide these details then we'll be able to give you specific instructions to create what you need in readyapi!/soapui

Cheers,

Rich
  • dratliff's avatar
    dratliff
    Occasional Contributor
    4 years ago

    Hello Rich,

     

    Here is the Postman conversation with the endpoint.

    POST https://url.used/PSIGW/HttpListeningConnector
400
236 ms
POST /PSIGW/HttpListeningConnector HTTP/1.1
Content-Type: application/xml
Accept: */*
Cache-Control: no-cache
Postman-Token: 1234
Cookie: xxx=xxxxx
 
<?xml version="1.0" encoding="utf-8"?>
<IBRequest>
<From>
<RequestingNode>SRC_ID</RequestingNode>
<OrigTimeStamp>1.00-0000</OrigTimeStamp>
</From>
<ExternalOperationName>TIMESHEET_CHECK.VERSION_1</ExternalOperationName>
<OperationType>async</OperationType>
<To>
<DestinationNode>DEST_ID</DestinationNode>
</To>
<ContentSections>
<ContentSection>
<Headers>
<version>VERSION_1</version>
</Headers>
<Data>
<![CDATA["TIMESHEET_CHECK", "2021-08-09", "00:00:00"]]>
</Data>
</ContentSection>
</ContentSections>
</IBRequest>
 
HTTP/1.1 400 Bad Request
X-Cnection: close
Date: Wed, 11 Aug 2021 14:03:37 GMT
Content-Length: 847
Content-Type: text/html; charset=UTF-8
Set-Cookie: xxxxx; Path=/
 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
<HTML>
<HEAD>
<TITLE>Error 400--Bad Request</TITLE>
</HEAD>
<BODY bgcolor="white">
<FONT FACE=Helvetica><BR CLEAR=all>
<TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all>
<FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 400--Bad Request</H2>
</FONT></TD></TR>
</TABLE>
<TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New"><FONT FACE="Helvetica" SIZE="3"><H3>From RFC 2068 <i>Hypertext Transfer Protocol -- HTTP/1.1</i>:</H3>
</FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.4.1 400 Bad Request</H4>
</FONT><P><FONT FACE="Courier New">The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.</FONT></P>
</FONT></TD></TR>
</TABLE>
</BODY>
</HTML>

    That is the entire message. 

    What I get from soap ui is even less 

    <IBResponse type="error">
   <DefaultTitle>Integration Broker Response</DefaultTitle>
   <StatusCode>20</StatusCode>
   <MessageSet>158</MessageSet>
   <MessageID>10843</MessageID>
   <DefaultMessage>Integration Gateway failed while processing the message.</DefaultMessage>
   <MessageParameters>
      <Parameter>DEST_ID</Parameter>
   </MessageParameters>
</IBResponse>

    I cannot duplicate the 400 response in soapui.

     

    I have some documentation that I have reviewed that I believe I have followed:  HttpListeningConnector | Integration Broker | The Missing Manual (cedarhillsgroup.com)

    • richie's avatar
      richie
      Community Hero
      4 years ago
      Hey dratliff

      Can you also publish the payload and headers from your readyapi/soapui request and response please, so i can compare against the postman submission? Ta

      You provided the readyapi/soapui response payload i think, but we need the request payload and headers too.

      Ta

      Rich
      • dratliff's avatar
        dratliff
        Occasional Contributor
        4 years ago

        Hello Rich,

         

        What a wild ride.  I figured it out, still more work to do, but the initial test has been successful.

         

        There are 2 portions of it.  In soap UI, the request can be formulated externally in some type of editor and then cut-n-pasted into the pane below the parameters.  Sometimes that pane has to be expanded.  That allowed for the message tests I had to be placed inside.  After talking with our developers for the PeopleSoft implementation, I realized the destination node was wrong.  I changed that, added an XML payload in the data section and was able to get a success.  

         

        Payload Data

        The trick with the payload was to use the XML but it had to have the field definitions preceding the actual data payload.  Once I started working with it, it become much easier.  

        I also wrote some C# code to also test this.  I still have a small component to finish but the initial testing works as expected.

         

        Thank you for you help and I hope I wrote enough here to help someone else that might be struggling with this problem.  

         

        Key takeaways:  Check syntax of To:/From: and provide field definitions before the field data.

         

        Cheers!

         

        Dave