Upgrade

Before you start the upgrade process, make sure you understand the impact the upgrade will have on your environment, and how various ActiveMatrix versions can coexist.

Upgrading your ActiveMatrix enterprise means upgrading the configuration of certain services and runtime objects. TIBCO provides a TIBCO Configuration Tool (TCT) wizard that you run to perform the upgrade process. The TCT wizard also allows you to run preliminary diagnostic tests and provides options to select runtime hosts in the enterprise that you want to upgrade.

To upgrade without difficulty, knowledge of the supported scenarios, upgrade impact, and the various steps in the upgrade process is helpful, and is summarized in the following sub-sections.

Supported Upgrade and Downgrade Scenarios

Following table lists the eligibility of various versions of ActiveMatrix platform for upgrading to ActiveMatrix Service Grid 3.4.1 or downgrading from ActiveMatrix Service Grid 3.4.1.
Version Eligible for Upgrading to ActiveMatrix 3.4.1? Can be Downgraded from ActiveMatrix 3.4.1?
ActiveMatrix 3.4.0 or ActiveMatrix 3.4.0 (with Hotfixes) Yes Yes
ActiveMatrix 3.3.1 or ActiveMatrix 3.3.1 (with Hotfixes) Yes Yes
ActiveMatrix 3.3.0 (with Hotfixes) upgraded to ActiveMatrix 3.3.1 (with Hotfixes) Yes ActiveMatrix 3.4.1 can only be downgraded to ActiveMatrix 3.3.1 (with Hotfixes)
ActiveMatrix 3.2.0 (with Hotfixes) upgraded to ActiveMatrix 3.3.1 (with Hotfixes) Yes ActiveMatrix 3.4.1 can only be downgraded to ActiveMatrix 3.3.1 (with Hotfixes)
ActiveMatrix 3.3.0 upgraded to ActiveMatrix 3.3.1 Yes ActiveMatrix 3.4.1 can only be downgraded to ActiveMatrix 3.3.1
ActiveMatrix 3.3.0 or ActiveMatrix 3.3.0 (with Hotfixes) Yes Yes
ActiveMatrix 3.2.0 upgraded to ActiveMatrix 3.3.0 Yes ActiveMatrix 3.4.1 can only be downgraded to ActiveMatrix 3.3.0
ActiveMatrix 3.1.x upgraded to ActiveMatrix 3.3.0 Yes ActiveMatrix 3.4.1 can only be downgraded to ActiveMatrix 3.3.0
ActiveMatrix 3.2.0 or ActiveMatrix 3.2.0 (with Hotfixes) Yes Yes
ActiveMatrix 3.1.x upgraded to ActiveMatrix 3.2.0 Yes ActiveMatrix 3.4.1 can only be downgraded to ActiveMatrix 3.2.0
ActiveMatrix 3.1.x No No
Note: If you have upgraded from ActiveMatrix Service Grid 3.1.5 to version 3.3.0 using scripts and then from version 3.3.0 to version 3.4.0. In this scenario, before upgrading to version 3.4.1, you must update the java.heap.size.max=512M to java.heap.size.max=1024M in the <TIBCO_HOME>/amx/3.4/bin/nodeutil.tra file.

Version Coexistence

In an enterprise, the hosts or nodes could have a version that is different from the ActiveMatrix Administrator that manages them. For example, in 3.4.1, ActiveMatrix Administrator can be upgraded to 3.4.1 while the host it manages could be running on an older version (3.3.0 or 3.2.0) and they can still coexist.
Note: Some Administration-related features (for example: updating a host's JVM parameters, downloading log files, and so on) will not work on these hosts and nodes which are "not upgraded" .

When a runtime host is upgraded to 3.4.1, all the nodes managed by that host are also upgraded to 3.4.1. As a result, the host and the nodes it manages are in sync and run the same version of ActiveMatrix.

Exceptions to Version Coexistence

As a rule, a Deployment Artifact Archive (DAA) can only be used with nodes whose version is greater than or equal to the Studio version used to create the DAA. For example, a DAA created by ActiveMatrix 3.3.0 requires nodes running ActiveMatrix 3.3.x or higher (for example, 3.4.x).

To find out the node version, you can use the tibcohost.exe describeNodes command or use the ActiveMatrix Administrator UI Nodes tab. An example of the tibcohost command is shown below: 

>tibcohost.exe describeNodes

The output of the command is: 

Invoking describeNodes
Description of node "DevNode" follows:
Node description: Development node
Current status: RUNNING
Node type: com.tibco.amf.hpa.tibcohost.node.hibernate.feature
Node type version: 3.4.1
Platform version: 3.4.1
Start mode: auto
...
...
The following scenarios are an exception to version coexistence:
DAA Created in Studio of Can be used with Cannot be used with
ActiveMatrix 3.4.1 ActiveMatrix 3.4.1 (and later version) Nodes

ActiveMatrix 3.4.0 Nodes

ActiveMatrix 3.3.1 Nodes

ActiveMatrix 3.3.0 Nodes

ActiveMatrix 3.2.0 Nodes

ActiveMatrix 3.1.5 Nodes

ActiveMatrix 3.4.0

For information on how you can find out the version of Business Studio, refer to the "Finding out the Version of TIBCO Business Studio Using which a Project was Created" section of the Composite Development Guide.

ActiveMatrix 3.4.0 (and later version) Nodes

ActiveMatrix 3.3.1 Nodes

ActiveMatrix 3.3.0 Nodes

ActiveMatrix 3.2.0 Nodes

ActiveMatrix 3.1.5 Nodes

ActiveMatrix 3.3.1

ActiveMatrix 3.3.1 (and higher) Nodes

ActiveMatrix 3.3.0 Nodes (provided Nodes are running with Java 1.8)

ActiveMatrix 3.2.0 Nodes

ActiveMatrix 3.1.5 Nodes

ActiveMatrix 3.3.0

ActiveMatrix 3.3.0 (and higher) Nodes

ActiveMatrix 3.2.0 nodes

ActiveMatrix 3.1.5 nodes

ActiveMatrix 3.2.0

ActiveMatrix 3.2.0 (and higher) Nodes ActiveMatrix 3.1.5 nodes

ActiveMatrix 3.1.5

ActiveMatrix 3.1.5 (and higher) Nodes

Nodes that are on versions prior to ActiveMatrix 3.1.5.

Note: While planning replication, ensure that both the Administrator Servers have the same set of software versions including the Hotfixes that were applied before upgrading to ActiveMatrix Service Grid 3.4.1.
Note: If your Application (DAA) deploys and runs fine in an earlier version of TIBCO ActiveMatrix Service Grid 3.4.1 but does not work properly in TIBCO ActiveMatrix Service Grid 3.4.1 environment, then check the logs to see if it is because of the Application's dependency on some Third Party Component Library (TPCL) jars whose TIBCO ActiveMatrix Service Grid 3.4.1 version drops export of some packages. If yes, then manually add those imports in your projects, rebuild and regenerate DAA, and deploy again.