Configuring Db2 database connection within Netcool/Impact

You can configure a connection to a valid Db2® database from within IBM® Tivoli® Netcool®/Impact.

Before you begin

In Netcool/Impact 7.1.0.13 and later releases, it is recommended to use the Event Analytics configuration wizard instead of the ./nci_trigger command to edit properties in the NOI Shared Configuration properties file. For more information, see Configuring Event Analytics using the wizard.

About this task

Users can run seasonality event reports and related event configurations, specifying the time range and name with Db2. Complete the following steps to configure the ObjectServer data source or data type.

Procedure

  1. Log in to the Netcool/Impact UI.
    https://impacthost:port/ibm/console
  2. Configure the ObjectServer data source and data type.
    1. In the Netcool/Impact UI, from the list of available projects, select the NOI project.
    2. Select the Data Model tab and select ObjectServerForNOI.
      1. Click Edit and enter information for <username>, <password>, <host name>, <port>.
      2. To save the Netcool/Impact data source, click Test Connection, followed by the Save icon.
    3. Edit the data type. Expand the data source and edit the data type to correspond to the ObjectServer event history database type.
      For example, AlertsForNOITable
    4. For Base Table, select <database table>.
    5. To update the schema and table, click Refresh and then click Save.
    6. Select the Data Model tab and select ObjectServerHistoryDb2ForNOI.
      1. Click Edit and enter information for <username>, <password>, <host name>, <port>.
      2. To save the Netcool/Impact data source, click Test Connection, followed by the Save icon.
    7. Edit the data type. Expand the ObjectServerHistoryDb2ForNOI data source and edit AlertsHistoryDb2Table.
    8. For Base Table, select <database name> and <database table name>
    9. To update the schema and table, click Refresh and then click Save.
    10. Select the Services tab and ensure that the following services are started.
      • ProcessRelatedEvents
      • ProcessSeasonalityEvents
      • ProcessRelatedEventConfig

  1. Configure the Db2 database connection within Netcool/Impact if it was previously configured for Oracle or MSSQL. The following steps configure the report generation to use the Db2 database. Export the default properties, change the default configuration, and update the properties.
    1. Generate a properties file, go to the <Impact install location>/bin directory to locate the nci_trigger, and run the following command from the command-line interface.
      nci_trigger <server> <username>/<password> NOI_DefaultValues_Export
       FILENAME directory/filename
      where
      <server>
      The server where Event Analytics is installed.
      <user name>
      The user name of the Event Analytics user.
      <password>
      The password of the Event Analytics user.
      directory
      The directory where the file is stored.
      filename
      The name of the properties file.
      For example:
      ./nci_trigger NCI impactadmin/impactpass NOI_DefaultValues_Export
       FILENAME /tmp/seasonality.props
    2. Update the properties file. Some property values are overwritten by the generated properties file, you might need to update other property values in the generated properties file. For a full list of effected properties, see Generated properties file.
      • If you do not have the following parameter values, update your properties file to reflect these parameter values.
        history_datasource_name=ObjectServerHistoryDb2ForNOI
        history_datatype_name=AlertsHistoryDb2Table
        history_database_table=<database table name>
        history_database_type=Db2
    3. Import the modified properties file into Netcool/Impact, enter the following command.
      nci_trigger <Server> <username>/<password> NOI_DefaultValues_Configure
       FILENAME directory/filename
      For example:
      ./nci_trigger NCI impactadmin/impactpass NOI_DefaultValues_Configure
       FILENAME /tmp/seasonality.props