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.
  Note: Using this level of message logging significantly increases the amount of information sent to the log file. Once you have verified that the probe runs correctly, change the value of the MessageLog property. For example, set the property to info.
- LocalHttpHost: Set this property to the name of the local host that runs the web service. The default value of this property is localhost.
- LocalHttpPort: Set this property to the port that the probe listens on for AMI events. The default value of this property is 8080.
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/linux2x86/nco_p_iec_cim_ami -help

Check that the output from this command begins as follows:

Using IBM Java
Version 1.6.7
Usage: "nco_p_iec_cim_ami" [options]

where options can be:

-autosaf                     Enable automatic Store and Forward on startup
-beatinterval                Probe failover heartbeat interval
-beatthreshold               Probe failover heartbeat threshold time
-buffer                      Turn on alert buffering

Start the probe as follows:

$NCHOME/omnibus/probes/linux2x86/nco_p_iec_cim_ami \
-propsfile $NCHOME/omnibus/probes/linux2x86/iec_cim_ami.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 and so check they are processed correctly.

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