org/schemas/spring/1.0"
class="managed2.MyReceiver" >
2
Chapter 17
[ 395 ]
Here the main difference is that we set name="managed2". Moreover we set flowN
ame="jms?jmsURL=tcp://localhost:61616" so that this managed server too will
form a part of the same cluster joined by the admin and previous managed server.
Then we deploy receiver2 and receiver3 services to this server.
So in a nutshell, receiver1 and receiver2 are pinned services whereas receiver3
is a clustered service.
Deploy and run the sample
To build the entire sample, it is easier to change directory to the top-level folder and
execute the build.xml file provided there:
cd ch17\03_Clustering
ant
This will build the entire codebase for the clustering demonstration. Now we need
to take three different command prompts and bring up all the server instances in the
cluster, in the same order as shown as follows:
cd ch17\03_Clustering\admin
%SERVICEMIX_HOME%\bin\servicemix servicemixadmin.
Pages:
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515