Skip to Content


During our SAP e-learning course study we came across a very distinct Process pattern called the Sync-Async bridge which is used to integrate synchronous and asynchronous systems using ccBPM tasks. Interconnecting async and synchronous systems is one of the more common situations which we face in any system landscape. One such scenario could be a need to interconnect web based synchronous request response systems like say an HTTP based client system to a legacy application (typical mainframe) which talks asynchronously using File based data transfer. This can be accomplished using the Sync-Async Bridge pattern provided in integration repository. I have demonstrated the features of this pattern using a simple use case which was originally designed to query a stock quote web service. The HTTP requesting application makes a Synchronous request thro’ Xi to a File based system which inturn responds asynchronously. XI manages the process chain and provides a synchronous response back to the HTTP client. The request and the response data are logically mapped using correlations in ccBPM.

Use Case:

The intention of this weblog is to demonstrate an typical integration scenario between a synchronous HTTP client and an asynchronous file based legacy application. The standard Sync-Async process pattern is used in this demo.

Request is a typical XML payload asking for a Stock Quote related information.The legacy application is expected to receive the request and post a response back to querying HTTP application asynchronously. Xi uses the ccBPM Sync – Async bridge pattern to manage the message flow, correlates the request and response messages and hook back the asynchronous response from the legacy application as a Synchronous response to HTTP client.

*Legacy Application configuration: *

For this demo to simulate the functionality of a legacy application, I have used a simple freeware called LOGMONITOR which is freely available for download from **+  . + This application monitors the incoming directory for the request file to be created and once the file is created the XI system, the application moves this request to an Archive folder and simultaneously it also moves an response file to the response folder. This simply simulates what a legacy file based application would do after processing a request message.We have retained the same schema for HTTPClient and legacy system, so no explicit message mappings/interface mappings are necessary in this use case configuration

+Note: Config of the tool is out of scope of this presentation, check the tool help for the same +

+Note: Please note that this response from legacy application has to be sent before pipeline timeout occurs in XI. Else HTTP Client would get a Pipeline timeout response and hence you may have to resend the request again.One can however manage this in ccBPM using WAIT task and using deadline branch so that any delay in response from end systems can be handled. +

*The flow is detailed in the process diagram given *


+Fig 1.1 Process Diagram +

*Client configuration *

Plain HTTP adapter is uses the XI server pipeline URL to directly send the payload to the XI system. We can reuse or develop a script based client which can post a payload along with the set of parameters to pipeline.One can also reuse an HTTP client from one of examples available in SDN for this purpose.

Standard Config params for HTTP Sender adapter needs to be mentioned including the

          Server Host – “”

         Server Port – 50000 ( + HTTP Port) +

                    Client             – 100 (<client number>)

         Sender Service – WEBAPPS

QOS – BE(Best Effort)

         Sender Interface – HTTPRequestInt+ (+Outbound Message Interface name)

         Sender Namespace – Interface name space

*Integration Builder – Design *

1) Create the data type/import the XSD representing the payload request-response – *StockQuoteRequest *


+Fig 1.2 Stock Quote Request-Response Schema +

2) Create the following Message Types

       – HTTPRequestType

       – HTTPResponseType

       Create the Message Interfaces

– HTTPRequestInt

    Purpose – Sender Interface used by HTTP Client to send payload to Xi

    Mode – Outbound Synchronous

– HTTPResponseInt

Purpose – inbound Interface used by File Receiver to send information to legacy application’s incoming folder

    Mode – Inbound Asynchronous

– FileResponsetoBPM

Purpose – Used to send the Async response information from File system (File sender adapter) to BPM

Mode – Outbound Asynchronous

3) Interfaces to be used in ccBPM Process

– HTTPRequestIntAbstract

Purpose: To Receive message from HTTP Sender adapter in ccBPM

Mode : Abstract Sync

– HTTPRequestIntAbstractAsync

Purpose: To send the request XML message to the Outbound Message interface of the File Receiver

Mode : Abstract Async

– HTTPResponseIntAsyncAbstract

Purpose: To Receive the response XML message from the File Outbound adapter (File sender) in Xi

Mode : Abstract Async

4) Design of ccBPM Process

We will reuse the standard Sync-Async pattern for the process

*HTTPtoFile_Sync_Async *

The process contains 4 steps to accomplish the Sync- Async scenario

    • SyncReceive – To Receive the payload synchronously from HTTPRequestInt interface
    • syncSend – To Send the request payload Asynchronously from BPM to the File system
    • syncReceive – To receive the response payload Asynchronously from Legacy File system to BPM
    • SyncSend – To Send the response Synchronously from BPM to LegacySystem

The relevant configurations in each of the tasks can be found in the snapshot below


+Fig 1.3 Sync-Async BPM Process definition in Repository +

A Correlation “QuoteName” is defined to link the Stock information in the request and the response messages so that ccBPM can map the correct stock quote for which the response is sent back by the legacy application.

A snapshot of this correlation definition is shown below.


+Fig 1.4 Correlation definition for the request and response structures +

*Integration Builder – Configurations *

Create a Business Service “TestFiler” and Configure the File adapter communication channels to receive and send the payload from Legacy application back to the ccBPM process.

We have configured 2 channels

