Skip to Content
avatar image
Former Member

I am having an error with this (seemingly) simple SOAP to SOAP scenario in PI 7.5

Hello experts,

I have this SOAP webservice that I need to do calls to. Let's call it the sandbox webservice. I made a simple integration flow using NWDS, consisting of the following:

SOAP sending channel

SOAP receiving channel

Outbound Synchronous interface (Stateless)

Inbound Synchronous interface (Stateless)

I don't use any message mappings as this is not necessary.

A pic of the outbound interface

The inbound interface

Sending SOAP cc

Receiving SOAP cc

Integration flow

Both service interfaces use the same request and response message, that I got by importing the wsdl of the sandbox. After deployment, I extracted the WSDL of the outbound interface, so that I can call the integration scenario, which in turn calls the sandbox webservice. For testing, I use SOAPui to do the call to PI. Doing this call gives me back a 500 internal server error from the sandbox. Doing a call directly to the sandbox, omitting PI, yields a good result.

Error from SOAPui

Perhaps I'm doing something wrong here. Can any of you guys and girls see any mistakes among the posted pictures, especially the service interfaces? Is it correct that they both can use the same request and response messages for example?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Jul 11, 2017 at 11:29 PM

    Hi,

    When you created the interface in SAP PO/AEX/PI, is the namespace is same as the target WSDL namespace? if it is not then you need to create ESR object in the same namespace.

    you can perform the quick comparison between the target WSDL and SAP PO/AEX/PI interface WSDL by retrieving the WSDL from configuration (ICO/Sender agreement etc.).

    regards,

    Harish

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 12, 2017 at 06:30 AM

    Hi Zakaria!

    Also you can enable http tracing for your receiver SOAP channel and monitor HTTP log to find more detailed information about error.

    But first you should follow Harish's suggestions.

    Regards, Evgeniy.

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 12, 2017 at 08:37 AM

    Are you using axis soap here?

    Can you change it to plain soap adapter and test it once.

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 12, 2017 at 10:24 AM

    Hi

    As i see in your screenshot, SOAP action is not specified in channel configuration.

    Regards

    Bhagya

    Add comment
    10|10000 characters needed characters exceeded