Server --> Control --> JMS Migrate
Overview
Use this page to migrate a JMS server from a failed clustered server to another server in the cluster.
Based on the list of candidate servers (in the cluster) selected on the Server - >Control - > JMS Migration Config. page, use the Destination field to select a destination server to take over for the server currently hosting the JMS server. Select the server where you want to migrate the JMS server, and then click the Migrate button.
Notes: If your JMS application uses persistent messaging, you can only migrate the JMS server from one server in a cluster to another server in the same cluster that can access the persistent JMS store of the failed server.
If your JMS applications use JTA transactions, also migrate the Transaction Recovery Service to another server. For more information see, Transaction Recovery After a Server Fails.
Tasks
JMS Server --> Target and Deploy
Server --> Control --> JMS Migration Config.
Server --> Control --> JTA Migration Config.
Server --> Control --> JTA Migrate
Related Topics
Migrating a Pinned Service to a Target Server Instance"
Migrating When the Currently Active Host is Unavailable"
Configuring JMS Migratable Targets"
Transaction Recovery After a Server Fails"
Attributes
Cluster - The name of the cluster to which the server belongs.
Current Server - The server that currently owns the JMS server. This may not necessarily be server that you are currently using to view the console (the server name at the top of the console page). In other words, if the JMS server was migrated to another server, that server is listed here. If the JMS server was not migrated, the current server is the server that is running the console.
Destination Server - A list of servers in the cluster. Select the server to which you want to migrate the JMS server. This list shows all servers in the cluster or a list of servers that you specify on the Server
|
|
|