en.help.ref-clusternew.html Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of console-cluster-plugin Show documentation
Clustering support plugin bundle for GlassFish Admin Console
The newest version!




New Cluster

Use the New Cluster page to create a cluster.
The New Cluster page contains the following options.

Cluster Name

The name of the cluster.
The name must meet the following requirements:


The name may contain only ASCII characters.


The name must start with a letter, a number, or an underscore.


The name may contain only the following characters:


Lowercase letters


Uppercase letters


Numbers


Hyphen


Period


Underscore




The name must be unique in the domain and must not be the name of a another cluster, a named configuration, a GlassFish Server instance, or a node.


The name must not be domain, server, or any other keyword that is reserved by GlassFish Server.



Configuration

Drop-down list of existing named configurations that the cluster can use. A cluster requires a named configuration that defines the configuration of all instances that are added to the cluster. One configuration must be selected from the list. The cluster will use the selected configuration when the cluster is created.

Make a Copy of the Selected Configuration

If this option is selected, the selected configuration is copied when the cluster is created. The copy of the configuration is assigned the name cluster-name-config, where cluster-name is the name of the cluster as typed in the Cluster Name field.
If default-config is selected from the Configuration drop-down list, you must select this option. The default-config configuration can only be copied, not referenced.

Reference the Selected Configuration

If this option is selected, the cluster will use the specified existing named configuration.
If default-config is selected from the Configuration drop-down list, you must not select this option. The default-config configuration cannot be referenced, only copied.

Message Queue Cluster Config Type

Use this option to specify the type of Message Queue broker cluster to use for the new GlassFish Server cluster. By default, GlassFish Server uses a conventional Message Queue broker cluster with a master broker, with a broker embedded in each of the instances in the GlassFish Server cluster.
If this option is set to Custom, several additional options are displayed to configure the Message Queue broker cluster to use for the GlassFish Server cluster. See Options for Custom Message Queue Broker Clusters.

Server Instances to be Created

A list of GlassFish Server instances that are to be created when the cluster is created. For each instance, the following information is provided:

Instance Name

The name of the instance.

Weight

An integer that represents the load-balancing weight of the instance.
The load-balancing weight determines the proportion of all requests to the cluster that the instance should process.
For example, in a two-instance cluster, you might require one instance to process one out of four requests, and the other instance to process three out of four requests. In this situation, set the weight of the instance that is process one out of four requests to 1 and set the weight of the other instance to 3. If you prefer to use percentages, set the weights of the instances to 25 and 75 respectively.
The default weight is 100.

Node

Drop-down list of existing nodes where the instance can reside. One node must be selected from the list. The instance will reside on the selected node when the cluster is created.


The Server Instances to be Created table also contains the following options.

New

Button to create an instance. Clicking this button adds a row to the Server Instances to be Created table.

Delete

Button to delete an instance.





Options for Custom Message Queue Broker Clusters
When the Message Queue Cluster Config Type is set to Custom, the following options are displayed to configure the Message Queue broker cluster to use for the GlassFish Server cluster.

JMS Service Type

The type of brokers (called JMS hosts in GlassFish Server) to use in the broker cluster. The type chosen determines what types of broker clusters are available. The broker types are as follows.

Embedded

Broker configuration and lifecycle are managed by GlassFish Server. Each GlassFish clustered instance is serviced by a broker running in the same JVM as the instance.
If the JMS Service Type option is set to Embedded, only conventional Message Queue broker clusters are supported. Options to configure the conventional cluster are displayed.

Local

Broker configuration and lifecycle are managed by GlassFish Server. Each GlassFish clustered instance is serviced by a broker running in a separate JVM on the same host as the instance.
If the JMS Service Type option is set to Local, both conventional and enhanced (highly available) Message Queue broker clusters are supported. Options to select the cluster type and to configure the cluster are displayed.

Remote

Broker and broker cluster configuration and lifecycle are managed using Message Queue administrative tools.
If the JMS Service Type option is set to Remote, no other options are displayed.



JMS Cluster Type

The type of Message Queue broker cluster to use for the GlassFish Server cluster.
If the JMS Cluster Type option is set to Conventional, the following options are displayed.

JMS Configuration Store Type

The type of data store to use for the conventional cluster's configuration data. If this option is set to Master Broker, one broker in the cluster is designated as the master broker and the configuration data is stored by it. If this option is set to Shared DB, the configuration data is stored in a JDBC data store accessible to all the brokers. In this case, the database-related options are displayed.

JMS Message Store Type

The type of data store each broker is to use to store its message data. If this option is set to File, each broker stores its message data in a file-based data store. If this option is set to JDBC, each broker stores its message data in a JDBC data store.


If the JMS Cluster Type option is set to Enhanced (HA), the database-related options are displayed.

Database Vendor
Database URL
Database User

The database vendor, access url, and user of the JDBC database to use in any of these situations:


When the configuration store type of a conventional cluster is set to Shared DB


When the message store type of a conventional cluster is set to JDBC


When the cluster type is set to Enhanced (HA)


For information about supported vendors and the formats of access urls for each vendor, see JDBC-Based Persistence in Eclipse GlassFish Message Queue Administration Guide.

Database Authentication
Database Password
Password Alias

The password information for the JDBC database user specified in Database User.
If Database Authentication is set to Password, the Database Password option is displayed. If Database Authentication is set to Password Alias, the Password Alias option is displayed.

JMS Cluster Properties

A list of one or more Message Queue broker properties to configure the brokers. The list is colon-separated (:) and has the form:
prop1Name=prop1Value:prop2Name=prop2Value:...

If a broker property name includes dots, preface the dots with two backslashes (\\); for example, to include the imq.system.max_count property, specify imq\\.system\\.max_count in the list.



Related Tasks
To Create a Cluster

Equivalent asadmin Subcommand
create-cluster(1)


Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices