Use this page to create dynamic clusters. To view this administrative console page, click Servers > Dynamic clusters > New
Name | The name field is a required, user-defined field. The name field cannot contain the following characters: # \ / , : ; " * ? < > | = + & % ' The name defined must be unique among dynamic clusters and cannot begin with a period (.) or a space. A space does not generate an error, but leading and trailing spaces are automatically deleted. |
Map to node group | Select from any available node groups. A default node group is selected for your dynamic cluster if you do not specify one. A node group and a dynamic cluster have a close relationship. The node group is a user-defined affiliation of nodes that share a common property. A dynamic cluster is a cluster of servers within a node group, whose members, server instances, reside on a node within a node group, and are application deployment targets. |
Prefer local enabled | To enable or disable node scoped routing optimization, select Prefer local enabled. The default is enabled, which indicates that, if possible, Enterprise JavaBeans (EJB) requests are routed to the client's node. If you enable this feature, performance is improved because client requests are sent to local EJBs. |
Create a replication domain for this cluster | To enable internal memory-to-memory replication, select Create a replication domain for this cluster. |
Select template | You must select an application server template on which to model the servers for the new dynamic cluster. You can select a default template, or map an existing application server. |
Existing application server | You must select the appropriate application server from this list. |
Minimum number of instances | Each entry must contain a set number of minimum running instances for a dynamic cluster. By default this field is set to 1, which is usually acceptable, particularly for dynamic clusters that will be running in supervisory or automatic mode. Acceptable entries for this field are integers greater than or equal to 1. If a minimum value is excessive, performance degradation might occur. To stop instances when there is no activity, select Stop all instances started during periods of inactivity and type the Time to wait before stopping instances in minutes. If you want one cluster instance started at all times, select Keep one instance started at all times. To have multiple cluster instances started at all times, select Keep multiple instances started at all times and type the Number of instances that you want started at all times. |
Maximum number of instances | Each entry must contain a set number of maximum running instances for a dynamic cluster. If you want to limit the number of cluster instances, select Limit number of cluster instances that can start and type the maximum Number of instances. If you want no limit on the number of cluster instances, select Do not limit the number of instances that can start. |
Vertical stacking of instances on node | Enable vertical stacking to improve bottleneck conditions between applications by selecting Allow more than one instance to start on the same node, and typing the Number of instances. |