Category Archives: Omnibus

Installing and Configuring the Netcool Omnibus SCOM 2007 Probe

In this article we will install and configure the Netcool Omnibus SCOM 2007 Probe. The probe will be installed on a separate machine and will contact the SCOM server across the network.

The following steps will be performed to achieve the integration:

  • Install probe support
  • Install the SCOM probe
  • Configure the SCOM probe to communicate with the probe server and connect to the Omnibus server
  • Configure SCOM to work with the probe

We used Netcool Omnibus version 7.4 and Windows 2008 R2 for the operating systems.

Install probe support

Start the installation by executing the install.exe coming with the Netcool Ombibus Server installation image.

netcool-install-splashClick OK to continue the installation.

pre-installAccept the license agreement then click Next to start the configuration of the Autonomic Deployment Engine.

autonomicnextSelect Do not change at the Deployment Engine Access Permission windows and click Next to continue the installation.

select-destination-folderSelect the Destination Folder and click Next to continue. We used the default folder offered.

choose-install-setSelect Custom at the Install Set selection and click Next.

select-probe-support-onlySelect Probe Support only and continue the installation by clicking the Next button.

click-install-probe-supportClick Install to kick off the installation procedure.

restart-windows-probe-supportReboot your windows system to finalize the installation.

Install the SCOM probe

Unpack the probe zip file into a directory of your choice.

start-installation-probeStart the nco_install_integration.vbs located in C:\IBM\Tivoli\Netcool\omnibus\install if you used the default omnibus installation folder.

netcool-install-splashClick OK to continue the installation.

select-probe-to-installLocate the directory where you unpacked the probe file. You need to specify the directory that contains the COI directory then click Next.

install-probeAccept the License Agreement at the next screen then click Install to start the installation of the SCOM probe.

install-complete-probeThe installation of the SCOM probe is now complete.

Configure the SCOM probe to communicate with the probe server and connect to the Omnibus server

As a first step you need to specify your omnibus servers in the server editor.

start-server-editor-omnibus

You can start the server editor by going to the Start Menu -> Netcool Suite -> System Utilities -> Servers Editor

netcool-configure-objectservers

Add your object servers on the list in the server editor, you can delete whatever you find there by default as it is irrelevant for the current setup.

SDK-locationThe next step is to move the SCOM SDK files from the SCOM Server to the probe machine. You will need to have the copy the following files in the following directories:

  • C:\Program Files\System Center Operations Manager 2007\SDK Binaries\BinariesMicrosoft.EnterpriseManagement.OperationsManager.dll
  • C:\Program Files\System Center Operations Manager 2007\SDK Binaries\Microsoft.EnterpriseManagement.OperationsManager.Common.dll

The following task is to modify the probe’s configuration file.The probe files are located in C:\IBM\Tivoli\Netcool\omnibus\probes\win32 directory if you used the default installation folder. Modify the scom2007r2.props file by adding the following:

Server                        :       “AGG_P”
ServerBackup                  :       “AGG_B”
ConnectorName                    :       “Netcool probe”
ConnectorUser                    :       “youruser”
ConnectorPassword                :       “yourpassword”
ConnectorDomain                :       “yourdomain”
ScomHost                        :       “your_scom_hostname_or_ip”

probe-startedNow you should start the probe with the following command: C:\IBM\Tivoli\Netcool\omnibus\probes\win32\nco_p_scom2007_r2.exe If the probe stays running that means it has successfully connected to both the Object server and the SCOM 2007 Server.

Configure SCOM to work with the probe

netcool-connectorOnce the probe connects to the SCOM server successfully it will create the Netcool Probe product connector.

scom-groupsWe set up a group called netcool and assigned 2 Windows 2008 servers to it.

subsriptionsIf you need to filter on what nodes or events should hit the Probe, you can do so by setting up a groups and assigning them to the Netcool probe connector. Click on the Add button.

add-netcool-test-groupAssign a name to the Subscription then click Next.

approve-groups-scomSelect “netcool” from the groups list then click Next.

approve-targetsLeave the default option at the approve targets screen and click Next.

select-criteria-scomSelect the desired items you would like to have alerts raised for and click Create.

netcool-connectedThe subscription is now created and the events should start flowing across to Omnibus.

SCOM-events

Integrating Omnibus and PRTG using SNMP probe

This guide contains instructions for configuring PRTG Network Monitor software to send SNMP traps to a Omnibus.

Prerequisites:

  • working Omnibus instance
  • SNMP probe (mttrapd) installed and configured

More info on installing and configuring mttrapd.

First step is importing the MIB file.

PRTG Network monitor comes with a MIB file called PRTG-MIB.mib this file you can find in PRTG installation directory. Open mib manager utility to do the import.

/app/IBM/tivoli/netcool/omnibus/bin/nco_mibmanager

PRTG-MIB.mib is depending on SNMPv2-SMI , RFC-1215 and SNMPv2-TC  MIB files, so make sure they are accessible. (all of them are in the default MIB set of Omnibus)

As we see , the trap OID is 0.10  (1.3.6.1.4.1.32446.0.10) , and other attributes can be defined with OIDs 1.1, 1.2, 1.3, and 1.4.

SNMP traps sent by PRTG always use SNMP V1 format. The following OIDs will be included in the trap:

