Skip to Content
avatar image
Former Member

Proxy to SOAP synchronous scenario in ICO

we having Proxy to SOAP synchronous scenario in single stack PI.

I did design and now the configuration.

I am using ICO object.

I created soap sender channel and soap receiver channel.

In the ICO, in the inbound parameters, I gave the SOAP sender channel I did for ECC system.

The flow is like this ECC - SOAP - ECC.

In the return flow we need SOAP receiver as we are pposting data back to ECC system

where do I use the receiver SOAP adapter for ECC system?

The SOAP sender adapter I used doesnt have details to add ECC system details so how will it post back to ECC?

Receiver side i guess SOAP receier will take care of both inbund and outbound flows?

Should we need two channels at source side?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Sep 29, 2015 at 01:13 PM

    Hello Midhun

    Configure a scenario like this

    ECC -------------------------> PI------------------------------------->Soap

              (soap channel with              (Soap Adapter with

               XI 3.0 Protocol)                        Http prtocol)

    Do request/respone mapping.

    Rest all PI will take care. 😊

    Soap Sender adapter will be triggered once you send message from need maintain  SM59 connections.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Midhun,

      No need to create two channels.

      This is a standard behavior for the adapters which supports synchronous communication in PI.

      For Ex: if we take proxy synchronous communication, you have generated a the proxy in ECC system for the synchronous sender service interface in ECC. Since the service interface has the meta data of the request and response. The coding has been done accordingly whenever any response gets from PI to ECC.

      You can just do a sample testing and check the outcome.