This topic describes the preparation needed
to use the z/OS® Load Balancing
Advisor, such as selecting a load balancing solution and considering
who has authority to start the Advisor and Agents.
Before you begin
- You must have at least one external load balancer that supports the Server/Application State Protocol (SASP). This load balancer must have IP connectivity to each z/OS system in the sysplex that is to participate in load balancing. If you are using TLS/SSL (through AT-TLS on z/OS) for incoming connections to the Load Balancing Advisor, the load balancer must also be capable of using TLS/SSL on its SASP communication flows.
- Read Application Transparent Transport Layer Security data protection and Policy-based networking to decide how you want the Advisor and Agents to use AT-TLS policies. To use AT-TLS, AT-TLS must be enabled and the Policy Agent must be configured and activated for each TCP/IP stack where the Load Balancing Advisors and Load Balancing Agents might run.
Procedure
Perform the following steps to prepare to use the z/OS Load Balancing Advisor:
- Consider whether you need to use TLS/SSL (using AT-TLS on z/OS). See Step 1: Consider whether to use TLS/SSL (using AT-TLS on z/OS).
- Evaluate TCP/IP workloads to be load balanced and select a load balancing solution. (optional) See Step 2: Evaluate TCP/IP workloads to be load balanced and select a load balancing solution (optional).
- Decide who will have authority to start the Advisor. (optional) See Step 3: Decide who will have authority to start the Advisor (optional).
- Decide who will have authority to start the Agents. (optional) See Step 4: Decide who will have authority to start the Agents (optional).
- Authorize the Agents to use WLM services. See Step 5: Authorize the Agents to use WLM services.
- Determine how the Advisor and agent are to interact in a subplexing environment (optional) See Step 6: Determine how the Advisor and agent are to interact in a subplexing environment (optional).