Migration process:How to add a secondary

server to a running Prodco JMS server

TheLem ns.c m Prodco

Producers Consumers

The present JMS server

JMS1

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

Producers Consumers

Why this procedure works

JMS1

Every consumer has at leastone load sharing partner.

Each queue of messages has at least two consumers.

Add new JMS server

JMS1

Producers Consumers

JMS2

Configure as Active member of a fault tolerant pair of JMS serversThe new JMS server is connected to SAN shared storage

Add new JMS server

JMS1

Producers Consumers

JMS2

Configure as Active member of a fault tolerant pair of JMS serversThe new JMS server is connected to SAN shared storage

Shared storage device

Add new secondary JMS server

Producers Consumers

JMS2

Configure a new server instance running on the same machineas the original JMS server

JMS1

JMS2b

Migrate half the consumers

Producers Consumers

Move some of the consumers to the new server

Consumers

JMS2

JMS1

JMS2b

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

Migrate the producers

ProducersConsumers

All producers are now connected to the fault tolerant pair

Consumers

JMS1

JMS2b

JMS2

Allow the server to empty of data

ProducersConsumers Consumers

JMS2b

JMS1

JMS2

Migrate the remaining consumers

Producers

Move the remaining consumers to the new serverAll consumers are now connected to the fault tolerant pair

Consumers

JMS1

JMS2b

JMS2

Turn the old server off

Producers Consumers

JMS1

JMS2b

JMS2

Finished

Producers

JMS2b

Consumers

JMS2

Running normally

Producers

JMS2b

Consumers

JMS2