1.3.6.1.4.1.32446.1.1.1: MessageID (as defined by the user in the Field “Message ID”)
1.3.6.1.4.1.32446.1.1.2: An integer representing the event that triggered the notification:
0 = State ended
1 = State started
2 = Volume reached
3 = Speed not reached
4 = Speed reached
5 = Threshold not reached
6 = Threshold reached
7 = Value changed
1.3.6.1.4.1.32446.1.1.3: The state of the object:
0 = None
1 = Unknown
2 = Collecting Data
3 = Up
4 = Warning
5 = Down
6 = No Probe
7 = Paused by User
8 = Paused by Dependency
9 = Paused by Schedule
10 = Unusual
11 = Paused by License
12 = Paused until
13 = Down (Acknowledged)
14 = Down (Partial)
1.3.6.1.4.1.32446.1.1.4: The message text of the notification as defined by the user.

Select the top level enterprise OID from OID browser, click export rules file. Select location for the rules file, and choose rules file type.

Select standalone if you use this SNMP source only, or Netcool knowledge library to export master rules and include rules for more kind of sources.

Now open PRTG Enterprise Console, and navigate to Setup -> Notifications  and create a new notification type clicking “add new notification” button.

Select “Send SNMP Trap” option, and enter connection info:

  • SNMP probe hostname or IP address
  • Port
  • Community string
  • Specific Trap Code  (10)
  • Message ID (used for filtering)
  • Message (configurable using PRTG specific parameters. See PRTG Help for info )

Save the notification and test it clicking “Test” button next to Notification you just created.

Now (if you’re lucky) an event pops up on Omnibus console.

This event is not formatted, ( fe.: Summary field is empty ) so you have to create mappings between PRTG Trap OID values and Omnibus fields. You can do it by editing the rules file you generated before.

Locate the following section :

And edit the Omnibus fields ( @Agent, @Summary, etc. ) enter the information what you want to present on your console. The values of the four OIDs sent with the trap are

  • 1.1 = $paesslerPrtgTrapID
  • 1.2 = $paesslerPrtgTrapEvent
  • 1.3 = $paesslerPrtgTrapSensorstate
  • 1.4 = $paesslerPrtgTrapMessage

In our example Summary field will contain the value of paesslerPrtgTrapMessage OID, but you can customize other fields as well.

Modifications Required on Omnibus Server

Extend the size of the Summary filed in the Alerts table from 255 to at least 1024 as PRTG sends long problem descriptions and it won’t fit into the 255 character default.

modsummaryIn order to make it work with the SNMP probe modify the probe’s def file located in /opt/IBM/tivoli/netcool/omnibus/var/

Replace the value from 255 to 1024:

Identifier 2 255 1
Serial 0 4 0
Node 2 64 0
NodeAlias 2 64 0
Manager 2 64 0
Agent 2 64 0
AlertGroup 2 255 0
AlertKey 2 255 0
Severity 0 4 0
Summary 2 1024 0
StateChange 1 4 0
FirstOccurrence 1 4 0
LastOccurrence 1 4 0
InternalLast 1 4 0
Poll 0 4 0

Restart the probe.

And the final result :

prtgsummary

 

Installing & Configuring the IBM Tivoli Monitoring Agent for Netcool/Omnibus 8.1

The IBM Tivoli Monitoring Agent for Netcool/Omnibus 8.1  is located in the IBM Tivoli Monitoring Agent for Netcool/Omnibus 8.1 eAssembly ( CRS7KML ) bundle. We used SLES 11 SP3 as our installation platform.

Installing the IBM Tivoli Monitoring Agent for Netcool/Omnibus 8.1 agent support on the ITM server(s).

First install the product support for TEPS, TEMS. We have a one box test system running ITM 6.3.0.4 so we will only have to perform the product support installation in this one server. We will install the following packages:

Tivoli Enterprise Portal Browser Client support
Tivoli Enterprise Portal Desktop Client support
Tivoli Enterprise Portal Server support
Tivoli Enterprise Monitoring Server support

Start the installation by executing install.sh from the installation media.

HUITM001-P1:/Downloads/TIVOLI-IMAGES/OMNIBUS8-PACK/agent # ./install.sh
INSTALL

Enter the name of the IBM Tivoli Monitoring directory
[ default = /opt/IBM/ITM ]: /app/IBM/ITM

ITM home directory “/app/IBM/ITM” already exists.
OK to use it [ 1-yes, 2-no; “1” is default ]?  1

The following processes are currently running:

Product = Tivoli Enterprise Monitoring Server  PID = 4206
Product = Tivoli Enterprise Monitoring Automation Server  PID = 4532
Product = IBM Eclipse Help Server  PID = 4836
Product = Tivoli Enterprise Portal Server  PID = 4928
Product = Warehouse Proxy  PID = 5371
Product = Monitoring Agent for Linux OS  PID = 5857
Product = Summarization and Pruning Agent  PID = 16319
install.sh warning: Existing products found to be running will be restarted during installation., continuing …