File_Receiver – Inbound adapter to receive data from Xi system to create XML files in the Legacy application’s incoming directory

File_Sender – Outbound adapter to Send files from Legacy Appln to the Xi systems as a Xi-SOAP message

Also configure the following Receiver Determinations

Ø HTTP Client (Sender) – BPM Process (Receiver)

Sender Service : TestFiler

Sender Interface: HTTPRequestInt

Receiver Service : HTTPSyncAsyncProcess

Receiver interface: HTTPRequestIntAbstract

Ø BPM Async Send Request(Sender) – File Receiver (Request)

Sender Service : HTTPSyncAsyncProcess

Sender Interface: HTTPRequestIntAbstractAsync

Receive Service : TestFiler

Receiver interface: HTTPRequestIntAbstract

Receiver Agreement: File Receiver channel

Ø File Sender (Response Sender)- BPM Async Receive Response

Sender Service : TestFiler

Sender Interface: FileResponsetoBPM

Receive Service : HTTPSyncAsyncProcess

Receiver interface: HTTPResponseIntAsyncAbstract

Sender Agreement: File Sender channel

*Finally Test the Entire process: *

Once the configuration is complete , we can test the interface by using a XML Payload as

Input.The ccBPM will receive the message from the pipeline and asynchronously send the message to File_Receiver inbound adapter, which will convert the file back to XML and place it in the “incoming” folder of legacy app.

The Logmon tool will immediately move the created file to an archive folder and triggers an action which will place a response XML in the “outgoing” folder.The File_Sender outgoing adapter picks up this file and sends it across to the XI system asynchronously.After correlating the stock Quote_Name from the response with request, ccBPM will route the response to corresponding process instance.

The response obtained in the HTTP Client will look as per snapshot below .. **


+Fig 1.5 Response snapshot of HTTP Response +

*Conclusion: *The above Use case illustrates how we can integrate Sync and Asynchronous systems using the ccBPM Sync-Async bridge.The scenario can be enhance with data conversion and message transformations between the systems as would happen in a live scenario.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    This is a good example, but I have a little different business requirement.  I am wondering if you have design idea?  We need a Synchronous to Asynchronous process, but not have the Synchronous thread wait for the Asynchronous process to complete.  The Synchronous process needs to hand off the message to a Asynchronous process and immediately response back to the Synchronous client.  This would be simulating the way EDI works.  The Synchronous reply is basically an acknowledgment.
  2. Former Member
    Very nice article. Good example.. Gives an overview on ccBPM..

    By the way this is off topic.. How do I become webloger?? When I click on ‘Post a Weblog’ it took me to a place to fillup my details.. I filled it up about 15 days back.. Nothing has happened.. In that form it was said that I would be contacted within a week.. Please  advise

    1. Former Member Post author

      Using ccBPM has its own reasons..Getting sync-async systems to talk to each other is just one of them.Performance is certainly a criteria but the actual execution depends on how you design your interface. Ideally try to avoid Integration processes to avoid the comm’n between Java and ABAP stacks.

  3. Marcos Oliveira Silva
    Hello, Sriram.

    Nice blog. It helped me a lot to come where I am now considering I had a course 2 years ago and had never used XI since that.
    In my scenario, I’ll send (RFC) a file (File-FTP)and I need to know whether it was successfully saved to delete from the table the entries that generated it.
    When the whole process is asynchronous, eveerything is okay, but when I convert to synchronous, it doesn’t work.
    Could you please sent the snapshot of your “File Sender Channel”?
    I also understood that, in the last step, BPM will receive the response coming from File Adapter. How can I specify a Sender Agreement when the destination is BPM?
    Thanks a lot,


  4. Former Member
    Hi Sriram,

    I am a new bee at XI and SAP itslef. I was practicing this one as my second scenario where as my first one was a simple file2file scenario. I could manage to complete till the repository objects but failed to catch you from the directory. I was not able to create the Recever Determination as told by you, as I was not able to figureout where to insert the interface details for each one. Could you push me from this point with some inputs?

    Anyways, the blog was helpful to learn/know about few important concepts like BPM Correalation etc.


  5. Former Member
    excellant Blog,highly informative and easy to understand,just a small question,for the HTTP scenarios i do,i actually use the HTTP port 8000(SMICM->GOTO->service)and 50000 is j2ee port
    do u mind telling me why are u using 50000 port for HTTP.
  6. Former Member
    Hello Sriram,

    Nice article.
    In your article, you mentioned the timeout issue:
    — “Note: Please note that this response from legacy application has to be sent before pipeline timeout occurs in XI. Else HTTP Client would get a Pipeline timeout response and hence you may have to resend the request again.One can however manage this in ccBPM using WAIT task and using deadline branch so that any delay in response from end systems can be handled” —

    I am facing this problem. Could you elborate some more on ways to solve this problem?


  7. Sigfrid Murillo

    Nice Post Sriram.

    Would you please send me the snapshots of your post updated?

    I cannot open any snapshot on it.

    Thanks and have a great weekend.

    Sigfrid Murillo.

    1. Former Member Post author


      Thanks. This is a pretty old post on this topic, so i dont have any of the snapshots with me right now but you can check the docmentation on under SAP Process Orchestration for Sync-Async scenarios. This is fairly standard pattern which has been used for years now..


Leave a Reply