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 .
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.
Configure the Primary UMP Server
No steps are required for configuring the primary UMP server.
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.
Follow these steps:
- 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.
- (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.
- After the UMP robot is installed, go toWindows Servicesand select the tab forChange the Nimbus robot watcher services logon.
- Change the logon account to the same account used in thedata_engineand the primary UIM serverNimbus robot watcher service.
- Restart theNimbus robot watcher service.
- Restart the UMP robot.
- In Admin Console or Infrastructure Manager, distribute the following UMP server packages from the Archive to the secondary UMP server:
- ump_<portlet_name>Ensure that you drag each of the ump_<portlet_name> packages required for your environment from the Archive.
- Configure the wasp probe to use the following probe addresses:
- data_engine - /<domain>/<hub>/<UIM_server>/data_engine
- Configure the wasp probe's relationshipviewer webapp to have the custom properties GraphServiceHost and GraphServicePort. GraphServiceHost is the IP address of the robot running the relationship_services probe, and GraphServicePort is the HTTP port relationship_services is using (default: 8182).
- 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
- discovery_server = /<domain>/<hub>/<UIM_server>/discovery_server
- nas = /<domain>/<hub>/<UIM_server>/nas
- service_host = /<domain>/<hub>/<UIM_server>/service_host
- sla_engine = /<domain>/<hub>/<UIM_server>/sla_engine
- ugs = /<domain>/<hub>/<UIM_server>/ugs
- Add the following keys with addresses as follows:
- maintenance_mode = /<domain>/<hub>/<UIM_server>/maintenance_mode
- udm_manager = /<domain>/<hub>/<UIM_server>/udm_manager
- mpse = /<domain>/<hub>/<UIM_server>/mpse
- Activate the wasp probe on the secondary UMP server.Activating the wasp 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:
- Deactivate the wasp probe on each UMP server.
- 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:
- 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.
- 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 themklinkcommand as follows:mklink /d c:\<UIM_installation>\probes\service\data\document_library \\primary\<document_library_share>
- For Linux, use themountcommand as follows:mount -t nfs <primary>:/<UIM_installation>/probes/service/data/document_library <UIM_installation>/probes/service/data/document_library
- (Only required for UMP servers that have network connections configured withboth IPv4 and IPv6 addresses). Add the following Java VM parameter to the wasp configuration:-Djava.net.preferIPv4Stack=true
- Activate the wasp probe on the primary UMP server.
- 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: 126.96.36.199Port: 23301
- IP: 188.8.131.52Port: 23302
- IP: 184.108.40.206Port: 23303
- IP: 220.127.116.11Port: 23304
- IP: 18.104.22.168Port: 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:
- Deploy the load balancer:
- Configure the load balancer with IP addresses for each UMP server.
- Create a node/device for each UMP server.
- Enter the name and IP address of each UMP server in your configuration.
- Create a pool/server farm:
- Provide a unique name for the pool/server farm.
- Add one or more health monitors, such as the gateway_icmp and http_head.
- 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.
- Add the nodes you created previously to the pool for port 80. Use port 443 for an HTTPS connection.
- Create a virtual server/context:
- Provide a unique name for the virtual server/context.
- Provide an IP address for the virtual server/context.
- Configure additional settings for the virtual server as follows:
Regardless of the load balancer, setting the Default Persistent Profile setting tocookieis required.
- Protocol = tcp
- HTTP Profile = httpsorhttp
- Source Port = preserve strict
- Default Persistent Profile = cookie.
- 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.