Continue with this installation [ 1-yes, 2-no; “1” is default ]?  1
Stopping TEMS…
It can take up to ten minutes.
TEMS stopped…
Processing. Please wait…
Stopping Tivoli Enterprise Monitoring Automation Server …
Product Tivoli Enterprise Monitoring Automation Server was stopped gracefully.
Agent stopped…
Processing. Please wait…
Stopping IBM Eclipse Help Server …
Product IBM Eclipse Help Server was stopped gracefully.
Agent stopped…
Processing. Please wait…
Stopping Tivoli Enterprise Portal Server …
Product Tivoli Enterprise Portal Server was stopped gracefully.
KCIIN0196E Agent is not running…
Processing. Please wait…
Stopping Warehouse Proxy …
Product Warehouse Proxy was stopped gracefully.
Agent stopped…
Processing. Please wait…
Stopping Watchdog process…
Watchdog process was stopped.
Stopping Monitoring Agent for Linux OS …
Product Monitoring Agent for Linux OS was stopped gracefully.
Agent stopped…
Processing. Please wait…
Stopping Summarization and Pruning Agent …
Product Summarization and Pruning Agent was stopped gracefully.
Agent stopped…
/app/IBM/ITM

Select one of the following:

1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding
4) Exit install.

Please enter a valid number:  1

Initializing …
International Program License Agreement

Part 1 – General Terms

BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR USING
THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF
YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON
OR A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT AND
WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON,
COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO NOT
AGREE TO THESE TERMS,

– DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE
PROGRAM; AND

Press Enter to continue viewing the license agreement, or
enter “1” to accept the agreement, “2” to decline it, “3”
to print it, “4” to read non-IBM terms, or “99” to go back
to the previous screen.
1

Product packages are available in /Downloads/TIVOLI-IMAGES/OMNIBUS8-PACK/agent/unix

The following products are currently installed in “/app/IBM/ITM”:

Agentless Monitoring for AIX Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Agentless Monitoring for AIX Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Agentless Monitoring for AIX Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Server support
Agentless Monitoring for HP-UX Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Agentless Monitoring for HP-UX Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Agentless Monitoring for HP-UX Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Server support
Agentless Monitoring for Linux Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Agentless Monitoring for Linux Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Agentless Monitoring for Linux Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Server support
Agentless Monitoring for Solaris Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Agentless Monitoring for Solaris Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Agentless Monitoring for Solaris Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Server support
Agentless Monitoring for Windows Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Agentless Monitoring for Windows Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Agentless Monitoring for Windows Operating Systems V06.30.04.00 @ Tivoli Enterprise Portal Server support
IBM Eclipse Help Server V06.30.04.00 @ Linux Intel R2.6, R3.0 (32 bit)/Intel R2.6 GCC 2.9.5 (64 bit)/Intel R2.6, R3.0 (64 bit)/x86_64 R2.6, R3.0 (32 bit)/x86_64 R2.6, R3.0 (64 bit)
IBM GSKit Security Interface V08.00.50.20 @ Linux x86_64 R2.6, R3.0 (64 bit)
IBM HTTP Server V08.00.06.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
IBM Installation Manager V01.06.03.01 @ Linux x86_64 R2.6, R3.0 (64 bit)
IBM Tivoli Enterprise Portal Server Extensions V08.00.06.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint V06.23.05.00 @ Tivoli Enterprise Portal Server support
Monitoring Agent for Linux OS V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Monitoring Agent for Linux OS V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Monitoring Agent for Linux OS V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Monitoring Agent for Linux OS V06.30.04.00 @ Tivoli Enterprise Portal Server support
Monitoring Agent for TADDM Serviceability and Manageability V07.22.00.00 @ Tivoli Enterprise Portal Browser Client support
Monitoring Agent for TADDM Serviceability and Manageability V07.22.00.00 @ Tivoli Enterprise Portal Desktop Client support
Monitoring Agent for TADDM Serviceability and Manageability V07.22.00.00 @ Tivoli Enterprise Portal Server support
Monitoring Agent for UNIX Logs V06.23.05.00 @ Tivoli Enterprise Portal Browser Client support
Monitoring Agent for UNIX Logs V06.23.05.00 @ Tivoli Enterprise Portal Desktop Client support
Monitoring Agent for UNIX Logs V06.23.05.00 @ Tivoli Enterprise Portal Server support
Monitoring Agent for UNIX OS V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Monitoring Agent for UNIX OS V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Monitoring Agent for UNIX OS V06.30.04.00 @ Tivoli Enterprise Portal Server support
Monitoring Agent for Windows OS V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Monitoring Agent for Windows OS V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Monitoring Agent for Windows OS V06.30.04.00 @ Tivoli Enterprise Portal Server support
Monitoring Agent for i5/OS V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Monitoring Agent for i5/OS V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Monitoring Agent for i5/OS V06.30.04.00 @ Tivoli Enterprise Portal Server support
Summarization and Pruning Agent V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Summarization and Pruning Agent V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Summarization and Pruning Agent V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Summarization and Pruning Agent V06.30.04.00 @ Tivoli Enterprise Portal Server support
TEC GUI Integration V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
TEC GUI Integration V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
TEC GUI Integration V06.30.04.00 @ Tivoli Enterprise Portal Server support
Tivoli Enterprise Monitoring Automation Server V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Monitoring SOAP Server V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Monitoring Server V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Portal Browser Client V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Portal Desktop Client V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Portal Server V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Services User Interface Extensions V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Services User Interface V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Performance Analyzer V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Tivoli Performance Analyzer V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Tivoli Performance Analyzer V06.30.04.00 @ Tivoli Enterprise Portal Server support
Universal Agent V06.23.05.00 @ Tivoli Enterprise Portal Browser Client support
Universal Agent V06.23.05.00 @ Tivoli Enterprise Portal Desktop Client support
Universal Agent V06.23.05.00 @ Tivoli Enterprise Portal Server support
Warehouse Proxy V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Warehouse Proxy V06.30.04.00 @ Tivoli Enterprise Portal Browser Client support
Warehouse Proxy V06.30.04.00 @ Tivoli Enterprise Portal Desktop Client support
Warehouse Proxy V06.30.04.00 @ Tivoli Enterprise Portal Server support

