FILE2FILE with BPM

[Former Member]

Hi All,

Now i am working on FILE2FILE scenario with BPM Asynchronous.

i created 4 message interfaces.

1.BPM_SENDER_MI

2.BPM_SENDER_MI_ABSTRACT

3.BPM_RECEIVER_MI

4.BPM_RECEIVER_MI_ABSTRACT

Message Mapping is

BPM_SENDER_MT2BPM_RECEIVER_MT

Interface Mapping is

BPM_SENDER_MI_ABSTRACT2BPM_RECEIVER_MI_ABSTRACT

My Integration Process:

Receove--->Transformation--->Send.

Now i got confusion in Integration Directory.

Please let me clear that,

how many comm channels required ?

And how many receiver determinations, interface determinations, sender agreements & receiver agreements required for me?

Anybody have the solution, Please get back to me ASAP.

I am very thankful to you in advance.

Regards,

Nagarjuna.

[Former Member]

Hi Nagarjuna,

if inside your BPM you really have only ONE transformation, then I suggest to you do NOT use a BPM, because it's not necessary !

your performance will decrease with the BPM... (remind BPM=workflow).

Moreover if you have NOT a BPM, your config will be easier:

Sender --> Mapping --> Receiver

Note: and in SXI_MONITOR you will have ONE message line.

And in case of BPM, you have;

1. Sender --> (no mapping) --> BPM

2. BPM --> (no mapping) --> Receiver

Remind: the mapping is done in your BPM.

Note: and in SXI_MONITOR you will have TWO message lines.

So there is no good point use BPM if you just have one transformation into your BPM.

BPM has to be used when you want to impelement a workflow flow, with correlation, alert, merge, split, etc...

Hope this help.

Mickael

Edited by: Mickael Huchet on Apr 15, 2008 8:23 AM

[Former Member]

HI

For file to file using BPM you only need three message interfaces.

1. Sender MI (out/async)

2. Receiver MI (in/async)

3. BpmMI(abstract)

create container element of type abstract in your bpm which will serve as sender and receiver interface

Communication Channels

One for sender and one for receiver (File communication channel)

Mapping

Mapping should be between sender MI and abstract MI

Receiver and Interface determination

1. For bpm abstract interface (from sender to bpm)

2. For Receiver Service (from bpm to receiver)

One Sender Agreement and One Receiver agreement.

Mandeep Virk

[Former Member]

HI,

Refer the below weblog for step by step solution.

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

Chirag

[Former Member]

Hi !

refer this Blog

/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM

Regds

Abhishek

[Former Member]

Hi ,

Check the below ID configuration :

2 coomunication channels required (1 for sender and 1 for receiver)

2 receiver determinations(1 for BPM , 1 for receiver service)

2 interface determinations ( 1 for BPM , 1 for receiver service)

-

---

Interface mapping is not required for the above 2 In De.

1 sender agrement

1 reciever agreemnet.

Let me know if you need any further help...

Thanks,

Sekhar D