1. Migration process:
How to add a secondary server to
a running Prodco JMS server
TheLem ns.c m Prodco

2. Producers Consumers
The present JMS server
JMS1

3. Producers Consumers
Why this procedure works
JMS1
All messages are held in JMS
queues on a fast internal disk
In general you can’t add a fault tolerant partner to a running server,
but in this case all messages are held in JMS queues

4. Producers Consumers
Why this procedure works
JMS1
Every consumer has at least
one load sharing partner.
Each queue of messages has at least two consumers.

5. Add new JMS server
JMS1
Producers Consumers
JMS2
Configure as Active member of a fault tolerant pair of JMS servers
The new JMS server is connected to SAN shared storage

6. Add new JMS server
JMS1
Producers Consumers
JMS2
Configure as Active member of a fault tolerant pair of JMS servers
The new JMS server is connected to SAN shared storage
Shared storage device

7. Add new secondary JMS server
Producers Consumers
JMS2
Configure a new server instance running on the same machine
as the original JMS server
JMS1
JMS2b

8. Migrate half the consumers
Producers Consumers
Move some of the consumers to the new server
Consumers
JMS2
JMS1
JMS2b

9. Migrate half the consumers
Producers Consumers Consumers
JMS2
Consumers are reconfigured so
that JMS2 is their primary server
and JMS2b is secondary
Move some of the consumers to the new server
JMS1
JMS2b

10. Migrate the producers
ProducersConsumers
All producers are now connected to the fault tolerant pair
Consumers
JMS1
JMS2b
JMS2

11. Allow the server to empty of data
ProducersConsumers Consumers
JMS2b
JMS1
JMS2

12. Migrate the remaining consumers
Producers
Move the remaining consumers to the new server
All consumers are now connected to the fault tolerant pair
Consumers
JMS1
JMS2b
JMS2

13. Turn the old server off
Producers Consumers
JMS1
JMS2b
JMS2

14. Finished
Producers
JMS2b
Consumers
JMS2

15. Running normally
Producers
JMS2b
Consumers
JMS2