All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents.

Product packages are available for this operating system and component support categories:

1) IBM Tivoli Monitoring components for this operating system
 2) Tivoli Enterprise Portal Browser Client support
 3) Tivoli Enterprise Portal Desktop Client support
 4) Tivoli Enterprise Portal Server support
 5) Tivoli Enterprise Monitoring Server support
 6) Other operating systems

Type the number or type “q” to quit selection
[ number “1” or “IBM Tivoli Monitoring components for this operating system” is default ]:  2

You selected number “2” or “Tivoli Enterprise Portal Browser Client support

Is the selection correct [ 1=Yes, 2=No ; default is “1” ] ? 1

The following application supports are available for installation:

1) Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00
2) all of the above

Type the numbers that correspond to the products that you want to install. Type “b” to change operating system, or type “q” to quit selection.
If you enter more than one number, separate the numbers by a comma or a space.

Type your selections here:  1

The following products will be installed:

Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00

Are your selections correct [ 1=Yes, 2=No ; default is “1” ] ? 1

… installing “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Browser Client support”; please wait.

=> installed “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Browser Client support”.
… Initializing component Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Browser Client support.
… Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Browser Client support initialized.

Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is “2” ] ? 1

Product packages are available for this operating system and component support categories:

 1) IBM Tivoli Monitoring components for this operating system
 2) Tivoli Enterprise Portal Browser Client support
 3) Tivoli Enterprise Portal Desktop Client support
 4) Tivoli Enterprise Portal Server support
 5) Tivoli Enterprise Monitoring Server support
 6) Other operating systems

Type the number or type “q” to quit selection
[ number “1” or “IBM Tivoli Monitoring components for this operating system” is default ]:  3

You selected number “3” or “Tivoli Enterprise Portal Desktop Client support

Is the selection correct [ 1=Yes, 2=No ; default is “1” ] ? 1

The following application supports are available for installation:

1) Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00
2) all of the above

Type the numbers that correspond to the products that you want to install. Type “b” to change operating system, or type “q” to quit selection.
If you enter more than one number, separate the numbers by a comma or a space.

Type your selections here:  1

The following products will be installed:

Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00

Are your selections correct [ 1=Yes, 2=No ; default is “1” ] ? 1

… installing “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Desktop Client support”; please wait.

=> installed “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Desktop Client support”.
… Initializing component Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Desktop Client support.
… Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Desktop Client support initialized.

Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is “2” ] ? 1

Product packages are available for this operating system and component support categories:

 1) IBM Tivoli Monitoring components for this operating system
 2) Tivoli Enterprise Portal Browser Client support
 3) Tivoli Enterprise Portal Desktop Client support
 4) Tivoli Enterprise Portal Server support
 5) Tivoli Enterprise Monitoring Server support
 6) Other operating systems

Type the number or type “q” to quit selection
[ number “1” or “IBM Tivoli Monitoring components for this operating system” is default ]:  4

You selected number “4” or “Tivoli Enterprise Portal Server support

Is the selection correct [ 1=Yes, 2=No ; default is “1” ] ? 1

The following application supports are available for installation:

1) Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00
2) all of the above

Type the numbers that correspond to the products that you want to install. Type “b” to change operating system, or type “q” to quit selection.
If you enter more than one number, separate the numbers by a comma or a space.

Type your selections here:  1

The following products will be installed:

Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00

Are your selections correct [ 1=Yes, 2=No ; default is “1” ] ? 1

… installing “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Server support”; please wait.

=> installed “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Server support”.
… Initializing component Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Server support.
… Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Portal Server support initialized.

Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is “2” ] ? 1

Product packages are available for this operating system and component support categories:

1) IBM Tivoli Monitoring components for this operating system
 2) Tivoli Enterprise Portal Browser Client support
 3) Tivoli Enterprise Portal Desktop Client support
 4) Tivoli Enterprise Portal Server support
 5) Tivoli Enterprise Monitoring Server support
 6) Other operating systems

Type the number or type “q” to quit selection
[ number “1” or “IBM Tivoli Monitoring components for this operating system” is default ]:  5

You selected number “5” or “Tivoli Enterprise Monitoring Server support

Is the selection correct [ 1=Yes, 2=No ; default is “1” ] ? 1

The following application supports are available for installation:

1) Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00
2) all of the above

Type the numbers that correspond to the products that you want to install. Type “b” to change operating system, or type “q” to quit selection.
If you enter more than one number, separate the numbers by a comma or a space.

Type your selections here:  1

The following products will be installed:

Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00

Are your selections correct [ 1=Yes, 2=No ; default is “1” ] ? 1

… installing “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Monitoring Server support”; please wait.

=> installed “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Monitoring Server support”.
… Initializing component Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Monitoring Server support.
… Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Tivoli Enterprise Monitoring Server support initialized.

Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is “2” ] ?
… postprocessing; please wait.
… running /app/IBM/ITM/lx8266/cq/bin/helpmerg.sh
… finished postprocessing.
Installation step complete.

