5.4 Distributing requests by the round-robin format

This section explains the distribution of requests by the round-robin format.

The following table describes the organization of this section.

Table 5‒6: Organization of this section (Distributing requests by the round-robin format)
Category	Title	Reference
Description	Overview of distributing requests by the round-robin format	5.4.1
	Examples of Request Distribution in the Round-robin Format	5.4.2
	Defining request distribution in the round robin format	5.4.3
Settings	Execution environment settings (When the Smart Composer functionality is used)	5.4.4
Settings	Execution environment settings (When the Smart Composer functionality is not used)	5.4.5
Notes	Precautions related to request distribution in the round-robin format	5.4.6

Note:: There is no specific description of Implementation and Operations for this functionality.

When Web containers are deployed with a cluster configuration, by using the redirector, requests are distributed in round-robin format to the respective Web containers. By referencing the session ID appended to each request, the redirector distributes the requests so that the requests from the same Web client are always transferred to the same Web container. However, if the session cookie name is changed from the default JSESSIONID to another name, the operation of transferring requests from the same Web client to the same Web container is not guaranteed.

If the processing efficiency of the Web containers to which requests are distributed is different, you can adjust the proportion of load on each host by defining load parameters. When distributing requests in the round-robin format, as a prerequisite, you must deploy the same Web application on each Web container performing the distribution processing.

Organization of this section

To Page Top