Configure Multiple UMP Servers

This article describes how you set up a first-time multiple-UMP configuration. If you are upgrading a multiple-UMP configuration, see .
uim81
This article describes how you set up a first-time multiple-UMP configuration. If you are upgrading a multiple-UMP configuration, see Multiple UMP Configuration Upgrade.
Contents
Configure the Primary UMP Server
Perform the steps in this section
only
if you are using any of the following deprecated portlets: Alarm Console, Custom Dashboards, Dashboard Designer, or Dynamic Views. Otherwise, proceed to the next section.
  1. Log into Admin Console or Infrastructure Manager.
  2. Locate the dashboard_engine probe, and use Raw Configure to modify the following parameters:
    1. In the <data> section, add or edit the key enable_multi_instance, and set its value to 1.
    2. In the <updateintervals> section, add or edit the key multi_instance_check_interval, and set its value to 30.
  3. Locate the wasp probe, and use Raw Configure to modify the following parameters:
    1. Under the <webapps> section, locate the <umpmedia> section.
    2. Add the following keys and values under <umpmedia>:
      • enable_multi_instance and set its value to 1 to enable synchronization of media files.
      • media_update_interval and set its value to 30.
The primary UMP server is now configured.
Configure a Secondary UMP Server
Use the steps in this section to configure a secondary UMP server. Repeat these steps to configure additional UMP servers.
If you are using the deprecated portlets Alarm Console, Custom Dashboards, Dashboard Designer, or Dynamic Views, you must perform all of the configuration steps in this section. Otherwise, you can omit certain steps as indicated.
Follow these steps:
  1. Deploy a robot to the host that you plan to use as the secondary UMP server.
    Do not run the UMP installer on the secondary UMP server.
  2. (Microsoft SQL Server Windows Authentication Only) Configure the secondary UMP server for Windows authentication. If you are using Microsoft SQL Server with Windows authentication, CA UIM cannot function until you configure Windows authentication on both the UIM and UMP servers.
    1. After the UMP robot is installed, go to 
      Windows Services
       and select the tab for 
      Change the Nimbus robot watcher services logon
      .
    2. Change the logon account to the same account used in the 
      data_engine
       and the primary UIM server 
      Nimbus robot watcher service
      .
    3. Restart the 
      Nimbus robot watcher service
      .
    4. Restart the UMP robot.
  3. In Admin Console or Infrastructure Manager, distribute the following UMP server packages from the Archive to the secondary UMP server:
    • java_jre
    • (Only required for deprecated portlets) dap
    • (Only required for deprecated portlets) dashboard_engine
    • nisapi_wasp
    • wasp
    • ump
    • ump_<portlet_name>
      Ensure that you drag each of the ump_<portlet_name> packages required for your environment from the Archive.
  4. (Only required for deprecated portlets). Configure the dap probe so that the data_engine address is /<domain>/<hub>/<UIM_server>/data_engine.
  5. (Only required for deprecated portlets). Configure the dashboard_engine probe so that the probe addresses are as follows:
    • Alarm Server - /<domain>/<hub>/<UIM_server>/nas
    • Data Access Probe - /<domain>/<hub>/<
      secondary
      _robot>/dap
    • Data Engine - /<domain>/<hub>/<UIM_server>/data_engine
    • Variable Server - /<domain>/<hub>/<UIM_server>/variable_server (if you do not use the variable_server probe, you can leave this field blank).
    Select No if you are prompted to restart the dashboard_engine probe.
  6. (Only required for deprecated portlets). Use Raw Configure to modify the dashboard_engine configuration:
    1. In the <data> section, add or edit the key enable_multi_instance, and set its value to 1.
    2. In the <updateintervals> section, add or edit the key multi_instance_check_interval, and set its value to 30.
  7. Configure the wasp probe to use the following probe addresses:
    • data_engine - /<domain>/<hub>/<UIM_server>/data_engine
    • (Only required for deprecated portlets) dashboard_engine - /<domain>/<hub>/<
      secondary
      _robot>/dashboard_engine
  8. Use Raw Configure to modify the <ump_common> section of the wasp configuration to use the following probe addresses:
    • ace = /<domain>/<hub>/<UIM_server>/ace
    • automated_deployment_engine = /<domain>/<hub>/<UIM_server>/automated_deployment_engine
    • (Only required for deprecated portlets) dap = /<domain>/<hub>/<
      secondary
      _robot>/dap
    • discovery_server = /<domain>/<hub>/<UIM_server>/discovery_server
    • maintenance_mode = /<domain>/<hub>/<UIM_server>/maintenance_mode
    • nas = /<domain>/<hub>/<UIM_server>/nas
    • nis_server = /<domain>/<hub>/<UIM_server>/nis_server
    • service_host = /<domain>/<hub>/<UIM_server>/service_host
    • sla_engine = /<domain>/<hub>/<UIM_server>/sla_engine
    • ugs = /<domain>/<hub>/<UIM_server>/ugs
    • mpse = /<domain>/<hub>/<UIM_server>/mpse
    • (Only required for deprecated portlets) variable_server = /<domain>/<hub>/<UIM_server>/variable_server
  9. (Only required for deprecated portlets) Use Raw Configure to modify the wasp configuration as follows:
    1. Add the following keys and values under <webapps>, <umpmedia>:
      • enable_multi_instance. Set its value to 1 to enable synchronization of media files.
      • media_update_interval. Set its value to 30.
    2. Under <webapps>, <relationshipviewer>, <custom>, <uncrypted>, set the key GraphServiceHost to the IP address of the primary hub.
  10. (Only required for deprecated portlets) Activate the dap probe and the dashboard_engine probe on the secondary UMP server.
  11. Activate the wasp probe on the secondary UMP server.
    Activating the wasp, and if applicable, dap and dashboard_engine is required to allow the probes to create database tables.