Following Tivoli Enterprise Monitoring Server product support were installed:
*) Monitoring Agent for Tivoli Netcool/OMNIbus

Note: This operation causes the monitoring server to restart.
Do you want to seed product support on the Tivoli Enterprise Monitoring Server? [ 1=Yes, 2=No ; default is “1” ] ?
Starting TEMS…
TEMS started…

The following new Tivoli Enterprise Monitoring Server product support packages will be seeded:
*) Monitoring Agent for Tivoli Netcool/OMNIbus

Choose one of the following options to add or update the situation distribution definition to include the default managed system groups:

1) ALL – This option adds the default managed system groups to all the applicable situations. Note that not all situations have the default managed group setting. For some, you might need to manually define the distribution in the Tivoli Enterprise Portal due to the specific content of the agent support package.
2) NONE – The default managed system group is not added to any situation.

Type your selections here [ number “1” or “ALL” is default ]:
1

Seeding support for Monitoring Agent for Tivoli Netcool/OMNIbus [1 of 1]
Product support seeding completed…
Stopping TEMS…
TEMS stopped…
All supports successfully seeded.

As a reminder, you should install product support on each of your TEM servers for any agents you have just installed.
This is done via the “/app/IBM/ITM/bin/itmcmd support” command on your TEM servers.

You may now configure any locally installed IBM Tivoli Monitoring product via the “/app/IBM/ITM/bin/itmcmd config” command.

insserv: warning: current start runlevel(s) (3 5) of script `vboxadd-x11′ overwrites defaults (empty).
insserv: Service network is missed in the runlevels 4 to use service ctrmc
insserv: Service syslog is missed in the runlevels 4 to use service ctrmc

Starting TEMS…
It can take up to ten minutes.
TEMS started…
Processing. Please wait…
Starting Tivoli Enterprise Monitoring Automation Server …
Tivoli Enterprise Monitoring Automation Server started
Processing. Please wait…
Starting IBM Eclipse Help Server …
IBM Eclipse Help Server started
Processing. Please wait…
Starting Tivoli Enterprise Portal Server …
Eclipse Help Server is required by Tivoli Enterprise Portal Server (TEPS) and will be started…
Eclipse Help Server is already started.
Tivoli Enterprise Portal Server started
Processing. Please wait…
Starting Warehouse Proxy …
Warehouse Proxy started
Processing. Please wait…
Starting Summarization and Pruning Agent …
Summarization and Pruning Agent started
Processing. Please wait…
Starting Monitoring Agent for Linux OS …
Monitoring Agent for Linux OS started

Reconfigure teps to complete the product support installation. Start the Manage Tivoli Enterprise Monitoring services console on the ITM server using the $CANDLEDIR/bin/itmcmd manage & command then right click Tivoli Enterprise Portal Server and select Configure from the drop down menu.

reconfigure-tepsTEPS will have to be stopped during configuration.reconfigure-teps-stopClick OK at the next popup window.

reconfigure-teps-common-event-console-configurationClick Save at the next window. Basically you do not want to change any parameters here, only want to reconfiguration to run and detect and include the new product support jar files. This procedure could take quite a while, so be patient.

reconfigure-teps-saveOnce the configuration is done, click Yes to start the TEPS server.

reconfigure-teps-start

Installing the IBM Tivoli Monitoring Agent for Netcool/Omnibus 8.1.

Start the monitoring agent installation on your omnibus server using install.sh

HUOMNIBUS001-P1:/Downloads/TIVOLI-IMAGES/OMNIBUS8-PACK/agent # ./install.sh
INSTALL

Enter the name of the IBM Tivoli Monitoring directory
[ default = /opt/IBM/ITM ]: /app/IBM/ITM

ITM home directory “/app/IBM/ITM” already exists.
OK to use it [ 1-yes, 2-no; “1” is default ]?

The following processes are currently running:

Product = Monitoring Agent for Linux OS  PID = 3773
install.sh warning: Existing products found to be running will be restarted during installation., continuing …

Continue with this installation [ 1-yes, 2-no; “1” is default ]?  1
Processing. Please wait…
Stopping Watchdog process…
Watchdog process was stopped.
Stopping Monitoring Agent for Linux OS …
Product Monitoring Agent for Linux OS was stopped gracefully.
Agent stopped…
/app/IBM/ITM

Select one of the following:

1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding
4) Exit install.

Please enter a valid number:  1

Initializing …
International Program License Agreement

Part 1 – General Terms

BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR USING
THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF
YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON
OR A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT AND
WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON,
COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO NOT
AGREE TO THESE TERMS,

– DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE
PROGRAM; AND

Press Enter to continue viewing the license agreement, or
enter “1” to accept the agreement, “2” to decline it, “3”
to print it, “4” to read non-IBM terms, or “99” to go back
to the previous screen.
1

Product packages are available in /Downloads/TIVOLI-IMAGES/OMNIBUS8-PACK/agent/unix

The following products are currently installed in “/app/IBM/ITM”:

IBM GSKit Security Interface V08.00.50.20 @ Linux x86_64 R2.6, R3.0 (64 bit)
Monitoring Agent for Linux OS V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)
Tivoli Enterprise Services User Interface V06.30.04.00 @ Linux x86_64 R2.6, R3.0 (64 bit)

All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents.

Product packages are available for this operating system and component support categories:

 1) IBM Tivoli Monitoring components for this operating system
 2) Tivoli Enterprise Portal Browser Client support
 3) Tivoli Enterprise Portal Desktop Client support
 4) Tivoli Enterprise Portal Server support
 5) Tivoli Enterprise Monitoring Server support
 6) Other operating systems

Type the number or type “q” to quit selection
[ number “1” or “IBM Tivoli Monitoring components for this operating system” is default ]:  1

You selected number “1” or “IBM Tivoli Monitoring components for this operating system”

Is the selection correct [ 1=Yes, 2=No ; default is “1” ] ? 1

The following products are available for installation:

1) Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00
2) all of the above

Type the numbers that correspond to the products that you want to install. Type “b” to change operating system, or type “q” to quit selection.
If you enter more than one number, separate the numbers by a comma or a space.

Type your selections here:  1

The following products will be installed:

  Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00

Are your selections correct [ 1=Yes, 2=No ; default is “1” ] ? 1

Do you want to check prerequisites for the above components? [ 1=Yes, 2=No ; default is “1” ] ? 1
Running Prerequisite Scanner.
This may take a few minutes depending on the number of components being checked and the machine’s performance.
Prerequisite Scanner results for the selected components:
NOT AVAILABLE    Monitoring Agent for Tivoli Netcool/OMNIbus        /app/IBM/ITM/logs/prereqscan/20150126-113643/COMMON/result.txt
NOT AVAILABLE    Tivoli Enterprise-supplied JRE        /app/IBM/ITM/logs/prereqscan/20150126-113643/COMMON/result.txt
NOT AVAILABLE    IBM Tivoli Monitoring Shared Libraries        /app/IBM/ITM/logs/prereqscan/20150126-113643/COMMON/result.txt
NOT AVAILABLE    IBM GSKit Security Interface        /app/IBM/ITM/logs/prereqscan/20150126-113643/COMMON/result.txt

PASS    Prerequisite Scanner Overall Result        /app/IBM/ITM/logs/prereqscan/20150126-113643/COMMON/result.txt

Do you want to continue with the installation [ 1=Yes, 2=No ; default is “1” ] ? 1

… installing “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Linux x86_64 R2.6, R3.0 (64 bit)”; please wait.

=> installed “Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Linux x86_64 R2.6, R3.0 (64 bit)”.
… Initializing component Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Linux x86_64 R2.6, R3.0 (64 bit).
… Monitoring Agent for Tivoli Netcool/OMNIbus  V07.40.00.00 for Linux x86_64 R2.6, R3.0 (64 bit) initialized.

Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is “2” ] ?
… postprocessing; please wait.
… finished postprocessing.
Installation step complete.

As a reminder, you should install product support on each of your TEM servers for any agents you have just installed.
This is done via the “/app/IBM/ITM/bin/itmcmd support” command on your TEM servers.

You may now configure any locally installed IBM Tivoli Monitoring product via the “/app/IBM/ITM/bin/itmcmd config” command.

insserv: warning: current start runlevel(s) (3 5) of script `vboxadd-x11′ overwrites defaults (empty).
insserv: Service network is missed in the runlevels 4 to use service ctrmc
insserv: Service syslog is missed in the runlevels 4 to use service ctrmc

