IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Customize Event Integration
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Update the IBM Tivoli Monitoring Situation Forwarder to forward event status updates to additional monitoring servers
If you are using the bidirectional architecture and have multiple hub monitoring servers forwarding situation events to the same Netcool/OMNIbus ObjectServer, the IBM Tivoli Monitoring Situation Update Forwarder must be defined with the list of monitoring servers that it should send event status updates to.
When you install the IBM Tivoli Monitoring Event Synchronization Component and specify the IBM Tivoli Monitoring Situation Forwarder configuration parameters, you specify the SOAP URL of one hub monitoring server.
To add additional hub monitoring servers to the list that can receive event status updates from the Netcool/OMNIbus ObjectServer, issue the sitconfuser command as described in the following steps. Ensure the IBM Tivoli Monitoring Situation Update Forwarder is configured for both the fully qualified host name and the short host name of the hub monitoring server.
If you have configured the Hot Standby feature, you must configure the host name information for both the primary and secondary hub monitoring servers.
This task is performed on the system where the Netcool/OMNIbus ObjectServer and IBM Tivoli Monitoring Situation Update Forwarder are installed.
cd <event_sync_installdir>\bin
sitconfuser.cmd add serverid=server userid=user password=password pathc=path_to_conf_file type=OMNIBUSwhere:
Repeat this command to add short host name information for the same hub monitoring server by specifying the short host name value for the serverid parameter.
- <event_sync_installdir>
- Is the directory where the IBM Tivoli Monitoring event synchronization component is installed on your Netcool/OMNIbus ObjectServer system.
- server
- Is the fully qualified host name of the hub monitoring server.
- user
- Is the user ID used to access the computer where the hub monitoring server is running.
- password
- Is the password of the user ID specified by the user parameter.
- path_to_conf_file
- Is the directory containing the situser.conf file. By default, the situser.conf file is in the <event_sync_installdir>\etc directory.
- Change to the <event_sync_installdir>/bin directory and enter the following command:
sitconfuser.sh add serverid=server userid=user password=password pathc=path_to_conf_file type=OMNIBUS
where:
Repeat this command to add short host name information for the same monitoring server by specifying the short host name value for the serverid parameter.
- <event_sync_installdir>
- Is the directory where the IBM Tivoli Monitoring event synchronization component is installed on your Netcool/OMNIbus ObjectServer system.
- server
- Is the fully qualified host name of the monitoring server.
- user
- Is the user ID used to access the computer where the monitoring server is running.
- password
- Is the password of the user ID specified by the user parameter.
- path_to_conf_file
- Is the directory containing the situser.conf file. By default, the situser.conf file is in the <event_sync_installdir>/etc directory.
Repeat this step for each monitoring server that you want to add.
You can also delete monitoring servers, see the for the full syntax of this command.
After you change the configuration of the event synchronization, you must manually stop and restart the IBM Tivoli Monitoring Situation Update Forwarder process from the <event_sync_installdir>/bin directory. On Windows operating systems use stopSUF.cmd and startSUF.cmd. On UNIX operating systems use stopSUF.sh and startSUF.sh.
Parent topic:
Customize Event Integration