Upgrading Runtime Hosts and Nodes

While upgrading a host, all nodes that are managed by that host are also upgraded. There is no separate workflow for upgrading nodes. The TCT upgrade/downgrade wizard only shows a list of hosts for you to select for upgrade.

Upgrading the host entails the following:

1. Installing product features on a host

   New version of the product features are installed on the host. Before installing the product features the Host Manager gets the currently installed product features from the host and installs the new version for only those product features. Also, the product features that are completely new in ActiveMatrix Service Grid 3.4.1 will be installed.

2. Enabling product features on a node

   New product features that are installed on the host are enabled on all the nodes managed by that host. This will make sure that the runtime nodes now run with the latest software.

3. Disabling old product features

   Old version of the product features are disabled from all the nodes managed by the host.

   Note: The old product features are not uninstalled from the host (that is, features are not removed from the CONFIG_HOME).
4. Updating JRE version of all hosts and nodes to version 1.8.0.

   This is done internally when the hosts and nodes are updated to use ActiveMatrix 3.4.1 rpfLauncher_classpath_3.4.1.tra file.

5. REST BT system applications installed previously are removed from all the nodes, if found.

   The dependency of all the REST BT user applications is updated to depend on platform application.

6. BPM system applications, amx.bpm.app and amx.bpm.apacheds, are stopped.
7. Updating executables of all hosts and node (for example, tibcohost.exe) to use new wrapper version 2.4.7.

   This will change the icons of all the executables (in Windows).

8. Platform application of all the nodes are now upgraded to a new version.

All the above steps can be verified in the upgrade logs. A sample output of all the above steps is provided in the Example: Upgrade Scenario section.