BPM FILE-- JDBC-- RFC

Question

Hi All,
I am doing the File to JDBC(Sync) to RFC through BPM
Start->Receive(Ansc)>Send(sync)>send(Anyc)>
I have created like this:
DT  and corresponding MT
1. File
2.JDBC_Req
3.JDBC_Req_response
i have created Message interfaces bellow
File outbound
File outbound Abstract
JDBC sync inound
JDBC Sync Abstract
JDBC response Asyc Abstract
I have created Mappings like this
File to File outbound Abstract
File Abstact JDBC_req
JDBC_Req Abstact to JDBC_Req
JDBC_res Abstact to JDBC_res
JDBC_res Abstact to RFC
I have created Interface Mappings like this
File to File Abstract
JDBC_req to JDBC_res
JDBC_res to RFC
while i am doing in BPM i am getting error like this:
Message File Abstact to be received and synchrounous interface MI_JDBC_req_Abstact are not of the same type
Pls suggest me how i can map the File Abstact and JDBC Abstact.
Thanks,
Venkat

Answer 1

Hi,
According to my understanding your scenario is:
1) Pick a file from some file server
2) Send it to a BPM
3) Send this file as a request to JDBC and get back the response....i.e synchronous..
4) Once you get the response from JDBC map it to a RFC structure and send it to the specified destination.
If the above flow is correctly understood by me then the following design won't work....
Start--Receive--Receive--Tranformation--Send(Sync)--Send--End
Your design should be:
Start --> Receive (async) --> Transformation --> Send (Sync) --> Send (Async) --> End
1)
a) Define an Outbound-Async MI for File Sender
b) Define an Abstract-Asynch MI for BPM ....(include in first receive step of BPM)
MT for (a) and (b) shoulde be same...
2) Define an Abstract-Async MI....this should have the request structure for the JDB
3) Create a mapping between MI from step 1a and 2...(include in the Transformation step of BPM)
4) Create an Abstract-Sync MI for BPM_to_JDBC....include the same message-type as that in step2....in the input message (request) part of the sync MI.....(include in the Sync-Send Step of BPM)
5) Create Inbound-Sync MI for the JDBC receiver...again both the message type should be same as that in the Abstract-Sync MI of step4
6) Create Abstract-Async MI for the RFC receiver....(include in the last Send step of the BPM)
I hope that you are defining the MIs with proper message-types and with proper direction...same applicable for container variable definition...please note that all the MIs involved in the BPM should be abstract
The error that you are getting is bcoz of the mismatch in the message-type in the MI....please check it.
Regards,
Abhishek.