Guidelines for deploying a load balancer in a shared services architecture
Management A hardware device or software that distributes requests from tenant users across all mid tiers in the cluster, which in turn, act as an interface between the tenants and the tenant users.
For more information, see
Configuring a hardware load balancer with BMC Remedy AR System
from the BMC Remedy AR System online documentation.
Guidelines for deploying load balancer in a shared service architecture
- Decide the rules for the load balancer that are in line with the deployment strategy.
For example, sticky session should always be used, but routing the requests to the appropriate clusters or mid tier must be based on which tenant is supported by which mid tier. You must define such rules when you decide the final deployment architecture with mid tier as a shared service. - Define the necessary rule changes for the following scenarios:
- N+1 scenario — adding a mid tier to the cluster
- N-1 scenario — removing a mid tier from the cluster
- Ensure that the sticky session behavior is set to ON.
- (Optional) If you are using F5 load balancer, the health monitor used by F5 Load Balancer for mid tier Virtual Pool should be http monitor.
Recommendation
BMC recommends that you use the http_15_46 monitor. The monitor checks the http traffic every 15 seconds. The monitor times out after 46 seconds (after trying three times), after which it marks the resource as unavailable.
Related topics
Remedy Mid Tier as a shared service
Enterprise Centralized Configuration Server as a shared service
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.