A cluster is a set of application servers that you manage together as a way to balance workload.
A cluster enables you to manage a group of application servers as a single unit, and distribute client requests among the application servers that are members of the cluster.
If you plan to create a cluster of servers that spans
multiple systems in a sysplex and has stateful session beans with
an activation policy of Transaction deployed in them, the passivation
directory should reside on an HFS (hierarchical file system) that
is shared across the multiple systems in the sysplex on which the
clustered servers are running.
To create a cluster:
If you create a cluster member by converting an existing application server, and any of the applications that you plan to deploy on members of this cluster require the functionality of one of the product feature packs, verify that the same level of deploy on any of the members of this cluster require the functionality of a feature pack, verify that the same level of that feature pack is installed on all of the cluster members. See the topic "Clusters and workload management" for more information about feature pack requirements in a cluster environment.
If you create a cluster member by converting an existing application server that is a member of a bus, you must migrate the messaging engine in the server to the scope of a cluster. To do this, use the wsadmin command migrateServerMEtoCluster. Do not delete the messaging engine at server scope and recreate it a cluster scope, because those actions prevent the messaging engine from working with previously configured destinations.
In this information ...Subtopics
Related concepts
Related reference
| IBM Redbooks, demos, education, and more(Index) |