Here, we have three different
ServiceMix instances. Since in cluster mode, all the ServiceMix instances must have
a unique name in the whole cluster. We will name the instances with different
names namely admin, managed1, and managed2. One of these ServiceMix instances
also manages a JMS connection broker, and hence we have arbitrarily named that
instance with the name "admin".
The JBI services can be deployed into any of the ServiceMix instances in this cluster.
To deploy a service into the cluster, we will deploy those services into all (or many)
instances into the cluster. When we do so, all the containers in the cluster are notified
of the deployment. Now the cluster can administer routing or load balancing policies
when it receives client requests by automatically routing MessageExchange(s)
between the members of the cluster. Such services which we deploy across clusters
are called clustered services. We can also deploy services into a single instance of the
JBI container in the cluster in which case we call the service a pinned service.
Transactions, Security, Clustering, and JMX
[ 390 ]
For a clustered service, even if one of the ServiceMix instances hosting the service is
down the service is still up since there are other cluster instances to serve the request.
Pages:
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508