Getting started

This section shows how to start the probe with the minimum required configuration. The procedure assumes that you have a version of Netcool/OMNIbus installed and running.

Use the following procedure to start the probe with a minimal configuration:

Note: The commands shown in this example are for a Linux system. Adapt these commands as necessary for the operating system that your probe server runs.

Download the probe's installation package following the instructions in http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html.
Install the probe following the instructions in http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html.
Edit the probe's properties file and set values for the following:
- Server: Set this property to the name of the ObjectServer that the probe sends events to. The default value of this property is NCOMS.
- MessageLevel: Set this property to Debug. This setting provides the maximum amount of information when the probe is running.
- EndpointHttpHost: Set this property to the HTTP host name or IP address of the OPC UA server host that provides alarms to the probe.
- EndpointHttpPort: Set this property to the HTTP port on the OPC UA server that the probe uses to retrieve alarms.
- EndpointSessionServiceName: Set this property to the service name path of the endpoint on the OPC UA server.
- OPCSessionName: Set this property to the name of the probe session on the OPC UA server to which you want to connect.
- MonitoredItemsConfigFile: Set this property to the full path of the XML file that contains information on the items that the probe is to monitor. The information in this file is used in the OPC UA CreateMonitoredItems service.
  See Notification retrieval and synchronization for more information on this file.
Ensure that $NCHOME/etc/omni.dat includes information on the ObjectServer.
If you made changes to omni.dat, regenerate the definition file by running $NCHOME/bin/nco_igen.
Check that the server where you have installed the probe can contact the ObjectServer using the ping utility. For example:
```
ping -c 10 server-name
```
Replace server-name with the name of the server where the ObjectServer is running.

Alternatively, if you have installed the Netcool/OMNIbus desktop feature, you can use the nco_ping utility to check connectivity to the ObjectServer. For example:
```
nco_ping object-server
```
Replace object-server with the name of the ObjectServer.
Obtain a listing of the probe's command line options to check the probe is installed correctly:
```
$NCHOME/omnibus/probes/nco_p_opc_ua -help
```

Start the probe as follows:

$NCHOME/omnibus/probes/nco_p_opc_ua \
-propsfile $NCHOME/omnibus/probes/linux2x86/opc_ua.props \
-messagelevel debug

Check the probe's log file to ensure the probe started correctly and is ready to receive, process, and dispatch events.
The probe's MessageLog property provides the name and location of the probe's log file.
Where possible, use a test tool to send events to the probe in order to check that the probe processes the events correctly.
For example, SoapUI (which allows you to set up a mock service server) and the OPC Foundation sample server, which provides sample implementations of OPC UA applications, both servers and clients.

See Using the OPC Foundation sample server for more information on the OPC Foundation sample server.

The probe is now successfully installed and operational. You can now configure the probe to suit your operating environment.