- In the administrative console, click Servers > Clusters > New.
The Create a new cluster wizard starts.
- Specify a name for the cluster.
- Select Prefer local if you want to enable node-scoped routing
optimization. This option is enabled by default. When this option
is enabled, if possible, EJB requests are routed to the client node. This
option improves performance because client requests are sent to local enterprise
beans.
- Select Configure HTTP session memory-to-memory replication if
you want a memory-to-memory replication domain created for this cluster.
The replication domain is given the same name as the cluster and is
configured with the default settings for a replication domain. When the default
settings are in effect, a single replica is created for each piece of data
and encryption is disabled. Also, the Web container for each cluster member
is configured for memory-to-memory replication.
To change these settings
for the replication domain, click Environment > Replication domains > replication_domain_name.
To modify the Web container settings, click Servers > Clusters > cluster_name >
Cluster members > cluster_member_name > Web container settings
> Session management > Distributed environment settings in the administrative
console. If you change these settings for one cluster member, you might also
need to change them for the other members of this cluster.
- Click Next.
- Choose whether to create an empty cluster or to create the first
member of the cluster.
If you decide to create an empty cluster,
to add members to this cluster, in the administrative console, click Servers
> Clusters > cluster_name > Cluster members > New.
To
create an empty cluster:
- Select None. Create an empty cluster.
- Click Next to display a summary of the defined cluster.
- Click Finish to create the cluster, or click Cancel if
you decide not to create this cluster.
When you create the first cluster member, remember that a
copy of the first cluster member that you create is stored as part of the
cluster data and becomes the template for all additional cluster members that
you create.
- Specify the name of the first cluster member.
- Select the node on which you want this cluster member to reside.
- Specify the weight value for the cluster member. The
weight value controls the amount of work that is directed to the application
server. If the weight value for this server is greater than the weight values
that are assigned to other servers in the cluster, then this server receives
a larger share of the workload. The weight value represents a relative proportion
of the workload that is assigned to a particular application server. The value
can range from 0 to 20.
- Select Generate unique HTTP ports if you want to generate
unique port numbers for every HTTP transport that is defined in the source
server. When this option is selected, which is the default setting,
this cluster member does not have HTTP transports or HTTP transport channels
that conflict with any of the other servers that are defined on the same node.
If you unselect this option, all of the cluster members will share the same
HTTP ports.
- Select the core group to which you want this cluster member
to belong. You are prompted for the core group only if you have
more than one core group defined for this cluster.
- Select one of the following options as the basis for the first
cluster member.
- Create the member using an application server template.
- Create the member using an existing application server as a template.
- Create the member by converting an existing application server.
You can only add an existing application server
to the cluster if you select that server as the first cluster member. You
cannot add other existing application servers to that cluster after you create
the first cluster member. If you add an existing server to a cluster, the
only way to remove that server from the cluster is to delete the server. Therefore,
you might want to use the existing server as a template for the first cluster
member instead of as the cluster member. If you keep the original application
server out of the cluster, you can reuse that server as the template if you
need to rebuild the configuration.
- Click Next.
- Create additional cluster members. Before you create
additional cluster members, check the configuration settings of the first
cluster member. These settings are displayed at the bottom of the Create additional
cluster members panel of the Create a new cluster wizard. For each additional
member that you want to create:
- Specify a unique name for the member. The name must
be unique within the node.
- Select the node to which you want to assign the cluster member.
- Specify the weight you want given to this member. The
weight value controls the amount of work that is directed to the application
server. If the weight value for the server is greater than the weight values
that are assigned to other servers in the cluster, then the server receives
a larger share of the workload. The value can range from 0 to 20.
- Select Generate unique HTTP ports if you want to generate
unique port numbers for every HTTP transport that is defined in the source
server.
- Click Add member. You can edit the configuration
settings of any of the newly created cluster members other than the first
cluster member, or you can create additional cluster members. Click Previous to
edit the properties of the first cluster member.
- When you finish creating cluster members, click Next.
- View the summary of the cluster and then click Finish to
create the cluster, click Previous to return to the previous wizard
panel and change the cluster, or click Cancel to exit the wizard without
creating the cluster.
- To further configure a cluster, click Servers > Clusters,
and then click the name of the cluster. Only the Configuration and Local
Topology tabs appear until you save your changes.
- Click Review to review your cluster configuration settings.
Repeat the previous step if you need to make additional configuration
changes.
- If you do not want to make any additional configuration changes,
select Synchronize changes with Nodes and then click Save. Your
changes are saved and synchronized across all of your nodes.
If
you click Save, but do not select Synchronize changes with Nodes, when
you restart the cluster, WebSphere Application Server does not start the cluster
servers because it cannot find them on the node. If you want to always synchronize
your configuration changes across your nodes, you can select Synchronize changes
with Nodes as one of your console preferences.
- Restart the cluster.