Update the Netcool/Impact configuration

Edit the default values of the Netcool®/Impact derby database to configure launch-in-context support and integration with IBM® Runbook Automation.

Note: This information only applies to a hybrid deployment of Netcool Operations Insight®. For more information, see Installing on a hybrid architecture.

Netcool/Impact configuration for fully automated runbooks is stored in the Netcool/Impact derby database in the rbaconfig.defaults table with the exception of the RBAAPIKeyPassword.

The table contains the following default values:

Table 1. Default values of Netcool/Impact derby database
Default value	Description
`RBAHost=''`	Specify the hostname where the RBA service is running in your deployment. The hostname where the NOI service is running within the OCP cluster. For example, netcool.apps.mycluster.mycompany.com. Ensure that this hostname is included in the certificate (at least by wildcard in the certificate's subject alternative names, for example, *.apps.mycluster.mycompany.com). For more information, see Creating a custom certificate for Red Hat OpenShift.
`RBAManualExecHost=''`	`RBAManualExecHost=` is the same value as `RBAHost=`.
`RBAPort='443'`	No changes are required for RBA Application Port.
`RBAProtocol='https'`	No changes are required for RBA Application Protocol.
`RBARESTPath='/api/v1/rba/'`	No changes are required for RBA REST path.
`RBARESTPathToView='/api/v1/rba/'`	No changes are required for RBA API path.
`RBAAPIKeyName=''` `RBAAPIKeyPassword=''`	API key to access Runbook Automation from Netcool/Impact. Generate an appropriate API key by using the API Keys page. For more information, see API Keys.The API Key password is not stored in the database but in a separate file, see Storing the API Key Password. Notes®: For more information about how to create API keys, see API Keys. All executions of fully automated runbooks are linked to the user ID that created the API key. It is therefore recommended to use a functional user ID to create the API keys. The following criteria apply: Log in to RBA using the functional user ID to create API keys. All fully automated runbooks that are executed will be linked to this functional user ID. To investigate fully automated runbook logs, login to RBA using the functional user ID. Runbook executions can be viewed in the Execution page.
`RBASubscription=''`	The Netcool Operations Insight subscription ID. You can find this in the URL for the Netcool Operations Insight UI directly after `aiops`, for example, `cfd95b7e-3bc7-4006-a4a8-a73a79c71255`.
`GetHTTPUseProxy='false'` `GetHTTPProxyHost='localhost'` `GetHTTPProxyPort='8080'`	Required only if your Netcool/Impact server connects to Runbook Automation through a proxy server.
`MaxNumTrialsToUpdateRBAStatus='600'`	Number of seconds on how long to retry for status of a fully automated runbook. The recommended value is 600 (10 minutes). If your fully automated runbooks take longer than this time frame to complete, increase the value for this property accordingly.
`NumberOfSampleEvents='10'`	Number of sample events that are displayed when a new trigger is created. Sample events are displayed in the View Sample Events dialog when you create a new trigger in IBM Runbook Automation.

Run the following commands to update the fields in the Impact Derby database:

$IMPACT_HOME/bin/nci_db connect

You will be prompted something similar to the following:

ij version 10.8

Connect to your database with the same connection string as identified in Installing the Netcool/Impact add-on for Runbook Automation. For example:

ij> connect 'jdbc:derby://localhost:1527/ImpactDB;user=impact;password=derbypass;'; 
ij>

Use the sample commands to update the fields:


update rbaconfig.defaults set FieldValue ='RBADevelopmentTeam/hytmamvirtex' WHERE FieldName='RBAAPIKeyName'; 
update rbaconfig.defaults set FieldValue = 'myrbaserver.mycompany.com' WHERE FieldName='RBAHost';
update rbaconfig.defaults set FieldValue = 'myrbaserver.mycompany.com' WHERE FieldName='RBAManualExecHost';
update rbaconfig.defaults set FieldValue = '600' WHERE FieldName='MaxNumTrialsToUpdateRBAStatus';
update rbaconfig.defaults set FieldValue = 'cfd95b7e-3bc7-4006-a4a8-a73a79c71255' WHERE FieldName='RBASubscription';

Note: Starting with IBM Tivoli Netcool/Impact 7.1.0.17: after you have changed the configuration, open the Netcool/Impact UI, switch to the Policies tab, and run the RBA_ResetConnectionParameters policy (you might need to switch to the Global project view to see this policy listed).

Storing the API Key Password

The API key password that Netcool/Impact uses to access Runbook Automation is based on the configuration property RBAAPIKeyPassword and must be encrypted by using $IMPACT_HOME/bin/nci_crypt <RBAAPIKeyPassword value >.

For example, an encrypted value can look as follows:

{aes}BE0A8FAB4084D460CBD664FECDE3674A8B728BE7986F56F8B2F542C2056B4A2D1E6F64EDFF51BA985778C690A2E95

This encrypted value must be stored in a text file within the Netcool/Impact install location. Create the file $IMPACT_HOME/etc/RBAAPIKeyPassword.txt and copy the encrypted value into this file.

Note: If there are any additional secondary Netcool/Impact server(s) installed, repeat all of the steps on each of the secondary Netcool/Impact server(s). This is necessary because the encrypted value of the API key password depends on the individual Netcool/Impact system and cannot be shared by the primary and secondary Netcool/Impact server(s).