Multiple Broker JMS

We have one Broker that clients access and it send JMS messages to multiple other Brokers at different locations. Right now, we're creating a ConnectionFactory for each of the other Brokers. Is this the intended way to handle that?

We thought about clustering, but due to security reasons, we can't

I guess I'm really wondering what is the preferred way to do Broker to Broker communication in Sun ONE Message Queue?

[445 byte] By [RyanSteckel] at [2007-11-25 8:38:17]
# 1

The preferred mechanism is broker clustering which is

available in the Enterprise Edition of MQ (or as a trial

in the Platform Edition).

For example if you have three brokers

clustered together a publishing client can connect to

broker A. Other clients can connect to brokers B and C

and subscribe to the same topic. When the publishing

client sends a message to broker A for the topic the

other clients are subscribed to broker A will

automatically forward the message to the two other

brokers in the cluster so that subscribing clients will

receive the message.

The brokers in the cluster have intelligence such that

they will not forward messages to brokers if there

are not clients attached to the broker interested in

receiving the message. This save bandwidth.

kasso at 2007-7-1 15:14:15 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 2
Is this the standard way to connect about 20 brokers? Do you know the details about the connections between brokers in a cluster? Does a connection stay open between brokers all the time? Are there any known security risks?Thanks for your help.
Ryan Steckel at 2007-7-1 15:14:15 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 3
They are fully-connected through TCP/IP.Please see Sun ONE MQ Administration Guide
amy.kang at 2007-7-1 15:14:15 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...