Skip to Content

Sync message split to (1) sync Soap and (2) async Idoc receiver

Hi All,

System: PI 7.4 dual stack

What are the options for splitting a Sync Soap message so that (1) first message goes to Soap receiver with response back to sender (2) second message goes to Async Idoc receiver.

- I believe this could be done using a BPM but want to avoid using a BPM

- Alternatively is there some way to write the original Soap message to a file (via a UDF perhaps?) which will then trigger the second Async interface to create an Idoc? if so how?

- Some other way to do this?


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    Posted on Apr 05, 2016 at 10:30 AM

    Hello Che,

    What you can do is :

    • Interface# 1 --> Build a SOAP to SOAP synchronous scenario -> This will be for the Synchronous flow which receives your input synch SOAP Message.
    • Interface# 2 --> Build a SOAP to IDoc Scenario ( Asynchronous ) -> This will be triggered using the SOAP Lookup API from the Message Mapping of above flow.
    • In the request message mapping of Interface#1->
      • Write a UDF that pushes the entire Request XML message to a SOAP Receiver Channel of PI using the SOAP LookUp API.
      • The SOAP Receiver will contain the URL that points to the SOAP Sender of Interface#2

    No BPM and two independent flows linked using a SOAP LoopBack Concept!



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 05, 2016 at 10:27 AM


    So you scenario is like







    You can try refering the below link and write it as file in some directory

    BufferedWriter (Java Platform SE 7 ).

    Then second scenario will be File--PI--SFTP.

    Any stopback for using BPM?

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 05, 2016 at 10:37 AM

    Hi Che,

    You can include two receivers in the receiver determination step one for web service and other one for IDOC receiver.

    The first interface do async to sync bridge using modules in the receiver soap adapter. Response message you can send it to original sender.

    I have actually one interface which uses async-sync bridge with modules in receiver channel, i added another receiver and send the same message via receiver file adapter and it is working, i have tested in my system.

    You can check this blog for async-sync bridge Generic PI Async-Sync Bridge Configuration for Any Adapters



    rec.png (7.0 kB)
    module.png (14.6 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 05, 2016 at 10:57 AM

    Good suggestions from both Bhavesh and Raghuraman. Will wait for a response from Praveen as a split in the adapter would be ideal but not sure if this copes with a sync sender.

    Add a comment
    10|10000 characters needed characters exceeded

    • As far as I know, the modules are used to convert a asynch request to a synch request and then direct the response to another interface.

      What happens if the request itself is synchronous to the Original calling application? Well its pretty interesting and something I haven't tried. Interesting option I must admit though!



  • Posted on Jul 28, 2016 at 11:54 AM

    Hi Che/Bhavesh,

    Was not the requirement like - only after sender of interface 1 receiving response data will be sent to an IDOC ?

    If SOAP Look up is done from the request MM of first interface then how is it guaranteed. Here -

    Data will be sent to idoc first I think here.

    It can also happen that data is sent to idoc but not to soap receiver of 1st inteface.



    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Apu,

      your concerns are defijntely valid. If the requirement is for a guaranteed delivery with exactly once QOS there are definitely flaws in this design and the one you have pointed out is valid.

      while PI does not support them, there are other QOS in the integration space that is supported by other middlewares,

      • utmost once - what this QOS means is that the middleware should send the message a maximum of one time. If it fails, it fails. No restarts etc. Something like our best effort.
      • atleast once - what this QOS means is the middleware should send the message minimum once and can resend the same Message any number of times.

      What I am trying to say is in the context of this requirement, it could Satisfy both of these QOS and maybe that is the requirement 😊 it is not explicit and I assume that it is . For pure exactly once where no duplications allow your concerns are valid.

      hope this clarifies..!

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.