Downgrade

Downgrading the ActiveMatrix enterprise means downgrading the configuration of certain services and runtime objects. TIBCO provides TCT wizard that you run to perform the downgrade process. The TCT wizard also allow you to run preliminary diagnostic test and provides options to select runtime hosts of your enterprise that you want to downgrade.

Prerequisites

New actions that are performed on the upgraded platform will potentially cause the downgrade to fail because of the compatibility issues. It is important to understand and proactively verify the state of the enterprise that will help to downgrade without any issues.

The following are some cases that could break the downgrade and the required actions to be taken before the downgrade.

  • Check for unbound hosts

    A new host that is created using the TIBCO Configuration Tool and is not bound or registered to ActiveMatrix Administrator cannot be downgraded. Do not select this unbound host for downgrade. Alternatively, remove the unbound hosts from the enterprise before downgrade.

    If CONFIG_HOME has any host that is not bounded to ActiveMatrix Administrator (that is, the host is created using TCT, but not yet bounded to any ActiveMatrix Administrator), do not select such unbounded host for downgrade. Selecting such unbounded host fails the downgrade process.

  • Check for new nodes created in 3.4.1

    When a new node is created after upgrading platform to ActiveMatrix 3.4.1, it cannot be downgraded to previous version. A host that contains the new node cannot be downgraded because the node does not exist in the previous version. Remove these new nodes before the downgrade or do not select these hosts from the list of hosts in the TCT wizard before downgrade. It is recommended to remove these nodes because after downgrading ActiveMatrix Administrator there may be compatibility issues in an earlier version of ActiveMatrix Administrator managing 3.4.1 nodes.

    If the user still downgrades the hosts that are created after upgrading to 3.4.1, they will be skipped and the upgrade procedure or scripts will not fail and will proceed to downgrade other hosts (if multiple hosts are selected).

  • Check for the HTTP Connector shared resource created after upgrading to ActiveMatrix 3.4.1

    HTTP Connector resource in ActiveMatrix 3.4.1 contains new properties that are not supported in the older version of ActiveMatrix (3.3.0 or earlier). As a result, after downgrade, these HTTP connector resource instances might go into a Not Running state and the applications using them might be in a Start Failed state. Refer to the Troubleshooting section to recover from this error state after the downgrade.

Note: Before downgrading from ActiveMatrix Service Grid 3.4.1 to ActiveMatrix Service Grid 3.3.1, update TIBCO JRE to the JRE 8 Update 162 or lower using command line (TIBCO_HOME\amx\<version>\bin\amx_jre_updater.exe). For more information, see TIBCO ActiveMatrix JRE Updater.
Note: If you have upgraded from an earlier version of TIBCO ActiveMatrix (including hotfixes) to TIBCO ActiveMatrix 3.4.1 and if you have installed and applied TIBCO ActiveMatrix 3.4.1 hotfix, when you revert the TIBCO ActiveMatrix 3.4.1 hotfix, downgrading to the earlier version of TIBCO ActiveMatrix is not supported. The same is applicable to an earlier version of TIBCO ActiveMatrix setup configured with TIBCO ActiveMatrix Policy Director Governance.