Verifying Upgrade

After upgrading to the current release, you can use the following methods to verify whether the Hosts, Nodes and System Applications are upgraded successfully and to check whether they are using the new version.

Checking Host and Node Version from the ActiveMatrix Administrator UI

After upgrading to 3.4.1, all Hosts that are upgraded show the new version in the Version column of the Infrastructure > Hosts screen in the ActiveMatrix Administrator UI.

After upgrading to 3.4.1, all the Nodes that are upgraded show the new version in the Version column of the Infrastructure > Nodes screen in the ActiveMatrix Administrator UI.

Checking Host and Node Version from the Command Line

The Host version can be verified from the command line using the TIBCO_HOME/amx/<version>/bin/tibamx_hostmanager.exe describeHostUpgradeHistory or using the host/bin/tibcoHost.exe describeHost command.

An example using the tibamx_hostmanager.exe describeHostUpgradeHistory command is shown below.

Command: 

tibamx_hostmanager.exe describeHostUpgradeHistory -configHomeLocation C:\amx.home\data -instanceName Admin-amxadmin-instanceOne

Output: 

Invoking describeHostUpgradeHistory
    -configHomeLocation C:\amx.home\data
    -instanceName Admin-amxadmin-instanceOne

Upgrade history, current to oldest:
    Host platform version: 3.4.1, associated patch(es): amx.platform.patch:3.4.1
    Host platform version: 3.3.0.HF15, associated patch(es): amx.platform.patch:3.3.0.HF15
    Host platform version: 3.3.0, no associated patch(es)
Host can be Downgraded:
    3.3.0.HF15

Using tibcoHost.exe describeHost command:

Command: 

tibcohost.exe describeHost
Output: 
Invoking describeHost

Host description follows:
    Host name: SystemHost
    Enterprise name: amxadmin
    HPA instance name: Admin-amxadmin-instanceOne
    Bind status: bound
    Internet host name: apcWin2k8R2x64-55
    HPA type: TibcoHost
    HPA specification version: 2.2.0
    Host platform version: 3.4.1
    Connect URL: service:jmx:jmxmp://apcWin2k8R2x64-55:6051
    O/S name: Windows Server 2008 R2
    O/S version: 6.1
    O/S process ID: 7424
    System architecture: amd64
    Secure connection: false
    Patch(es) associated with this version:
    Upgrade history, current to oldest:
        Host platform version: 3.4.1, associated patch(es): amx.platform.patch:3.4.1
        Host platform version: 3.3.0.HF15, associated patch(es): amx.platform.patch:3.3.0.HF15
        Host platform version: 3.3.0, no associated patch(es)
    Upgrade status: none

Using tibcoHost.exe describeNodes command:

Command: 

tibcohost.exe describeNodes

Output: 

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
Description of node "ProxyNode" follows:
    Node description: ProxyNode
    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
Description of node "SystemNode" follows:
    Node description: Admin Default 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

Checking Node Logs for New Version

After upgrading, when the Node is started, look for the following log lines at the beginning of the Node log. It shows the version of TIBCO ActiveMatrix that the Node is running. Here is an example from the SystemNode.log. 

com.tibco.amx.hpa.node.Node - %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
com.tibco.amx.hpa.node.Node - TIBCO-AMX-HPA-014681: node "SystemNode" is running version 3.4.1 of TIBCO ActiveMatrix Platform
com.tibco.amx.hpa.node.Node - %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Checking Platform Application Version

After upgrading to ActiveMatrix Service Grid 3.4.1, the platform application (com.tibco.amx.platform) version is changed to 3.4.100. This can be verified from the Applications screen of the ActiveMatrix Administrator UI.

Also, check whether all the Applications are in the Running state.

Checking All Applications in the SystemEnvironment are Running

After upgrading to ActiveMatrix Service Grid 3.4.1, check whether all the Applications in the SystemEnvironment are in the Running state.

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.
  • After performing preceding step, upgrade to version 3.4.1 is successful but some runtime host fails during start after upgrade and the com.tibco.amx.platform.artifactserver application in the SystemEnvironment is in the Start failed state. In this case, manually start Host and Nodes OR undeploy and deploy the com.tibco.amx.platform.artifactserver application.