|Maintenance Notice - PDF Generation|
|Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.
|Purpose: To describe how to implement Load Balancing for your web engagement servers.|
Genesys Web Engagement supports any third-party load balancer as long as the load balancing features include cookie support and URL encoding-based routing methods.
Load balancing deployment should occur at the latest stage of your deployment. Genesys recommends that you follow these steps:
- Install Genesys Web Engagement, as described in the Installation chapter.
- Develop and test a Web Engagement Application, as described in Application Development Workflow.
- Follow the Load Balancing guidelines to install your servers.
- Deploy your application on the Web Engagement servers, as detailed in Deploying to Production Environment
The following diagram shows how you can implement a load balancing configuration for your Web Engagement servers.
In the above example:
- The load balancer for the Frontend Server implements sticky sessions for the deployed Web Engagement application;
- The load balancer for the Backend Server implements sticky sessions to route IP addresses when customers are engaged.
Genesys Web Engagement uses sticky sessions as follows:
- The load balancer for the Frontend Server implements sticky sessions based on URL encoding static parameters for the deployed Web Engagement application. Web Engagement creates the parameter as follows:
"." + <CME_Application_Name>.
- Note: If you are using Apache, you do not need to add
"."to your static parameter; this will be done by the Web Engagement Server.
- The load balancer for the Backend Server implements sticky sessions based on cookies to route IP addresses when the customers are engaged. The load balancer for the Backend Server must support the following features:
- Cookie-based stickiness to enable engagement.
- Storage of sticky parameters into cookies.
Apache is used by default as a sample in the configuration instructions, which are available on the following page: