Install Operations Hub on Cluster Nodes

Procedure

  1. In the downloaded ISO files/folders, open the OperationsHub folder and run ophub_bundle.exe to start Operations Hub installation.
    The welcome screen appears.
  2. Do the following:
    Screen Do This
    Welcome Select Next.
    License agreement
    1. Select the Accept check box.
    2. Select Next.
    TCP port check Select Next.
    Host Names Default values are populated. Make sure your cluster name reflects in the following fields:
    • All Host Names: Enter the fully qualified domain name of the client access point, followed by the client access point itself, and then any additional hostname/s (see screenshot).
    • Primary Host Name
    Proficy Authentication Service Default values are populated.

    Select Next.
    Create Tenant Admin Account Enter the following fields and select Next.
    • User Id
    • Password
    • Re-enter Password
    Note: In a clustered environment, ensure that the user id and password are identical across nodes (Node1 and Node2) to facilitate the application's access to shared resources.
    Customize Log Files and Postgres Data Locations Under 'Advanced option', you need to enter the path to the shared drive folder. To do so, ensure/create this folder structure in your shared drive: (note that we already created the Postgres > uaa structure in a previous step.)
    • Postgres
      • iqp
      • uaa
      • webhmi
    Enter the location path as shown here:
    Install Dataflow Editor If you want to install the Dataflow Editor tool along with Operations hub, provide details on this screen and select Next.
    Configuration Hub Integration Replace 'localhost' with your cluster's client access point name and select Next.
    You are ready to install Select Install.

What to do next

Important: While the Operations Hub installation is in progress, do the following:
  1. Access the Windows temporary files folder.

    Open the Run dialog, type %temp% and press ENTER on your keyboard.

  2. Locate and copy the temp_windows_<timestamp>.env file.
  3. Save the copied file to a different location.
    Important: Do not store the .env file on the nodes servers. Consider storing the file on a dedicated Secret Manager server, which is isolated and configured to communicate only with the cluster nodes.
This temporary file contains installation parameter values, including auto-generated ones, which are crucial for installing Operations Hub on Node2.
Open (preserved temporary file) temp_windows_<timestamp>.env in a text editor, and extract the following information.
Tip: Within the temporary file, search and retain the following data (and their unique values). Remove all other data.
  • UAA_ADMIN_CLIENT_SECRET
  • UAA_POSTGRES_PASSWORD
  • UAA_USER_PASSWORD
  • OPHUB_TENANT_PASSWORD
  • NODERED_HTTPNODE_PASSWORD
  • CH_CLIENT_AUTH
  • UAA_ZONE_URL
  • PASSWORD_ENV_VARIABLE
  • IQP_POSTGRES_ENCRYPTKEY_CANDIDATE
  • REDIS_PASSWORD
  • UAA_CLIENT_SECRET
  • HAZELCAST_PASSWORD
  • OPHUB_POSTGRES_PASSWORD
  • KAFKA_ADMIN_USER_SECRET
  • KAFKA_USER_SECRET
  • ZK_USER_SUPER_PASSWORD
  • ZK_USER_KFAKA_PASSWORD
  • WEBHMI_POSTGRES_PASSWORD
  • DD_ENCRYPT_KEY
  • WEBHMI_SVC_OAUTH2_CLIENT_SECRET
  • NODERED_CLIENT_SECRET

We shall pass the information variables as command line arguments when executing Operations Hub installation on Node2.

Play video: