Features Reference

For each Feature, you can display the name, type, feature status, and Node state. You can include system features in the feature list or display only features that you added to the Enterprise.

By default, a Node's Features list contains a Feature named TIBCO ActiveMatrix Platform. This Feature contains the runtime and implementations of the components in the platform application.

To view a list of plugins for each feature version, navigate to Infrastructure > Software Management > Features tab in TIBCO ActiveMatrix Administrator UI.
Note: The list of plugins can be seen only for Custom Features that may be deployed on any Node or associated with any Node. Plugins for System Features cannot be seen.

Click Show System Features to view the installed system features. This link toggles between Show System Features and Hide System Features.

Column Description
Name The feature name.
Type The type of the feature:
  • System - defined by a system.
  • Shared Library - features.
Version The feature version. When deleting a feature though CLI, the version functions as a wildcard. For example, specifying a version of 1.0 deletes all features whose version starts with 1.0.

Expand the version to view additional details.

Node The node where the feature is deployed.
Feature Status The runtime status of the feature:
  • Marked for Install - after a feature has been added to a node and before the change has been applied to runtime.
  • Marked for Uninstall - after a feature is removed and before the change is applied to runtime.
  • Installed - after a feature has been applied to runtime.
Node Runtime State
The runtime state of the node:
  • Not Installed - after a node has been created and before is has been installed
  • Not Running - after a node has been installed or when it was detected that the node ended without being stopped by the host. This applies when the process is detected as stopped.
  • Stopping - Stopping a node is expected to be a quick activity. If the node is stuck at Stopping for more than a few minutes, checking the logs may indicate the problem.
  • Stopped - the node was explicitly stopped. This is a normal and expected condition.
  • Starting - Starting a node is expected to be a quick activity. If the node is stuck at Starting for more than a few minutes, checking the logs may indicate the problem.
  • Start Failed - The host was not able to start the node process. Possible causes are that the node_classpath.tra file contains errors, the JRE libraries are not found, or the OS is unable spawn additional processes. After this state ,the node is disabled and must be manually enabled.
  • Running