Can EMS datastore files be reused?
Article ID: KB0092651
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
Is it permissible to create a datastore on one EMS instance and use it with other EMS instances? If so, are there any other requirements that are necessary to make this work?
Environment:
All
Resolution:
EMS datastore files created on one EMS instance can be reused on another EMS instance.
It is required that the same set of configuration files used with the original EMS instance be used when starting the new EMS server with the reused datastore files.
Furthermore, if you upgrade from EMS 4.x to 5.x, tibesmd makes some changes to your store files that allow them to function with the multiple store feature. These changes are incompatible with EMS 4.x, and will prevent an EMS 4.x server from starting if you try to roll back to an older version of EMS from a 5.x version . The tibemsdb5revert tool is included with EMS 5.x in order to remove the changes made to those files. The tool takes one argument, which is the directory where the store files are located. By default, the files are located in the tibemsd working directory.
You must give the absolute path to the directory when using this utility. For example:
tibemsdb5revert /filesystem/datastore
Run tibemsdb5revert after reverting to EMS 4.x but before restarting the EMS server. The tool only makes changes to the default store files sync-msgs.db, async-msgs.db, and meta.db. If you have altered the default configuration to change these file names, tibemsdb5revert will fail.
For more details, please refer to the EMS Release Notes, section entitled, "Compatibility With Previous Versions".
Description:
Is it permissible to create a datastore on one EMS instance and use it with other EMS instances? If so, are there any other requirements that are necessary to make this work?
Environment:
All
Resolution:
EMS datastore files created on one EMS instance can be reused on another EMS instance.
It is required that the same set of configuration files used with the original EMS instance be used when starting the new EMS server with the reused datastore files.
Furthermore, if you upgrade from EMS 4.x to 5.x, tibesmd makes some changes to your store files that allow them to function with the multiple store feature. These changes are incompatible with EMS 4.x, and will prevent an EMS 4.x server from starting if you try to roll back to an older version of EMS from a 5.x version . The tibemsdb5revert tool is included with EMS 5.x in order to remove the changes made to those files. The tool takes one argument, which is the directory where the store files are located. By default, the files are located in the tibemsd working directory.
You must give the absolute path to the directory when using this utility. For example:
tibemsdb5revert /filesystem/datastore
Run tibemsdb5revert after reverting to EMS 4.x but before restarting the EMS server. The tool only makes changes to the default store files sync-msgs.db, async-msgs.db, and meta.db. If you have altered the default configuration to change these file names, tibemsdb5revert will fail.
For more details, please refer to the EMS Release Notes, section entitled, "Compatibility With Previous Versions".
Issue/Introduction
Can EMS datastore files be reused?
Feedback
Yes
No
Powered by
