Upgrade Action Logs

Upgrade logs contain detailed information about the Upgrade process. The Upgrade section describes all the steps related to the Upgrade process in detail. The following are examples (headers and sample log) from the upgrade logs corresponding to each step in the Upgrade process.

  1. Installing Product Features on a Host: This can be verified under the following header. 
    --------------------------------------------------
Installing product features for version : 3.4.0
--------------------------------------------------

--------------------------------------------------
Following product features will be INSTALLED on host
--------------------------------------------------
  2. Enabling Product Features on Node: Corresponding log entries can be found under the following header. 
    -------------------------------------
Enabling product features on nodes
-------------------------------------

-------------------------------------
Following product features will be ENABLED on node :SystemNode
-------------------------------------
  3. Disabling old Product Features: Corresponding log entries can be found under the following header which contains the list of product features that are disabled on the node. 
     ----------------------------------------------------------------
 Following product features will be DISABLED on node :SystemNode
----------------------------------------------------------------
  4. Upgrading Wrappers Logs 
    Updating wrappers for the Host instances and Nodes
Updating wrapper for the Host instance: Admin-amxadmin-instanceOne
Successfully updated wrapper for the Host instance: Admin-amxadmin-instanceOne
Updating wrapper for Nodes on Host instance: Admin-amxadmin-instanceOne
Updating wrapper for the Node: DevNode
Successfully updated wrapper for the Node: DevNode
Updating wrapper for the Node: SystemNode
Successfully updated wrapper for the Node: SystemNode
  5. Upgrading Platform Application and REST Binding System Application: Logs for upgrading platform application and removing the add-on REST Binding System Applications can be seen under the following header. 
    print-report-start-process: 
[19 Jul 2017 19:13:27,578] Doing upgrade
[19 Jul 2017 19:13:27,578] AMX Node(s): [DevNode,SystemNode] found in CONFIG_HOME [C:\amx.home\data\config_admin\tibcohost\Admin-amxadmin-instanceOne]
 ********************************************************************************************************
This script will upgrade all node's AMX Platform Application listed below
Total Nodes to process: 2
Node: DevNode
Node: SystemNode
Tibco Home for this AMX Nodes is: C:\tibco
Configuration Home for this AMX Nodes is: C:\amx.home\data\config_admin\tibcohost\Admin-amxadmin-instanceOne
Tibcohost name is : Admin-amxadmin-instanceOne
 ********************************************************************************************************
  6. Summary: Once the applications are upgraded, it prints a summary of the result as follows. 
    ###########################################################################################################
####### Report of platform App upgrade for each node in CONFIG_HOME : C:\amx.home\data\
###########################################################################################################
#Ant properties
#Wed Jul 19 19:16:06 PDT 2017
Admin-amxadmin-instanceOne.node.DevNode=SUCCESS
Admin-amxadmin-instanceOne.node.DevNode.timetaken=1\:17.010 sec
Admin-amxadmin-instanceOne.node.SystemNode=SUCCESS
Admin-amxadmin-instanceOne.node.SystemNode.timetaken=1\:19.559 sec
###########################################################################################################