Creating and customizing the InfoSphere Information Governance Dashboard configuration tables

IBM® InfoSphere® Information Governance Dashboard stores translation mappings, threshold values, and connection information in configuration tables. You must create these configuration tables before running any of the reports.

Before you begin

If a prior version of InfoSphere Information Governance Dashboard is installed, complete the following steps to prepare for the new configuration tables:
  1. Make a note of the current values for the XXX_URL parameters (where XXX is IGC, SMC, DQEC, and STC) so you can refer to these values when you set up the configuration tables.
  2. Run the script DropIGDConfigTables.sql, which is in the folder Information_Server_Home/Clients/InformationGovernanceDashboard/setup/configuration, to drop the current configuration tables.

About this task

IBM InfoSphere Information Governance Dashboard accesses configuration data to provide content that is adapted to the environment in which you use InfoSphere Information Governance Dashboard. This configuration data is stored in two tables, MSG_LIB and SETUP_PARAMETER. The tables store the following information:
  • Mappings of report labels to translations of that descriptive text for specific locales
  • Connection information that links report content with other client applications such as IBM InfoSphere Information Governance Catalog
  • Threshold values that are used in reports to highlight success and failure rates for runs of data rules
The configuration tables are created in the metadata repository and populated with sample content based on SQL scripts. The following four scripts are used to create and populate configuration tables:
CreateIGDConfigTables_DB2.sql
Creates configuration tables on a DB2 database.
CreateIGDConfigTables_ORA.sql
Creates configuration tables on an Oracle database.
CreateIGDConfigTables_MSSQL.sql
Creates configuration tables on a Microsoft SQL Server database.
PopulateIGDConfigTables.sql
Populates the configuration tables with data. This script is database independent.

To drop configuration tables, use the script DropIGDConfigTables.sql. This script is database independent.

Procedure

  1. Copy the SQL file PopulateIGDConfigTables.sql from Information_Server_Home/Clients/InformationGovernanceDashboard/setup/configuration to a temporary location.
  2. Open the SQL file in a text editor.
    The file contains lines that include parameter name and parameter value pairs. For example: INSERT INTO IGDCONFG.SETUP_PARAMETER VALUES ('<parameter name>','<parameter value>');.
  3. Edit the SQL file by updating URL parameter values according to which components you plan to use. To ensure proper linkage to the URLs, see Configuring Cognos Application Firewall to accept URLs.
    1. Replace the string <parameter value> for the parameter IGC_URL with the URL for opening IBM InfoSphere Information Governance Catalog.
      For example, if you access InfoSphere Information Governance Catalog on host1.mycompany.com by using port 9443, the entry becomes: 
      INSERT INTO IGDCONFG.SETUP_PARAMETER VALUES ('IGC_URL','https://host1.mycompany.com:9443/ibm/iis/igc/')
    2. To add a button to the Data Rules Details page that you can use to enable data rules for exception management, replace the string <parameter value> for the parameter SMC_URL with the URL for opening the Subscription Manager UI.
      Data rules that are enabled for exception management feed the exception set dimensions that the exception management metrics are based on.
      For example, if you access the Subscription Manager UI on host2.mycompany.com by using port 9443, the entry becomes:
      INSERT INTO IGDCONFG.SETUP_PARAMETER VALUES ('SMC_URL',
'https://host2.mycompany.com:9443/ibm/iis/events')
      Unless you are using a certificate authority, make sure the value of the SMC_URL parameter in the configuration table matches the URL that you use if you access the Subscription Manager with a browser. For example, if you log on to the Subscription Manager with a numeric IP address such as https://172.16.254.1/ibm/iis/events, the value of the SMC_URL parameter must be https://172.16.254.1/ibm/iis/events#subscriptions. If you use a symbolic IP address, it must match the symbolic IP address of your SMC_URL parameter value.
    3. To enable a link from the exception management reports to the Data Quality Exception Console, replace the string <parameter value> for the parameter DQEC_URL with the URL for opening the Data Quality Exception Console.
      For example, if you access the Data Quality Exception Console on host3.mycompany.com by using port 9443, the entry becomes:
      INSERT INTO IGDCONFG.SETUP_PARAMETER VALUES ('DQEC_URL',
'https://host3.mycompany.com:9443/ibm/iis/dqec')
    4. To enable a link from the exception management reports to the IBM Stewardship Center, replace the string <parameter value> for the parameter STC_URL with the URL for opening the IBM Stewardship Center.
      For example, if you access the IBM Stewardship Center on host4.mycompany.com by using port 9444, the entry might become:
      INSERT INTO IGDCONFG.SETUP_PARAMETER VALUES ('STC_URL',
'https://host4.mycompany.com:9444/ProcessPortal')
    5. If necessary, change the default thresholds for indicating failure and success rates for runs of data rules.
      These thresholds are used in some reports to give a quick indication of the status.
      Threshold name Default value
      GLOBAL_TARGET_UPPER_THRESHOLD 0.98
      GLOBAL_TARGET_LOWER_THRESHOLD 0.94
  4. For Oracle databases only, create the user igdconfg and assign it to the XMETA table space. Connect to the metadata repository as a user with administrative permissions (such as sysdba), and give the user igdconfg the required permissions to create and read tables.
  5. Create the schema IGDCONFG.
  6. Connect to the metadata repository as a user with sufficient privileges to create tables in the IGDCONFG schema. On a DB2 database, this user is xmeta. On an Oracle database, this user is igdconfg. In both cases, the user must be given permissions to create tables in the schema igdconfg and to insert values into them.
  7. Create the required tables and views by running the appropriate CreateIGDConfigTables_(database).sql script for your database.
  8. Populate the tables by running the PopulateIGDConfigTables.sql script.