Configure Multiple OC Servers

This article describes how to set up an initial multiple-OC configuration. If you are upgrading a multiple-UMP/OC to OC configuration, see .
uim203
This article describes how to set up an initial multiple-OC configuration. If you are upgrading a multiple-UMP/OC to OC configuration, see Upgrade a Multiple OC Configuration.
2
  • To upgrade from a previous version of OC to OC 20.3.3, use the OC 20.3.3 upgrade installer that is released as part of the UIM 20.3.3 release. For more information about the UIM 20.3.3 release, see the UIM 20.3.3 article.
  • UIM 20.3.3 has removed dependency on CA Business Intelligence (CABI) for rendering the native OC screens: Home page, Group view page, Device view page, and Monitoring Technologies (probes) view page. Custom and Out-of-the-Box dashboards and reports are still rendered by using CABI; that is, they have a dependency on CABI. However, the native OC screens are no longer dependent on CABI (Jaspersoft) and are rendered by using HTML5. For more information about the native OC screens using HTML5, see the Configuring and Viewing Monitoring Data article or the "Removing CABI Dependency (Native Operator Console)" section in the UIM 20.3.3 article.
  • To upgrade from a previous version of OC to OC 20.3.2, use the OC 20.3.2 upgrade installer. OC 20.3.2 is a patch release.. For more information about the OC 20.3.2 patch, see the OC 20.3.2 Patch article.
  • To upgrade from OC 20.3.0 to OC 20.3.1, use the upgrade installer for Operator Console that the UIM 20.3.1 patch contains. Note that UIM 20.3.1 is a patch release over UIM 20.3.0. The UIM 20.3.1 patch does not include any upgrade installer for the UIM Server. The patch includes the OC upgrade installer along with the separate standalone artifacts that you can use to upgrade the respective components to 20.3.1. For more information about the artifacts that are available as part of the UIM 20.3.1 patch release, see the UIM 20.3.1 article.
  • Ensure that you deploy the wasp_alarmviewer_api package to the secondary OC.
Configure a Secondary OC Server
Use the steps in this section to configure a secondary OC server. Repeat these steps to configure additional OC servers.
No steps are required for configuring the primary OC server.
Review the following points:
  • A secondary OC server can only be installed on a robot. Do not attempt to install a secondary OC server on a hub.
  • All probe addresses, for example,
    /domain/hub/robot/<probe_name>
    , are case sensitive.
  • Before wasp is started on the secondary OC server, import the .pem file to the secondary OC server and add the cryptkey path for that .pem file in the robot.cfg file. For more information, see Configure the robot.cfg File.
  • Verify that robot 9.31 (or later) is running on the secondary OC robot (without this the wasp will not start).
Follow these steps:
  1. Deploy a robot to the host that you plan to use as the secondary OC server.
    • The robot you choose must report directly to the primary hub, and must be on the same network subnet.
    • Installing a secondary OC instance on a robot that reports to a secondary hub is not supported.
    • Do not run the OC installer on the secondary OC server.
  2. For 20.3.3
    1. Launch the OC installer on the primary hub and navigate to the
      Select Robot
      dialog.
    2. Specify the IP address of the required robot, where you want to install the OC, in the
      Specify IP
      field. This robot must be reporting to the primary hub. Alternatively, you can also use the
      Choose
      option to select the robot that you deployed for your OC installation
      • It is recommended to use the
        Specify IP
        field if you have a large number of robots connected to the primary hub.
      • If you try to perform the installation on the primary hub, you receive a message prompting you to confirm whether you want to proceed with the installation on the primary hub. It is not recommended to install OC on a primary hub.
      • The OC installer displays an error message if you do not provide the valid IP address or the robot is not connected to the primary hub.
      • If wasp is down or cryptkey is not configured, the OC installer displays the appropriate error.
      • If the same OC version is already installed, the OC installer prompts you to reinstall or uninstall the instance.
      • If a previous version of OC is detected, the OC installer prompts you to upgrade to the latest OC version.
    3. Follow the remaining steps to complete the installation. For more information about the steps, see the Install Operator Console (OC) article.
  3. Prior to 20.3.3
    1. In Admin Console or Infrastructure Manager, distribute the following OC server packages from the Archive to the secondary OC server in the below order. Ensure that you drag each of the ump_portlet_name packages that are required for your environment from the archive.
      • java_jre
      • wasp
      • wasp_service_wrapper
      • nisapi_wasp
      • ump
      • ump_operatorconsole
      • wasp_alarmviewer_api
      • policy_management_ws
      • mcsuiapp_portlet
      • ump_cabi
      • ump_accountadmin (Optional)
      • ump_dashboard (Optional)
    2. Configure the wasp probe to use the correct data_engine probe address. For example,
      /domain/hub/robot
      /data_engine
    3. Use Raw Configure to modify the
      <ump_common>
      section of the wasp configuration to specify the following probe addresses:
      • ace: /
        domain/hub/robot
        /ace
        The ace probe has been deprecated in UIM 20.3.3.
      • automated_deployment_engine: /
        domain/hub/robot
        /automated_deployment_engine
      • discovery_server: /
        domain/hub/robot
        /discovery_server
      • nas: /
        domain/hub/robot
        /nas
      • service_host: /service_host Functionality for the service_host probe has been moved to wasp, and the probe is no longer installed as part of CA UIM v8.47 or later. The address key for the probe still exists in wasp but is not functional.
      • sla_engine: /
        domain/hub/robot
        /sla_engine
    4. Add the following keys with addresses as follows:
      • maintenance_mode = /
        domain/hub/robot
        /maintenance_mode
      • udm_manager = /
        domain/hub/robot
        /udm_manager
      • mpse = /
        domain/hub/robot
        /mpse
    5. Activate the wasp probe on the secondary OC server. When the wasp probe is activated, the probes create database tables.
      These manual steps will work for 20.3.3 also. However, it is recommended that you use the 20.3.3 OC installer as explained in the previous step (Step 2) while configuring multiple OC servers in 20.3.3.
  4. Repeat the same steps on other robots to implement more OC servers.
Configure a Load Balancer
This section provides the high-level steps for configuring a load balancer for a multiple OC server configuration. Use the steps in this section after you install and configure the primary and secondary OC server.
Load balancers and the terms that vendors use to describe them vary. Refer to the documentation for your load balancer for specific configuration details. You may need to perform the high-level steps in this section in a different order than shown.
Follow these steps:
  1. Deploy the load balancer:
    1. Configure the load balancer with IP addresses for each OC server.
  2. Create a node/device for each OC server.
    1. Enter the name and IP address of each OC server in your configuration.
  3. Create a pool/server farm:
    1. Provide a unique name for the pool/server farm.
    2. Add one or more health monitors, such as the gateway_icmp and http_head.
    3. Select a load balancing algorithm. The most common load balancing algorithm is round robin, where one connection is sent to each server on the list in turn.
    4. Add the nodes you created previously to the pool for port 80. Use port 443 for an HTTPS connection.
  4. Create a virtual server/context:
    1. Provide a unique name for the virtual server/context.
    2. Provide an IP address for the virtual server/context.
    3. Configure additional settings for the virtual server as follows:
      • Protocol = tcp
      • HTTP Profile = https
        or
        http
      • Source Port = preserve strict
      • Default Persistent Profile = cookie.
      Regardless of the load balancer, setting the Default Persistent Profile setting to
      cookie
      is required.
  5. Verify the load balancer was successfully configured by entering the IP of the virtual server/context in a web browser.
The load balancer is now configured for a multiple OC server configuration.