Sync/Async Bridge without Asynchronous Send / Receive Steps

[Former Member]

Hello together,

we have a synchronous HTTP <--> RFC Scenario using a sync/async Bridge in BPM with the following characteristics:

1. HTTP Payload is received (opens Sync/Async bridge)

2. lookup is done in an LDAP System (we use an UDF here)

3. Customzied JCo is called which takes the XML String as input parameter (done by Java Mapping)

4. Return Value of JCo then is delivered back to HTTP Client (closes Sync/Async Bridge)

--> No RFC Adapter is used here as the provided JCo does all the parsing

When testing the sync/async bridge is started but we receive an timeout after 30 sec.

Could it be that the sync/async required exactly a pair of async send and receive steps (which we do not have in our scenario and which we do not need)?

This would be a problem, as we have to use BPM in this synchronous scenario. Do you have any idea?

Thank you very much for your help.

[Former Member]

HI,

You should have to use Async/Sync bridge with Send and receive steps.

I think you are using exactly opposite of it.

Please can you confirm about it.

HTTP (Async) > XI <-->(Sync) RFC

Thanks

SWarup

[Former Member]

Thank you for your reply, but I think you misunderstood me. Please let me try to clarify once more:

1. Synchronous HTTP Sender Interface (Request/Response) opens Sync/Async Bridge

2. LDAP Lookup is done by UDF using the Request Message in Transformation Step

3. Switch is done based on result of Lookup

4. Branch 1 in switch calls customized JCo with Java Mapping in Transformation Step (Request Message as input, Response message as output)

5. Response message (delivered from JCo Call) should close the Async/Sync Bridge and be send back to HTTP Sender

--> We have no async send / receive steps in this scenario.

The customized Jco has been provided by an external partner as there is lots of parsing logic implemented. So we want to connect to the backend SAP system using this JCo and not via a send step.

My key qestion is therefore: Is it absolutely necessary to use exactly a pair of async send / receive steps in a sync/async bridge?

In this case we have to look for another design concept without BPM which would make the solution very difficult I think....

[Former Member]

I just found this discussion here which describes a similiar scenario (authentification and checks):

Also in this case there seems to be no asynchronous send/receive steps in BPM. So I am really wondering whether this is a strict requirement for an async/snyc bridge to work...

[Former Member]

Hello,

no idea on this issue whether a sync/async bridge definitely requires a pair of asny send/receive steps?

[Former Member]

Hi,

Are you sure that the branch condition is satisfied. Try using a step for identification in the false branch/default branch. I suspect that the branch condition is not working perfectly. As far as I know, I dont feel that exact number of asynch send receive steps are required inside the bridge. All that is needed is the bridge to be closed.

Regards,

Sudharshan N A

[Former Member]

Hello,

thank you for this information. I tried again to simplify the process for testing purposes to test the basic functionality of the sync/async bridge.

I only have a receive step now (opening the bridge) one transformation step creating the response message and then a send step closing the bridge.

Even in this simple case I get a timeout exception. Either there is really the requirement of a pair of async send/receive steps or there seems to be another issue....

[Former Member]

Short Update:

The simple scenario with only one transformations step in between works fine. However not if I have additional complex structures in between. I will do some more investigation on this. Thank you for your help anyway.