Resolution:
Description:
= = = = = = =

Steps to migrate/upgrade from RV 7.x to RV 8.x.

Environment:
= = = = = = =
ALL

Resolution:
= = = = = =

1. Stop all applications connected to the RV daemon. Stop all TIBCO applications that are using RV (BW, Adapters, etc).

2. Stop or kill all the TIBCO daemons (RVD, RVRD, etc).

3. Backup all the important files including:

a). The tibrv.tkt file
b). Any custom configuration files, those you have created, configured or modified.
c).  store files for RVRDs or rvcache.
d).  ledger files if you use RVCM.
e). Any important log files.

Do not save these copies in the default RV directory. There is a chance that they will be either deleted of overwritten by later installations/upgrades. Instead, copy these files to a non-TIBCO directory.

4. Un-install RV 7.x .

5. Install RV 8.x . Follow the RV 8.x installation steps in the RV 8.x Installation Guide.

6. Verify the new RV installation by following the instructions under “Administration” in the Tibco Rendezvous documentation.

7. Copy the ticket file "tibrv.tkt" to TIBRV/bin directory.

8. Copy the configuration/store/ledger files back to RV directory and apply any custom configurations.

-If RVRD is used the store files of RV 7.x and 8.x have the same format and are compatible, so those store files can be copied and used without modifications.

-If RVCM is used the RV 7.x and RV 8.x ledger files are compatible. The CM ledger file created by the RV 7.x API and the ledger file created by the RV 8.x API are compatible and do not require modification.

9. For C/C++ applications: If the applications were dynamically linked, the RV 7.x clients can be re-linked with the RV 8.x client libraries with no changes. If the applications were statically linked, you will need to rebuild the applications with the RV8.x client library.

For Java applications built with RV 7.x, the client libraries can be re-linked with the RV 8.x client libraries with no changes.  

For .NET clients, two new files were added to the distribution:
a). TIBCO.Rendezvous.dll.config
b). policy.1.0.TIBCO.Rendezvous.dll.

In the directory that contains these files run the following command:

gacutil /i policy.1.0.TIBCO.Rendezvous.dll

Your applications should be able to use the latest release of the .NET library without needing to be rebuilt.

10. Start the newly installed RV daemon and then restart the applications connecting to the RVD/RVRD daemons.

Note that the installation path of the new RV 8.x is different than the installation path of RV 7.x . If there are any RV applications that are running on the same box as the newly installed RV, make sure that the old applications are able to access the new RV daemon in the new installation path.  For example, in RV 7.5.4, RVD is located under tibco/tibrv/bin; . Under RV 8.1.2, RVD is located under tibco/tibrv/8.1/bin. Since the RV8 release, the directory structure has been changed to tibco/tibrv/&ltversion>.  Because of the change in directory structure, you may need to manually modify your configuration file in other applications, such as TRA/BW in order to use RV 8.1.2.

RV 7.x and 8.x daemons are compatible and applications built with the RV 7.x client libraries can be run against RV 8.x daemons, and vice-versa. RV 7.x and RV 8.x applications and daemons can also be intermixed.

Keywords/Tags:
= = = = = = = = =
Migration, Upgrade, 7.x, 8.x

Steps to migrate / upgrade RV 7.x to RV 8.x .