Customizing which exception sets are sent to Data Quality Exception Console

You can control which exception sets are displayed in the Data Quality Exception Console.

Before you begin

To work with the subscription for NEW_EXCEPTIONS_EVENT, you must have the InfoSphere® Information Server Suite Administrator role.

About this task

By default, all exception sets generated by IBM® InfoSphere Information Server products and components are displayed in Data Quality Exception Console. However, you might have test jobs, sample jobs, or low priority jobs that generate exceptions that you do not want to include with the data that you are monitoring in Data Quality Exception Console. You customize which exception sets are sent to the Data Quality Exception Console by creating new subscriptions and filtering the exception sets by certain properties.

Procedure

  1. Open Subscription Manager.
  2. On the Subscriptions tab, delete the subscription to Data Quality Exception Console that is created by default. To identify this subscription, select it and confirm that it has the following properties:
    Table 1. Properties of the default subscription that enables all exceptions for exception management
    Subscription properties Values
    Name NEW_EXCEPTIONS_EVENT/<Unique_ID>, where <Unique_ID> is a unique identifier that is generated by the exception provider.
    Event type NEW_EXCEPTIONS_EVENT
    Creation date <SubMgrAndDataQuality_patch_run_date>
    Application Data Quality Exception Console
    Event filters None
  3. Create new subscriptions with event filters that specify which exception sets are sent to Data Quality Exception Console.
    1. Specify these values for the subscription.
      Table 2. Properties of a NEW_EXCEPTIONS_EVENT subscription
      Property Value
      Name A descriptive name for your subscription. For example, IA_rule_AgeCheckCustomer.
      Event Type NEW_EXCEPTIONS_EVENT
      Notification Type Application
      Application Data Quality Exception Console
    2. Specify values for the event filters for each subscription. You can filter by application, project, or a data rule in IBM InfoSphere Information Analyzer. You can use the following event filters.
      Table 3. Event filters to limit exception sets
      Event filters Valid values
      applicationType
      • Information Analyzer
      • Exception Stage

      Type the strings exactly as they appear here. The filter is case sensitive.
      projectName
      • IA_project_name
      • DS_project_name, for example, IOD_Bank_Demo
      .
      exceptionSummaryName
      • If you specify Information Analyzer for applicationType, specify the name of a data rule in the project.
      • If you specify Exception Stage for applicationType, specify the name of an exception descriptor in an Exceptions stage in the project.

      Your subscription includes selected event types that occur in any stage of any job of the specified project, where the stage contains an exception descriptor of the specified name. To limit the subscription to events from a single stage, define a unique name for the exception descriptor in that stage.

  4. To restore the default configuration so that all exception sets are sent, delete all subscriptions for the event type NEW_EXCEPTIONS_EVENT. Create a subscription that sends the exception sets. Do not specify filter properties for this subscription.

Example

A data steward manager wants to send only the following exception sets to Data Quality Exception Console for tracking and monitoring:
  • All exception sets that are generated by IBM InfoSphere DataStage® jobs
  • Exception sets that are generated by a specific data rule from InfoSphere Information Analyzer, for example IA_rule_AgeCheckCustomer.

On the Subscriptions tab of Subscription Manager, the administrator deletes the subscription to Data Quality Exception Console that is created by default.

Next, the administrator clicks Add, and then specifies details in the Add New Subscription window. The administrator selects NEW _EXCEPTIONS_EVENT as the event type, and then selects Application as the form of notification. The administrator selects the application Data Quality Exception Console to send notifications to Data Quality Exception Console. The administrator filters the events by using the applicationType property to specify Exception Stage. All exceptions that are generated by jobs are sent to Data Quality Exception Console and

Finally, the administrator creates another subscription with the same properties, and filters the events by using the exceptionSummaryName property to specify that the subscription is for only those exceptions from the data rule IA_rule_AgeCheckCustomer. With this configuration, exception sets that are generated by other data rules are ignored and are not sent to Data Quality Exception Console.

Parent topic: Configuring and managing exceptions in Data Quality Exception Console