JMS Migration Capabilities
To migrate the JMS assets from Broker to Universal Messaging, use the brokerjmsmigration.{bat/sh} migration script. The script does the following:
Migrates all the following JMS assets from a source
Broker to the target
Universal Messaging server:
Topics
Queues
Note:
JNDI destinations for topics and queues are auto-generated for the migrated JMS assets in the target Universal Messaging server.
Client groups
The Broker client groups are migrated as security groups to Universal Messaging. For topics with durable subscribers, the durable subscribers will be re-created in Universal Messaging when the client connects.
Writes the following migration information to the brokerjmsmigrationout.txt log file in the same directory as the migration scripts:
List of JMS topics, queues, client groups, and the corresponding JNDI Destinations of the source
Broker that were successfully migrated to the target
Universal Messaging server.
Warning messages if there is a mismatch between the properties of the JMS assets in the source
Broker and the target
Universal Messaging server.
Writes the error messages to the brokerjmsmigrationerr.txt file in the same directory where the migration scripts are placed.
For more information about running the JMS migration script, see
Running the JMS Migration Script.