NodeUtil

Caution: This tool can cause irreversible damage to ActiveMatrix if not used exactly per TIBCO guidelines. As such, it should not be used unless advised by TIBCO Support.

The NodeUtil utility is used to remove components where attempts to undeploy or force undeploy an application does not remove the components from the node's runtime.

A typical sequence for this use case:
  1. Undeploy or force undeploy an application using the Administrator UI or CLI command. The application components should be removed from the node's runtime.
  2. Delete the application using the Administrator UI or CLI command. The application and it's components should be removed from the Administrator database.
  3. If either of the above steps fail, use the force delete option using the Administrator UI or CLI command to remove the application and it's components from the Administrator database.
  4. Use the nodeutil to remove the application components from the node's runtime.
Note: The nodeutil -removeApplication command removes components and endpoints of an application. However, it does not remove resource instances with scope defined to an application. In cases where an application has scoped resource instances, they need to be removed explicitly using OSGi console.
When using this utility for updating the dependency metadata for components, use it only when the component instance is not visible from the Administrator UI. When a component instance is not visible from the Administrator UI, any upgrade of dependent components would leave the component instance in a Waiting for dependency state. A typical sequence for this use case:
  1. Find the URI of the component dependency before and after the upgrade.
  2. Shut down the runtime node. This can be done from Administrator UI or CLI command or the tibcohost command.
  3. Use the nodeutil utility to update the dependency for the component.
  4. Start the node. Verify that the component is no longer in the Waiting for dependency state.