How to migrate publisher and subscriber applications using TIBCO Rendezvous Certified Messaging (RVCM) or TIBCO Rendezvous Distributed Queues using certified messaging (RVCMQ) to another machine using a different OS or RV versions?
Article ID: KB0088390
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
Description:
Often, there is a need of migrating RVCM/RVCMQ applications running on one machine to another machine using different RV or different OS versions. While migrating the CM applications in these situations, the most important part is the migration of ledger files.
The ledger files between RV 7.x and RV 8.x are compatible with each other, i.e., an application using RV 8.x API can use a ledger file generated by an application using RV 7.x API and the vice versa.
Similarly, the ledger files are platform independent, i.e., a ledger file generated on SunOS 5.8 can be copied back to Red Hat Enterprise Linux AS release 4 and used by the same application without any problem.
Resolution:
The basic steps for migration are as follows:
1). Stop all subscribers and publishers.
2). Make a backup of all subscriber ledgers (if any) and move them back to the new box.
3). Port the subscriber applications to the new box.
4). Make a backup of all your publisher ledgers and move them to the new box.
5). Port the publisher applications to the new box.
6). Start the subscribers one by one. Make sure that the CMNames of the subscribers remain intact.
7). Start the publisher applications. Make sure that the CMNames of all publishers also remain intact.
TIBCO recommends following the above procedure in a test environment before attempting the move to production. If there is a problem during the test, we can analyze the information and provide a solution which will help reduce the chance of a production outage.
Description:
Often, there is a need of migrating RVCM/RVCMQ applications running on one machine to another machine using different RV or different OS versions. While migrating the CM applications in these situations, the most important part is the migration of ledger files.
The ledger files between RV 7.x and RV 8.x are compatible with each other, i.e., an application using RV 8.x API can use a ledger file generated by an application using RV 7.x API and the vice versa.
Similarly, the ledger files are platform independent, i.e., a ledger file generated on SunOS 5.8 can be copied back to Red Hat Enterprise Linux AS release 4 and used by the same application without any problem.
Resolution:
The basic steps for migration are as follows:
1). Stop all subscribers and publishers.
2). Make a backup of all subscriber ledgers (if any) and move them back to the new box.
3). Port the subscriber applications to the new box.
4). Make a backup of all your publisher ledgers and move them to the new box.
5). Port the publisher applications to the new box.
6). Start the subscribers one by one. Make sure that the CMNames of the subscribers remain intact.
7). Start the publisher applications. Make sure that the CMNames of all publishers also remain intact.
TIBCO recommends following the above procedure in a test environment before attempting the move to production. If there is a problem during the test, we can analyze the information and provide a solution which will help reduce the chance of a production outage.
Issue/Introduction
How to migrate publisher and subscriber applications using TIBCO Rendezvous Certified Messaging (RVCM) or TIBCO Rendezvous Distributed Queues using certified messaging (RVCMQ) to another machine using a different OS or RV versions?
Feedback
Yes
No
Powered by
