IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Installation and configuration > Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Update the OMNIbus database schema on single-tier or aggregation tier ObjectServers

Update the Netcool/OMNIbus ObjectServer with the attributes and triggers that allow the ObjectServer to correctly process IBM Tivoli Monitoring events and forward events to the IBM Tivoli Monitoring Situation Update Forwarder when using bidirectional communication.

To verify if specific customization settings are needed, see Customize how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers.

Perform the steps in this section for each ObjectServer in a single-tier architecture or for each ObjectServer in the aggregation tier of a multitier architecture.

The tasks in this section should be completed by the Netcool/OMNIbus Administrator.

If you are setting up a unidirectional architecture and have installed the IBM Tivoli Monitoring Event Synchronization Component on a system other than your Netcool/OMNIbus ObjectServer, you must manually copy the SQL files to your ObjectServer. The files are located in the event_sync_install_dir/omnibus directory. Also, for a unidirectional architecture, you must modify the contents of the itm_proc.sql file, changing every instance of the word REJECT to the word ACCEPT and ensure that the path specified for the itmfile variable exists on the system with Netcool/OMNIbus ObjectServer. You only need to load the itm_proc.sql and itm_db_update.sql files. If you later decide to convert your environment to a bidirectional architecture, you must also load the itm_sync.sql file.

If you are setting up a bidirectional architecture, you might want to customize the itm_proc.sql file before loading it. See Customize how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers. Also review the information at the end of the topic about ensuring that the eventcmd procedure is correctly configured to send events back to the hub monitoring server.

If you are integrating IBM Tivoli Monitoring and Tivoli Business Service Manager, you must also complete the following steps:

  1. If you are using Tivoli Business Service Manager V4.2.1, add the Tivoli Business Service Manager schema updates before you add the Tivoli Monitoring schema updates. If you add the Tivoli Monitoring schema updates before the Tivoli Business Service Manager schema updates, rerun the procedure in this section to add the IBM Tivoli Monitoring schema updates again to ensure that the latest definitions are used.

  2. After updating the OMNIbus schema with the Tivoli Monitoring updates, run the Tivoli Business Service Manager discover schema utility (rad_discover_schema). See the Tivoli Business Service Manager Information Center for detailed instructions on using this utility: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.tivoli.itbsm.doc/welcome.htm.

  3. After running the discover schema utility, remember to restart the Tivoli Business Service Manager Dataserver. Failure to do so can cause connection problems.

If the OMNIbus ObjectServer is running on a UNIX system as a non-root user and the event synchronization component is installed and run as either root or another user, verify that the user under which the ObjectServer is running has write permission to the event_sync_install_dir/log directory before updating the OMNIbus database schema. If the user does not have write permission to this directory there will be error messages related to itmfile when the itm_proc.sql file is loaded into Netcool/OMNIbus and ITM-OMNIbus event synchronization will not work.

The command to configure OMNIbus pipes the SQL command set into the SQL command-line tool and performs the updates to the ObjectServer.

  1. Update the Object Server database with the following commands: 

      • type path_to_file\itm_proc.sql | %OMNIHOME%\..\bin\redist\isql -U username 
-P password 
-S server_name

type path_to_file\itm_db_update.sql | %OMNIHOME%\..\bin\redist\isql -U username
-P password
-S server_name

      Only run this command if you are using the bidirectional architecture: 

        type path_to_file\itm_sync.sql | %OMNIHOME%\..\bin\redist\isql -U username 
-P password 
-S server_name

      Only run this command if you are using the bidirectional architecture: 

        type path_to_file\itm_event_cache.sql  | %OMNIHOME%\..\bin\redist\isql -U username 
-P password 
-S server_name

      where:

      $OMNIHOME

      Is the system-defined variable defining the installation location of OMNIbus.

      username

      Is the OMNIbus Object Server user name.

      password

      Is the OMNIbus Object Server password.

      server_name

      Is the OMNIbus Object Server name defined for process control.

      path_to_file

      Is the fully qualified path to the specified SQL file.

      • $OMNIHOME/bin/nco_sql -user username
    -password password
    -server server_name
    < path_to_file/itm_proc.sql

$OMNIHOME/bin/nco_sql -user username
    -password password
    -server server_name
    < path_to_file/itm_db_update.sql

      Only run this command if you are using the bidirectional architecture: 

        $OMNIHOME/bin/nco_sql -user username
    -password password
    -server server_name
    < path_to_file/itm_sync.sql

      Only run this command if you are using the bidirectional architecture: 

        $OMNIHOME/bin/nco_sql -user username
    -password password
    -server server_name
    < path_to_file/itm_event_cache.sql

      where:

      $OMNIHOME

      Is the system-defined variable defining the installation location of OMNIbus.

      username

      Is the OMNIbus ObjectServer user name.

      password

      Is the OMNIbus ObjectServer password.

      server_name

      Is the OMNIbus ObjectServer name defined for process control.

      path_to_file

      Is the fully qualified path to the specified SQL file. The SQL files are located in the event_sync_install_dir/omnibus directory where event_sync_install_dir is the location where the IBM Tivoli Monitoring Event Synchronization component is installed.

  1. "Object exists" and "Attempt to insert duplicate row" errors occur if the scripts were previously run. These errors are harmless.

  2. If you are running the SQL database schema for the first time, the following harmless error messages are displayed:

    • ERROR=Object not found on line 4 of statement "-- A workspace table for the ITM event clear automation...", at or near "itm_event_clear".

    • ERROR=Object not found on line 1 of statement "delete from alerts.itm_problem_events;...", at or near "itm_problem_events".

    • ERROR=Object not found on line 1 of statement "drop table alerts.itm_problem_events;...", at or near "itm_problem_events".


Parent topic:

Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers

+

Search Tips   |   Advanced Search