JMS AutoMigration

JMS AutoMigration

In this I will be help you understanding the configuration and working of JMS Auto Migration.

WebLogic Server supports migration at the server level—a complete server instance, and all of the services it hosts can be migrated to another machine, either automatically, or manually. For more information

WebLogic Server supports service-level migration for JMS-related services, the JTA Transaction Recovery Service, and user-defined singleton services. These are referred to as migratable services, because you can move them from one server to another within a cluster.

For this you will need below setup configured.

1)      A WebLogic 11g or higher server

2)      1 Admin and (atleast) 2 Managed Server in a cluster.

3)      Node Manager should be configured and both the managed server should be in its server list.

Below are the steps to configure and test the JMS auto migration.

First decide which type of migration you want to use.

* Database -- requires that Data Source For Automatic Migration field is set with a valid JDBC system resource. It implies that there is a table created on that resource that migrating servers will use for leasing.

  * Consensus -- requires that all servers that are migratable, or which could host an auto-migratable target, have a Node Manager associated with them.

In my example I am using Consensus method for which you need to set the cluster -à Migration tab like
below.

1)      Make sure that the NodeManager is running and reachable.


2)      Create 2 JMS server and target them to ms1 (migratable) and ms2 (migratable) respectively.

 3)      Create a connection factory and Queue targeting to cluster and JMS server 1(JMS server 1 is inturn targeted to managed server 1)

4)      The Migration policy of both the server should be “Auto-Migrate Exactly-Once Services” (Same can be found in Admin Console-à Configuration -à  Migration page)

Also in the “Constrained Candidate Servers:” tab make sure both the server are in chosen tab.

 5)      Start both Managed servers
We can see that the JMS servers are targeted to their respective servers.

 Check the JNDI tree of both the server and confirm that the connection factory and Queue name is mapped properly

Shutdown one server (Say ms1).

Check the JMS server summary. In the Current server you will see that JMS Server-1 is now targetted to ms2 instead of ms1.
Same can be confirmed by checking the JNDI tree