Hybrid (High Availability mode)

Edit online

Learn how to configure a high availability (HA) hybrid deployment, which is composed of cloud native Netcool® Operations Insight® components on Red Hat® OpenShift®, with an on-premises Operations Management installation that has multiple WebGUI instances to provide redundancy.

About this task

Use this topic to help you setup a HA hybrid deployment where your on-premises Operations Management installation has multiple WebGUI instances. If your Operations Management installation has only one WebGUI instance, then do not use the topic, and follow the installation roadmap.

Extra deployment steps, which are tagged with the HA tag icon, are required for a HA hybrid deployment.
Note: In HA hybrid deployment, only policies get pushed to the backup cluster through the backup or restore pods. No event and topology data synchronize across the Cassandra. The Cassandra instances do not communicate with each other.

To download a PDF of the HA hybrid deployment process, click here.

Procedure

  1. Prepare for your HA hybrid deployment.
    Follow the instructions in Preparing to install on-premises Operations Management and prepare for the HA hybrid deployment.
  2. Setup load balancing for your on-premises WebGUI instances.
    The on-premises WebGUI/DASH servers must be set up with load balancing by using an HTTP Server that balances the UI load. If you do not already have load balancing configured for your on-premises WebGUI/DASH nodes, then follow the instructions here: Configuring load balancing for on-premises Web GUI or Dashboard Application Services Hub nodes (HA only)
  3. Configure your on-premises Operations Management to work with a hybrid deployment.
    Follow these instructions: Configuring on-premises Operations Management.
  4. Set up persistence for the OAuth service.
    Follow the instructions in this link: https://www.ibm.com/docs/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cwbs_oauthdb2.htmlexternal link.
    This creates another Db2® database to persist OAuth tokens and clients for use by all WebGUI nodes. You can use the same Db2 instance that you use for your load-balancing database.
    1. When instructed to create a client in the Db2 database, use the following values: 
      INSERT INTO OAuthDBSchema.OAUTH20CLIENTCONFIG
(
  COMPONENTID,
  CLIENTID,
  CLIENTSECRET,
  DISPLAYNAME,
  REDIRECTURI,
  ENABLED
)
VALUES
(
  'NetcoolOAuthProvider',
  'client_id',
  'client_secret',
  'My Client',
  'redirect_url',
  1
)
      Where
      • client_id is the value of client-id in custom-resource-was-oauth-cnea-secrets. For more information, see Configuring authentication.
      • client_secret is the value of client-secret in custom-resource-was-oauth-cnea-secrets. For more information, see Configuring authentication.
      • redirect_url is the value that you specified for Redirect URL when you installed the integration kit. For more information, see Installing the integration kit.
    2. Create a JDBC entry to enable connection to your Db2 instance from WebSphere®. In DASH, click Console Settings > WebSphere Administrative console > WebSphere Administrative console, and then Resources > JDBC > JDBC providers and add an entry for Db2.
    3. Create a WebSphere datasource that has the credentials to connect to the OAuth Db2 database:
      In DASH, click Console Settings > WebSphere Administrative console > WebSphere Administrative console, and then Resources > JDBC > Data Sources and add an entry for the OAuth Db2 database that you created. This datasource must have a different name to the datasource created for the load-balancing feature. jdbc/oauthProvider is the suggested value. The value of JNDI name for the datasource must be used for the value of the oauthjdbc.JDBCProvider parameter in NetcoolOAuthProvider.xml in step 6.
  5. Configure WebGUI with OAuth database.
    On each WebGUI node, update the file $JazzSM_Profile_Home/config/cells/JazzSMNode01Cell/oauth20/NetcoolOAuthProvider.xml with the changes that are made to the OAuthConfigSample.xml file here: https://www.ibm.com/docs/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cwbs_oauthsql.htmlexternal link.
    The value of the oauthjdbc.JDBCProvider parameter in NetcoolOAuthProvider.xml must match the JNDI name used for the datasource in step 3b.
    To avoid potential conflict, move the base.clients.xml file with the following command: 
    cd $JazzSM_Profile_Home/config/cells/JazzSMNode01Cell/oauth20
mv base.clients.xml base.clients.xml.backup
    Note: Complete this step each time that the Netcool Hybrid Deployment Option Integration Kit is redeployed.
  6. Install cloud native Netcool Operations Insight components on Red Hat OpenShift.
    Follow these instructions: Installing cloud native components on hybrid.
  7. Restart on-premises Dashboard Application Services Hub instances.
    Restart all Dashboard Application Services Hub instances on your Operations Management on-premises installation by using the following commands:
    cd JazzSM_WAS_Profile/bin
./stopServer.sh server1 -username smadmin -password password
./startServer.sh server1
    where JazzSM_WAS_Profile is the location of the application server profile that is used for Jazz® for Service Management. This is usually /opt/IBM/JazzSM/profile.
  8. Restart the common-ui and cem-users pods on your cloud native Netcool Operations Insight components deployment.
    1. Find the names of the common-ui pod and cem-users pods on your cloud native Netcool Operations Insight components deployment with the following command:
      oc get pod | grep common-ui
oc get pod | grep cem-users
    2. Restart these pods with the following command: 
      oc delete pod pod_name
      where pod_name is the name of the pod to be restarted.
  9. Complete the post installation steps in Post installation setup and verification.