Enable the Agent Client Collector load balancer

Enable a load balancer to ensure that you have functional MID Servers. A load balancer distributes resources over multiple MID Servers to ensure that no single MID Server is overloaded.

Before you begin

1. Install the Agent Client Collector Framework.
2. Configure the Agent Client Collector web server.
3. Ensure that you have access to the internal application's load balancer configuration.
4. Verify that the file <mid_server_install_path>/static/hello.txt was created during MID Server setup.

Role required: agent_client_collector_admin

Procedure

1. Configure the load balancer so that it can be used in the backend-url parameter in the acc.yml configuration file.
2. Perform the following setup actions on the load balancer:
   1. Increase the idle timeout to 300 seconds.
   2. Configure the load balancer target group with https and port 443.
      Configure all MID Servers behind the load balancer as targets.
   3. Configure the load balancer health check to monitor the <mid_server_install_path>/static/hello.txt file created during MID Server setup.
      The health check ensures that there are no communication interruptions between the load balancer and the MID Server.
3. Add the <mid_server_install_path>/static/hello.txt file to the static folder for each MID Server.
   You can place the file in another location that doesn't require credentials, to simplify the setup.
4. Update the acc.yml configuration file with the appropriate FQDN (backend-url value) and port number, and turn off automatic MID Server selection.

   backend-url:
    - wss://<fqdn>:<port>/ws/events
   enable_auto_mid_selection: false

5. Restart the Agent Client Collector.

Result

The Agent Client Collector data flow proceeds as described in Agent Client Collector architecture.

Note:

For information on enhancing security with SSL/TLS configuration, see the ITOM Agent Client Collector documentation material article in the Now Support Knowledge Base.