4 Replies Latest reply on Oct 17, 2012 4:56 AM by 968817

    Response with attachment


      We got one scenario. In one of the integration with third party using WSDL we are getting response with attachment. Below is the raw XML response (Using SOAPUI). We are not sure how to handle this RESPONSE in PS. Please share ur thoughts.

      HTTP/1.1 200 OK
      Date: Mon, 08 Oct 2012 06:46:54 GMT
      Server: Apache
      Cache-Control: no-store
      Transfer-Encoding: chunked
      Content-Type: multipart/related; type="text/xml"; boundary="uuid:b4ee8c4f-7749-4146-a0c8-42ac06e19046"

      Content-Type: text/xml

      <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body /></S:Envelope>
      Content-Type: application/octet-stream
      Content-Transfer-Encoding: binary

      "Application Id","Template Id","Country","Job Code"
        • 1. Re: Response with attachment
          This appears to be a multi-part MIME message. The XML "part" is just an empty soap envelope, not valuable. The real content appears to be the comma delimited content of part II.

          When you call the service operation from PeopleSoft, can you print anything from the response message to file?
          • 2. Re: Response with attachment

            Still am not able to read the response. This doesnt look like normal xml response.

            Basically this is synchronous type and I hope it got stopped in Integration gateway. Am getting HttpTargetConnector:External Application Exception.

            Is there anyway to handle this type of content type.

            • 3. Re: Response with attachment
              Jim/Any PS Experts,

              Please help me to handle this scenario. Am yet to crack.

              • 4. Re: Response with attachment
                As per Oracle Support..This wont work in PS.

                The message that is failing has a Content Type for MIME [Content-Type: multipart/related;] . This is not a supported format for a Third Party post. Integration Broker only accepts a text/xml content type at the gateway level. Message Type of MIME [Content-Type: multipart/related;] is only supported between two PeopleSoft systems. The reason for having a MIME [Content-Type: multipart/related;] type between two PeopleSoft systems is to carry the IBInfo in one section and another to carry the content. In Integration Broker the the content with attachments, which is the primary reason why other third parties might be using the "multipart/related" media type, will not work at the gateway level. So posting a message via a ThirdParty to a PeopleSoft system using a MIME type [Content-Type: multipart/related; ] is not supported for this very reason.