1.2 Forwarding AppManager Events to Netcool

When an AppManager Knowledge Script job running on a managed client raises an event, the AppManager agent sends the event information to the management server. The management server then places the event in the AppManager repository.

The connector polls the AppManager repository at regular intervals for new events. When it finds an event that meets the category and severity criteria, the connector sends the event to the Netcool MTTRAPD probe on the ObjectServer computer. ObjectServers store and manage alert information. You can use the Netcool Event List that is present in the Netcool Suite program folder to view the events forwarded by the connector.

The first time an event is forwarded to Netcool, its count is displayed as one irrespective of the number of times the event has actually occurred. However, during the subsequent forwards, the correct count of the event is displayed.

Use the connector Configuration Utility to specify configuration options for Netcool. For more information about setting the AppManager repository polling interval, see Configuring AppManager Event Settings.

By default, the AppManager event updates are synchronized from AppManager to Netcool. However, the event updates are not visible in Netcool unless you configure the deduplication and deduplicate_details triggers.

Review the following sections:

1.2.1 Configuring the Deduplication Trigger

For the event updates to be visible in Netcool version 7.2.0 / 7.2.1 / 7.3.0 / 7.3.1, you must replace the default deduplication trigger.

To replace the default deduplication trigger:

  1. Start Administrator in the Netcool Suite program folder.

  2. In NETCOOL/OMNIbus Administrator, expand Reports.

  3. Click ObjectServers.

  4. Double-click the ObjectServer that handles AppManager events.

  5. In the ObjectServer Security dialog box, specify the credentials and click OK.

  6. Expand Automation and click Triggers.

  7. Double-click the deduplication trigger.

  8. In the Edit Database Trigger dialog box, click the Actions tab.

  9. Replace the existing SQL statement with the following:

    begin
            if(%user.app_name = 'PROBE')
            then
                if((old.LastOccurrence > new.LastOccurrence) or ((old.ProbeSubSecondId >= new.ProbeSubSecondId) and 
                                        (old.LastOccurrence = new.LastOccurrence)) and (new.Class!=40235))
                 then
                      cancel;
                 end if;
             end if;
    
             set old.Tally = old.Tally + 1;
             set old.LastOccurrence = new.LastOccurrence;
             set old.StateChange = getdate();
             set old.InternalLast = getdate();
             set old.Summary = new.Summary;
             set old.AlertKey = new.AlertKey;
             set old.ProbeSubSecondId = new.ProbeSubSecondId;
             if ((old.Severity = 0) and (new.Severity > 0))
             then
               set old.Severity = new.Severity;
             end if;
    end
  10. Click OK.

1.2.2 Configuring the Deduplicate_details Trigger

When the Collapse duplicate events into a single event option is enabled for a job, the Connector sends every occurrence of the duplicate event with an updated count and details to Netcool. If Save to Netcool Details option is selected to enable the connector to send AppManager event details to Netcool MTTRAPD probe, you cannot view the updated event details unless you modify the deduplicate_details trigger.

To replace the default deduplicate_details trigger:

  1. Start Administrator in the Netcool Suite program folder.

  2. In NETCOOL/OMNIbus Administrator, expand Reports.

  3. Click ObjectServers.

  4. Double-click the ObjectServer that handles AppManager events.

  5. In the ObjectServer Security dialog box, specify the credentials and click OK.

  6. Expand Automation and click Triggers.

  7. Double-click the deduplicate_details trigger.

  8. In the Edit Database Trigger dialog box, click the Actions tab.

  9. Replace the existing SQL statement with the following:

    declare flag bool;
    begin
    
    set flag = true;
    
    for each row srow in alerts.status where srow.Identifier = new.Identifier
    
    Begin
    if (srow.Class = 40235) then
    set flag = false;
    break;
    end if;
    end;
    
    if (flag=true) then
    cancel;
    end if;
    set old.Detail = new.Detail;
    end
  10. Click OK.