Removing ABAP dump when JDBC is down in RFC->JDBC->RFC scenario

[Former Member]

Hi All,

I need help to build one scenario.

I am working on RFC->XI->JDBC->XI->RFC scenario. It is working fine.

But problem is that whenever JDBC server is down RFC is giving ABAP dump in SAP. How can i Remove ABAP dump in SAP and give information to RFC that "JDBC is out of order"

Is it possible to implement without BPM, then How?

If not possible then what could be the steps of BPM?

Thanks & Regards

[Former Member]

closed

[MichalKrawczyk]

hi,

in a sync BPM you can do it very easily send step (jdbc)

and just wrap it into an exception branch

that will catch any jdbc excetion

and in the exception branch

you can put a mapping to the RFC.response "jdbc down"

Regards,

michal

[Former Member]

Dear Michal,

Thanks for reply.

Please correct my BPM steps I am designing as follows:

1)Synchronous Receiver step to get RFC data in BPM

2) Synchronous Sender step inside Block to send & receive from JDBC

3) In side exception branch, A transformation step with RFC asynchronous receiver in target message

4) last sender step close bridge

Is above BPM is correct or any other BPM object needs to be add.?

Regards

[moorthy]

ROhan,

TO achieve synchrnous BPM, you need to follow this approach as mentioned in the BLog

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]

Regards,

Moorthy

[Former Member]

Dear Krishna,

Thanks for reply. It is very usefull blog.

Please Help how to add "JDBC down error handeling" in this scenario to send information to RFC.

Is my above step 3 is correct? To send information back to RFC for error information back.

Regards

[moorthy]

Hi,

This you need to handle , before sending the response back to RFC, i.e before closing the sync/async bridge.

Regards,

Moorthy

[Former Member]

Dear krishna,

Thanks for reply.

This is my question. How can i add this information to RFC.res? Is exception block with transformation block will not solve the problem.

Or any other design you suggest.

Regards

[moorthy]

Exception block with Transformation step which maps data into RFC.res will solve your problem.

Also just to get an hint , on exception branch-

http://help.sap.com/saphelp_nw2004s/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm

Regards,

Moorthy

[bhavesh_kantilal]

Rohan,

1.Recive Step should open the Synch - Asynch Bridge

2. Block Step --> Send Synchronous inside this step with an Exception Hanler.

3. Now in the exception ahndler step, do the necessary error handling requirement.

4. Send Step --> closes Synch Asynch bridge.

My question is what data do you want to send back to the RFC if the DB is down? This data should be populated inside the exception handling block and then this data should be mapped to the corresponding RFC response and used in the step 4.

Regards,

Bhavesh