Defining Nodes

There are two types of Nodes in AlarmPoint; this section explains how to define each type of Node.

Defining an Application Server Node

Application Server Nodes are responsible for receiving events and translating them into notifications. Once the notifications are prepared, the Application Server Node either delivers them via an integrated Device Engine or forwards the notifications to a remote Notification Server Node for delivery to the appropriate Devices.

To modify Application Server Node details:
  1. On the Application Server Node Details page, enter the following information into the form:
Application Server Node details

Detail

Description

Callback Number

Type the phone number Users should call when responding to notifications sent by this Node.

Active

Select this check box to activate the Node, or clear the check box to disable the Node.

Identifier

Type a unique identifier for the Node to be stored in the configuration database.

Description

Type a few words or a phrase that describes the Node. (Optional)

Select Cluster

Specify the Notification Server Cluster which will contain this Node. For more information, see Clusters.

Client Connections

Maximum number of Java Clients that can connect simultaneously. This value is license-controlled.

Host

Specify the externally-addressable hostname or IP for this Node. (Used for inter-node communications.)

Port

Type the port number to use for inter-node communications.

Port Hub

Type the port number to listen on for Java Client connections.

Logging

For an explanation of the Logging settings for Nodes, see Configuring Node Logging.

Executable

Fully-qualified path to an executable file to launch whenever a Health Monitor event occurs (e.g., on a Windows node computer, “C:\Program Files\eclipse\eclipse.exe" will open the Eclipse application; on a Linux node computer, “\usr\bin\vim” opens the VIM editor). Note that the Health Monitor does not accept parameters. For more information on the Health Monitor and the conditions that trigger an event, see About the Health Monitor.

  1. When you are satisfied with the information you have provided, click Save.

Defining a Notification Server Node

Notification Server Nodes contain Device Engines, which are responsible for sending notifications and receiving responses via service providers and device protocols.

Note: For more information about Device Engines, see Device Engines.
To modify Notification Server Node details:
  1. On the Notification Server Node Details page, enter the following information into the form:

Detail

Description

Callback Number

Type the phone number Users should call when responding to notifications sent by this Node.

Note: If a Call In Number is specified for the Company (as described on Call In Number), that number will take precedence over this setting.

Active

Select this check box to activate the Node, or clear the check box to disable the Node.

Identifier

Type a unique identifier for the Node to store in the configuration database.

Description

Type a few words or a phrase that describes the Node. (Optional)

Select Cluster

Specify the notification server cluster which will contain this Node.

Host

Specify the externally-addressable hostname or IP for this Node. (Used for inter-node communications.)

Port

Type the port number to use for inter-node communications

Logging

For an explanation of the Logging settings for Nodes, see Configuring Node Logging.

Executable

Fully-qualified path to an executable file to launch whenever a Health Monitor event occurs. For more information on the Health Monitor and the conditions that trigger an event, see About the Health Monitor.

  1. When you are satisfied with the information you have provided, click Save.
Note: When a Notification Server Node is created using the web user interface, the displayed node status may remain listed as "Not Deployed". To resolve this, delete the Node in the web user interface and recreate it using the AlarmPoint installer.