Monitoring Node Status

Edit online

You can view all the information about the nodes in the cluster through the Node Status page.

If you are working in a clustered environment, information is available about all the nodes in the cluster.

To view node status information:
  1. From the Administration menu, select Operations > System > Cluster > Node Status. The Node Status page displays the information described in the following table:
    Heading Description
    Name Displays the names of the nodes.
    URL Displays the uniform resource locator of node.
    Troubleshooter Provides a link to the System Troubleshooter.
    Token Node

    Indicates whether this is a token node.

    • True – Indicates that this is the token node.
    • False – Indicates that this is not the token node.
    Creation Time Displays the date and time on which a node was created.
    Status

    Displays the status of a node.

    • Active – Indicates that a node is working and is available for processing.
    • Node went down – Indicates that a node is not working and is not available for processing.
    • Node completely down – Indicates that all the services of a node have been stopped completely.
    • Starting Ops – Indicates that a node is starting up, but is not available for processing.
    Notes:
    • If it is indicated that a node has gone down, in the install_dir/bin directory of the node, run the hardstop.sh (for UNIX) or the hardstop.cmd (for Windows) script, and then run the run.sh (for UNIX) or the startWindowsService.cmd (for Windows) script. This stops all processing, and restarts the node.
    • Rerun the script of a node when its status is Node completely down. You can monitor the status of the restarted node in the other nodes of the cluster too.
  2. To view more details about a node, click the name of the node in the Node Status page. This displays a details page containing the information described in the following table:
    Heading Description
    Node Name Displays the name of the node.
    URL Displays the uniform resource locator of node.
    Token

    Indicates whether this is a token node.

    • True – Indicates that this is the token node.
    • False – Indicates that this is not the token node.
    Creation Time Displays the date and time on which a node was created.
    Status

    Displays the status of a node.

    • Active – Indicates that a node is working and is available for processing.
    • Node went down – Indicates that a node is not working and is not available for processing.
    • Node completely down – Indicates that all the services of a node have been stopped completely.
    • Starting Ops – Indicates that a node is starting up, but is not available for processing.
    Notes:
    • If it is indicated that a node has gone down, in the install_dir/bin directory of the node, run the hardstop.sh (for UNIX) or the hardstop.cmd (for Windows) script, and then run the run.sh (for UNIX) or the startWindowsService.cmd (for Windows) script. This stops all processing, and restarts the node.
    • Rerun the script of a node when its status is Node completely down. You can monitor the status of the restarted node in the other nodes of the cluster too.
    Location Displays the directory path on which the node is installed.
    Role States the role of the node.
    Operation Controller Host Displays the name of the server acting as the Operation Controller Host.
    Operation Controller Port Displays the port number of the Operation Controller.
    Sterling B2B Integrator Version Displays the version of Sterling B2B Integrator that is installed in the node.
    JVM Version Displays the version number for the Java™ Virtual Machine (JVM™).
    JVM Vendor Shows the vendor who provided the JVM™.

    The information described in the following rows is displayed only if queueWatcher=true in the install_dir/properties/noapp.properties_platform_ifcresources_ext file.

    Multicast Info

    Provides information about the communication mechanism across nodes. This is used to provide load factor and status information about a node to all the other nodes in a cluster.

    Clustering uses the JGroups communication toolkit, which supports the following communication protocols, which can be configured during deployment:
    • UDP (User Datagram Protocol) (IP multicast)
    • TCP
    Engine Queue Content

    Provides a link to the Engine Queue Content page for the node and queue. This page contains details about active threads, and the items in the queue that are waiting for a thread.

    Use the drop-down menu to select the queue you want to review
    Distribution Size

    Provides a link to the Distribution Size page. This page contains the following information:

    • Scheduling policy details
    • Soft reference cache details
    • Queue details (for each queue)