If you used an Apache load balancer for your clustered Orchestrators prior to upgrade, we recommend that you retain this load balancer until you have verified that everything is working smoothly with your new release. This requires that you update your Apache configuration with new templates provided in the installation media.
The change to NGINX after an upgrade is no different from setting up NGINX in a new release except that for upgrades, you install NGINX on the same server where the Apache load balancer currently exists. This lets you leverage the previously established URL and the previously established host names and ports.
For details on the setup, see NGINX Load Balancer.
Agents communicate with Orchestrators; Orchestrators communicate with agents. Release 4.2 introduces an improved simplified communication method. Apache uses the deprecated communication method. By default, existing agents are configured to use deprecated communication. This default setting allows you to switch load balancers from Apache to NGINX and convert existing agents to use simplified communication at a convenient time after you complete the mandatory upgrade tasks. NGINX supports simplified communication. (NGINX also supports deprecated communication.)
|
Copyright © 2014 CA.
All rights reserved.
|
|