-1

I am aware of how to create bridges in EMS But What is the use of creating bridges in EMS...instead of directly specifying the name of the destination queue or subscriber ..

Is it for reliability purposes ?

Kindly explain me with the "WHY" part of usings bridges in EMS with suitable examples Thanks

darshan kamat
  • 374
  • 7
  • 23

1 Answers1

2

I see many "why" for EMS bridges.

Of the top of my head:

  • Create a topic out of an existing (and currently used) queue
  • By bridging a topic to a queue, make a more versatile durable subscriber (more options)
  • The "Topic to queue" pipe and filter pattern: Imagine all your (EAI) modules. All shall read from a queue, and write to a topic. Connectivity is not done in BW (or another writing application), but directly in the EMS configuration with bridges. A message from module A needs to be read by module B and module C ? Simply create 2 bridges from the module A outbound topic to module B and C inbound queues. Done ! Now the code does NOT have to be edited to adjust routing, and every module "stack" is well maintained by the inbound queues. (even if the module is off-line)
  • Bridges are useful with routes (multiple EMS instances), because of message selector feature (a JMS feature, not EMS, but very helpful with bridges). If a message in one queue needs to be sent to ONE out of 3 different EMS instances, based on a JMS property... then use a bridge with a message selector. No need for code.

I got more ;-) Seriously, it is a cool feature of EMS.

GhislainCote
  • 1,502
  • 11
  • 18