If desired, repeat the steps in this section on other robots to configure additional UMP servers.
Configure the Portal for Multiple UMP Servers
Use the steps in this section after configuring the secondary UMP server.
Be sure that you have permissions to change directories for your operating system before following these steps. Minimum permissions include Read, Write, and Execute.
Follow these steps:
  1. Deactivate the wasp probe on each UMP server.
  2. On each UMP server, add or uncomment the following two lines in <UIM_installation>/probes/service/wasp/webapps/ROOT/WEB-INF/classes/portal-ext.properties:
    • cluster.link.enabled=true
    • lucene.replicate.write=true
  3. Create and share a shared document_library directory on the primary UMP server.
    • For Windows, share the directory <UIM_installation>/probes/service/data/document_library with full read/write access.
    • For Linux, share the directory <UIM_installation>/probes/service/data/document_library via NFS, and ensure that no_root_squash is enabled.
  4. On the secondary UMP server, replace the directory <UIM_installation>/probes/service/data/document_library with a link to the primary document_library share.
    • For Windows, use the
      mklink
      command as follows:
      mklink /d c:\<UIM_installation>\probes\service\data\document_library \\primary\<document_library_share> 
    • For Linux, use the
      mount
      command as follows:
      mount -t nfs <primary>:/<UIM_installation>/probes/service/data/document_library <UIM_installation>/probes/service/data/document_library
  5. (Only required for UMP servers that have interfaces configured with
    both IPv4 and IPv6 addresses
    ). Add the following Java VM parameter to the wasp configuration:
    -Djava.net.preferIPv4Stack=true
  6. Activate the wasp probe on the primary UMP server.
  7. When the wasp is running on the primary UMP server, activate the wasp on the secondary UMP server.
The portal is now configured for multiple UMP servers.
Once configured, the UMP servers communicate through multicasting on the following IP address and port settings. Be sure that the ports are open in order to enable multicast traffic to pass between UMPs through a firewall or other restriction.
  • IP: 239.255.0.1
    Port: 23301
  • IP: 239.255.0.2
    Port: 23302
  • IP: 239.255.0.3
    Port: 23303
  • IP: 239.255.0.4
    Port: 23304
  • IP: 239.255.0.5
    Port: 23305
Configure a Load Balancer
This section provides the high-level steps for configuring a load balancer for a multiple UMP server configuration. Use the steps in this section after you install and configure the primary and secondary UMP 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 UMP server.
  2. Create a node/device for each UMP server.
    1. Enter the name and IP address of each UMP 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 UMP server configuration.