Action History

Action history displays information about actions performed on objects such as a node, host, or an application using ActiveMatrix Administration UI or the CLI.

  • Start, Stop, Install, Uninstall, Deploy, Undeploy are actions.
  • You can view the Action history in the Administrator web interface.
  • Action history does not record actions performed outside of the Administrator such as a TIBCO host restart.
  • Action history of an application displays the outcome of completed tasks and actions of the application's components and bindings .
  • The runtime status column of a host, node, and application displays the current status of an object.
The following scenarios explain how action history is helpful:
  • An application is redeployed without clearing the previous version of a feature. If the resolve mode for the redeploy action was not used, the node assumes the earlier version of the feature is needed. In this case, the action history displays Deploy with Start Failed and Runtime State displays Running. Click the Action History link and open the last action. Few successful actions and one failed action, Cleanup Features node name failed, displays.
  • Let us say, Application A is successfully deployed in Node A and uses an HTTP Connector resource instance A. Another instance HTTP resource instance B from the same resource template is created in Node B in the same machine. Action history will display Install Failed when instance B is installed. However, the instance status displays Installed (Start Failed). Stop and Restart the host. If instance B starts first, it will display Installed and instance A will display Installed (Start Failed). However, action history will not change as no action was initiated from the Administrator. The application Action History will display Successful, and the Application State will display Start Failed.
  • Let us say, Application A is successfully deployed in Node A and uses an HTTP resource instance A. Another instance HTTP resource instance B from the same resource template is created in Node B in the same machine. Start instance B from the Administrator. Since instance B is not running, the start will fail and Action History will display Start Failed. Now, remove instance B and restart the node with the application. The Application State will display Running. The Action History will continue to display Start Failed since no action was initiated from the Administrator.