BMS vs NO BPM

[Former Member]

hey,

I am implementing a File -> RFC -> File scenario.

I could use a BPM or implement it without BPM.

What are the pros and cons of each approach....?

thnx

[Shabarish_Nair]

<i>I am implementing a File -> RFC -> File scenario.

I could use a BPM or implement it without BPM.

What are the pros and cons of each approach....?</i>

>>>

if you are on SP 19 on XI 3.0 and SP 10 on PI 7.0 then you can utilize the standard modules provided by SAP and avoid BPM. The pro side is that avoiding BPM gives you a better performance.

Without BPM

[justin_santhanam]

Shabarish,

Thanks for pointing me out!! I need to try it out.

raj.

[justin_santhanam]

Shabarish,

One more quick question, in the thread Bhavesh mentioned the scenario is similar to Synch scenario, thatz fine. But where does receiver file adapter fits into the scenario? We will have one sender agreement - Sender file adapter and one receiver agreement - Receive RFC Adapter, am I right?

raj.

[Shabarish_Nair]

<i>1. The Receiver Determination , Interface Determination will be the same as in HTTP - RFC synch scenario. Create the Sender File Adapter, Receiver RFC Adapter and Receiver File Adapter.</i>

>>

ref. that point in the thread that is for the reply back from the RFC to the file

[Former Member]

hi sabbir,

I do agree with Raj, it is not possible to implement your requirement without BPM.

By using BPM this scenario can be achieved.

But using BPM is always a overhead in terms of performance.

regards

Ramesh P

[Former Member]

Dear Raj and Ramesh,

This is what I thought as well. but then, I read the following thread by Bhabesh

which says that you can do it without BPM.

[justin_santhanam]

Sabbir,

I think we can't achieve this scenario without the use of BPM Scenario. But using BPM you can achieve it.

Receive -

---

> Transformation->Send Synchronously->Transformation--->Send Asynchronously.

The above is the only pattern which can be used to achieve your scenario. Please correct me if i'm wrong.

raj.