Enabling scope-based event grouping

Scope-based grouping must be enabled on your on-premises ObjectServer in order for scope-based correlations to work on your hybrid deployment. Learn how to check whether scope-based grouping is enabled, and how to configure it if it is not enabled.

1. Check whether you already have scoping enabled on your on-premises ObjectServer. Run the following command.

   $OMNIHOME/bin/nco_sql -user username -password password -server server_name

   Where

   • username is the administrative user for the ObjectServer, usually root.
   • password is the password for the administrative user.
   • server_name is the name of your ObjectServer.
   Verify that:

   • A row is returned by the following query: select TriggerName from catalog.triggers where TriggerName='correlation_new_row';
   • The ScopeID field is present in the alerts.status table.
2. To enable scope-based grouping, use the following steps:
   1. Follow the instructions in this link: https://www.ibm.com/docs/en/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/task/omn_con_ext_installingscopebasedegrp.html
   2. Download the file legacy_scoping_procedures.sql from here.
   3. Run the downloaded SQL file on your primary ObjectServer to update the triggers.

      $OMNIHOME/bin/nco_sql -server servername -user username -password password < legacy_scoping_procedures.sql

      Where

      • username is the administrative user for the ObjectServer, usually root.
      • password is the password for the administrative user.
      • server_name is the name of your primary ObjectServer.
   4. Run the downloaded SQL file on your backup ObjectServer to update the triggers.

      $OMNIHOME/bin/nco_sql -server servername -username username -password password < legacy_scoping_procedures.sql

      Where

      • username is the administrative user for the ObjectServer, usually root.
      • password is the password for the administrative user.
      • server_name is the name of your backup ObjectServer.