Viewing and managing Nodes
You can modify Node details using the xMatters web user interface.
To view and manage Nodes:
- Note the Status column that indicates whether the Node is active (green check mark), or inactive (red 'x'); an inactive Node cannot process notifications.
- In the All Nodes list, do any of the following:
- To modify an existing Node, click the name of the Node in the list to view its Node Details. For more information, about editing Node Details, see "Defining Nodes".
- To remove a Node from the list, select the check box next to the Node you want to remove, and then click Remove Selected.
- To view and manage the list of Device Engines for a Node, click the Device Engines link in the View Components column. For more information about adding and managing Device Engines, see Device Engines.
- To view and manage the Resources for a Node, click the Resources link in the View Resources column. For more information about adding and managing Resources in Nodes, see Resources.
- To add a new Node, click the Add New link, and then select the type of Node you want to add from the drop-down list. Click Continue to specify the details for the new Node. For more information about the types of Nodes, and the specific details for each type, see the tables in "Defining Nodes".
|
Note:
|
Nodes must be installed using the xMatters installer. You can add a Node in the web user interface before installing it, but you must still run the installer against the target machine using the "Use Existing Node" option. |
Activity States
The list identifies the possible values for the All Nodes table's "Activity States" column, and provides an explanation of what each value means.
- Running: Indicates that the Node is active, and maintaining its scheduled heartbeat activity with the xMatters database.
- Stopping: Indicates that the Node is in the process of completing required tasks in preparation for shutting down. This status is usually the result of stopping the Node manually.
- Stop: The Node has been successfully stopped or shut down, and is no longer processing notifications or communicating with the database.
- Warning: The Node is still running, but has not successfully completed a heartbeat with the database for more than 30 seconds.
- Unreachable: The Node has not successfully completed a heartbeat with the database for more than 60 seconds. At this point, xMatters no longers considers the Node to be active, and will change its status to Inactive. Should the heartbeat function resume, xMatters will reactivate the Node automatically.
Configuring the maximum node shutdown timeout
Once the node manager receives a shutdown command, it tries to shut down all components in an orderly manner. By default, if the manager cannot shut down a component after five minutes, the node will be terminated regardless of the issue. However, if this five minute maximum node shutdown timeout is not appropriate for your environment, you can modify it.
To modify the maximum node shutdown timeout:
- If you do not already have a custom.properties file, copy (and rename) the custom.properties.sample file (located at <xMHOME>\node\config\) to <xMHOME>\node\config\custom.properties.
- Open the copied file in a text editor and add the following line (where <seconds> is the maximum number of seconds to wait before shutting down the node):
nodeManager.shutdownTimeout=<seconds>
- Save the file and restart the node.