+

Search Tips   |   Advanced Search

Planning for multiple clusters

Multiple clusters are sets of servers that are managed together within a single administrative domain (or cell), and participate in workload management.

IBM WebSphere Application Server Network Deployment can manage many application servers and application server clusters within a single administrative domain, or cell. The single cell has the following advantages:

An administrator's goal is to manage as many HCL Portal and portal-based products within the same managed cell as possible. It takes advantage of the administrative and runtime features.

HCL Portal can federate multiple, independently configured portals into the same cell. While there are limitations to this support, it allows multiple clusters to be managed together. One portal might be providing different applications or services than another portal. With a common server identity, these services and applications can integrate seamlessly at the browser through the latest in web 2.0 technology. For example, it uses Ajax and REST services.


How multiple clusters work in a single cell

It is important to understand that a cell's configuration has the notion of scope. The scope controls the visibility of that resource to other resources and application server instances. An example of a resource might be a data source definition, or a WebSphere variable definition. Scopes are typically defined as being one of the following options:



Note: Resources defined within a circle, can be seen by all other resources and scopes that are defined within that circle.

Within this concept of scope, an important point is that all enterprise applications are cell-scoped. In other words, there can be only one enterprise application with a given name in the cell. If multiple servers and clusters, or multiple clusters require the use of that enterprise application, they must share it.

Typically, when installing an enterprise application that is shared across multiple clusters, the administrator installs the enterprise application archive into the cell's Deployment Manager. Then, it maps the application to the target clusters where it runs. HCL Portal installs several enterprise applications as part of its basic configuration and before any cluster is defined. Special steps must be followed to ensure that these infrastructure applications are appropriately shared when multiple clusters are defined within the same cell. And by extension, since they are infrastructure applications, all HCL Portal clusters must be at the same version.

Since portlets are enterprise applications of a special type, it is possible, but not always appropriate, to share portlets across multiple clusters. Many portlets (for example HCL Portal administration) are considered part of the infrastructure, and as a result can be shared across multiple clusters. Most user application portlets are specific to certain clusters and are installed as such.

Also, the Java Platform, Enterprise Edition security configuration for the cell is shared by all servers and clusters that are managed in the cell. Therefore, each server and cluster must share an underlying user repository.

To summarize at a high level, supporting multiple clusters in the same cell involves:


Limitations