Open topic with navigation

TIBCO ActiveSpaces® 4.8.0

# Upgrading from an Earlier Version

Read these instructions before upgrading from an earlier version of ActiveSpaces. If you are running multiple data grids, it is recommended to upgrade one data grid at a time following the procedure in this section for each data grid.

Before you begin You must take a backup of all data directories: the realm server, all state keepers, and nodes. The location of the `data` directory for the realm server can be found in the TIBCO FTL® Administration guide. The location of the data directories for the ActiveSpaces processes can be found in TIBCO ActiveSpaces® Administration .
During the upgrade process, do not make changes to the data 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 ActiveSpaces. If you must upgrade TIBCO FTL, follow the "Upgrade Migration to a New Release" section documented in the document TIBCO FTL® Administration.
   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.

   Note the following when migrating TIBCO FTL versions for use with ActiveSpaces:

   1. Use tibftlserver instead of tibrealmserver. For more details on converting TIBCO FTL 5.x tibftlserver command-line options into the appropriate configuration options for tibrealmserver, see "FTL Server Configuration" in TIBCO FTL Administration . Most of the options use the same name. For example,`--server.user` is the `server.user` configuration file option.
   2. Use the `ftl-internal` authorization group.
      As of TIBCO FTL 6.0, the authorization groups `ftl-primary`,`ftl-satellite`,`ftl-backup`, and`ftl-dr` are obsolete.
2. Install the latest version of ActiveSpaces on all computers running the data grid processes (tibdgnode, tibdgkeeper, tibdgproxy, tibdgadmind), and the systems that run the tibdg tool to administer the data grid.
3. If you are running tibdgadmind, perform the following steps for each tibdgadmind process to be upgraded:

   1. Ensure the latest version of ActiveSpaces has been installed on the computer running tibdgadmind.

   2. Stop the tibdgadmind process that you want to upgrade by using the following command:

          tibdg -t <tibdgadmind_listen_URL> admind stop

      By default, tibdbadmind listens on http://localhost:7171

   3. Restart the tibdgadmind process using the latest installed version of ActiveSpaces.

4. 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 <grid_name>

   Before upgrading ActiveSpaces components, the ActiveSpaces administrative command tibdg grid rebuild must be run on the existing data grid.
5. 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> [-g <grid_name>] status

   Remember: When 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.
6. To upgrade an individual state keeper, perform the following steps:
   1. Install the latest version of ActiveSpaces on the computer 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.
7. Before upgrading each node in your copysets, use the following command to check the role of each node:

       tibdg -r <realm_service_URL> [-g <grid_name>] status

   Remember: When upgrading the nodes of each copyset, start by upgrading the one or more secondary nodes followed by the primary node.
8. To upgrade an individual node, perform the following steps:
   1. Install the latest version of ActiveSpaces on the computer 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 by using the latest installed version of ActiveSpaces. See the section "Starting a Node" in TIBCO ActiveSpaces® Administration.
   4. For each copyset, repeat step 7 to upgrade one or more secondary nodes followed by the primary node.
9. To upgrade an individual proxy, perform the following steps:
   1. Install the latest version of ActiveSpaces on the computer 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 by using the latest installed version of ActiveSpaces. See the section "Starting a Proxy" in TIBCO ActiveSpaces® Administration.
   4. Repeat Step 8 to upgrade all proxies.
10. To upgrade an individual client, perform the following steps:
    1. Install the latest version of ActiveSpaces on the computer 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 by 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. Repeat step 9 to upgrade all clients.

Copyright © 2009-2022. Cloud Software Group, Inc. All Rights Reserved.