Any Thumb Rule to decide on Message Interface

[Former Member]

Hi All,

Is there any way to know or decide on how many message interfaces we need depending on the situation.

As in F2F we need to have one sender and one receiver interface,but when we have BPM's I would like to know how we decide on this message interface.

Is there any thumb rule to go with this?

Thanks

Sudharshan

[Former Member]

HI

No their is no such specific thumb rule.

sender n receiver(inbound n outbound) direction specific

abstract nterface(no direction specific). It is also called as Hidden interface.

cheers

[Former Member]

Hi,

Message Interface Design flow:

Inbound and outbound (direction oriented)

Abstract Interface (No direction specific) we can able to use both inbound and outbound message flow)

Thanks,

Boopathi

[Former Member]

HI,

There is no such specific rule available to identify. Its based on the requirments.

BPM can interact and deal with only Abstract Interfaces. And so, if you have a transformation step inside the BPM , the source and target interface will have to be abstract interfaces.

So based on no of senders and receivers you need Outbound and Inbound interfaces.

Now to communicate with all these outbound and Inbound interfaces you need one-one abstract interface.

There may be the possibility to re-use the same abstract interface....that depedns upon the situation and requirments.

Thanks

Swarup

Edited by: Swarup Sawant on May 28, 2008 10:07 AM

[Former Member]

Hi,

There is no thumb rule to identify the message interfaces needed for the scenario.

BPMs deal only with abstract interfaces.

Suppose if you take your file to file scenario using BPM i.e.

Sender -> XI(BPM) ->Receiver

here from sender to XI you need one outbound asynch interface

and from BPM will be receiving the message using abstract asynch interface and BPM will be seding out the same message using abstract async interface and finally receiver will be receiving the message using inbound async interface.

Thanks,

Vijaya.