Oracle GlassFish Server 3.1 Section 1: asadmin Utility Subcommands
create-connector-connection-pool(1)
create-connector-security-map(1)
create-connector-work-security-map(1)
create-jdbc-connection-pool(1)
create-message-security-provider(1)
create-resource-adapter-config(1)
delete-connector-connection-pool(1)
delete-connector-security-map(1)
delete-connector-work-security-map(1)
delete-jdbc-connection-pool(1)
delete-message-security-provider(1)
delete-resource-adapter-config(1)
disable-http-lb-application(1)
disable-secure-admin-internal-user(1)
disable-secure-admin-principal(1)
enable-secure-admin-internal-user(1)
enable-secure-admin-principal(1)
list-connector-connection-pools(1)
list-connector-security-maps(1)
list-connector-work-security-maps(1)
list-message-security-providers(1)
list-resource-adapter-configs(1)
list-secure-admin-internal-users(1)
list-secure-admin-principals(1)
list-supported-cipher-suites(1)
unfreeze-transaction-service(1)
update-admin-server-coordinates(1)
update-admin-server-local-coordinates(1)
update-connector-security-map(1)
update-connector-work-security-map(1)
Oracle GlassFish Server 3.1 Section 1M: Utility Commands
Oracle GlassFish Server 3.1 Section 5ASC: GlassFish Server Concepts
- creates a GlassFish Server cluster
create-cluster [--help] [--config config-name] [--systemproperties (name=value)[:name=value]*] [--properties (name=value)[:name=value]*] [--gmsenabled={true|false}] [--multicastport multicast-port] [--multicastaddress multicast-address] [--bindaddress bind-address] [--hosts hadb-host-list] [--haagentport port-number] [--haadminpassword password] [--haadminpasswordfile file-name] [--devicesize devicesize ] [--haproperty (name=value)[:name=value]*] [--autohadb=false] [--portbase port-number] cluster-name
The create-cluster subcommand creates a GlassFish Server cluster. Initially the cluster contains no GlassFish Server instances, applications, or resources.
A cluster requires a reference to the named configuration that defines the configuration of all instances that are added to the cluster. The configuration can be specified in the command to create the cluster, but is not required. If no configuration is specified, the subcommand creates a configuration that is named cluster-name-config for the cluster. The cluster that is created is a standalone cluster because the cluster's configuration is not shared with any other clusters or standalone instances.
To add instances to the cluster, set the --cluster option to the name of the cluster when using either of the following subcommands:
To delete server instances from the cluster at any time, use one of the following subcommands:
To associate applications and resources with all instances in the cluster, set the --target option to the name of the cluster when performing the following operations:
Deploying applications by using the deploy(1) subcommand
Creating resources by using subcommands such as create-jdbc-resource(1)
Creating references to applications that are already deployed in other targets by using the create-application-ref(1) subcommand
Creating references to resources that are already created in other targets by using the create-resource-ref(1) subcommand
This subcommand is supported in remote mode only.
Displays the help text for the subcommand.
Specifies the named configuration that the cluster references. The configuration must exist and must not be named default-config or server-config. Specifying the --config option creates a shared cluster. If this option is omitted, a standalone cluster is created.
Defines system properties for the configuration that is created for the cluster. These properties override the property values in the default-config configuration. The following properties are available:
This property specifies the port number of the HTTP port or HTTPS port through which the DAS connects to the instance to manage the instance. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number of the port that is used to listen for HTTP requests. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number of the port that is used to listen for HTTPS requests. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number of the port that is used for IIOP connections. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number of the port that is used for secure IIOP connections. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number of the port that is used for secure IIOP connections with client authentication. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number of the port that is used for connections to the Java Platform Debugger Architecture (JPDA) debugger. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number for the Java Message Service provider. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number on which the JMX connector listens. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
This property specifies the port number of the port that is used for connections to the Apache Felix Remote Shell. This shell uses the Felix shell service to interact with the OSGi module management subsystem. Valid values are 1–65535. On UNIX, creating sockets that listen on ports 1–1024 requires superuser privileges.
Defines properties for the cluster. The following properties are available:
The port number of the port on which the cluster listens for messages from the Group Management Service (GMS). The default value should suffice in most situations.
Specifies whether an instance may receive from itself application-level messages that the instance broadcasts to the cluster.
Possible values are as follows:
The instance may not receive messages from itself (default).
The instance may receive messages from itself. Use this setting for testing an instance when the instance is the only instance in a cluster.
The maximum number of iterations or transmissions that a multicast message for the following types of events can experience before the message is discarded:
Group discovery
Member heartbeats
Membership changes
To match the configuration of the network on which the DAS and clustered instances are deployed, set this value as low as possible. To determine the lowest possible value for your system, use the validate-multicast(1) subcommand.
A value of 0 ensures that multicast messages never leave the host from which they are broadcast.
A value of 1 might prevent the broadcast of messages between hosts on same subnet that are connected by a switch or a router.
The default is 4, which ensures that messages are successfully broadcast to all cluster members in networks where hosts are connected by switches or routers.
Specifies whether GMS is enabled for the cluster.
Possible values are as follows:
GMS is enabled for the cluster (default).
When GMS is enabled for a cluster, GMS is started in each server instance in the cluster and in the DAS. The DAS participates in each cluster for which this option is set to true.
GMS is disabled for the cluster.
The address on which GMS listens for group events. This option must specify a multicast address in the range 224.0.0.0 through 239.255.255.255. The default is 228.9.XX.YY, where XX and YY are automatically generated independent values between 0 and 255.
The port number of communication port on which GMS listens for group events. This option must specify a valid port number in the range 2048–32000. The default is an automatically generated value in this range.
The Internet Protocol (IP) address of the network interface to which GMS binds. This option must specify the IP address of a local network interface. The default is all public network interface addresses.
On a multihome machine, this option configures the network interface that is used for the GMS. A multihome machine possesses two or more network interfaces.
To specify an address that is valid for all GlassFish Server instances in the cluster, use a system property to set the address individually for each instance.
For example, use the create-system-properties subcommand to create the system property GMS-BIND-INTERFACE-ADDRESS-cluster-name. Then set the --bindaddress option of this subcommand to ${GMS-BIND-INTERFACE-ADDRESS-cluster-name} to specify the system property. Finally, for each instance in the cluster, set the GMS-BIND-INTERFACE-ADDRESS-cluster-name system property to the required network interface address on the instance's machine.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
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 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.
Example 1 Creating a Cluster
This example creates a cluster that is named ltscluster for which port 1169 is to be used for secure IIOP connections. Because the --config option is not specified, the cluster references a copy of the named configuration default-config that is named ltscluster-config.
asadmin> create-cluster --systemproperties IIOP_SSL_LISTENER_PORT=1169 ltscluster Command create-cluster executed successfully.
command executed successfully
error in executing the command
create-application-ref(1), create-instance(1), create-jdbc-resource(1), create-local-instance(1), create-resource-ref(1), delete-cluster(1), delete-instance(1), delete-local-instance(1), deploy(1), list-clusters(1), start-cluster(1), stop-cluster(1), validate-multicast(1)
Apache Felix Remote Shell, Java Platform Debugger Architecture (JPDA)