Message Branching

[Former Member]

hi Gurus,

Is Message Branching is applicable/available only with EOIO? If so please help to understand why only with EOIO and Why its not with the other QoS i.e BE and EO.

Thanks in advance.

Regards

Sekhar

[Former Member]

Hey

Message branching(multiple receivers) is possible for all 3 Quality of server(EO,EOIO,BE)

the only difference is if you have Best Effort(synchronous scenario) then you need to use BPM to get response(to correlate the correct response with its request) but in case of EO and EOIO you don't need BPM(since both are used in async scenarios).

Thanx

Aamir

[Former Member]

Normally, sender uses this attribute to determine how message is to be delivered.

Exactly Once - qRFC queues - asynchronous communication.

This quality of service guarantees that XML messages are processed exactly once.

Exactly once in order - qRFC queues - asynchronous communication.

Messages are delivered with the same queue names (supplied by the application) in the same sequence that they were sent from the sender system.

Best Effort - Synchronous communication.

The sender waits for the response before continuing the process.

If quality of service is BE, an error occurs if more than one receiver is determined for a message.

If quality of service is EO or EOIO, then the message is branched. A new message with a new message ID is created from the original message for each interface/receiver pair in the receiver list.

QOS shall change while using Async-sync bridge. EO for former and BE for later.

Thanks

Kiran

[Former Member]

Yes, both EO & EOIO supports Message Branching.....but the message branching with EO eventually switches from EO to EOIO.

because, after branching if multiple messages are targed for same receiver then all those messages have to be delivered in sequence as a result, it's EOIO.

Thanks

Sekhar

[Former Member]

Hi,

Can you please explain your question clearly ??

Kulwinder

[Former Member]

I got the Answer as below....

Yes, both EO & EOIO supports Message Branching.....but the message branching with EO eventually switches from EO to EOIO.

because, after branching if multiple messages are targed for same receiver then all those messages have to be delivered in sequence as a result, it's EOIO.

Thanks

Sekhar