CommandCenter

From ServersCheck Wiki

Prerequisite

You need to install the msp.lic file in the /lic subfolder of your main ServersCheck directory. On the appliance this is typically

D:>Program Files>ServersCheck Monitoring>lic

Restart all ServersCheck services after copying the license file to the correct folder.

Configuring Command Center (NOC) Data Exchange for HTTP Data Exchange

The ServersCheck Monitoring Software pushes over HTTP the status to the central Command Center application. The server running the Command Center application has to be visible to the appliance.

The server can be running on a public IP with an ISP or as for ServersCheck live demo on a cloud server (in our case Amazon EC2) - however one could also setup a VPN tunnel between Appliance & Command Center server

We will now assume that the communication channel between Appliance & Command Center server has been set up.

We first need to give the appliance a unique identifier. This has to be unique as otherwise data between different appliances can be mixed up.

In the ServersCheck Monitoring Software go to Configuration > General Settings > Set Appliance Identifier

ServersCheck will suggest automatically a unique identifier but you can set it to any alpha numeric combination.

Now go back to the main General Settings menu and click on the Command Center Integration option. A window similar as following will open. In this screen set following parameters:

- NOC Update Frequency Status: minimum value is 30 seconds. This is the frequency at which you want the appliance to push its status to the Command Center. The more frequent the quicker you centrally see on the main screen an issue but the more traffic is generated

- NOC Communication Protocol: currently we only support HTTP as communication protocol

- NOC Password: this password has to be identical as set in the Command Center software - this ensures that only allowed people can send data through. You can also secure the web app on a firewall to only accept incoming requests from trusted IP's.

- NOC Command Center IP Address: this is the IP address of the server running the Command Center software; you can also use the domain name instead

- NOC Command Center Port: this is the port on which the Command Center software (receiver) is running. Typically this is 80 for a web server

Click on the TEST SETTINGS button to verify your configuration. A test window like the one shown below will open. A message similar as in the shown window means that the data exchange has been setup correctly.

Click now on the SAVE SETTINGS button.

it is recommended to restart all ServersCheck services following this configuration.