Skip to Content
0
Former Member
Jun 16, 2009 at 08:40 AM

need help with scenario BPM Http-RFC Sync/async bridge

28 Views

hi all!

i've got the following scenario: HTTP-BPM(XI)-RFC synchronous both of them. for that, i'm using S/A bridge in the BPM, but i'm getting the error 'Timeout condition of pipeline reached'. i think the problem is that the process gets lost in the sync/async communication, because in the trace level shows CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV" and after that every message are 'wait time starting'.

don't know the reason of the error. Maybe I missed something to configure?

the BPM is like this:

Receiver(Open Sync/Async bridge) -> Transformation (mapping from http request to RFC request) -> SyncSend (RFC request and response) -> Transformation (mapping from rfc response to http response) -> Send (Close S/A Bridge)

the IR is configured like this:

Message Types u2013 External Definitions u2013 Imported Objects

mt_cxml_request -> contains xsd of xcml request template.

mt_cxml_response -> contains xsd of xcml response template.

zintegracion_pedidos -> imported RFC from R/3

zintegracion_pedidos.response -> imported RFC from R/3

Message Interfaces

mi_cxml_request_async_abs

mi_cxml_request_sync_abs

mi_cxml_request_sync_out

mi_xcml_response_async

mi_rfc_request_asyn_abs

mi_rfc_request_sync_abs

mi_rfc_request_sync_in

mi_rfc_response_async_abs

Message Mappings

mm_cxml_request_to_rfc_request -> mapping from http request (cxml) to rfc request.

mm_rfc_response_to_cxml_response -> mapping from rfc response to http response (cxml).

Interface Mappings

im_cxml_request_async_abs_to_rfc_request_async_abs

im_rfc_response_async_abs_to_cxml_response_async_abs

and the ID is configured like this:

Business system DES -> created business system for RFC adapter with interface mi_rfc_request_sync_in as receiver. Comunication channel u2018RFC Receiveru2019

Businnes service VW -> created businnes service for HTTP adapter with interface mi_cxml_request_sync_out as sender. Comunication channel u2018HTTP Senderu2019

Receiver Determination

two receiver determinations. One for BPM and the other one for RFC(R/3):

|VW| mi_cxml_request_sync_out:

|BPM_PO| mi_rfc_request_sync_abs:

Interface Determination

two interface determinations:

|VW| mi_cxml_request_sync_out | | BPM_PO:

|BPM_PO| mi_rfc_request_sync_abs | * | * :

Sender Agreement

VW

mi_cxml_request_sync_out

Receiver Agreement

|BPM_PO| |DES| mi_rfc_request_sync_in