In addition to load balancing to distribute incoming client requests, you can make your components available on every server within your cluster or restrict access to components by partitioning your applications.
To deploy components on a cluster so that every component is available from every cluster member, see Chapter 6, “Clusters and Synchronization.”
Partitioning restricts components to a subset of servers within a cluster. Partition an application by creating different logical server names, then installing component subsets into each logical server definition. Partitioning allows you to manually load balance within your cluster.
The Installed Packages folder lists the packages that are installed in a particular server. Even if a package is defined in a server's repository, and all files required for components in the package are available to the server, the server does not allow creation of instances of components for packages that are not installed in the server.
The following is a partitioning example:
Cluster “MyCluster” has
three members:
iiop://host1:9000;iiop://host2:9000;iiop://host3:9000
Server iiop://host1:9000 has
package “P1” installed.
Server iiop://host2:9000 has
package “P2” installed.
Server iiop://host3:9000 has
packages “P1” and “P2” installed.
Package P1 is available from iiop://host1:9000 and iiop://host3:9000,
and package P2 is available from iiop://host2:9000 and iiop://host3:9000.
See Chapter 3, “Managing Applications and Packages in EAServer Manager,” in the EAServer Programmer’s Guide for more information about installing packages.
You may want to use partitioning to separate CPU-bound
components from database-bound components.
| Copyright © 2003. Sybase Inc. All rights reserved. |
|
|