Processing. Please wait…
Starting Monitoring Agent for Linux OS ..

To complete the agent installation the itm_os.sql file will have to be run by omnibus to apply the necessary modifications on the Omnibus database. In our case this file was located in:

/app/IBM/ITM/lx8266/no/bin

So we executed the following command:

HUOMNIBUS001-P1:/app/IBM/ITM/lx8266/no/bin # /app/IBM/tivoli/netcool/omnibus/bin/nco_sql -user root -S NCOMS -P ****** < /app/IBM/ITM/lx8266/no/bin/itm_os.sql
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)

Configuring the IBM Tivoli Monitoring Agent for Netcool/Omnibus 8.1.

Start the Manage Tivoli Enterprise Monitoring services console on the Omnibus server using the $CANDLEDIR/bin/itmcmd manage & command then right click on Tivoli Monitoring Agent for Netcool/Omnibus and select Configure from the drop down menu.

omnibus-itm-agent-configureSpecify the log directory of the installed Netcool Omnibus 8.1 Server.

omnibus-itm-agent-configure-log-directoryThen specify the name of the running objectserver. We used the default objectserver name which is NCOMS. Click OK to continute to the second configuration step.

omnibus-itm-agent-configure-objectserverSpecify the name of the TEMS or RTEMS where you want to get your agent connected to, then click save.

omnibus-itm-agent-CONNECTION

Right click on the monitoring agent, then select Start Service to start the monitoring agent.

omnibus-itm-agent-startAfter a few seconds the agent should be popping up on your TEPS console like this:

teps-omnibus-agent

 

Step by Step Installing & Configuring Netcool/OMNIbus EIF probe for Omnibus 8.1

This article will describe, how to install and configure the Netcool/OMNIbus EIF probe that comes with the 8.1 version of Netcool/OMNIbus. As usual we will use SLES 11 SP3 as host OS.

Netcool/OMNIbus 8 Plus Probe for Tivoli EIF provides the capability to capture events sent from ITM and forward them onto the Omnibus console. It is not to be confused with IBM Tivoli Netcool/OMNIbus Gateway for Tivoli EIF which is used to forward events from IBM Tivoli Netcool/OMNIbus to applications that accept events in EIF format.

