Creating Netcool connections

• Open a terminal.
• Connect to the Netcool ObjectServer Host.
• Save the following SQL commands in a file called add_trigger.sql:

  -- Add AIOps required fields ---
  alter table alerts.status add column AIOpsAlertId varchar(64);
  go
  
  alter table alerts.status add column AIOpsState varchar(16);
  go
  
  -- Add the Netcool Connector automation trigger group --
  create or replace trigger group NetcoolConnectorAutomation;
  go
  
  -- Enable the trigger --
  alter trigger group NetcoolConnectorAutomation set enabled true;
  go
  
  -- Add the clear automation trigger --
  create or replace trigger netcool_connector_clear_alerts
  group NetcoolConnectorAutomation
  priority 1
  comment 'Netcool Connector clear alerts that are closed in AIOps.'
  every 10 seconds
  when get_prop_value('ActingPrimary')%='TRUE'
  begin
     -- Set Sev to 0  if AIOpsState is closed
     for each row problem in alerts.status where
         problem.Type = 1 and problem.Severity > 0 and problem.AIOpsAlertId != '' and problem.AIOpsState = 'closed'
     begin
         update alerts.status via problem.Identifier set Severity = 0;
     end;
  end;
  go

  Note: The ScopeID column is available by default on Red Hat® OpenShift® container platform. However, use the following command for setting it up for on-premises ObjectServer:

  alter table alerts.status add column ScopeID varchar(255);
  go

• Run the following command to install the required columns and trigger with the add_trigger.sql file:

   $OMNIHOME/bin/nco_sql -server <object_server_name> -username root -password <password> < add_trigger.sql

• Name: The display name of your connection.
• Description: An optional description for the connection.
• Deployment options: Select the Local or Remote option.

• Filter is not valid

• Unable to connect to Object Server

• AIOPS fields not present

• Enable data collection: This toggle is set to on by default. It starts to collect event data from Netcool/OMNIbus immediately on creation of the connection.
• Mapping: This field provides mapping for standard Netcool/OMNIbus event columns that use Jsonata syntax. You can add your own custom ObjectServer columns to this mapping. If they have custom alert columns in your ObjectServer, you must add them to the Jsonata mapping provided in the Mapping text box.
  Note: If customizing the mapping, copy the text out of the mapping text box and into your preferred text editor. Then, add the mapping for those custom columns and check the code syntax. When done, copy the Jsonata code back into the mapping text box. If successful, a Valid Jsonata configuration message is displayed.

You created a Netcool connection in your instance, and a message appears on the connections page that states, Connection completed. IBM Cloud Pak for Watson AIOps has successfully processed your request.

oc get noi --all-namespaces

NOI_INSTANCE=<noi instance>
NOI_NAMESPACE=<noi namespace>
NOI_PROXY_SVC=$NOI_INSTANCE-proxy
NOI_PROXY_PRIMARY_PORT=$(oc get svc -n $NOI_NAMESPACE $NOI_PROXY_SVC -o jsonpath='{.spec.ports[?(@.name=="aggp-proxy-port")].port}')
NOI_PROXY_BACKUP_PORT=$(oc get svc -n $NOI_NAMESPACE $NOI_PROXY_SVC -o jsonpath='{.spec.ports[?(@.name=="aggb-proxy-port")].port}')
NOI_OMNI_USERNAME=root
NOI_OMNI_PASSWORD=$(oc get secret -n $NOI_NAMESPACE $NOI_INSTANCE-omni-secret -o jsonpath='{.data.OMNIBUS_ROOT_PASSWORD}' | base64 --decode && echo)

oc extract secret/$NOI_INSTANCE-proxy-tls-secret -n $NOI_NAMESPACE --to=. --keys=tls.crt

1. Create an omni.kdb file if it's not already available:

   $NCHOME/bin/nc_gskcmd -keydb -create \
   -db "$NCHOME/etc/security/keys/omni.kdb" \
   -pw mypassword \
   -stash \
   -expire 3660

   Note: Use a FIPS-compliant password for a Netcool/OMNIbus key database. The password must have the following features:

   • The minimum password length is 14 characters.
   • The password must have at least one lowercase character, one uppercase character, and one digit or special character.
   • Each character must not occur more than three times in a password.
   • No more than two consecutive characters of the password can be identical.
   • As an example, a FIPS-compliant password can look like V3ry-S3cretPass.
2. Generate a self-signed certificate labeled CA:

   $NCHOME/bin/nc_gskcmd -cert -create \
   -db "$NCHOME/etc/security/keys/omni.kdb" -stashed \
   -label "CA" \
   -size 2048 \
   -ca true \
   -dn "CN=CA,O=IBM,OU=Support,L=SouthBank,ST=London,C=GB" \
   -expire 3660 \
   -X509version 3

   Note: The CN, O, OU, L, ST, and C attributes are optional. Fill these values in accordance with your organization. For more information about these attributes, see the -dn string in nc_gskcmd command-line options.
3. Export the CA-labeled certificate to a file:

   $NCHOME/bin/nc_gskcmd -cert -extract \
   -db "$NCHOME/etc/security/keys/omni.kdb" -stashed \
   -label "CA" \
   -target "$NCHOME/etc/security/keys/cacert.arm"

1. Create a certificate request .arm file:

   $NCHOME/bin/nc_gskcmd -certreq -create \
   -db "$NCHOME/etc/security/keys/omni.kdb" -stashed \
   -label "${CERT_LABEL}" \
   -size 2048 \
   -dn "CN=${OS_FDQN},O=IBM,OU=Support,L=SouthBank,ST=London,C=GB" \
   -file "$NCHOME/etc/security/keys/${CERT_LABEL}_req.arm"

2. Generate a certificate by using the request .arm file.
   Note: Before you generate the certificate, define the following variables:

      ${OS_FDQN}
      ${CERT_LABEL}

   where OS_FDQN is the hostname of the ObjectServer, and CERT_LABEL is the label for identifying the certificate.

   This example shows defined variables:

      export OS_FDQN=myhost.ibm.com  
      export CERT_LABEL=AGG_V

   Use the request .arm file to generate the certificate:

   $NCHOME/bin/nc_gskcmd -cert -sign \
   -db "$NCHOME/etc/security/keys/omni.kdb" -stashed \
   -label "CA" \
   -target "$NCHOME/etc/security/keys/${CERT_LABEL}_cert.arm" \
   -expire 3660 \
   -file "$NCHOME/etc/security/keys/${CERT_LABEL}_req.arm" \
   -sig_alg SHA512_WITH_RSA

3. Export the certificate to a file.

   $NCHOME/bin/nc_gskcmd -cert -receive \
   -db "$NCHOME/etc/security/keys/omni.kdb" -stashed \
   -file "$NCHOME/etc/security/keys/${CERT_LABEL}_cert.arm"