Upgrading from an Earlier Version

Read these instructions before upgrading from an earlier version of ActiveSpaces.

Prerequisites

You must take a backup of all data directories: the realm server, all state keepers, and nodes.
Note: During the upgrade process, do not make changes to the grid configuration such as adding or removing tables and adding or removing indexes.

Procedure

  1. Determine if the TIBCO FTL realm server needs to be upgraded to a later version of TIBCO FTL. See TIBCO ActiveSpaces readme file for the versions of TIBCO FTL that can be run with this version of TIBCO ActiveSpaces. If you have to upgrade TIBCO FTL, follow the "Upgrade Migration to a New Release" section documented in the document TIBCO FTL Administration.
    Note: When migrating to TIBCO FTL 6.1 or later, ActiveSpaces uses the realm service capabilities of TIBCO FTL and does not use its other services such as the persistence, transport bridge or disaster recovery services.
  2. Install the latest version of ActiveSpaces on all machines running the data grid processes (tibdgnode, tibdgkeeper, tibdgproxy, tibdgadmind), as well as machines that will run the tibdg tool to administer the grid.
  3. Run the following command from the latest version on an existing data grid before you start any of the nodes in the latest version:
    tibdg -r realm_service_URL grid rebuild
    Note: Before upgrading ActiveSpaces components, the ActiveSpaces administrative command tibdg grid rebuild must be run on the existing grid.
  4. Before upgrading each state keeper in your quorum, use the following command to check the role of each state keeper:
        tibdg -r realm_service_URL status
    Remember: While upgrading the state keepers, start with the state keepers which are not lead state keepers and then upgrade the lead state keeper in the end. To identify the lead state keeper, run the tibdg status command and look for the text "leader" in the ROLE column.
  5. To upgrade an individual state keeper, perform the following steps:
    1. Install the latest version of ActiveSpaces on the machine running the state keeper.
    2. Stop the existing state keeper by using the following command:
      tibdg -r <realm_service_URL> [-g <grid_name>] keeper stop <keeper_name>
    3. Restart the state keeper by using the latest installed version of ActiveSpaces. See the section "Starting a State Keeper" in TIBCO ActiveSpaces Administration.
  6. Before upgrading each node in your copysets, use the following command to check the role of each node:
    tibdg -r realm_service_URL status
    Remember: While upgrading the nodes of each copyset, start by upgrading the one or more secondary nodes followed by the primary node.
  7. To upgrade an individual node, perform the following steps:
    1. Install the latest version of ActiveSpaces on the machine running the node.
    2. Stop the existing node by using the following command:
      tibdg -r <realm_service_URL> [-g <grid_name>] node stop <node_name>
    3. Restart the node using the latest installed version of ActiveSpaces. See the section "Starting a Node" in TIBCO ActiveSpaces Administration.
    4. Optional: For each copyset, repeat Step 7 to upgrade one or more secondary nodes followed by the primary node.
  8. To upgrade an individual proxy, perform the following steps:
    1. Install the latest version of ActiveSpaces on the machine running the proxy.
    2. Stop the existing proxy by using the following command:
      tibdg -r <realm_service_URL> [-g <grid_name>] proxy stop <proxy_name>
    3. Restart the proxy using the latest installed version of ActiveSpaces. See the section "Starting a Proxy" in TIBCO ActiveSpaces Administration.
    4. Optional: Repeat Step 8 to upgrade all proxies.
  9. To upgrade an individual client, perform the following steps:
    1. Install the latest version of ActiveSpaces on the machine running the client.
    2. Review the TIBCO ActiveSpaces Release Notes for any changes to the API which might affect your client application.
    3. Stop the client.
    4. Make the necessary changes to your client application, if any.
    5. Restart the client using the latest installed version of ActiveSpaces.
      Note: The steps for stopping and restarting your ActiveSpaces clients depends on the design of your clients.
    6. Optional: Repeat Step 9 to upgrade all clients.