RHEL: Upgrade vFabric GemFire from the VMware YUM Repository

If your guest operating system is Red Hat Enterprise Linux (RHEL) and you have installed a previous version of GemFire using yum and RPM, VMware recommends that you use yum to upgrade vFabric GemFire. You complete the upgrade procedure on every virtual and physical machine that will run GemFire.

When you upgrade vFabric Suite components on RHEL from the VMware RPM repository, the components are installed into different directories and are owned by different users in different groups. The vFabric GemFire installation is owned by the gemfire user in the vfabric group.

The default installation directory is /opt/vmware/vfabric_gemfire/vFabric_GemFire_XXX where XXX corresponds to the version of GemFire (for example, vFabric_GemFire_662) that you have installed.

When you upgrade vFabric GemFire using the RPM, the upgrade process installs the new version into its own installation directory (/opt/vmware/vfabric_gemfire/vFabric_GemFire_XXX where XXX corresponds to the newly installed version). No files are overwritten during the upgrade process. Therefore, you can have two different versions of GemFire installed on the same machine for the purposes of performing a rolling upgrade.

  • Confirm that your system meets the hardware and software requirements described in Supported Configurations and System Requirements.
  • Install the vFabric 5 RPMs (you do this procedure only once):
    1. Log in to the RHEL VM as the root user (or as an unprivileged user who has sudo privileges) and start a terminal.
    2. Depending on the version of the vFabric platform you wish to upgrade to, install the appropriate repository RPMs. These repository RPMs make it easy for you to browse all the available vFabric component RPMs.
      Note: The version of vFabric GemFire included in the repository RPMs is the same across the platforms. You choice of vFabric platform will hinge on which other vFabric components and component versions you wish to install. See https://www.vmware.com/support/pubs/vfabric-pubs.html for more details on the different platform versions. Select the appropriate release from the "Select a release" drop-down list to view the components and component versions associated with each vFabric platform.

      • If you are installing vFabric GemFire standalone or installing vFabric Suite 5.2, use these commands to install the vFabric repository RPM. The URLs differ depending on the version of RHEL you are using.
        For RHEL 5:
        prompt# wget -q -O - http://repo.vmware.com/pub/rhel5/vfabric/5.2/vfabric-5.2-suite-installer | sh
        For RHEL 6:
        prompt# wget -q -O - http://repo.vmware.com/pub/rhel6/vfabric/5.2/vfabric-5.2-suite-installer | sh
        The command performs the following tasks:
        • Imports the vFabric GNU Privacy Guard (GPG) key.

        • Installs the vFabric 5.2 repository RPM.

        • Launches the VMware End User License Agreement (EULA) acceptance and repository configuration script.

        • Outputs the EULA for you to read; you must answer yes to accept the terms and continue.

      • If you are planning to upgrade to vFabric Suite 5.1 (Standard or Advanced), install the vfabric-5.1-repo-5.1-1 and vfabric-all-repo RPMs using the rpm command.
        For RHEL 5 users:
        prompt# rpm -Uvh 
        prompt # rpm -Uvh 
        For RHEL 6 users:
        prompt# rpm -Uvh 
        prompt# rpm -Uvh 
        If necessary, use sudo to run the preceding commands if you are not logged in as the root user.
      • If you are planning to upgrade to vFabric Cloud Application Platform 5.0, install the vfabric-5-repo-5-2 and vfabric-all-repo RPMs:
        prompt# rpm -Uvh
        prompt# rpm -Uvh
        If necessary, use sudo to run the preceding commands if you are not logged in as the root user.
    3. Use the yum search vfabriccommand to view the list of vFabric components that you can install from the VMware repository. The vFabric GemFire RPM is called vfabric-gemfire.
  1. Review the items listed in Before You Upgrade and make any appropriate preparations.
  2. From the RHEL computer on which you will upgrade vFabric GemFire, log in as the root user or as an unprivileged user using sudo.
  3. Execute the following yum command:
    prompt# yum upgrade vfabric-gemfire
    The yum command begins the upgrade process, resolves dependencies, and displays the packages it plans to install.
    The yum upgrade vfabric-gemfire command upgrades to the most recent version of the vFabric GemFire RPM that it finds in all installed repositories. If you want to upgrade to a different version of GemFire, you must explicitly specify the version with the yum install command. For example:
    prompt# yum upgrade vfabric-gemfire-661
    Use yum search vfabric-gemfire --showduplicates to find all versions that are available in the installed RPM repositories.
  4. Enter y at the prompt to begin the actual upgrade. If you have not already accepted the VMware license terms, a prompt asks you and you must answer yes to continue.

    If the upgrade is successful, you see a Complete! message at the end.

  5. Repeat this upgrade procedure for every virtual or physical machine on which you will run vFabric GemFire.
  6. Review the changes and upgrade notes that are documented in the vFabric GemFire Release Notes.
    • Review the vFabric GemFire 6.6.2 Release Notes. Make any changes to your applications that are required for you to migrate to this version. See Upgrading to GemFire 6.6.2 for a complete list of upgrade considerations.
    • If you are upgrading from a version earlier than GemFire 6.6, review all changes documented in the vFabric GemFire 6.6 Release Notes. Make any changes to your programs required for you to migrate to this version. In particular, you must update your licensing and licensing configuration to upgrade to GemFire 6.6.
  7. Recompile your Java applications against the gemfire.jar in this version of the product. After you have recompiled your Java applications, the location where you place the updated JARs will vary depending on your configuration. You may put them in the GemFire product tree or you could directly copy in the gemfire.jar file to a location appropriate for your application.
  8. Stop all members of the system running with the prior version.
    • Shut down all members running a cache by using the gemfire shut-down-all command: Using the command:
      gemfire –J-DgemfirePropertyFile=mygemfire.properties shut-down-all 
      In the sample command, substitute mygemfire.properties with the location of the previous vFabric GemFire's gemfire.properties file for the distributed system you are shutting down. See Shutting Down the System for more details.
    • Shut down any locators. To shut down a locator in 6.x.x deployments, issue the following command:
      gemfire stop-locator -port=port -address=ipAddr -dir=locatorDir
      Replace port, ipAddr and locatorDir with the appropriate values.
  9. Redeploy your environment's license or configuration files to the new version's installation. For example, you may need to do one of the following tasks depending on your GemFire deployment configuration:
    • If you are upgrading from GemFire 6.6 or later, you may need to copy any existing license files to the new product installation location. See How GemFire Manages Licenses for information for possible license file locations.
    • If you are using common configuration files, update your configuration files as required with the path to the new installation. See Deploying vFabric GemFire Configuration Files for more information on how to deploy configuration files.
    • If you are using local configuration files, update each set of configuration files that are local to the distributed system you are upgrading. If you are using local files, you also have the option to do a rolling upgrade and upgrade each distributed system one at a time. See Deploying vFabric GemFire Configuration Files for more information on how to deploy configuration files.
  10. Point all member sessions to the new installation of GemFire. For example, you may need to do one of the following tasks depending on your application's configuration:
    • Modify your applications to point to the new GemFire product tree location.
    • Copy the gemfire.jar file out of the new GemFire product tree location and replace the existing gemfire.jar file in your application.
  11. Restart all system members according to your usual procedures. See Starting Up Your System for more information.
What to do next