First locate the Netcool/OMNIbus 8 Plus Probe for Tivoli EIF (nco-p-tivoli-eif 13_0) Multiplatform English (CN1FVEN ) package on Passport Advantage, if you do not have it downloaded already. Make sure that you download the one that is coming with the 8.1 version of Omnibus.

Installing Netcool/OMNIbus 8 Plus Probe for Tivoli EIF

From version 8.1 probe installation is being done using the IBM Installation Manager not with the nco_install_integration utility.

Start the IBM Installation Manager using the IBMIM command. Usually this is located in /opt/IBM/InstallationManager/eclipse directory. Once started go to File-> Preferences.

IBM_Installation_Manager_propertiesSelect Add repository. Specify the location of the repository.config file in the EIF probe image directory. This will add that location to the repository list.

IBM_Installation_Manager_add_repositoryClick install on the main screen to start the installation.

IBM_Installation_Install_startingSelect Netcool/Omnibus Probe nco-p-tivoli-eif then click next.

IBM_Installation_Install_select_packageAccept the License agreement, then click next at the Install packages window. If your prerequisites are not met you will see a list of missing package groups.

IBM_Installation_Install_Install_packagesConfirm the installation package by clicking next and the following window.

IBM_Installation_Install_confirmClick Install to start the installation at the next window.

IBM_Installation_Install_buttonIf everything goes fine your installation should now be done.

IBM_Installation_finish

Installing the Situation Update Forwarder

The Situation Update Forwarder is located on the IBM Tivoli Monitoring tools CD, the latest version can be downloaded from fixcentral. In this example I am using the the tools package from ITM 6.3 Fixpack 4:

  • 6.3.0-TIV-ITM_TMV-Tools-FP0004

After unpacking the image the installation can be started using the ESync3000Linux.bin command.

Situation_update_forwarder_welcomeAfter accepting the License Agreement select the installation location of the Situation Update Forwarder the click Next.

Situation_update_forwarder_select_install_locationLeave the setting on default in the following window then click Next.

Situation_update_forwarder_settingsAdd the login credentials for your ITM server in the next pane. Remember situation update forwarder changes events on TEP once they are modified on the Omnibus console, however if you change ( acknowledge for example ) an event in ITM. The change will not be synchronized into Omnibus.

Situation_update_forwarder_itm_settings Click Next at the following pane and the installation starts immediately. If everything goes fine you should see the following window:

Situation_update_forwarder_finish

Execute Situation Update Forwarder SQL scripts on Omnibus

Situation Update Forwarder SQL scripts are used update the Omnibus DB Schema.This will create the required DB modifications by the Netcool/OMNIbus 8 Plus Probe for Tivoli EIF.

Apply the SQL files located in the Situation Event Forwarder’s omnibus directory in following order:

$OMNIHOME/bin/nco_sql -user root -password ******* -server NCOMS < ./itm_proc.sql
$OMNIHOME/bin/nco_sql -user root -password ******* -server NCOMS < ./itm_db_update.sql
$OMNIHOME/bin/nco_sql -user root -password ******* -server NCOMS < ./itm_sync.sql

HUOMNIBUS001-P1:/app/IBM/SitForwarder/omnibus # $OMNIHOME/bin/nco_sql -user root -password ********* -server NCOMS < ./itm_proc.sql
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
HUOMNIBUS001-P1:/app/IBM/SitForwarder/omnibus # $OMNIHOME/bin/nco_sql -user root -password ********* -server NCOMS < ./itm_db_update.sql
ERROR=Object exists on line 48 of statement
‘—————————————————————-…’, at or
near ‘TECHostname’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
TECFQHostname varchar(64);…’, at or near ‘TECFQHostname’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
TECDate varchar(64);…’, at or near ‘TECDate’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
TECRepeatCount int;…’, at or near ‘TECRepeatCount’
ERROR=Object exists on line 7 of statement
‘—————————————————————–…’, at or
near ‘ITMStatus’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMDisplayItem varchar(128);…’, at or near ‘ITMDisplayItem’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMEventData varchar(3096);…’, at or near ‘ITMEventData’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMTime varchar(23);…’, at or near ‘ITMTime’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMHostname varchar(64);…’, at or near ‘ITMHostname’
ERROR=Object exists on line 3 of statement ‘alter table alerts.status add column
ITMPort varchar(64);…’, at or near ‘ITMPort’
ERROR=Object exists on line 3 of statement ‘alter table alerts.status add column
ITMIntType varchar(1);…’, at or near ‘ITMIntType’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMResetFlag varchar(1);…’, at or near ‘ITMResetFlag’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMSitType varchar(1);…’, at or near ‘ITMSitType’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMThruNode varchar(64);…’, at or near ‘ITMThruNode’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMSitGroup varchar(1284);…’, at or near ‘ITMSitGroup’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMSitFullName varchar(256);…’, at or near ‘ITMSitFullName’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMApplLabel varchar(8);…’, at or near ‘ITMApplLabel’
ERROR=Object exists on line 2 of statement ‘alter table alerts.status add column
ITMSitOrigin varchar(32);…’, at or near ‘ITMSitOrigin’
ERROR=Attempt to insert duplicate row on line 8 of statement
‘——————————————————————…’
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
ERROR=Object not found on line 9 of statement
‘——————————————————————…’, at or
near ‘thrunode_change_handler’
(0 rows affected)
(0 rows affected)
HUOMNIBUS001-P1:/app/IBM/SitForwarder/omnibus # $OMNIHOME/bin/nco_sql -user root -password ********* -server NCOMS < ./itm_sync.sql
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)

