Installing scope-based event grouping

Scope-based event grouping is provided as an extension in Tivoli® Netcool®/OMNIbus. To use event grouping, you need to import the SQL file that contains the triggers into your existing ObjectServers, and then update the Gateway mapping and table replication files to propagate the new fields and tables.

To install scope-based event grouping:

1. Install the event grouping triggers into both your primary and backup Aggregation ObjectServers by running the following SQL file against both:

   In Fix Pack 4 and later:

   • $OMNIHOME/bin/nco_sql -server Primary Aggregation ObjectServer -user root -password password < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_aggregation.sql
   • $OMNIHOME/bin/nco_sql -server Backup Aggregation ObjectServer -user root -password password < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_aggregation.sql
   • "%OMNIHOME%\bin\isql" -S Primary Aggregation ObjectServer -U root -i %OMNIHOME%\extensions\eventgrouping\objectserver\scope_event_grouping_aggregation.sql
   • "%OMNIHOME%\bin\isql" -S Backup Aggregation ObjectServer -U root -i %OMNIHOME%\extensions\eventgrouping\objectserver\scope_event_grouping_aggregation.sql

   For example:

   $OMNIHOME/bin/nco_sql -server AGG_P -user root -password netcool < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_aggregation.sql

   Note: Ensure that you import the SQL file into both your primary and backup Aggregation ObjectServers. The triggers work only on the acting primary ObjectServer.

   You can remove the event grouping triggers by using the same procedure and running the $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_aggregation_remove.sql scripts.

   Note: In Fix Pack 3, the SQL commands are all in $OMNIHOME/extensions/eventgrouping and the SQL command for the Aggregation ObjectServers is ootb_event_grouping.sql

   If you remove the triggers, and then reinstall the triggers an error message displays, similar to the following error message. This error message is an informational message and is not a cause for concern. When you run the removal script, the script does not remove ParentIdentiifer and TTNumber from the alerts.status table because these fields can be referenced by other Object Server functions. Therefore, when you run the installation script for a second time the installation script is unable to create the fields as the fields exist. Instead, the error message displays but the scope-based event grouping functions work as designed.

   ERROR=Object exists on line 1 of statement 'ALTER TABLE alerts.status ADD
         COLUMNParentIdentifier VARCHAR(255);...', at or near
         'ParentIdentifier'ERROR=Object exists on line 1 of statement 
   'ALTER TABLE alerts.status
         ADD COLUMNTTNumber VARCHAR(64);...', at or near 'TTNumber'

2. Add the extra fields to the mapping file of your bidirectional Aggregation ObjectServer Gateway. Copy the contents of $OMNIHOME/extensions/eventgrouping/gateway/AGG_GATE.map.parts to $OMNIHOME/etc/AGG_GATE.map.
   Note: In Fix Pack 3, the mapping files are all in $OMNIHOME/extensions/eventgrouping.
3. Add the extra parts to the table replication file of your bidirectional Aggregation ObjectServer Gateway. Copy the contents of $OMNIHOME/extensions/eventgrouping/gateway/AGG_GATE.tblrep.def.parts to $OMNIHOME/etc/AGG_GATE.tblrep.def.
   Note: In Fix Pack 3, the mapping files are all in $OMNIHOME/extensions/eventgrouping.
4. Restart your Aggregation Gateway for the changes to take effect.
5. Optional: You can install scope-based event grouping in a tiered environment, into Collection and Display ObjectServers.

   For the Collection layer:

   1. If you have a tiered setup with Collection layers, install the event grouping triggers into both your primary and backup Collection ObjectServers by running the following SQL file against both:
      • $OMNIHOME/bin/nco_sql -server Primary Collection ObjectServer -user root -password password < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_collection.sql
      • $OMNIHOME/bin/nco_sql -server Backup Collection ObjectServer -user root -password password < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_collection.sql
      • "%OMNIHOME%\bin\isql" -S Primary Collection ObjectServer -U root -i %OMNIHOME%\extensions\eventgrouping\objectserver\scope_event_grouping_collection.sql
      • "%OMNIHOME%\bin\isql" -S Backup Collection ObjectServer -U root -i %OMNIHOME%\extensions\eventgrouping\objectserver\scope_event_grouping_collection.sql

      For example:

      $OMNIHOME/bin/nco_sql -server COL_P_1 -user root -password netcool < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_collection.sql

      $OMNIHOME/bin/nco_sql -server COL_B_1 -user root -password netcool < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_collection.sql

      You can remove the scope-based event grouping setup from the Collection layers by using the same procedure and running the $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_collection _remove.sql scripts.

   2. Add the extra fields to the mapping file of your unidirectional Collection-to-Aggregation ObjectServer Gateway. Copy the contents of $OMNIHOME/extensions/eventgrouping/gateway/C_TO_A_GATE.map.parts to $OMNIHOME/etc/C_TO_A_GATE.map.
   3. Restart your unidirectional Collection-to-Aggregation ObjectServer Gateways for the changes to take effect.

   For the Display layer:

   1. If you have a tiered setup with Display layers, install the event grouping triggers into both your Display ObjectServers by running the following SQL file against each:
      • $OMNIHOME/bin/nco_sql -server Display ObjectServer 1 -user root -password password < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_display.sql
      • $OMNIHOME/bin/nco_sql -server Display ObjectServer 2 -user root -password password < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_display.sql
      • "%OMNIHOME%\bin\isql" -S Display ObjectServer 1 -U root -i %OMNIHOME%\extensions\eventgrouping\objectserver\scope_event_grouping_display.sql
      • "%OMNIHOME%\bin\isql" -S Display ObjectServer 2 -U root -i %OMNIHOME%\extensions\eventgrouping\objectserver\scope_event_grouping_display.sql

      For example:

      $OMNIHOME/bin/nco_sql -server DIS_1 -user root -password netcool < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_display.sql

      $OMNIHOME/bin/nco_sql -server DIS_2 -user root -password netcool < $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_display.sql

      You can remove the scope-based event grouping setup from the Display layers by using the same procedure and running the $OMNIHOME/extensions/eventgrouping/objectserver/scope_event_grouping_display _remove.sql scripts.

   2. Add the extra fields to the mapping file of your unidirectional Aggregation-to-Display ObjectServer Gateway. Copy the contents of $OMNIHOME/extensions/eventgrouping/gateway/A_TO_D_GATE.map.parts to $OMNIHOME/etc/A_TO_D_GATE.map.
   3. Restart your unidirectional Aggregation-to-Display ObjectServer Gateways for the changes to take effect.
6. To visualize the grouping, open the Event Viewer and apply a View that uses the IBM Related Events relationship. Use the Edit Views button in the Event Viewer or use the Views editor, and select the Relationships tab, and then select IBM Related events from the drop-down menu.