About Hosting and Deploying Applications for Load Balancing
Balancing application-request loads requires that you duplicate AppLogic objects on multiple Netscape Application Servers and configure each server to "know" about the AppLogic objects on the other servers. For more information about load balancing, see "About Load Balancing."
When you deploy an application from one Netscape Application Server to another, you are asked if and, if so, how you are going to configure the application for load balancing. When deploying an application, you have the following load balancing configuration choices:
These configuration choices are useful for the different scenarios you might have within your enterprise. For example, you might have three Netscape Application Servers used as a test enterprise where the developers deploy their applications for testing. The runtime enterprise, where users' requests are actually processed, also consists of three Netscape Application Servers. Because the AppLogic objects could be different between the two groups of servers, you do not want application load balancing to occur. Therefore, when you deploy an application from the test servers to the runtime servers, you would choose to only balance the loads between the destination servers.
At a later date, you scale the enterprise and add three more Netscape Application Servers to the runtime group. When deploying the applications from one of the existing runtime servers to the new servers, you would join all the servers in that group. The application loads are then balanced between the existing servers and the new servers.
The following illustration depicts a load-balancing distribution among the destination servers only:
The next illustration depicts a joining of servers when adding new servers to a group and deploying an application to those servers with the join option.
If you choose a local distribution during deployment, no balancing of application-request loads occurs between any of the servers.
For information about deploying applications and enabling load balancing, see "Deploying an Application."
For information about enabling load balancing for already deployed applications, see "Changing the Distribution Level for an AppLogic Object."
|
Previous