Configuring Netcool/OMNIbus 8 Plus Probe for Tivoli EIF

  • Copy the itm_event.rules file from the omnibus directory of the Situation Update Forwarder installation location to $OMNIHOME/probes/linux2x86/
  • Uncomment the itm_event.rules include definition in tivoli_eif.rules
    located in $OMNIHOME/probes/linux2x86

# This is the generic ITM situation handling. This may get modified if
# later include files are used. Must be included if the predictive or
# virtualization include lines are

include “itm_event.rules”

Make Netcool/OMNIbus 8 Plus Probe for Tivoli EIF start with Process Agent ( PA )

What is Process Control System and Process Agent?

“The process control system runs external procedures that are specified in automations. Automations detect changes in the ObjectServer and run automated responses to those changes. It also manages local and remote processes. Use process control to configure remote processes in order to simplify the management of Tivoli Netcool/OMNIbus components such as ObjectServers, probes, and gateways. The process control system consists of Process agents, which are programs installed on each host for managing processesand  A set of command-line utilities that provide an interface to process management.”

We use this to manage every probe / gateway running on our Omnibus server. Repeat the following steps to configure the Process Agent to manage Netcool/OMNIbus 8 Plus Probe for Tivoli EIF:

Start the Administration Console using the nco_config command in $OMNIHOME/bin/

netcool_process_agent_gui

Log in to your process agent using the OS user id and password.

netcool_process_agent_login

Click on New process from the drop down menu after right clicking on Core:

process_agent_create_processDefine the location of the nco_p_tivoli_eif executable, then click OK.

starting_process_process_agent

Start the nco_p_tivoli_eif process using the drop down menu.

process_agent_start_probeIf everything was configured properly you should see something similar.

process_agent_started_probe

Start the Situation Update Forwarder

If you would like to have synchronization between TEP and Omnibus you can run the Situation Update Forwarder. It is important to point out that this is not required for proper event forwarding from ITM to Omnibus, only required if you would like to have your changes done on Omnibus to be synched down to TEP. You can run SUF with the following command:

../SitForwarder/bin/StartSUF.sh

 

 

Configuring Netcool Omnibus 7.4 on SLES 11

Please note that this is NOT a detailed installation information just made notes to myself not to forget how I got this sorted 🙂

1: Install the product from the provided media

2: Create the object server by running the following command

sudo ./nco_dbinit

This will create the default object sever NCOMS.

3: Edit the omni.dat file

The omni.dat file has to be edited. The defined “omnihost” hostname has to be replaced with the server’s hostname. This file is located at ./netcool/etc/ directory NOT in ./netcool/omnibus/etc directory. The replacable sections are highlighted below:

#
# omni.dat file as prototype for interfaces file
#
# Ident: $Id: omni.dat 1.5 1999/07/13 09:34:20 chris Development $
#
[NCOMS]
{
Primary: omnihost 4100
}
[NCO_GATE]
{
Primary: omnihost 4300
}
[NCO_PA]
{
Primary: omnihost 4200
}
[NCO_PROXY]
{
Primary: omnihost 4400
}

4: Create the interfaces with nco_igen or nco_xgen command. This will generate the interface file in ./netcool/etc using the data provided in omni.dat

-rw-rw-r– 1 root root 3928 Mar 14 10:06 tds.dat
drwxrwxr-x 3 root root 4096 Mar 14 10:07 security
drwxrwxr-x 2 root root 4096 Mar 14 10:08 default
-rw-r–r– 1 root root    0 Mar 14 15:13 interfaces
-rw-rw-r– 1 root root  283 Mar 14 15:21 omni.dat
-rw-r–r– 1 root root  664 Mar 14 15:23 interfaces.linux2x86

5: Create group ncoadmin and add administrative users to that group. Only users belonging to this group can execute process control commands.

6: Define ncoadmin as admin group using  ./nco_pad -admingroup ncoadmin command

8: Define IDUC port. This will fix the IDUC port to any specified port number. If this is not done a random available port will be used. Add the following line to /etc/services

nco_NCOMS 3832/tcp

7: Make Omnibus server PA ware by adding the hostname at ./netcool/omnibus/etc/nco_pa.conf

nco_process ‘MasterObjectServer’
{
Command ‘$OMNIHOME/bin/nco_objserv -name NCOMS -pa NCO_PA’ run as 0
Host            =       ‘yourhostname
Managed         =       True
RestartMsg      =       ‘${NAME} running as ${EUID} has been restored on ${HOST}.’
AlertMsg        =       ‘${NAME} running as ${EUID} has died on ${HOST}.’
RetryCount      =       0
ProcessType     =       PaPA_AWARE
}

8: Start process control in ./netcool/omnibus/bin/

./nco_pad -name NCO_PA

9. Start omnibus server

./netcool/omnibus/bin/nco_pa_start -process MasterObjectServer

10. Check status of Omnibus Server

./netcool/omnibus/bin # ./nco_pa_status
Login Password:
——————————————————————————-
Service Name         Process Name         Hostname   User      Status      PID
——————————————————————————-
Core                 MasterObjectServer   omnihost   root      RUNNING   12830
——————————————————————————-