Architecture

Exception management within IBM® InfoSphere® Information Server collects data quality issues in a unified way, either as data is processed within data integration or cleansing jobs, or during data rule analysis that might be executed by subject matter experts.

The following scenario shows the relationship between the exception management components (IBM Stewardship Center, Data Quality Exception Console, and the Exception Management Dashboard in IBM InfoSphere Information Governance Dashboard), the Subscription Manager, the event services, and the components of InfoSphere Information Server.

A typical exception management scenario consists of the following phases:
  1. A job developer or data analyst identifies or creates a job or process that might generate exceptions and runs it.
  2. Exception records that are generated by IBM InfoSphere DataStage® and QualityStage® are stored in the exceptions database. Exception records that are generated by IBM InfoSphere Information Analyzer are stored in the analysis database. The additional details about the exception records that were generated are in exception sets, which are stored in the metadata repository.
  3. If an administrator configured InfoSphere Information Governance Dashboard for exception management reporting, information about exception sets in the metadata repository can read by InfoSphere Information Governance Dashboard and displayed in exception management reports in the Exception Management Dashboard workspace.
  4. When exceptions are generated, an exception event is created. An event service sends a notification of the exception event to Data Quality Exception Console and the exceptions are displayed there.
  5. After the exception sets arrive in Data Quality Exception Console, data stewards, data steward managers, and business stewards can browse and monitor them. Data stewards and data steward managers are also able to click View Details to see additional information associated with the exception set, as well as the individual records contained in the exception set. Data steward managers can manage the priority of exception sets from Data Quality Exception Console.
  6. A data steward manager selects an exception set that is displayed in Data Quality Exception Console and clicks Manage to send those exception sets and all subsequent exception sets that meet the same filter conditions to IBM Stewardship Center. Filter conditions might be projectName or applicationType. An event service is notified and sends the exception sets and corresponding exception records to IBM Stewardship Center. The exception sets can be managed by using Data Quality Exception sample process application in IBM Stewardship Center, or by using your own custom process application in IBM Stewardship Center.
  7. If a data steward manager wants to stop future exception sets that meet the same filter conditions from being sent to IBM Stewardship Center, the data steward manager clicks Monitor. Future exception sets that are generated with those filter conditions continue to appear in the Data Quality Exception Console and can be monitored there, but they are not sent to IBM Stewardship Center.
  8. If a data steward manager wants to prevent exception sets that meet certain filter conditions from appearing in the Data Quality Exception Console, the data steward manager uses Subscription Manager to delete the original subscription. The data steward manager creates a new subscription with different filter conditions.