Downgrading Runtime Hosts and Nodes

While downgrading a host all the nodes that are managed by that host will also be downgraded. There is no separate workflow for downgrading nodes. TCT Upgrade or Downgrade wizard only shows a list of hosts that you can select for downgrade.

Following steps are performed while downgrading the host:

  1. Installing product features on host

    Old 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 old version for only those product features. Also the product features that are completely new in ActiveMatrix 3.4.1 for which the corresponding old version cannot be found are removed.

  2. Enabling product features on node

    Old product features that are installed on the host are enabled on all the nodes managed by that host. This makes sure that the runtime nodes now run with the preferred version of the software.

  3. Disabling and uninstalling ActiveMatrix 3.4.1 product features

    ActiveMatrix 3.4.1 version of the product features are disabled from all the nodes managed by the host and then they are uninstalled from the host.

  4. Downgrading JRE version and Wrapper version

    Hosts and nodes are updated to use JRE version that they were using before upgrading to this release. Similarly, all host and node executables are updated to use the wrapper version before downgrade.

    Note: When you downgrade from ActiveMatrix Service Grid 3.4.1 to a previous version, the JRE version is not reverted to an earlier version used before upgrade (for example: ActiveMatrix Service Grid 3.4.0 which uses JRE 1.8 update 192). JRE version will remain JRE 1.8 update 321. To revert the earlier JRE version, you can take a backup of tibcojre64 folder from the old TIBCO_HOME and replace the current one.
  5. Downgrading platform application of all the nodes to an old version

    This is done by removing the ActiveMatrix 3.4.1 platform application and provisioning the old platform application (from the backup) directly in the runtime node.