Configuring the ObjectServer

Prior to deploying rules based on related event events or patterns you must run SQL to update the ObjectServer. This SQL introduces relevant triggers into the ObjectServer to enable to rules to be fully functional.

1. Copy the SQL file IMPACT_HOME/add-ons/RelatedEvents/db/relatedevents_objectserver.sql from Netcool®/Impact into the tmp directory on your ObjectServer.
2. Run the SQL against your ObjectServer, enter the following command.
   • On Windows, enter the command %OMNIHOME%\..\bin\redist\isql -U <username> -P <password> -S <server_name> < C:\tmp\relatedevents_objectserver.sql
   • On Linux® and UNIX, enter the command $OMNIHOME/bin/nco_sql -user <username> -password <password> -server <server_name> < /tmp/relatedevents_objectserver.sql
3. If you have not previously configured the Event Analytics ObjectServer, you must enter the following command.
   • On Windows, enter the command %OMNIHOME%\..\bin\redist\isql -U <username> -P <password> -S <server_name> < C:\tmp\relatedevents_objectserver.sql
   • On Linux and UNIX, enter the command $OMNIHOME/bin/nco_sql -user <username> -password <password> -server <server_name> < /tmp/relatedevents_objectserver.sql
4. All users must run the SQL against your ObjectServer, enter the following command.
   • On Windows, enter the command %OMNIHOME%\..\bin\redist\isql -U <username> -P <password> -S <server_name> < C:\tmp\relatedevents_objectserver_update_fp5.sql
   • On Linux and UNIX, enter the command $OMNIHOME/bin/nco_sql -user <username> -password <password> -server <server_name> < /tmp/relatedevents_objectserver_update_fp5.sql
5. To ensure that Event Analytics functions correctly in an ObjectServer failover or failback configuration, you must perform this step.
   The following 3 Event Analytics services use the alerts.status field Serial when selecting events to process.

   • ProcessRelatedEvents
   • ProcessRelatedEventPatterns
   • ProcessSeasonalityEvents

   The problem with using the Serial field is that in a Netcool/OMNIbus failover configuration each ObjectServer has its own unique values for Serial. During failover and failback the query that is issued by Netcool/Impact can result in events not being read or the same events being read again. The Serial value used in the OMNIbusEventReader query does not consider the unique value Serial has for each ObjectServer instance. Following failover, when the ObjecServer fails back to the primary ObjectServer, it will be using a higher Serial value than what currently exists in the primary ObjectServer. Therefore, the service does not read events and does not trigger the SE_PROCESSEVENT policy.

   To resolve this problem, you must perform the configuration task described in the following topic: Netcool/Impact documentation: Managing the OMNIbusEventReader with an ObjectServer pair for New Events or Inserts.