About Hosting Partitioned Applications on Multiple Servers
A partitioned application is divided into sections where AppLogic objects are hosted by separate Netscape Application Servers. Partitioned applications allow you to specialize the type of processing each Netscape Application Server is performing.
For example, AppLogic objects that mostly perform data access are CPU intensive. Objects that are performing a lot of calculations are CPU and active-memory intensive. You can partition the application by hosting these groups of objects on separate Netscape Application Servers. Then you can configure the hardware of those servers to support the type of resources needed by the AppLogic objects hosted there.
The easiest approach to configure a partitioned application is to install the complete application on all the Netscape Application Servers, enabling load balancing so each server knows about the AppLogic objects hosted on the other servers, and then disable the specific AppLogic objects on a server by server basis, leaving no objects enabled on more than one server. Of course, if you want to also balance request loads for specific objects, you can leave them enabled on more than one server. When you enable or disable a distributed AppLogic object on a server, the servers across which the object is distributed are automatically updated so as to not attempt to forward requests to the server for which the object is disabled.
For example, if objects X and Y are hosted on servers A and B, but object X is disabled on server A, server B does not attempt to forward requests for object X to server A. All requests for object X are processed by server B.
For information about partitioning applications, see "Partitioning an Application."
|
Previous
