do we require abstract interfaces for the procedure ?

[Former Member]

hi

while going through the file to DB scenario by Mukeshlal Parida at:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5474f19e-0701-0010-4eaa-97c... , I had a doubt regardign as to why we need to create a abstract message interface for the procedure request and procedure response.Is it necessary to do so?mapping is already done b/w request and DB and DB-response to the final response.The ID part will call the stored procedure.Then where does the need to introduce 2 more abstract async message interface arise?

please try to clear this doubt so that i may understand the logic behind it.

[Former Member · Accepted solution]

Hi,

yes you will need to have abstract interfaces for your this scenario because BPM is used........abstract interfaces are required for BPM to process your data because BPM can only deal with abstract interfaces............BPM is required because you are making a synch scenario by sending a req msg and getting a response msg for it from JDBC to your file adapter but the file adapter can process only asynch msgs by default, so BPM is required to handle this asynch - synch - asynch bridge.

Regards,

Rajeev Gupta

Edited by: RAJEEV GUPTA on Jan 19, 2009 3:19 PM

[Former Member · Accepted solution]

hi rajeev

my question is not why BPM uses abstract interfaces but why do we require 2 more abstract interfaces specifically for the STORED PROCEDURE request and STORED PROCEDURE response when we have already made the abstract interfaces for the for the BPM side,both sync and async.

if possible , go through the link of the pdf i've given and refer pasge number 26 ,STEP 5 and then elaborate on as to why the message interface are 8 instead of 6 ,with addition of 2 more namely_:DBCustomerProc_req_ABS*_ and *DBCustomerProcres_ABS_

[Former Member · Accepted solution]

Hi,

DBCustomerProc_req_ABS is required because it is used in first transformation step of mapping file req msg to JDBC stored procedure req msg...........similarly DBCustomerProc_res_ABS is required because after your synch send step, you need it in transformation step to map it file response status msg.

Regards,

Rajeev Gupta

[Former Member · Accepted solution]

why aren't we doign the IM as follows:

Source Interface as CustomerDetails_Async_ABS and target interface as DBCustomer_Sync_ABS

AND

Source Interface as DBCustomer_Sync_ABS and target interface as DBStatus_Async_ABS

Instead we're using Source Interface as CustomerDetails_Async_ABS and target interface as DBCustomerProc_req_ABS AND

Source Interface as DBCustomerProc_res_ABS and target interface as DBStatus_Async_ABS

we're using the same Message type so no problem should come in mapping in either cases.

[Former Member · Accepted solution]

Hi,

why aren't we doign the IM as follows:

Source Interface as CustomerDetails_Async_ABS and target interface as DBCustomer_Sync_ABS

AND

Source Interface as DBCustomer_Sync_ABS and target interface as DBStatus_Async_ABS - No you can't do this thing because see you can specify a IM as async-async or synch-synch in IR......but you cannot specify a mapping as asynch-synch and if do so, then only req will be mapped but response will not be mapped..............Moreover if this thing was possible, then there was no need of BPM in this scenario ..............the purpose of using BPM is to achive this asycn-synch mapping via two asnyc-asnynch tranformation step mappings.

Regards,

Rajeev Gupta

[Former Member · Accepted solution]

hmmm....thats interesting:)

thanks for the info.

[Former Member]

Hi...

Find the below link.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/soa-middleware/soa...

In the above link it is showing Soap to JDBC Sceanrio which is synchronous. For JDBC, only simple table is used. Instead you can use the stored procedure.

For how to use stored prcodeure follow the below link

/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi

Regards,

Leela

[dharamveer_gaur2]

Hi

You are using BPM in your scenario and it understands only Abstract Interfaces.

JDBC Receiver Sync also done without using BPM, look this blog

/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step

[Former Member]

my scenario is related to stored procedure.

the link you have sent is simple JDBC.

my doubts are regardign teh usage of stored procedure so am afraid the link u mentioned wasnt much of a help.

however thanks for ur input.

[Former Member]

Hi Itisa

for usage of stored procedure just have look at

Check SAP Note 941317

also at 3.3 section at this pdf

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/81a22ee1-0701-0010-45aa-ec852e88...

also this Blog

/people/jegathees.waran/blog/2007/03/02/oracle-table-functions-and-jdbc-sender-adapter

Regards

Abhishek