Using the desktop and Webtop tools

The Acknowledge Alert and Resolve Alert tools issue commands using the probe's command port.

The Acknowledge Alert tool connects to the probe's command port and issues the acknowledge_alarm @AlertKey command. Running the tool has the following results:
  • The value of @AlertKey is normally set to the value of the $id token of the event, which is the identifier required to acknowledge alerts in Microsoft SCOM 2016.
  • The resolution state of the event in Microsoft SCOM 2016 is set to 85 (Acknowledged).
  • The Netcool/OMNIbus alert is set to Acknowledged.
The Resolve Alert tool connects to the probe's command port and issues the resolve_alarm @AlertKey command. Running the tool has the following results:
  • The value of @AlertKey is set to the value of the $id token of the event, which is the identifier required to resolve alerts in Microsoft SCOM 2016.
  • The resolution state of the event in Microsoft SCOM 2016 is set to 255 (Resolved).
  • The severity of the Netcool/OMNIbus alert is set to 0 (clear).

The Probe for SCOM 2016 can send Acknowledge Alert and Resolve Alert messages using HTTP/HTTPS instead of CommandPort through options found in EventList (if the Desktop tool is configured) or WebGui (if the Webtop tool is configured).

The probe is started with HTTP enabled by setting the following OMNIbus core properties as follows:

NHttpd.EnableHTTP     :     true
NHttpd.ListeningPort  :     8080

Each alert sent from SCOM 2016 to the probe comes with a protocol URL similar to one of the following formats enabling a callback to probe using HTTP/HTTPS:

http://localhost:8080/probes/nco_p_scom2016
http://127.1.1.1:8080/probes/nco_p_scom2016
http://WIN-ABKVNR510EQ:8080/probes/nco_p_scom2016

Note: The URL will have HTTPS when SSL is enabled.

When the probe is started with CommandPort enabled, each alert is tagged with one of the following formats enabling a callback to the probe using Telnet:

telnet://localhost:6970
telnet://127.1.1.1:6970
telnet://WIN-ABKVNR510EQ:6970

In both cases, it enables an Acknowledge Alert/Resolve Alert callback to the probe from either EventList or WebGui. Depending on the protocol URL attached to the SCOM alert, a different protocol is used in the callback.

Note: During callback using HTTP/HTTPS or Telnet it can only succeed with a probe enabled with the same listening mode. For example, HTTP callbacks require the probe to have HTTP enabled; this is because a probe started in CommandPort does not listen to a HTTP/HTTPs port and vice versa.