0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

1

0

0

0

0

1

1

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

Server is not running, will attempt to start it...
Waiting for domain1 to start ............
Successfully started the domain : domain1
domain  Location: /home/cdctest/glassfish4_b80/glassfish/domains/domain1
Log File: /home/cdctest/glassfish4_b80/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command restart-domain executed successfully.

Waiting for the domain to stop ..
Command stop-domain executed successfully.

Waiting for domain1 to start ............
Successfully started the domain : domain1
domain  Location: /home/cdctest/glassfish4_b80/glassfish/domains/domain1
Log File: /home/cdctest/glassfish4_b80/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command start-domain executed successfully.

Starting database in Network Server mode on host 0.0.0.0 and port 1527.
--------- Derby Network Server 情報 --------
バージョン: CSS10080/10.8.1.2 - (1095077)  ビルド: 1095077  DRDA 製品 ID: CSS10080
-- listing properties --
derby.drda.traceDirectory=/home/cdctest/glassfish4_b80/glassfis...
derby.drda.maxThreads=0
derby.drda.sslMode=off
derby.drda.keepAlive=true
derby.drda.minThreads=0
derby.drda.portNumber=1527
derby.drda.logConnections=false
derby.drda.timeSlice=0
derby.drda.startNetworkServer=false
derby.drda.host=0.0.0.0
derby.drda.traceAll=false
------------------ Java 情報 ------------------
Java バージョン:       1.7.0_11
Java ベンダー:         Oracle Corporation
Java ホーム:           /home/cdctest/glassfish4_b80/jdk7/jre
Java クラスパス:       /home/cdctest/glassfish4_b80/glassfish/lib/asadmin/cli-optional.jar:/home/cdctest/glassfish4_b80/javadb/lib/de
rby.jar:/home/cdctest/glassfish4_b80/javadb/lib/derbytools.jar:/home/cdctest/glassfish4_b80/javadb/lib/derbynet.jar:/home/cdctes
t/glassfish4_b80/javadb/lib/derbyclient.jar
OS 名:                 Linux
OS アーキテクチャー:   amd64
OS バージョン:         2.6.32-100.34.1.el6uek.x86_64
Java ユーザー名:       cdctest
Java ユーザー・ホーム: /home/cdctest
Java ユーザー dir:     /home/cdctest/JavaEE7/cmdant
java.specification.name: Java Platform API Specification
java.specification.version: 1.7
java.runtime.version: 1.7.0_11-b21
--------- Derby 情報 --------
JRE - JDBC: Java SE 6 - JDBC 4.0
[/home/cdctest/glassfish4_b80/javadb/lib/derby.jar] 10.8.1.2 - (1095077)
[/home/cdctest/glassfish4_b80/javadb/lib/derbytools.jar] 10.8.1.2 - (1095077)
[/home/cdctest/glassfish4_b80/javadb/lib/derbynet.jar] 10.8.1.2 - (1095077)
[/home/cdctest/glassfish4_b80/javadb/lib/derbyclient.jar] 10.8.1.2 - (1095077)
------------------------------------------------------
----------------- ロケール情報 ----------------
現行ロケール :  [日本語/日本 [ja_JP]]
ロケールのサポートが見つかりました: [cs]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [de_DE]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [es]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [fr]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [hu]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [it]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [ja_JP]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [ko_KR]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [pl]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [pt_BR]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [ru]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [zh_CN]
	 バージョン: 10.8.1.2 - (1095077)
ロケールのサポートが見つかりました: [zh_TW]
	 バージョン: 10.8.1.2 - (1095077)
------------------------------------------------------

Starting database in the background.
Log redirected to /home/cdctest/glassfish4_b80/glassfish/databases/derby.log.
Command start-database executed successfully.

Wed Mar 20 02:20:16 EDT 2013 : 次のホストの接続を確立しました: 0.0.0.0、ポート番号 1527。
Wed Mar 20 02:20:17 EDT 2013 : Apache Derby Network Server - 10.8.1.2 - (1095077) はシャットダウンしました
Command stop-database executed successfully.

Can't find remote man page, looking locally...
enable-secure-admin(1)    asadmin Utility Subcommands   enable-secure-admin(1)

NAME
       enable-secure-admin - enables secure admin (if it is not already
       enabled), optionally changing the alias used for DAS-to-instance admin
       messages or the alias used for instance-to-DAS admin messages.

SYNOPSIS
           enable-secure-admin [--help]
           [--adminalias=alias]
           [--instancealias=alias]

DESCRIPTION
       The enable-secure-admin subcommand causes the DAS and the instances in
       the domain to use SSL certificates for encrypting the messages they
       send to each other. This subcommand also allows the DAS to accept
       administration messages from remote admin clients such as the asadmin
       utility and IDEs.

           Note
           +----------------------------------------+
           |           You must restart any running |
           |           servers in the domain after  |
           |           you enable or disable secure |
           |           admin. It is simpler to      |
           |           enable or disable secure     |
           |           admin with only the DAS      |
           |           running, then restart the    |
           |           DAS, and then start any      |
           |           other instances.             |
           +----------------------------------------+

       By default, when secure admin is enabled the DAS and the instances use
       these SSL certificates to authenticate to each other as security
       "principals" and to authorize admin access. The --asadminalias value
       indicates to the DAS which SSL certificate it should use to identify
       itself to the instances. The --instancealias value determines for
       instances which SSL certificate they should use to identify themselves
       to the DAS.

       The enable-secure-admin subcommand fails if any administrative user in
       the domain has a blank password.

       Alternatively, you can use the enable-secure-admin-internal-user
       subcommand to cause the servers to identify themselves using a secure
       admin user name and password.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --adminalias
           The alias that refers to the SSL/TLS certificate on the DAS. This
           alias is used by the DAS to identify itself to instances. The
           default value is s1as.

       --instancealias
           The alias that refers to the SSL/TLS certificate on the instances.
           This alias is used by the instances to identify themselves to the
           DAS. The default value is glassfish-instance.

EXAMPLES
       Example 1, Enabling secure admin for a domain
           The following example shows how to enable secure admin for a domain
           using an admin alias adtest and an instance alias intest

               asadmin> enable-secure-admin --adminalias adtest --instancealias intest
               server-config
               default-config

               Command enable-secure-admin executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       disable-secure-admin(1)

       enable-secure-admin-principal(1)

       enable-secure-admin-internal-user(1)

       asadmin(1M)

Java EE 7                         25 Jun 2011           enable-secure-admin(1)
Command enable-secure-admin executed successfully.

You must restart all running servers for the change in secure admin to take effect.
Command enable-secure-admin executed successfully.

Can't find remote man page, looking locally...
disable-secure-admin(1)   asadmin Utility Subcommands  disable-secure-admin(1)

NAME
       disable-secure-admin - disables secure admin if it is already enabled.

SYNOPSIS
           disable-secure-admin [--help]

DESCRIPTION
       The disable-secure-admin subcommand disables secure admin if it is
       already enabled.

           Note
           +----------------------------------------+
           |           You must restart any running |
           |           servers in the domain after  |
           |           you enable or disable secure |
           |           admin. It is simpler to      |
           |           enable or disable secure     |
           |           admin with only the DAS      |
           |           running, then restart the    |
           |           DAS, and then start any      |
           |           other instances.             |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

EXAMPLES
       Example 1, Disabling secure admin for a domain
           The following example shows how to disable secure admin for a
           domain.

               asadmin> disable-secure-admin
               server-config
               default-config

               Command disable-secure-admin executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       enable-secure-admin(1)

       asadmin(1M)

Java EE 7                         25 Jun 2011          disable-secure-admin(1)
Command disable-secure-admin executed successfully.

You must restart all running servers for the change in secure admin to take effect.
Command disable-secure-admin executed successfully.

Command create-node-ssh executed successfully.

Command create-cluster executed successfully.

Command _create-instance-filesystem executed successfully.
Port Assignments for server instance ins2: 
JMX_SYSTEM_CONNECTOR_PORT=28686
JMS_PROVIDER_PORT=27676
HTTP_LISTENER_PORT=28080
ASADMIN_LISTENER_PORT=24848
JAVA_DEBUGGER_PORT=29009
IIOP_SSL_LISTENER_PORT=23820
IIOP_LISTENER_PORT=23700
OSGI_SHELL_TELNET_PORT=26666
HTTP_SSL_LISTENER_PORT=28181
IIOP_SSL_MUTUALAUTH_PORT=23920
The instance, ins2, was created on host localhost
Command create-instance executed successfully.

Can't find remote man page, looking locally...
export-sync-bundle(1)     asadmin Utility Subcommands    export-sync-bundle(1)

NAME
       export-sync-bundle - exports the configuration data of a cluster or
       standalone instance to an archive file

SYNOPSIS
           export-sync-bundle [--help]
           --target target
           [--retrieve={false|true}]
           [file-name]

DESCRIPTION
       The export-sync-bundle subcommand exports the configuration data of a
       cluster or standalone instance to an archive file. The archive file can
       then be used with the import-sync-bundle(1) subcommand to restore the
       configuration data.

       Importing an instance's configuration data transfers the data to a host
       for an instance without the need for the instance to be able to
       communicate with the domain administration server (DAS). Importing an
       instance's configuration data is typically required for the following
       reasons:

       *   To reestablish the instance after an upgrade

       *   To synchronize the instance manually with the DAS when the instance
           cannot contact the DAS

       The subcommand creates an archive that contains the following files and
       directories in the current domain directory:

       *   All the files in the following directories:

           *   config

           *   docroot

       *   The entire contents of the following directories and their
           subdirectories:

           *   applications

           *   config/target, where target is the cluster or standalone
               instance for which configuration data is being exported

           *   generated

           *   lib

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           The cluster or standalone instance for which to export
           configuration data. The --target option is required.

           This option must not specify a clustered GlassFish Server instance.
           If this option specifies a clustered instance, an error occurs. To
           export configuration data for a clustered instance, specify the
           name of the cluster of which the instance is a member, not the
           instance.

       --retrieve
           Specifies whether the archive file is downloaded from the DAS host
           to the host where the subcommand is run.

           Possible values are as follows:

           true
               The archive file is downloaded to the host where the subcommand
               is run.

           false
               The archive file is not downloaded and remains on the DAS host
               (default).

OPERANDS
       file-name
           The file name and location of the archive file to which to export
           the data.

           The default depends on the setting of the --retrieve option:

           *   If --retrieve is false, the default is
               sync/target-sync-bundle.zip in the current domain directory.

           *   If --retrieve is true, the default is target-sync-bundle.zip in
               the current working directory.

           target is the cluster or standalone instance that the --target
           option specifies.

           If a relative path is specified, the directory to which the path is
           appended depends on the setting of the --retrieve option:

           *   If --retrieve is false, the path is appended to the config
               subdirectory of the current domain directory.

           *   If --retrieve is true, the path is appended to the current
               working directory.

           If an existing directory is specified without a filename, the file
           name of the archive file is target-sync-bundle.zip, where target is
           the cluster or standalone instance that the --target option
           specifies.

EXAMPLES
       Example 1, Exporting the Configuration Data of a Cluster
           This example exports the configuration data of the cluster
           pmdcluster.

               asadmin> export-sync-bundle --target=pmdcluster
               Sync bundle: /export/glassfish3/glassfish/domains/domain1/sync/
               pmdcluster-sync-bundle.zip

               Command export-sync-bundle executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       import-sync-bundle(1)

       asadmin(1M)

Java EE 7                         7 Dec 2010             export-sync-bundle(1)
Command export-sync-bundle executed successfully.

Sync bundle: /home/cdctest/glassfish4_b80/glassfish/domains/domain1/sync/server-sync-bundle.zip
Command export-sync-bundle executed successfully.

import-sync-bundle(1)     asadmin Utility Subcommands    import-sync-bundle(1)

NAME
       import-sync-bundle - imports the configuration data of a clustered
       instance or standalone instance from an archive file

SYNOPSIS
           import-sync-bundle [--help]
           --instance instance-name
           [--nodedir node-dir] [--node node-name]
           file-name

DESCRIPTION
       The import-sync-bundle subcommand imports the configuration data of a
       clustered instance or standalone instance from an archive file that was
       created by the export-sync-bundle(1) subcommand.

       You must run this subcommand on the host where the instance resides. To
       contact the domain administration server (DAS), this subcommand
       requires the name of the host where the DAS is running. If a nondefault
       port is used for administration, this subcommand also requires the port
       number. You must provide this information through the --host option and
       the --port option of the asadmin(1M) utility.

       Importing an instance's configuration data transfers the data to a host
       for an instance without the need for the instance to be able to
       communicate with the DAS. Importing an instance's configuration data is
       typically required for the following reasons:

       *   To reestablish the instance after an upgrade

       *   To synchronize the instance manually with the domain administration
           server (DAS) when the instance cannot contact the DAS

       The subcommand imports an instance's configuration data by performing
       the following operations:

       *   Creating or updating the instance's files and directories

       *   Attempting to register the instance with the DAS

       If the attempt to register the instance with the DAS fails, the
       subcommand does not fail. Instead, the subcommand displays a warning
       that the attempt failed. The warning contains the command to run to
       register the instance with the DAS.

       The import-sync-bundle subcommand does not contact the DAS to determine
       the node on which the instance resides. If the node is not specified as
       an option of the subcommand, the subcommand determines the node from
       the DAS configuration in the archive file.

       This subcommand is supported in local mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --instance
           The instance for which configuration data is being imported. The
           instance must already exist in the DAS configuration. The archive
           file from which the data is being imported must contain data for
           the specified instance.

       --nodedir
           The directory that contains the instance's node directory. The
           instance's files are stored in the instance's node directory. The
           default is as-install/nodes.

       --node
           The node on which the instance resides. If this option is omitted,
           the subcommand determines the node from the DAS configuration in
           the archive file.

OPERANDS
       file-name
           The name of the file, including the path, that contains the archive
           file to import. This operand is required.

EXAMPLES
       Example 1, Importing Configuration Data for a Clustered Instance
           This example imports the configuration for the clustered instance
           ymli2 on the node sj02 from the archive file
           /export/glassfish3/glassfish/domains/domain1/sync/ymlcluster-sync-bundle.zip.

           The command is run on the host sj02, which is the host that the
           node sj02 represents. The DAS is running on the host sr04 and uses
           the default HTTP port for administration.

               sj02# asadmin --host sr04 import-sync-bundle --node sj02 --instance ymli2
               /export/glassfish3/glassfish/domains/domain1/sync/ymlcluster-sync-bundle.zip
               Command import-sync-bundle executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       export-sync-bundle(1)

       asadmin(1M)

Java EE 7                         7 Dec 2010             import-sync-bundle(1)
Command import-sync-bundle executed successfully.

DAS is offline. Could not set rendezvousOccurred property. Use the set command to set rendezvousOccurred property to true:
set servers.server.ins2.property.rendezvousOccurred=true.
Command import-sync-bundle executed successfully.

create-service(1)         asadmin Utility Subcommands        create-service(1)

NAME
       create-service - configures the starting of a DAS or a GlassFish Server
       instance on an unattended boot

SYNOPSIS
           create-service [--help] [--name service-name]
           [--serviceproperties service-properties]
           [--dry-run={false|true}] [--force={false|true}]
           [--serviceuser service-user]
           [--domaindir domain-dir]
           [--nodedir node-dir] [--node node]
           [domain-or-instance-name]

DESCRIPTION
       The create-service subcommand configures the starting of a domain
       administration server (DAS) or a GlassFish Server instance on an
       unattended boot on Windows, Linux, and Oracle Solaris systems.

       If no operand is specified and the domains directory contains only one
       domain, the subcommand configures the starting of the DAS for the
       default domain. If no operand is specified and the domains directory
       contains multiple domains, an error occurs.

       If the operand specifies an instance, the create-service subcommand
       does not contact the domain administration server (DAS) to determine
       the node on which the instance resides. To determine the node on which
       the instance resides, the subcommand searches the directory that
       contains the node directories. If multiple node directories exist, the
       node must be specified as an option of the subcommand.

       The subcommand contains internal logic to determine whether the
       supplied operand is a DAS or an instance.

       This subcommand is supported in local mode only.

   Behavior of create-service on Windows Systems
       On Windows systems, the create-service subcommand creates a Windows
       service to represent the DAS or instance. The service is created in the
       disabled state. After this subcommand creates the service, you must use
       the Windows Services Manager or the Windows Services Wrapper to start,
       stop, uninstall, or install the service.

       On Windows systems, this subcommand must be run as the OS-level
       administrator user.

       The subcommand creates the following Windows Services Wrapper files for
       the service in the domain-dir\bin directory or the instance-dir\bin
       directory:

       *   Configuration file: service-nameService.xml

       *   Executable file: service-nameService.exe

       On Windows systems, this subcommand requires the Microsoft .NET
       Framework

       (http://www.microsoft.com/net/) . Otherwise, the subcommand fails.

   Behavior of create-service on Linux Systems
       On Linux systems, the create-service subcommand creates a
       System-V-style initialization script
       /etc/init.d/GlassFish_domain-or-instance-name and installs a link to
       this script in the /etc/rc?.d directories. After this subcommand
       creates the script, you must use this script to start, stop, or restart
       the domain or instance.

       On Linux systems, this subcommand must be run as the OS-level root
       user.

   Behavior of create-service on Oracle Solaris Systems
       On Oracle Solaris systems, the create-service subcommand creates a
       Service Management Facility (SMF) service to represent the DAS or
       instance. The service is created in the disabled state. After this
       subcommand creates the service, you must use SMF commands to start,
       enable, disable, delete, or stop the service. For more information
       about SMF, see the following documentation for the Oracle Solaris
       operating system:

       *   "Managing Services (Overview)" in System Administration Guide:
           Basic Administration

       *   "Managing Services (Tasks)" in System Administration Guide: Basic
           Administration

       On Oracle Solaris systems, this subcommand must be run as the OS-level
       user with superuser privileges. The configuration file for the DAS or
       instance must be stored in a directory to which the superuser has
       access and cannot be stored on a network file system. The service that
       is created is controlled by the OS-level user who owns the directory
       where the configuration of the DAS or instance resides.

       On Oracle Solaris systems, the manifest file is created in the
       following directory by default:

           /var/svc/manifest/application/GlassFish/domain-or-instance-name_domain-or-instance-root-dir

       To run this subcommand, you must have solaris.smf.*  authorization. For
       information about how to grant authorizations to users, see the
       useradd(1M) and usermod(1M) man pages.

       To run these commands as non-root user, the system administrator must
       be contacted so that the relevant authorizations are granted. You must
       also ensure that the following conditions are met:

       *   Oracle Solaris 10 administration commands such as svccfg(1M),
           svcs(1), and auths(1) are available through the PATH statement, so
           that these commands can be executed. A simple test to do so is to
           run the command which svccfg in the shell.

       *   You must have write permission for the path
           /var/svc/manifest/application/GlassFish. Usually, the superuser has
           write permission to this path.

       If you delete a service that you created by using the create-service
       subcommand, you must delete the directory that contains the manifest
       file and the entire contents of the directory. Otherwise, an attempt to
       re-create the service by using the create-service subcommand fails. The
       Oracle Solaris command svccfg does not delete this directory.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --name
           (Windows and Oracle Solaris systems only) The name of the service
           that you will use when administering the service through Oracle
           Solaris SMF commands or the service management features of the
           Windows operating system. The default is the name of the domain or
           instance that is specified as the operand of this subcommand.

       --serviceproperties
           Specifies a colon(:)-separated list of various properties that are
           specific to the service.

           To customize the display name of the service in the Windows Service
           list, set the DISPLAY_NAME property to the required name.

           For Oracle Solaris 10 systems, if you specify net_privaddr, the
           service's processes will be able to bind to the privileged ports
           (<1024) on the platform. You can bind to ports< 1024 only if the
           owner of the service is superuser, otherwise, this is not allowed.

       --dry-run, -n
           Previews your attempt to create a service. Indicates issues and the
           outcome that will occur if you run the command without using the
           --dry-run option. Nothing is actually configured. Default is false.

       --force
           Specifies whether the service is created even if validation of the
           service fails.

           Possible values are as follows:

           true
               The service is created even if validation of the service fails.

           false
               The service is not created (default).

       --serviceuser
           (Linux systems only) The user that is to run the GlassFish Server
           software when the service is started. The default is the user that
           is running the subcommand. Specify this option if the GlassFish
           Server software is to be run by a user other than the root user.

       --domaindir
           The absolute path of the directory on the disk that contains the
           configuration of the domain. If this option is specified, the
           operand must specify a domain.

       --nodedir
           Specifies the directory that contains the instance's node
           directory. The instance's files are stored in the instance's node
           directory. The default is as-install/nodes. If this option is
           specified, the operand must specify an instance.

       --node
           Specifies the node on which the instance resides. This option may
           be omitted only if the directory that the --nodedir option
           specifies contains only one node directory. Otherwise, this option
           is required. If this option is specified, the operand must specify
           an instance.

OPERANDS
       domain-or-instance-name
           The name of the domain or instance to configure. If no operand is
           specified, the default domain is used.

EXAMPLES
       Example 1, Creating a Service on a Windows System
           This example creates a service for the default domain on a system
           that is running Windows.

               asadmin> create-service
               Found the Windows Service and successfully uninstalled it.
               The Windows Service was created successfully.  It is ready to be started.  Here are
               the details:
               ID of the service: domain1
               Display Name of the service:domain1 GlassFish Server
               Domain Directory: C:\glassfish3\glassfish\domains\domain1
               Configuration file for Windows Services Wrapper: C:\glassfish3\glassfish\domains\
               domain1\bin\domain1Service.xml
               The service can be controlled using the Windows Services Manager or you can use the
               Windows Services Wrapper instead:
               Start Command:  C:\glassfish3\glassfish\domains\domain1\bin\domain1Service.exe  start
               Stop Command:   C:\glassfish3\glassfish\domains\domain1\bin\domain1Service.exe  stop
               Uninstall Command:  C:\glassfish3\glassfish\domains\domain1\bin\domain1Service.exe
               uninstall
               Install Command:  C:\glassfish3\glassfish\domains\domain1\bin\domain1Service.exe
               install

               This message is also available in a file named PlatformServices.log in the domain's
               root directory
               Command create-service executed successfully.

       Example 2, Creating a Service on a Linux System
           This example creates a service for the default domain on a system
           that is running Linux.

               asadmin> create-service
               Found the Linux Service and successfully uninstalled it.
               The Service was created successfully. Here are the details:
               Name of the service:domain1
               Type of the service:Domain
               Configuration location of the service:/etc/init.d/GlassFish_domain1
               User account that will run the service: root
               You have created the service but you need to start it yourself.
               Here are the most typical Linux commands of interest:

               * /etc/init.d/GlassFish_domain1 start
               * /etc/init.d/GlassFish_domain1 stop
               * /etc/init.d/GlassFish_domain1 restart

               For your convenience this message has also been saved to this file:
               /export/glassfish3/glassfish/domains/domain1/PlatformServices.log
               Command create-service executed successfully.

       Example 3, Creating a Service on an Oracle Solaris System
           This example creates a service for the default domain on a system
           that is running Oracle Solaris.

               asadmin> create-service
               The Service was created successfully. Here are the details:
               Name of the service:application/GlassFish/domain1
               Type of the service:Domain
               Configuration location of the service:/home/gfuser/glassfish-installations
               /glassfish3/glassfish/domains
               Manifest file location on the system:/var/svc/manifest/application
               /GlassFish/domain1_home_gfuser_glassfish-installations_glassfish3
               _glassfish_domains/Domain-service-smf.xml.
               You have created the service but you need to start it yourself.
               Here are the most typical Solaris commands of interest:
               * /usr/bin/svcs -a | grep domain1 // status
               * /usr/sbin/svcadm enable domain1 // start
               * /usr/sbin/svcadm disable domain1 // stop
               * /usr/sbin/svccfg delete domain1 // uninstall
               Command create-service executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       asadmin(1M)

       auths(1), svcs(1)

       svccfg(1M), useradd(1M), usermod(1M)

       "Managing Services (Overview)" in System Administration Guide: Basic
       Administration, "Managing Services (Tasks)" in System Administration
       Guide: Basic Administration

       Microsoft .NET Framework (http://www.microsoft.com/net/)

Java EE 7                         8 Dec 2011                 create-service(1)
Command create-service executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help uptime [options] ...
uptime(1)                 asadmin Utility Subcommands                uptime(1)

NAME
       uptime - returns the length of time that the DAS has been running

SYNOPSIS
           uptime [--help]

DESCRIPTION
       The uptime subcommand returns the length of time that the domain
       administration server (DAS) has been running since it was last
       restarted.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

EXAMPLES
       Example 1, Showing How Long the DAS Has Been Running
           This example shows the length of time that the DAS has been
           running.

               asadmin> uptime
               Uptime: 2 days, 1 hours, 30 minutes, 18 seconds, Total milliseconds: 178218706
               Command uptime executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-domains(1), start-domain(1), stop-domain(1)

       asadmin(1M)

Java EE 7                         8 Sep 2009                         uptime(1)
Command uptime executed successfully.

Up 50 secs
Command uptime executed successfully.

verify-domain-xml(1)      asadmin Utility Subcommands     verify-domain-xml(1)

NAME
       verify-domain-xml - verifies the content of the domain.xml file

SYNOPSIS
           verify-domain-xml [--help]
           [--domaindir domain-dir] [domain-name]

DESCRIPTION
       Verifies the content of the domain.xml file by checking the following:

       *   That the domain.xml file can be parsed

       *   That the names for elements that have them are unique

       This subcommand is supported in local mode only.

OPTIONS
       -h --help
           Displays the help text for the subcommand.

       --domaindir
           Specifies the domain root directory, where the domains are located.
           The path must be accessible in the file system. The default is
           as-install/domains.

OPERANDS
       domain_name
           Specifies the name of the domain. The default is domain1.

EXAMPLES
       Example 1, Using verify-domain-xml

               asadmin> verify-domain-xml
               All Tests Passed.
               domain.xml is valid

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       asadmin(1M)

Java EE 7                         17 Nov 2010             verify-domain-xml(1)
Command verify-domain-xml executed successfully.

All tests passed; domain.xml is valid.
Command verify-domain-xml executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help generate-domain-schema [options] ...
NAME
     generate-domain-schema

SYNOPSIS
     Usage: generate-domain-schema [--format=html] [--showsubclas
     ses=false] [--showdeprecated=false] 

OPTIONS
     --format

     --showsubclasses

     --showdeprecated

Command generate-domain-schema executed successfully.

Finished generating html documentation in /home/cdctest/glassfish4_b80/glassfish/domains/domain1/config
Command generate-domain-schema executed successfully.

validate-multicast(1)     asadmin Utility Subcommands    validate-multicast(1)

NAME
       validate-multicast - validates that multicast transport is available
       for clusters

SYNOPSIS
           validate-multicast [--help] [--multicastport multicastport]
           [--multicastaddress multicastaddress]
           [--bindaddress bindaddress]
           [--sendperiod sendperiod]
           [--timeout timeout]
           [--timetolive timetolive]
           [--verbose={false|true}]

DESCRIPTION
       The validate-multicast subcommand validates that multicast transport is
       available for clusters. You should run this subcommand at the same time
       on each of the hosts to be validated. This subcommand is available in
       local mode.

           Note
           +----------------------------------------+
           |           Do not run the               |
           |           validate-multicast           |
           |           subcommand using the DAS and |
           |           cluster's multicast address  |
           |           and port values while the    |
           |           DAS and cluster are running. |
           |           Doing so results in an       |
           |           error.                       |
           |           The validate-multicast       |
           |           subcommand must be run at    |
           |           the same time on two or more |
           |           machines to validate whether |
           |           multicast messages are being |
           |           received between the         |
           |           machines.                    |
           +----------------------------------------+

       As long as all machines see each other, multicast is validated to be
       working properly across the machines. If the machines are not seeing
       each other, set the --bindaddress option explicitly to ensure that all
       machines are using interface on same subnet, or increase the
       --timetolive option from the default of 4. If these changes fail to
       resolve the multicast issues, ask the network administrator to verify
       that the network is configured so the multicast messages can be seen
       between all the machines used to run the cluster.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --multicastport
           The port for the multicast socket on which the Group Management
           Service (GMS) listens for group events. Specify a standard UDP port
           number in the range 2048-32000. The default is 2048.

       --multicastaddress
           The address for the multicast socket on which the GMS listens for
           group events. Specify a class D IP address. Class D IP addresses
           are in the range 224.0.0.0 to 239.255.255.255, inclusive. The
           address 224.0.0.0 is reserved and should not be used. The default
           is 228.9.3.1.

       --bindaddress
           The local interface to receive multicast datagram packets for the
           GMS. The default is to use all available binding interfaces.

           On a multi-home machine (possessing two or more network
           interfaces), this attribute enables you to indicate which network
           interface is used for the GMS. This value must be a local network
           interface IP address.

       --sendperiod
           The number of milliseconds between test messages sent between
           nodes. The default is 2000.

       --timeout
           The number of seconds before the subcommand times out and exits.
           The default is 20. You can also exit this subcommand using Ctrl-C.

       --timetolive
           The default time-to-live for multicast packets sent out on the
           multicast socket in order to control the scope of the multicasts.
           The time-to-live value must be between zero and 255 inclusive. The
           default is the JDK default or a minimum defined by a constant in
           the GMS subsystem, whichever is lower. To see the time-to-live
           value being used, use the --verbose option.

       --verbose
           If used without a value or set to true, provides additional
           debugging information. The default is false.

EXAMPLES
       Example 1, Validating multicast transport
           Run from host machine1:

               asadmin> validate-multicast
               Will use port 2,048
               Will use address 228.9.3.1
               Will use bind address null
               Will use wait period 2,000 (in milliseconds)

               Listening for data...
               Sending message with content "machine1" every 2,000 milliseconds
               Received data from machine1 (loopback)
               Received data from machine2
               Exiting after 20 seconds. To change this timeout, use the --timeout command line option.
               Command validate-multicast executed successfully
           Run from host machine2:

               asadmin> validate-multicast
               Will use port 2,048
               Will use address 228.9.3.1
               Will use bind address null
               Will use wait period 2,000 (in milliseconds)

               Listening for data...
               Sending message with content "machine2" every 2,000 milliseconds
               Received data from machine2 (loopback)
               Received data from machine1
               Exiting after 20 seconds. To change this timeout, use the --timeout command line option.
               Command validate-multicast executed successfully

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       get-health(1)

       asadmin(1M)

Java EE 7                         10 Feb 2011            validate-multicast(1)
Command validate-multicast executed successfully.

asadmin(1M)                    Utility Commands                    asadmin(1M)

NAME
       asadmin - utility for performing administrative tasks for Oracle
       GlassFish Server

SYNOPSIS
           asadmin [--host host]
           [--port port]
           [--user admin-user]
           [--passwordfile filename]
           [--terse={true|false}]
           [--secure={false|true}]
           [--echo={true|false}]
           [--interactive={true|false}]
           [--detach={true|false}]
           [--help]
           [subcommand [options] [operands]]

DESCRIPTION
       Use the asadmin utility to perform administrative tasks for Oracle
       GlassFish Server. You can use this utility instead of the
       Administration Console interface.

   Subcommands of the asadmin Utility
       The subcommand identifies the operation or task that you are
       performing. Subcommands are case-sensitive. Each subcommand is either a
       local subcommand or a remote subcommand.

       *   A local subcommand can be run without a running domain
           administration server (DAS). However, to run the subcommand and
           have access to the installation directory and the domain directory,
           the user must be logged in to the machine that hosts the domain.

       *   A remote subcommand is always run by connecting to a DAS and
           running the subcommand there. A running DAS is required.

   asadmin Utility Options and Subcommand Options
       Options control the behavior of the asadmin utility and its
       subcommands. Options are also case-sensitive.

       The asadmin utility has the following types of options:

       *   asadmin utility options.  These options control the behavior of the
           asadmin utility, not the subcommand. The asadmin utility options
           may precede or follow the subcommand, but asadmin utility options
           after the subcommand are deprecated. All asadmin utility options
           must either precede or follow the subcommand. If asadmin utility
           options are specified both before and after the subcommand, an
           error occurs. For a description of the asadmin utility options, see
           the "Options" section of this help information.

       *   Subcommand options.  These options control the behavior of the
           subcommand, not the asadmin utility. Subcommand options must follow
           the subcommand. For a description of a subcommand's options, see
           the help information for the subcommand.

       A subcommand option may have the same name as an asadmin utility
       option, but the effects of the two options are different.

       The asadmin utility options and some subcommand options have a long
       form and a short form.

       *   The long form of an option has two dashes (--) followed by an
           option word.

       *   The short form of an option has a single dash (-) followed by a
           single character.

       For example, the long form and the short form of the option for
       specifying terse output are as follows:

       *   Long form: --terse

       *   Short form: -t

       Most options require argument values, except Boolean options, which
       toggle to enable or disable a feature.

   Operands of asadmin Subcommands
       Operands specify the items on which the subcommand is to act. Operands
       must follow the argument values of subcommand options, and are set off
       by a space, a tab, or double dashes (--). The asadmin utility treats
       anything that follows the subcommand options and their values as an
       operand.

   Escape Characters in Options for the asadmin Utility
       Escape characters are required in options of the asadmin utility for
       the following types of characters:

       *   Meta characters in the UNIX operating system.  These characters
           have special meaning in a shell. Meta characters in the UNIX
           operating system include: \/,.!$%^&*|{}[]"'`~;.

           To disable these characters, use the backslash (\) escape character
           or enclose the entire command-line argument in single quote (')
           characters.

           The following examples illustrate the effect of escape characters
           on the * character. In these examples, the current working
           directory is the domains directory.

           *   The following command, without the escape character, echoes all
               files in the current directory:

                   prompt% echo *
                   domain1 domain2

           *   The following command, in which the backslash (\) escape
               character precedes the * character, echoes the * character:

                   prompt% echo \*
                   *

           *   The following command, in which the * character is enclosed in
               single quote (') characters, echoes the * character:

                   prompt% echo '*'
                   *

           The escape character is also a special character in the UNIX
           operating system and in the Java language. Therefore, in the UNIX
           operating system and in multimode, you must apply an additional
           escape character to every escape character in the command line.
           This requirement does not apply to the Windows operating system.

           For example, the backslash (\) UNIX operating system meta character
           in the option argument Test\Escape\Character is specified on UNIX
           and Windows systems as follows:

           *   On UNIX systems, each backslash must be escaped with a second
               backslash:

                   Test\\Escape\\Character

           *   On Windows systems, no escape character is required:

                   Test\Escape\Character

               Note
               +----------------------------------------+
               |In contexts where meta characters in    |
               |the UNIX operating system are           |
               |unambiguous, these characters do not    |
               |require escape characters. For example, |
               |in the set(1) subcommand, the value     |
               |that is to be set is specified as       |
               |name=value. Because name can never      |
               |include an equals sign, no escape       |
               |character is required to disable the    |
               |equals sign. Therefore, everything      |
               |after the equals sign is an             |
               |uninterpreted string that the set       |
               |subcommand uses unchanged.              |
               +----------------------------------------+

       *   Spaces.  The space is the separator in the command-line interface.
           To distinguish a space in a command-line argument from the
           separator in the command-line interface, the space must be escaped
           as follows:

           *   For the UNIX operating system in single mode and multimode, and
               for all operating systems in multimode, use the backslash (\)
               escape character or enclose the entire command-line argument in
               single quote (') characters or double quote (") characters.

           *   For the Windows operating system in single mode, enclose the
               entire command-line argument in double quote (") characters.

       *   Option delimiters.  The asadmin utility uses the colon character
           (:) as a delimiter for some options. The backslash (\) escape
           character is required if the colon is part of any of the following
           items:

           *   A property

           *   An option of the Virtual Machine for the Java platform (Java
               Virtual Machine or JVM machine)The terms "Java Virtual Machine"
               and "JVM" mean a Virtual Machine for the Java platform.

           For example, the operand of the subcommand create-jvm-options(1)
           specifies JVM machine options in the following format:

               (jvm-option-name[=jvm-option-value])
               [:jvm-option-name[=jvm-option-value]]*
           Multiple JVM machine options in the operand of the
           create-jvm-options subcommand are separated by the colon (:)
           delimiter. If jvm-option-name or jvm-option-value contains a colon,
           the backslash (\) escape character is required before the colon.

           The backslash (\) escape character is also required before a single
           quote (') character or a double quote (") character in an option
           that uses the colon as a delimiter.

           When used without single quote (') characters, the escape character
           disables the option delimiter in the command-line interface.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the colon character and the
           backslash character in an option that uses the colon as a delimiter
           must be specified as follows:

           *   To pass a literal backslash to a subcommand, two backslashes
               are required. Therefore, the colon (:) must be escaped by two
               backslashes (\\).

           *   To prevent a subcommand from treating the backslash as a
               special character, the backslash must be escaped. As a result,
               two literal backslashes (\\) must be passed to the subcommand.
               To prevent the shell from interpreting these backslashes as
               special characters, each backslash must be escaped. Therefore,
               the backslash must be specified by a total of four backslashes
               (\\\\).

           For the Windows operating system in single mode, a backslash (\) is
           required to escape the colon (:) and the backslash (\) in an option
           that uses the colon as a delimiter.

       Instead of using the backslash (\) escape character, you can use the
       double quote (") character or single quote (') character. The effects
       of the different types of quote characters on the backslash (\)
       character are as follows:

       *   Between double quote (") characters, the backslash (\) character is
           a special character.

       *   Between single quote (') characters, the backslash (\) character is
           not a special character.

   Requirements for Using the --secure Option
       The requirements for using the --secure option are as follows:

       *   The domain that you are administering must be configured for
           security.

       *   The security-enabled attribute of the http-listener element in the
           DAS configuration must be set to true.

           To set this attribute, use the set subcommand.

   Server Restart After Creation or Deletion
       When you use the asadmin subcommands to create or delete a
       configuration item, you must restart the DAS for the change to take
       effect. To restart the DAS, use the restart-domain(1) subcommand.

   Help Information for Subcommands and the asadmin Utility
       To obtain help information for an asadmin utility subcommand, specify
       the subcommand of interest as the operand of the help subcommand. For
       example, to obtain help information for the start-domain(1) subcommand,
       type:

           asadmin help start-domain

       If you run the help subcommand without an operand, this help
       information for the asadmin utility is displayed.

       To obtain a listing of available asadmin subcommands, use the
       list-commands(1) subcommand.

OPTIONS
       --host, -H
           The machine name where the DAS is running. The default value is
           localhost.

       --port, -p
           The HTTP port or HTTPS port for administration. This port is the
           port in the URL that you specify in your web browser to manage the
           domain. For example, in the URL http://localhost:4949, the port is
           4949.

           The default port number for administration is 4848.

       --user, -u
           The user name of the authorized administrative user of the DAS.

           If you have authenticated to a domain by using the asadmin login
           command, you need not specify the --user option for subsequent
           operations on the domain.

       --passwordfile, -W
           Specifies the name, including the full path, of a file that
           contains password entries in a specific format.

           The entry for a password must have the AS_ADMIN_ prefix followed by
           the password name in uppercase letters, an equals sign, and the
           password.

           The entries in the file that are read by the asadmin utility are as
           follows:

           *   AS_ADMIN_PASSWORD=administration-password

           *   AS_ADMIN_MASTERPASSWORD=master-password

           The entries in this file that are read by subcommands are as
           follows:

           *   AS_ADMIN_NEWPASSWORD=new-administration-password (read by the
               start-domain(1) subcommand)

           *   AS_ADMIN_USERPASSWORD=user-password (read by the
               create-file-user(1) subcommand)

           *   AS_ADMIN_ALIASPASSWORD=alias-password (read by the
               create-password-alias(1) subcommand)

           *   AS_ADMIN_MAPPEDPASSWORD=mapped-password (read by the
               create-connector-security-map(1) subcommand)

           *   AS_ADMIN_WINDOWSPASSWORD=windows-password (read by the
               create-node-dcom(1), install-node-dcom(1), and
               update-node-dcom(1) subcommands)

           *   AS_ADMIN_SSHPASSWORD=sshd-password (read by the
               create-node-ssh(1), install-node(1), install-node-ssh(1), and
               update-node-ssh(1) subcommands)

           *   AS_ADMIN_SSHKEYPASSPHRASE=sshd-passphrase (read by the
               create-node-ssh(1), install-node(1), install-node-ssh(1), and
               update-node-ssh(1) subcommands)

           *   AS_ADMIN_JMSDBPASSWORD= jdbc-user-password (read by the
               configure-jms-cluster(1) subcommand)

           These password entries are stored in clear text in the password
           file. To provide additional security, the create-password-alias
           subcommand can be used to create aliases for passwords that are
           used by remote subcommands. The password for which the alias is
           created is stored in an encrypted form. If an alias exists for a
           password, the alias is specified in the entry for the password as
           follows:

               AS_ADMIN_password-name=${ALIAS=password-alias-name}
           For example:

               AS_ADMIN_SSHPASSWORD=${ALIAS=ssh-password-alias}
               AS_ADMIN_SSHKEYPASSPHRASE=${ALIAS=ssh-key-passphrase-alias}
           In domains that do not allow unauthenticated login, all remote
           subcommands must specify the administration password to
           authenticate to the DAS. The password can be specified by one of
           the following means:

           *   Through the --passwordfile option

           *   Through the login(1) subcommand

           *   Interactively at the command prompt

           The login subcommand can be used to specify only the administration
           password. For other passwords that remote subcommands require, use
           the --passwordfile option or specify them at the command prompt.

           After authenticating to a domain by using the asadmin login
           command, you need not specify the administration password through
           the --passwordfile option for subsequent operations on the domain.
           However, only the AS_ADMIN_PASSWORD option is not required. You
           still must provide the other passwords, for example,
           AS_ADMIN_USERPASSWORD, when required by individual subcommands,
           such as update-file-user(1).

           For security reasons, a password that is specified as an
           environment variable is not read by the asadmin utility.

           The master password is not propagated on the command line or an
           environment variable, but can be specified in the file that the
           --passwordfile option specifies.

           The default value for AS_ADMIN_MASTERPASSWORD is changeit.

       --terse, -t
           If true, output data is very concise and in a format that is
           optimized for use in scripts instead of for reading by humans.
           Typically, descriptive text and detailed status messages are also
           omitted from the output data. Default is false.

       --secure, -s
           If set to true, uses SSL/TLS to communicate with the DAS.

           The default is false.

       --echo, -e
           If set to true, the command-line statement is echoed on the
           standard output. Default is false.

       --interactive, -I
           If set to true, only the required options are prompted.

           The default depends on how the asadmin utility is run:

           *   If the asadmin utility is run from a console window, the
               default is true.

           *   If the asadmin utility is run without a console window, for
               example, from within a script, the default is false.

       --detach
           If set to true, the specified asadmin subcommand is detached and
           executed in the background in detach mode. The default value is
           false.

           The --detach option is useful for long-running subcommands and
           enables you to execute several independent subcommands from one
           console or script.

           The --detach option is specified before the subcommand. For
           example, in single mode, asadmin --detach subcommand.

           Job IDs are assigned to subcommands that are started using asadmin
           --detach. You can use the list-jobs(1) subcommand to view the jobs
           and their job IDs, the attach(1) subcommand to reattach to the job
           and view its status and output, and the configure-managed-jobs(1)
           subcommand to configure how long information about the jobs is
           kept.

       --help, -?
           Displays the help text for the asadmin utility.

EXAMPLES
       Example 1, Running an asadmin Utility Subcommand in Single Mode
           This example runs the list-applications(1) subcommand in single
           mode. In this example, the default values for all options are used.

           The example shows that the application hello is deployed on the
           local host.

               asadmin list-applications
               hello <web>

               Command list-applications executed successfully.

       Example 2, Specifying an asadmin Utility Option With a Subcommand
           This example specifies the --host asadmin utility option with the
           list-applications subcommand in single mode. In this example, the
           DAS is running on the host srvr1.example.com.

           The example shows that the applications basic-ezcomp, scrumtoys,
           ejb31-war, and automatic-timer-ejb are deployed on the host
           srvr1.example.com.

               asadmin --host srvr1.example.com list-applications
               basic-ezcomp <web>
               scrumtoys <web>
               ejb31-war <ejb, web>
               automatic-timer-ejb <ejb>

               Command list-applications executed successfully.

       Example 3, Specifying an asadmin Utility Option and a Subcommand Option
           This example specifies the --host asadmin utility option and the
           --type subcommand option with the list-applications subcommand in
           single mode. In this example, the DAS is running on the host
           srvr1.example.com and applications of type web are to be listed.

               asadmin --host srvr1.example.com list-applications --type web
               basic-ezcomp <web>
               scrumtoys <web>
               ejb31-war <ejb, web>

               Command list-applications executed successfully.

       Example 4, Escaping a Command-Line Argument With Single Quote
       Characters
           The commands in this example specify the backslash (\) UNIX
           operating system meta character and the colon (:) option delimiter
           in the property value c:\extras\pmdapp.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the backslash (\) is required
           to escape the backslash (\) meta character and the colon (:) option
           delimiter:

               asadmin deploy --property extras.home='c\:\\extras\\pmdapp' pmdapp.war
               Application deployed with name pmdapp.
               Command deploy executed successfully
           For the Windows operating system in single mode, the single quote
           (') characters eliminate the need for other escape characters:

               asadmin deploy --property extras.home='c:\extras\pmdapp' pmdapp.war
               Application deployed with name pmdapp.
               Command deploy executed successfully

       Example 5, Specifying a UNIX Operating System Meta Character in an
       Option
           The commands in this example specify the backslash (\) UNIX
           operating system meta character in the option argument
           Test\Escape\Character.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the backslash (\) is required
           to escape the backslash (\) meta character:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname sampleClassName
               --description Test\\Escape\\Character
               sampleJDBCConnectionPool
           For the Windows operating system in single mode, no escape
           character is required:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname sampleClassName
               --description Test\Escape\Character
               sampleJDBCConnectionPool

       Example 6, Specifying a Command-Line Argument That Contains a Space
           The commands in this example specify spaces in the operand
           C:\Documents and Settings\gfuser\apps\hello.war.

           For all operating systems in single mode or multimode, the entire
           operand can be enclosed in double quote (") characters:

               asadmin deploy "C:\Documents and Settings\gfuser\apps\hello.war"
               Application deployed with name hello.
               Command deploy executed successfully.
           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the entire command-line
           argument can be enclosed in single quote (') characters:

               asadmin> deploy 'C:\Documents and Settings\gfuser\apps\hello.war'
               Application deployed with name hello.
               Command deploy executed successfully.
           Alternatively, for the UNIX operating system in single mode and
           multimode, and for all operating systems in multimode, the
           backslash (\) escape character can be used before each space in the
           operand. In this situation, the backslash (\) escape character is
           required before each backslash in the operand:

               asadmin> deploy C:\\Documents\ and\ Settings\\gfuser\\apps\\hello.war
               Application deployed with name hello.
               Command deploy executed successfully.

       Example 7, Specifying a Meta Character and an Option Delimiter
       Character in a Property
           The commands in this example specify the backslash (\) UNIX
           operating system meta character and the colon (:) option delimiter
           character in the --property option of the
           create-jdbc-connection-pool(1) subcommand.

           The name and value pairs for the --property option are as follows:

               user=dbuser
               passwordfile=dbpasswordfile
               DatabaseName=jdbc:derby
               server=http://localhost:9092
           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, a backslash (\) is required to
           escape the colon (:) and the backslash (\):

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property user=dbuser:passwordfile=dbpasswordfile:
               DatabaseName=jdbc\\:derby:server=http\\://localhost\\:9092 javadb-pool
           Alternatively, the entire argument to the --property option can be
           enclosed in single quote (') characters:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property 'user=dbuser:passwordfile=dbpasswordfile:
               DatabaseName="jdbc:derby":server="http://localhost:9092"' javadb-pool
           For the Windows operating system in single mode, a backslash (\) is
           required to escape only the colon (:), but not the backslash (\):

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property user-dbuser:passwordfile-dbpasswordfile:
               DatabaseName=jdbc\:derby:server=http\://localhost\:9092 javadb-pool
           For all operating systems, the need to escape the colon (:) in a
           value can be avoided by enclosing the value in double quote
           characters or single quote characters:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property user=dbuser:passwordfile=dbpasswordfile:
               DatabaseName=\"jdbc:derby\":server=\"http://localhost:9092\" javadb-pool

       Example 8, Specifying an Option Delimiter and an Escape Character in a
       JVM Machine Option
           The commands in this example specify the following characters in
           the -Dlocation=c:\sun\appserver JVM machine option:

           *   The colon (:) option delimiter

           *   The backslash (\) escape character

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, these characters must be
           specified as follows:

           *   To pass a literal backslash to a subcommand, two backslashes
               are required. Therefore, the colon (:) must be escaped by two
               backslashes (\\).

           *   To prevent the subcommand from treating the backslash as a
               special character, the backslash must be escaped. As a result,
               two literal backslashes (\\) must be passed to the subcommand.
               To prevent the shell from interpreting these backslashes as
               special characters, each backslash must be escaped. Therefore,
               the backslash must be specified by a total of four backslashes
               (\\\\).

           The resulting command is as follows:

               asadmin create-jvm-options --target test-server
               -e -Dlocation=c\\:\\\\sun\\\\appserver
           For the Windows operating system in single mode, a backslash (\) is
           required to escape the colon (:) and the backslash (\):

               asadmin create-jvm-options --target test-server
               -e -Dlocation=c\:\\sun\\appserver

       Example 9, Specifying an Option That Contains an Escape Character
           The commands in this example specify the backslash (\) character
           and the double quote (") characters in the
           "Hello\App"\authentication option argument.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, a backslash (\) is required to
           escape the double quote character (") and the backslash (\):

               asadmin set-web-env-entry --name="Hello User" --type=java.lang.String
               --value=techscribe --description=\"Hello\\App\"\\authentication hello
           For the Windows operating system in single mode, a backslash (\) is
           required to escape only the double quote ("), but not the backslash
           (\):

               asadmin set-web-env-entry --name="Hello User" --type=java.lang.String
               --value=techscribe --description=\"Hello\App\"\authentication hello

ENVIRONMENT VARIABLES
       Environment variables modify the default values of asadmin utility
       options as shown in the following table.

       +-----------------------------+------------------------+
       |       Environment           |        asadmin Utility |
       |       Variable              |        Option          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_TERSE        |        --terse         |
       +-----------------------------+------------------------+
       |       AS_ADMIN_ECHO         |        --echo          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_INTERACTIVE  |        --interactive   |
       +-----------------------------+------------------------+
       |       AS_ADMIN_HOST         |        --host          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_PORT         |        --port          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_SECURE       |        --secure        |
       +-----------------------------+------------------------+
       |       AS_ADMIN_USER         |        --user          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_PASSWORDFILE |        --passwordfile  |
       +-----------------------------+------------------------+
       |       AS_ADMIN_HELP         |        --help          |
       +-----------------------------+------------------------+

ATTRIBUTES
       See attributes(5) for descriptions of the following attributes:

       +---------------------------+------------------------+
       |       ATTRIBUTE TYPE      |        ATTRIBUTE VALUE |
       +---------------------------+------------------------+
       |       Interface Stability |        Unstable        |
       +---------------------------+------------------------+

SEE ALSO
       attach(1), configure-jms-cluster(1), configure-managed-jobs(1),
       create-connector-security-map(1), create-file-user(1),
       create-jdbc-connection-pool(1), create-jvm-options(1),
       create-node-dcom(1), create-node-ssh(1), create-password-alias(1),
       deploy(1), install-node(1), install-node-dcom(1), install-node-ssh(1),
       list-applications(1), list-commands(1), list-jobs(1), login(1),
       restart-domain(1), set(1), set-web-env-entry(1), start-domain(1),
       update-file-user(1), update-node-dcom(1), update-node-ssh(1)

       attributes(5)

Java EE 7                         12 Feb 2013                      asadmin(1M)
Command help executed successfully.

Version string could not be obtained from Server [localhost:4848].
(Turn debugging on e.g. by setting AS_DEBUG=true in your environment, to see the details.)
Using locally retrieved version string from version class.
Version = GlassFish Server Open Source Edition  4.0  (build 80)
Command version executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass login [options] ...
Login information is not saved for host name [localhost] and port [4848]
Command login executed successfully.

********** Local Commands **********
backup-domain
change-admin-password
change-master-password
create-domain
create-local-instance
create-service
delete-domain
delete-local-instance
export
export
help
help
import-sync-bundle
install-node
install-node-dcom
install-node-ssh
list-backups
list-commands
list-commands
list-domains
login
login
monitor
multimode
multimode
osgi-shell
restart-domain
restart-local-instance
restore-domain
setup-local-dcom
setup-ssh
start-database
start-domain
start-local-instance
stop-database
stop-domain
stop-local-instance
uninstall-node
uninstall-node-dcom
uninstall-node-ssh
unset
unset
validate-multicast
verify-domain-xml
version
version

********** Remote Commands **********
add-library                             enable
add-resources                           enable-http-lb-application
apply-http-lb-changes                   enable-http-lb-server
attach                                  enable-monitoring
change-master-broker                    enable-secure-admin
collect-log-files                       enable-secure-admin-internal-user
configure-batch-runtime                 enable-secure-admin-principal
configure-jms-cluster                   export-http-lb-config
configure-lb-weight                     export-sync-bundle
configure-ldap-for-admin                flush-connection-pool
configure-managed-jobs                  flush-jmsdest
copy-config                             freeze-transaction-service
create-admin-object                     generate-domain-schema
create-application-ref                  generate-jvm-report
create-audit-module                     generate-rest-client
create-auth-realm                       get
create-cluster                          get-active-module-config
create-connector-connection-pool        get-client-stubs
create-connector-resource               get-health
create-connector-security-map           jms-ping
create-connector-work-security-map      list
create-context-service                  list-admin-objects
create-custom-resource                  list-application-refs
create-file-user                        list-applications
create-http                             list-audit-modules
create-http-health-checker              list-auth-realms
create-http-lb                          list-batch-job-executions
create-http-lb-config                   list-batch-job-steps
create-http-lb-ref                      list-batch-jobs
create-http-listener                    list-batch-runtime-configuration
create-http-redirect                    list-clusters
create-iiop-listener                    list-components
create-instance                         list-configs
create-jacc-provider                    list-connector-connection-pools
create-javamail-resource                list-connector-resources
create-jdbc-connection-pool             list-connector-security-maps
create-jdbc-resource                    list-connector-work-security-maps
create-jms-host                         list-containers
create-jms-resource                     list-context-services
create-jmsdest                          list-custom-resources
create-jndi-resource                    list-file-groups
create-jvm-options                      list-file-users
create-lifecycle-module                 list-http-lb-configs
create-managed-executor-service         list-http-lbs
create-managed-scheduled-executor-service list-http-listeners
create-managed-thread-factory           list-iiop-listeners
create-message-security-provider        list-instances
create-module-config                    list-jacc-providers
create-network-listener                 list-javamail-resources
create-node-config                      list-jdbc-connection-pools
create-node-dcom                        list-jdbc-resources
create-node-ssh                         list-jms-hosts
create-password-alias                   list-jms-resources
create-profiler                         list-jmsdest
create-protocol                         list-jndi-entries
create-protocol-filter                  list-jndi-resources
create-protocol-finder                  list-jobs
create-resource-adapter-config          list-jvm-options
create-resource-ref                     list-libraries
create-ssl                              list-lifecycle-modules
create-system-properties                list-log-attributes
create-threadpool                       list-log-levels
create-transport                        list-loggers
create-virtual-server                   list-managed-executor-services
delete-admin-object                     list-managed-scheduled-executor-services
delete-application-ref                  list-managed-thread-factories
delete-audit-module                     list-message-security-providers
delete-auth-realm                       list-modules
delete-cluster                          list-network-listeners
delete-config                           list-nodes
delete-connector-connection-pool        list-nodes-config
delete-connector-resource               list-nodes-dcom
delete-connector-security-map           list-nodes-ssh
delete-connector-work-security-map      list-password-aliases
delete-context-service                  list-persistence-types
delete-custom-resource                  list-protocol-filters
delete-file-user                        list-protocol-finders
delete-http                             list-protocols
delete-http-health-checker              list-resource-adapter-configs
delete-http-lb                          list-resource-refs
delete-http-lb-config                   list-secure-admin-internal-users
delete-http-lb-ref                      list-secure-admin-principals
delete-http-listener                    list-sub-components
delete-http-redirect                    list-supported-cipher-suites
delete-iiop-listener                    list-system-properties
delete-instance                         list-threadpools
delete-jacc-provider                    list-timers
delete-javamail-resource                list-transports
delete-jdbc-connection-pool             list-virtual-servers
delete-jdbc-resource                    list-web-context-param
delete-jms-host                         list-web-env-entry
delete-jms-resource                     migrate-timers
delete-jmsdest                          osgi
delete-jndi-resource                    ping-connection-pool
delete-jvm-options                      ping-node-dcom
delete-lifecycle-module                 ping-node-ssh
delete-log-levels                       recover-transactions
delete-managed-executor-service         redeploy
delete-managed-scheduled-executor-service remove-library
delete-managed-thread-factory           restart-instance
delete-message-security-provider        rollback-transaction
delete-module-config                    rotate-log
delete-network-listener                 set
delete-node-config                      set-log-attributes
delete-node-dcom                        set-log-file-format
delete-node-ssh                         set-log-levels
delete-password-alias                   set-web-context-param
delete-profiler                         set-web-env-entry
delete-protocol                         show-component-status
delete-protocol-filter                  start-cluster
delete-protocol-finder                  start-instance
delete-resource-adapter-config          stop-cluster
delete-resource-ref                     stop-instance
delete-ssl                              undeploy
delete-system-property                  unfreeze-transaction-service
delete-threadpool                       unset-web-context-param
delete-transport                        unset-web-env-entry
delete-virtual-server                   update-connector-security-map
deploy                                  update-connector-work-security-map
deploydir                               update-file-user
disable                                 update-node-config
disable-http-lb-application             update-node-dcom
disable-http-lb-server                  update-node-ssh
disable-monitoring                      update-password-alias
disable-secure-admin                    uptime
disable-secure-admin-internal-user      validate-dcom
disable-secure-admin-principal          

Command list-commands executed successfully.

Nothing to list.
No applications are deployed to this target server.
Command list-components executed successfully.

List all known application containers
jpa
jpa
grizzly
security
osgi
web
weld
weld
connector
appclient
ear
ejb
webservices
resources
resources_ear
Command list-containers executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-modules [options] ...
list-modules(1)           asadmin Utility Subcommands          list-modules(1)

NAME
       list-modules - lists GlassFish Server modules

SYNOPSIS
           list-modules [--help]

DESCRIPTION
       The list-modules subcommand displays a list of modules that are
       accessible to the GlassFish Server module subsystem. The version of
       each module is shown.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

EXAMPLES
       Example 1, Listing GlassFish Server Modules
           This example provides a partial listing of modules that are
           accessible to the GlassFish Server module subsystem

               asadmin> list-modules
               List Of Modules

               Module : org.glassfish.transaction.jts:3.0.0.b66
                   Module Characteristics : List of Jars implementing the module
                       Jar : file:/home/gfuser/GlassFish/glassfishv3/glassfish/modules/jts.jar
                   Module Characteristics : Provides to following services
                   Module Characteristics : List of imported modules
                       Imports : org.glassfish.transaction.jts:3.0.0.b66
               Module : com.sun.enterprise.tiger-types-osgi:0.3.96
               Module : org.glassfish.bean-validator:3.0.0.JBoss-400Beta3A
               Module : org.glassfish.core.kernel:3.0.0.b66
                   Module Characteristics : Provides to following services
                   Module Characteristics : List of imported modules
                       Imports : org.glassfish.core.kernel:3.0.0.b66
                   Module Characteristics : List of Jars implementing the module
                       Jar : file:/home/gfuser/GlassFish/glassfishv3/glassfish/modules/kernel.jar
               Module : org.glassfish.common.util:3.0.0.b66
                   Module Characteristics : List of Jars implementing the module
                       Jar : file:/home/gfuser/GlassFish/glassfishv3/glassfish/modules/common-util.jar
                   Module Characteristics : Provides to following services
                   Module Characteristics : List of imported modules
                       Imports : org.glassfish.common.util:3.0.0.b66
               ...
               Command list-modules executed successfully

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-commands(1), list-components(1), list-containers(1)

       asadmin(1M)

Java EE 7                         9 Oct 2009                   list-modules(1)
Command list-modules executed successfully.

List Of Modules
Module Status Report Begins
OSGiModuleImpl:: Bundle = [org.glassfish.main.concurrent.admin [233]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-jts-plugin [231]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.dataprovider [164]], State = [READY]
OSGiModuleImpl:: Bundle = [javax.servlet-api [61]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-community-branding-plugin [248]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.connectors.internal-api [176]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.class-model [334]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.gf-restadmin-connector [91]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.web.javax.servlet.jsp [302]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.services [275]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-ejb-container [360]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.registration.registration-impl [312]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.fileinstall [346]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.config [122]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.websecurity [111]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.flashlight.framework [106]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.gogo.command [359]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.batch.spi-impl [20]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.appclient.server.appclient-server-core [175]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.deployment.admin [39]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.transaction.jts [253]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.utils [51]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.cluster.gms-bootstrap [27]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.gf-jpa-connector [216]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.grizzly.glassfish-grizzly-extra-all [55]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.grizzly.nucleus-grizzly-all [276]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.orb.enabler [38]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.ee [59]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.cli [89]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.javax.el [214]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.util [133]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.jsf-connector [94]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-jca-plugin [12]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.registration.registration-api [130]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.bundlerepository [256]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.glassfish-naming [293]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.batch.connector [321]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.osgi-platforms.osgi-container [200]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-javaee-base [349]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.connectors.admin [114]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.config-api [291]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-concurrent-plugin [107]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-jpa [347]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.core.javaee-kernel [295]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.gf-web-connector [169]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.deployment.javaee-core [268]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.transaction.jta [262]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.external.bean-validator [230]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-cluster-plugin [317]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.runlevel [49]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.locator [166]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.ha [251]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.gf-weld-connector [263]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.deployment.common [212]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.deployment.autodeploy [160]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-cdi [345]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.hk2 [141]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.internal-api [62]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.deployment.deployment-client [18]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.connectors.runtime [144]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.glassfish-osgi-console-plugin [155]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.connectors.gf-connectors-connector [25]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.monitoring-core [260]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.loadbalancer.gf-load-balancer-connector [48]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.osgi-platforms.osgi-cli-remote [204]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.osgi-resource-locator [4]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.appclient.server.appclient-connector [104]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.ssl-impl [331]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.core [278]], State = [READY]
OSGiModuleImpl:: Bundle = [com.sun.pkg.client [16]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.transaction.internal-api [274]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-ejb-plugin [154]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.deployment.javaee-full [31]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.glassfish-api [116]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.resources.javamail-connector [167]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.scr [348]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.weld-integration [117]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.ejb.gf-ejb-connector [22]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.osgi-platforms.felix-webconsole-extension [361]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-jdbc-plugin [299]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-plugin-service [54]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.cli [211]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-ejb-lite-plugin [341]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.jdbc.config [80]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-jpa-extension [68]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.metro.webservices-api-osgi [1]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-common-full-plugin [232]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.jms.gf-jms-connector [162]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.core.glassfish [153]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-corba-plugin [223]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-web-plugin [171]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.war-util [136]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-http [356]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.core [189]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.gogo.runtime [358]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.registration.glassfish-registration [279]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.external.cglib [179]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.naming [267]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.jms.admin [96]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.core.kernel [36]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.jms.core [192]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.gui-plugin-common [10]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.webservices.connector [132]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security [57]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.container-common [78]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.loadbalancer.load-balancer-admin [165]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-web-container [353]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.jdbc.admin [252]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.jspcaching-connector [37]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-jdbc [355]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-ee-resources [344]], State = [READY]
OSGiModuleImpl:: Bundle = [com.sun.jsftemplating [156]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-updatecenter-plugin [209]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.jstl-connector [6]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.eventadmin [351]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.cluster.ssh [240]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.cluster.admin [272]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-jms-plugin [149]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.resourcebase.resources.nucleus-resources [41]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.glue [322]], State = [READY]
OSGiModuleImpl:: Bundle = [javax.servlet.jsp-api [174]], State = [READY]
OSGiModuleImpl:: Bundle = [jaxb-api [2]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.webservices.jsr109-impl [53]], State = [READY]
OSGiModuleImpl:: Bundle = [javax.annotation-api [3]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.ejb.ejb-container [140]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.webconsole [350]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.rest-service [205]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.osgi-adapter [294]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.deployment.dol [184]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.gogo.shell [357]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.util [206]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.concurrent.config [310]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.fighterfish.osgi-jta [352]], State = [READY]
OSGiModuleImpl:: Bundle = [org.apache.felix.configadmin [354]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.external.javax.inject [81]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.api [225]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.glassfish-mbeanserver [46]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.cluster.gms-adapter [145]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.orb.connector [73]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.core.logging [67]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.resources.connector [44]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.external.asm-all-repackaged [306]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.console-common [261]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.main.ha.shoal-cache-bootstrap [95]], State = [READY]
OSGiModuleImpl:: Bundle = [org.glassfish.hk2.config-types [323]], State = [READY]

OSGiModuleImpl:: Bundle = [org.glassfish.main.external.libpam4j-repackaged [228]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.containers.glassfish.jersey-gf-ejb [103]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.jaspic.provider.framework [259]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.jdbc.runtime [217]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.persistence [229]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.web.javax.servlet.jsp.jstl [168]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.metro.webservices-extra-jdk-packages [186]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [stax2-api [329]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.media.jersey-media-json-jackson [121]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.glassfish-ee-api [226]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.connectors.inbound-runtime [247]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.metro.webservices-osgi [32]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [com.google.guava [218]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [JSR352.API [245]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.enterprise.deploy-api [227]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [pfl-dynamic [65]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.core.glassfish-extra-jre-packages [90]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.external.jmxremote_optional-repackaged [127]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.rest-client [143]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [GlassFish-Application-Common-Module [170]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.jboss.weld.osgi-bundle [147]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.resource-api [307]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.containers.jersey-container-servlet [265]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [pfl-tf [66]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [JSR352.RI.SPI [112]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.corba.glassfish-corba-omgapi [324]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.media.jersey-media-sse [318]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.external.ant [86]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [jackson-core-asl [190]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.jpa [282]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.javax.faces [283]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.ejb-api [8]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.flashlight.flashlight-extra-jdk-packages [7]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.oracle [304]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [woodstox-core-asl [161]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.weld-integration-fragment [335]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.core [195]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jsonp-jaxrs [314]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.sse [188]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.interceptor-api [52]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.external.management-api [47]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.security.jacc [301]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.cluster.common [257]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.corba.glassfish-corba-orb [35]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [jackson-jaxrs [296]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.core [198]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.containers.jersey-container-grizzly2-http [76]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [pfl-basic [72]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.scattered-archive-api [84]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.ext.jersey-bean-validation [24]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.ws.rs.javax.ws.rs-api [97]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admingui.connector.gf-admingui-connector [131]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.websocket-core [138]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.web.embed-api [134]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.servlet.jsp.jstl-api [101]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.javax.json [152]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.external.ldapbp-repackaged [325]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.external.trilead-ssh2-repackaged [311]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [gmbal [124]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.transaction-api [19]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.server [146]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [pfl-asm [303]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.shoal.gms-api [326]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.containers.jersey-container-servlet-core [234]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.jpa.jpql [250]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.security.auth.message [313]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.websocket-api [336]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.xml.registry-api [339]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.annotation-framework [45]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.jvnet.mimepull [88]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.shoal.gms-impl [308]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.media.jersey-media-json-jettison [254]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.media.jersey-media-multipart [197]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.core.jersey-server [135]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.external.schema2beans-repackaged [13]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.glassfish-oracle-jdbc-driver-packages [309]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.corba.glassfish-corba-internal-api [342]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.stats77 [297]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [com.sun.mail.javax.mail [123]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [jackson-mapper-asl [201]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [com.sun.xml.bind [34]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.xml.rpc-api [181]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.ha.ha-api [98]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.ejb.internal-api [316]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.media.jersey-media-json-processing [241]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.main.external.j-interop-repackaged [273]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.asm [202]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.antlr [43]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.spi [237]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [com.sun.xml.bind.extra [284]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.codehaus.jettison.jettison [126]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.core.jersey-common [163]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.container-servlet [208]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [javax.jms-api [26]], State = [RESOLVED]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.core.jersey-client [290]], State = [RESOLVED]

OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.utility [328]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.appclient.security [74]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.amx-javaee [183]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.orb.iiop [110]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.connectors.work-management [75]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.enhancer [300]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.webservices.soap-tcp [9]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.webservices.metro-glue [243]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.client [29]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.external.dbschema-repackaged [330]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.jpa-container [239]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.dbws [191]], State = [NEW]
OSGiModuleImpl:: Bundle = [javax.enterprise.concurrent-api [213]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.container-grizzly [337]], State = [NEW]
OSGiModuleImpl:: Bundle = [javax.management.j2ee-api [151]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.ejb.ejb-full-container [235]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.inmemory.jacc.provider [129]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.generator-database [64]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.shoal.cache [93]], State = [NEW]
OSGiModuleImpl:: Bundle = [pfl-basic-tools [224]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.moxy [137]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.core [327]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.common [203]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.javax.enterprise.concurrent [338]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.cli-l10n [242]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.ejb.security [244]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.jersey.media.jersey-media-moxy [77]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.resources.runtime [119]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.eclipse.persistence.jpa.modelgen [292]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.security.webservices.security [30]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.simple-glassfish-api [85]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.backup [288]], State = [NEW]
OSGiModuleImpl:: Bundle = [JSR352.Runtime [148]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.concurrent.runtime [280]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.ha.ha-file-store [246]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.admin.launcher [193]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.cluster.cli-l10n [187]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.corba.glassfish-corba-csiv2-idl [113]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.appclient.acc-config [180]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.internal-api [150]], State = [NEW]
OSGiModuleImpl:: Bundle = [pfl-tf-tools [58]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.ha.shoal-cache-store [185]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.common.amx-core [70]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.model [71]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.external.antlr-repackaged [157]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.support-ejb [236]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.entitybean-container [319]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.support-sqlstore [21]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.persistence.cmp.ejb-mapping [23]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.tyrus.container-glassfish-cdi [281]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.appclient.gf-client-module [305]], State = [NEW]
OSGiModuleImpl:: Bundle = [jackson-xc [60]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.jms.gf-jms-injection [320]], State = [NEW]
OSGiModuleImpl:: Bundle = [org.glassfish.main.resources.javamail-runtime [210]], State = [NEW]
Module Status Report Ends
Command list-modules executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help multimode [options] ...
multimode(1)              asadmin Utility Subcommands             multimode(1)

NAME
       multimode - allows multiple subcommands to be run while preserving
       environment settings and remaining in the asadmin utility

SYNOPSIS
           multimode [--help] [--file filename]
           [--printprompt={true|false}] [--encoding encode]

DESCRIPTION
       The multimode subcommand processes asadmin subcommands sequentially in
       a single session. The command-line interface prompts for a subcommand,
       runs that subcommand, displays the results of that subcommand, and then
       prompts for the next subcommand. All the asadmin options set in
       multimode apply to subsequent commands until the multimode session is
       exited. You exit multimode by typing exit, quit, or Ctrl-D.

       You can use the export subcommand to set your environment, or use the
       unset subcommand to remove environment variables from the multimode
       environment. You can also provide subcommands by passing a previously
       prepared list of subcommands from a file or standard input (pipe).

       You can invoke multimode from within a multimode session. When you exit
       the second multimode environment, you return to your original multimode
       environment.

       All the remote asadmin utility options can be supplied when invoking
       the multimode subcommand. The settings will apply as defaults for all
       subcommands that are run within the multimode session. For a list of
       the asadmin utility options, see the asadmin(1M) help page.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --file, -f
           Reads the subcommands in the specified file.

       --printprompt
           Controls printing of the asadmin prompt. By default, this option is
           set to the same value as the --interactive asadmin utility option.
           Normally you will not need to specify this option. Default is true.

       --encoding
           Specifies the character set for the file to be decoded. By default,
           the system character set is used.

EXAMPLES
       Example 1, Starting a Multimode Session
           This example starts a multimode session where: % is the system
           prompt.

               % asadmin multimode
               asadmin>
           You can also start a multimode session by typing asadmin without
           options or subcommands at the system prompt.

       Example 2, Running Multiple Commands From a File
           This example runs a sequence of subcommands from the
           commands_file.txt file.

               % asadmin multimode --file commands_file.txt

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       export(1), unset(1)

       asadmin(1M)

Java EE 7                         20 Dec 2010                     multimode(1)
Command multimode executed successfully.

Use "exit" to exit and "help" for online help.
Command multimode executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-password-alias [options] ...
create-password-alias(1) asadmin Utility Subcommands; create-password-alias(1)

NAME
       create-password-alias - creates a password alias

SYNOPSIS
           create-password-alias [--help]
           aliasname

DESCRIPTION
       The create-password-alias subcommand creates an alias for a password.
       An alias is a token of the form ${ALIAS=aliasname}. The password that
       corresponds to the alias name is stored in an encrypted form.

       The create-password-alias subcommand can be run interactively or
       noninteractively.

       *   When run interactively, the subcommand prompts the user for the
           alias password and to confirm the alias password.

       *   When run noninteractively, the subcommand reads the alias password
           from a file that is passed through the --passwordfile option of the
           asadmin(1M) utility. The file must contain an entry of the form
           AS_ADMIN_ALIASPASSWORD=alias-password, where alias-password is the
           alias password. The noninteractive form of this command is suitable
           for use in scripts.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       aliasname
           Your choice of name for the password alias.

EXAMPLES
       Example 1, Creating a Password Alias Interactively
           This example creates the password alias jmspassword-alias
           interactively.

               asadmin> create-password-alias jmspassword-alias
               Enter the alias password>
               Enter the alias password again>
               Command create-password-alias executed successfully.

       Example 2, Creating a Password Alias Noninteractively
           This example uses the --passwordfile option of the asadmin utility
           to create the password alias winuser noninteractively.

               $ asadmin --passwordfile aspwfile.txt create-password-alias winuser
               Command create-password-alias executed successfully.
           The file aspwfile.txt contains the following entry to specify the
           alias password:

               AS_ADMIN_ALIASPASSWORD=sp@rky

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       delete-password-alias(1), list-password-aliases(1),
       update-password-alias(1)

       asadmin(1M)

Java EE 7                         22 Jan 2012         create-password-alias(1)
Command create-password-alias executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-password-aliases [options] ...
list-password-aliases(1)  asadmin Utility Subcommands list-password-aliases(1)

NAME
       list-password-aliases - lists all password aliases

SYNOPSIS
           list-password-aliases [--help]

DESCRIPTION
       Thissubcommand lists all of the password aliases.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

EXAMPLES
       Example 1, Listing all password aliases

               asadmin> list-password-aliases
               jmspassword-alias
               Command list-password-aliases executed successfully

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       delete-password-alias(1), update-password-alias(1),
       create-password-alias(1)

       asadmin(1M)

Java EE 7                       28 August 2009        list-password-aliases(1)
Command list-password-aliases executed successfully.

Nothing to list
Command list-password-aliases executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help update-password-alias [options] ...
update-password-alias(1) asadmin Utility Subcommands; update-password-alias(1)

NAME
       update-password-alias - updates a password alias

SYNOPSIS
           update-password-alias [--help]
            aliasname

DESCRIPTION
       This subcommand updates the password alias IDs in the named target. An
       alias is a token of the form ${ALIAS=password-alias-password}. The
       password corresponding to the alias name is stored in an encrypted
       form. The update-password-alias subcommand takes both a secure
       interactive form (in which the user is prompted for all information)
       and a more script-friendly form, in which the password is propagated on
       the command line.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       aliasname
           This is the name of the password as it appears in domain.xml.

EXAMPLES
       Example 1, Updating a Password Alias

               asadmin> update-password-alias jmspassword-alias
               Please enter the alias password>
               Please enter the alias password again>
               Command update-password-alias executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       delete-password-alias(1), list-password-aliases(1),
       create-password-alias(1)

       asadmin(1M)

Java EE 7                       28 August 2009        update-password-alias(1)
Command update-password-alias executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-password-alias [options] ...
delete-password-alias(1)  asadmin Utility Subcommands delete-password-alias(1)

NAME
       delete-password-alias - deletes a password alias

SYNOPSIS
           delete-password-alias [--help]
            aliasname

DESCRIPTION
       This subcommand deletes a password alias.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       aliasname
           This is the name of the substitute password as it appears in
           domain.xml.

EXAMPLES
       Example 1, Deleting a Password Alias

               asadmin>delete-password-alias
               jmspassword-alias
           Command delete-password-alias executed successfully

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-password-alias(1), list-password-aliases(1),
       update-password-alias(1)

       asadmin(1M)

Java EE 7                       28 August 2009        delete-password-alias(1)
Command delete-password-alias executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help change-admin-password [options] ...
change-admin-password(1) asadmin Utility Subcommands; change-admin-password(1)

NAME
       change-admin-password - changes the administrator password

SYNOPSIS
           change-admin-password [--help]
           [--domaindir domain-root-dir [--domain_name domain-name]]

DESCRIPTION
       The change-admin-password subcommand modifies the administrator
       password. The change-admin-password subcommand is interactive because
       the subcommand prompts the user for the old administrator password, for
       the new administrator password, and for confirmation of the new
       administrator password. The new password must contain at least 8
       characters.

       If the only user is an anonymous user without a password, this
       subcommand fails.

       If a blank password is provided, this subcommand fails if secure
       administration is enabled.

       For security purposes, create a password-protected user account with
       administrator privileges. To create this account, use the
       create-file-user(1) or the Administration Console. After creating this
       user account, remove the anonymous user to restrict access to GlassFish
       Server settings.

       If more than one administrator is configured for GlassFish Server, you
       must run the asadmin command with the --user option to change the
       password for that user. For more information, see the examples in this
       help page.

       This subcommand is supported in local mode and remote mode. If the
       --domaindir or --domain_name option is specified, the
       change-admin-password subcommand operates in local mode. If neither
       option is specified, the change-admin-password subcommand first
       attempts to operate in remote mode. If neither option is specified and
       the DAS is not running, the change-admin-password subcommand operates
       in local mode, using the default values for the --domaindir and
       --domain_name options.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --domaindir
           Specifies the parent directory of the domain specified in the
           --domain_name option. When this option is used, the
           change-admin-password subcommand operates in local mode.

       --domain_name
           Specifies the domain of the admin user.

           This option is not required if the directory specified by the
           --domaindir option contains only one domain.

EXAMPLES
       Example 1, Changing the Administrator Password For a Single User in
       Multimode

               asadmin --user admin
               asadmin> change-admin-password
               Please enter the old admin password>
               Please enter the new admin password>
               Please enter the new admin password again>
               Command change-admin-password executed successfully.

       Example 2, Changing the Administrator Password For a Single User in
       Single Mode

               asadmin --user admin change-admin-password
               Please enter the old admin password>
               Please enter the new admin password>
               Please enter the new admin password again>
               Command change-admin-password executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           command failed

SEE ALSO
       create-file-user(1), delete-password-alias(1),
       list-password-aliases(1), update-password-alias(1)

       asadmin(1M)

Java EE 7                         28 Aug 2009         change-admin-password(1)
Command change-admin-password executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help change-master-password [options] ...
change-master-password(1) asadmin Utility Subcommandschange-master-password(1)

NAME
       change-master-password - changes the master password

SYNOPSIS
           change-master-password [--help] [--nodedir node-dir] [--domaindir domain-dir]
            [--savemasterpassword={false|true}] [domain-name|node-name]

DESCRIPTION
       The change-master-password subcommand is used to modify the master
       password. The change-master-password subcommand is interactive in that
       the user is prompted for the old master password, as well as the new
       master password. This subcommand will not work unless the server is
       stopped. In a distributed environment, this command must run on each
       machine in the domain.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --nodedir
           The name of the directory containing the node instance for which
           the password will be changed. If this option is omitted, the change
           is applied to the entire domain.

       --domaindir
           The name of the domain directory used for this operation. By
           default, the --domaindir option is $AS_DEF_DOMAINS_PATH, which is
           an environment variable defined in the file asenv.bat or
           asenv.conf.

       --savemasterpassword
           This option indicates whether the master password should be written
           to the file system. This is necessary so that the start-domain(1)
           command can start the server without having to prompt the user.

           The default is false.

               Caution
               +--------------------------------------+
               |Saving the master password on disk is |
               |extremely insecure and should be      |
               |avoided.                              |
               +--------------------------------------+

               Note
               +--------------------------------------+
               |If the --savemasterpassword option is |
               |not set, the master password file, if |
               |it exists, will be deleted.           |
               +--------------------------------------+

OPERANDS
       domain-name|node-name
           This name of the domain or node for which the password will be
           changed. If there is only a single domain, this is optional.

EXAMPLES
       Example 1, Changing the Master Password
           This example shows how to changed the master password for the
           domain44ps domain.

               asadmin>change-master-password domain44ps
               Please enter the new master password>
               Please enter the new master password again>
               Master password changed for domain44ps

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-password-alias(1), list-password-aliases(1), start-domain(1),
       update-password-alias(1)

       asadmin(1M)

Java EE 7                         11 Feb 2011        change-master-password(1)
Command change-master-password executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-domain [options] ...
create-domain(1)          asadmin Utility Subcommands         create-domain(1)

NAME
       create-domain - creates a domain

SYNOPSIS
           create-domain [--help]
           [--adminport adminport]
           [--instanceport instanceport]
           [--portbase portbase]
           [--profile profile-name]
           [--template template-name]
           [--domaindir domaindir]
           [--savemasterpassword={false|true}]
           [--usemasterpassword={false|true}]
           [--domainproperties (name=value)[:name=value]*]
           [--keytooloptions (name=value)[:name=value]*]
           [--savelogin={false|true}]
           [--checkports={true|false}]
           [--nopassword={false|true}]
           domain-name

DESCRIPTION
       The create-domain subcommand creates a GlassFish Server domain. A
       domain in GlassFish Server is an administrative namespace that complies
       with the Java Platform, Enterprise Edition (Java EE) standard. Every
       domain has a configuration, which is stored in a set of files. Any
       number of domains, each of which has a distinct administrative
       identity, can be created in a given installation of GlassFish Server. A
       domain can exist independently of other domains.

       Any user who has access to the asadmin utility on a given system can
       create a domain and store its configuration in a folder of the user's
       choosing. By default, the domain configuration is created in the
       default directory for domains. You can override this location to store
       the configuration elsewhere.

       If domain customizers are found in JAR files in the as-install/modules
       directory when the create-domain subcommand is run, the customizers are
       processed. A domain customizer is a class that implements the
       DomainInitializer interface.

       The create-domain subcommand creates a domain with a single
       administrative user specified by the asadmin utility option --user. If
       the --user option is not specified, and the --nopassword option is set
       to true, the default administrative user, admin, is used. If the
       --nopassword option is set to false (the default), a username is
       required. In this case, if you have not specified the user name by
       using the --user option, you are prompted to do so.

       You choose an appropriate profile for the domain, depending on the
       applications that you want to run on your new domain. You can choose
       the developer, cluster, or enterprise profile for the domain you
       create.

       This subcommand is supported in local mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --adminport
           The HTTP port or the HTTPS port for administration. This port is
           the port in the URL that you specify in your web browser to manage
           the domain, for example, http://localhost:4949. The --adminport
           option cannot be used with the --portbase option. The default value
           is 4848.

           The --adminport option overrides the domain.adminPort property of
           the --domainproperties option.

       --instanceport
           The domain provides services so that applications can run when
           deployed. This HTTP port specifies where the web application
           context roots are available for a web browser to connect to. This
           port is a positive integer and must be available at the time of
           domain creation. The --instanceport option cannot be used with the
           --portbase option. The default value is 8080.

           The --instanceport option overrides the domain.instancePort
           property of the --domainproperties option.

       --portbase
           Determines the number with which port assignments should start. A
           domain uses a certain number of ports that are statically assigned.
           The portbase value determines where the assignment should start.
           The values for the ports are calculated as follows:

           *   Administration port: portbase + 48

           *   HTTP listener port: portbase + 80

           *   HTTPS listener port: portbase + 81

           *   JMS port: portbase + 76

           *   IIOP listener port: portbase + 37

           *   Secure IIOP listener port: portbase + 38

           *   Secure IIOP with mutual authentication port: portbase + 39

           *   JMX port: portbase + 86

           *   JPDA debugger port: portbase + 9

           *   Felix shell service port for OSGi module management: portbase +
               66

           When the --portbase option is specified, the output of this
           subcommand includes a complete list of used ports.

           The --portbase option cannot be used with the --adminport,
           --instanceport, or the --domainproperties option.

       --profile
           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.

       --template
           The file name, including a relative or absolute path, of a domain
           configuration template to use for creating the domain. If a
           relative path is specified, the subcommand appends the path to the
           as-install/lib/templates directory to locate the file. If it is an
           absolute pathname, the subcommand locates the file in the specified
           path.

           This option enables domains of different types to be created and
           custom domain templates to be defined.

       --domaindir
           The directory where the domain is to be created. If specified, the
           path must be accessible in the filesystem. If not specified, the
           domain is created in the default domain directory,
           as-install/domains.

       --savemasterpassword
           Setting this option to true allows the master password to be
           written to the file system. If this option is true, the
           --usemasterpassword option is also true, regardless of the value
           that is specified on the command line. The default value is false.

           A master password is really a password for the secure key store. A
           domain is designed to keep its own certificate (created at the time
           of domain creation) in a safe place in the configuration location.
           This certificate is called the domain's SSL server certificate.
           When the domain is contacted by a web browser over a secure channel
           (HTTPS), this certificate is presented by the domain. The master
           password is supposed to protect the store (a file) that contains
           this certificate. This file is called keystore.jks and is created
           in the configuration directory of the domain created. If however,
           this option is chosen, the master password is saved on the disk in
           the domain's configuration location. The master password is stored
           in a file called master-password, which is a Java JCEKS type
           keystore. The reason for using the --savemasterpassword option is
           for unattended system boots. In this case, the master password is
           not prompted for when the domain starts because the password will
           be extracted from this file.

           It is best to create a master password when creating a domain,
           because the master password is used by the start-domain subcommand.
           For security purposes, the default setting should be false, because
           saving the master password on the disk is an insecure practice,
           unless file system permissions are properly set. If the master
           password is saved, then start-domain does not prompt for it. The
           master password gives an extra level of security to the
           environment.

       --usemasterpassword
           Specifies whether the key store is encrypted with a master password
           that is built into the system or a user-defined master password.

           If false (default), the keystore is encrypted with a well-known
           password that is built into the system. Encrypting the keystore
           with a password that is built into the system provides no
           additional security.

           If true, the subcommand obtains the master password from the
           AS_ADMIN_MASTERPASSWORD entry in the password file or prompts for
           the master password. The password file is specified in the
           --passwordfile option of the asadmin(1M)utility.

           If the --savemasterpassword option is true, this option is also
           true, regardless of the value that is specified on the command
           line.

       --domainproperties
           Setting the optional name/value pairs overrides the default values
           for the properties of the domain to be created. The list must be
           separated by the colon (:) character. The --portbase options cannot
           be used with the --domainproperties option. The following
           properties are available:

           domain.adminPort
               This property specifies the port number of the HTTP port or the
               HTTPS port for administration. This port is the port in the URL
               that you specify in your web browser to manage the instance,
               for example, http://localhost:4949. Valid values are 1-65535.
               On UNIX, creating sockets that listen on ports 1-1024 requires
               superuser privileges.

               The domain.adminPort property is overridden by the --adminport
               option.

           domain.instancePort
               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.

               The domain.instancePort property is overridden by
               --instanceport option.

           domain.jmxPort
               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.

           http.ssl.port
               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.

           java.debugger.port
               This property specifies the port number of the port that is
               used for connections to the Java Platform Debugger Architecture
               (JPDA)

               (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

               debugger. Valid values are 1-65535. On UNIX, creating sockets
               that listen on ports 1-1024 requires superuser privileges.

           jms.port
               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.

           orb.listener.port
               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.

           orb.mutualauth.port
               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.

           orb.ssl.port
               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.

           osgi.shell.telnet.port
               This property specifies the port number of the port that is
               used for connections to the Apache Felix Remote Shell

               (http://felix.apache.org/site/apache-felix-remote-shell.html) .
               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.

       --keytooloptions
           Specifies an optional list of name-value pairs of keytool options
           for a self-signed server certificate. The certificate is generated
           during the creation of the domain. Each pair in the list must be
           separated by the colon (:) character.

           Allowed options are as follows:

           CN
               Specifies the common name of the host that is to be used for
               the self-signed certificate. This option name is case
               insensitive.

               By default, the name is the fully-qualified name of the host
               where the create-domain subcommand is run.

       --savelogin
           If set to true, this option saves the administration user name and
           password. Default value is false. The username and password are
           stored in the .asadminpass file in user's home directory. A domain
           can only be created locally. Therefore, when using the --savelogin
           option, the host name saved in .asadminpass is always localhost. If
           the user has specified default administration port while creating
           the domain, there is no need to specify --user, --passwordfile,
           --host, or --port on any of the subsequent asadmin remote commands.
           These values will be obtained automatically.

               Note
               +----------------------------------------+
               |When the same user creates multiple     |
               |domains that have the same              |
               |administration port number on the same  |
               |or different host (where the home       |
               |directory is NFS mounted), the          |
               |subcommand does not ask if the password |
               |should be overwritten. The password     |
               |will always be overwritten.             |
               +----------------------------------------+

       --checkports
           Specifies whether to check for the availability of the
           administration, HTTP, JMS, JMX, and IIOP ports. The default value
           is true.

       --nopassword
           Specifies whether the administrative user will have a password. If
           false (the default), the password is specified by the
           AS_ADMIN_PASSWORD entry in the asadmin password file (set by using
           the --passwordfile option). If false and the AS_ADMIN_PASSWORD is
           not set, you are prompted for the password.

           If true, the administrative user is created without a password. If
           a user name for the domain is not specified by using the --user
           option, and the --nopassword option is set to true, the default
           user name, admin, is used.

OPERANDS
       domain-name
           The name of the domain to be created. The name may contain only
           ASCII characters and must be a valid directory name for the
           operating system on the host where the domain is created.

EXAMPLES
       Example 1, Creating a Domain
           This example creates a domain named domain4.

               asadmin>create-domain --adminport 4848 domain4
               Enter admin user name [Enter to accept default "admin" / no password]>
               Using port 4848 for Admin.
               Using default port 8080 for HTTP Instance.
               Using default port 7676 for JMS.
               Using default port 3700 for IIOP.
               Using default port 8181 for HTTP_SSL.
               Using default port 3820 for IIOP_SSL.
               Using default port 3920 for IIOP_MUTUALAUTH.
               Using default port 8686 for JMX_ADMIN.
               Using default port 6666 for OSGI_SHELL.
               Distinguished Name of the self-signed X.509 Server Certificate is:
               [CN=sr1-usca-22,OU=GlassFish,O=Oracle Corp.,L=Redwood Shores,ST=California,C=US]
               No domain initializers found, bypassing customization step
               Domain domain4 created.
               Domain domain4 admin port is 4848.
               Domain domain4 allows admin login as user "admin" with no password.
               Command create-domain executed successfully.

       Example 2, Creating a Domain in an Alternate Directory
           This example creates a domain named sampleDomain in the
           /home/someuser/domains directory.

               asadmin> create-domain --domaindir /home/someuser/domains --adminport 7070
               --instanceport 7071 sampleDomain
               Enter admin user name [Enter to accept default "admin" / no password]>
               Using port 7070 for Admin.
               Using port 7071 for HTTP Instance.
               Using default port 7676 for JMS.
               Using default port 3700 for IIOP.
               Using default port 8181 for HTTP_SSL.
               Using default port 3820 for IIOP_SSL.
               Using default port 3920 for IIOP_MUTUALAUTH.
               Using default port 8686 for JMX_ADMIN.
               Using default port 6666 for OSGI_SHELL.
               Enterprise ServiceDistinguished Name of the self-signed X.509 Server Certificate is:
               [CN=sr1-usca-22,OU=GlassFish,O=Oracle Corp.,L=Redwood Shores,ST=California,C=US]
               No domain initializers found, bypassing customization step
               Domain sampleDomain created.
               Domain sampleDomain admin port is 7070.
               Domain sampleDomain allows admin login as user "admin" with no password.
               Command create-domain executed successfully.

       Example 3, Creating a Domain and Saving the Administration User Name
       and Password
           This example creates a domain named myDomain and saves the
           administration username and password.

               asadmin> create-domain --adminport 8282 --savelogin=true myDomain
               Enter the admin password [Enter to accept default of no password]>
               Enter the master password [Enter to accept default password "changeit"]>
               Using port 8282 for Admin.
               Using default port 8080 for HTTP Instance.
               Using default port 7676 for JMS.
               Using default port 3700 for IIOP.
               Using default port 8181 for HTTP_SSL.
               Using default port 3820 for IIOP_SSL.
               Using default port 3920 for IIOP_MUTUALAUTH.
               Using default port 8686 for JMX_ADMIN.
               Using default port 6666 for OSGI_SHELL.
               Enterprise ServiceDistinguished Name of the self-signed X.509 Server Certificate is:
               [CN=sr1-usca-22,OU=GlassFish,O=Oracle Corp.,L=Redwood Shores,ST=California,C=US]
               No domain initializers found, bypassing customization step
               Domain myDomain created.
               Domain myDomain admin port is 8282.
               Domain myDomain allows admin login as user "admin" with no password.
               Login information relevant to admin user name [admin]
               for this domain [myDomain] stored at
               [/home/someuser/.asadminpass] successfully.
               Make sure that this file remains protected.
               Information stored in this file will be used by
               asadmin commands to manage this domain.
               Command create-domain executed successfully.

       Example 4, Creating a Domain and Designating the Certificate Host
           This example creates a domain named domain5. The common name of the
           host that is to be used for the self-signed certificate is trio.

               asadmin> create-domain --adminport 9898 --keytooloptions CN=trio domain5
               Enter the admin password [Enter to accept default of no password]>
               Enter the master password [Enter to accept default password "changeit"]>
               Using port 9898 for Admin.
               Using default port 8080 for HTTP Instance.
               Using default port 7676 for JMS.
               Using default port 3700 for IIOP.
               Using default port 8181 for HTTP_SSL.
               Using default port 3820 for IIOP_SSL.
               Using default port 3920 for IIOP_MUTUALAUTH.
               Using default port 8686 for JMX_ADMIN.
               Using default port 6666 for OSGI_SHELL.
               Distinguished Name of the self-signed X.509 Server Certificate is:
               [CN=trio,OU=GlassFish,O=Oracle Corp.,L=Redwood Shores,ST=California,C=US]
               No domain initializers found, bypassing customization step
               Domain domain5 created.
               Domain domain5 admin port is 9898.
               Domain domain5 allows admin login as user "admin" with no password.
               Command create-domain executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       login(1), delete-domain(1), start-domain(1), stop-domain(1),
       list-domains(1)

       asadmin(1M)

       Apache Felix Remote Shell
       (http://felix.apache.org/site/apache-felix-remote-shell.html), Java
       Platform Debugger Architecture (JPDA)
       (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

Java EE 7                         14 Jun 2011                 create-domain(1)
Command create-domain executed successfully.

Using port 4850 for Admin.
Default port 8080 for HTTP Instance is in use. Using 35990
Default port 7676 for JMS is in use. Using 37946
Default port 3700 for IIOP is in use. Using 42004
Default port 8181 for HTTP_SSL is in use. Using 39959
Using default port 3820 for IIOP_SSL.
Using default port 3920 for IIOP_MUTUALAUTH.
Default port 8686 for JMX_ADMIN is in use. Using 38312
Using default port 6666 for OSGI_SHELL.
Using default port 9009 for JAVA_DEBUGGER.
Distinguished Name of the self-signed X.509 Server Certificate is:
[CN=bej301053.cn.oracle.com,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
Distinguished Name of the self-signed X.509 Server Certificate is:
[CN=bej301053.cn.oracle.com-instance,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
Domain domain2 created.
Domain domain2 admin port is 4,850.
Domain domain2 admin user is "admin".
Command create-domain executed successfully.

list-domains(1)           asadmin Utility Subcommands          list-domains(1)

NAME
       list-domains - lists the domains in the specified directory

SYNOPSIS
           list-domains [--help]
           [--domaindir domaindir]
           [--long[={false|true}]]
           [--header[={false|true}]]

DESCRIPTION
       The list-domains subcommand lists the domains in the specified domains
       directory. If the domains directory is not specified, the domains in
       the default directory are listed. If there is more that one domains
       directory, the --domaindir option must be specified. The status of each
       domain is included.

       This subcommand is supported in local mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --domaindir
           The directory where the domains are to be listed. If specified, the
           path must be accessible in the files stem. If not specified, the
           domains in the domain root directory are listed. The default
           location of the domain root directory is as-install/domains.

       --long, -l
           Displays detailed information about the administration servers in
           the listed domains, including host names and port numbers. The
           default value is false.

       --header, -h
           Specifies whether a header is displayed when the --long option is
           used. The default value is true. To suppress the header, set the
           --header option to false.

EXAMPLES
       Example 1, Listing Domains
           This example lists the domains in the default directory.

               asadmin> list-domains
               Name: domain1 Status: Running
               Name: domain2 Status: Not running
               Name: domain4 Status: Running, restart required to apply configuration changes
               Command list-domains executed successfully

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-domain(1), delete-domain(1), start-domain(1), stop-domain(1),

       asadmin(1M)

Java EE 7                         12 Feb 2013                  list-domains(1)
Command list-domains executed successfully.

domain1 running, restart required to apply configuration changes
domain2 not running
Command list-domains executed successfully.

stop-domain(1)            asadmin Utility Subcommands           stop-domain(1)

NAME
       stop-domain - stops the Domain Administration Server of the specified
       domain

SYNOPSIS
           stop-domain [--help] [--domaindir domaindir]
           [--force={true|false}] [--kill={false|true}]
           [domain-name]

DESCRIPTION
       The stop-domain subcommand stops the Domain Administration Server (DAS)
       of the specified domain. If the domain directory is not specified, the
       domain in the default domains directory is stopped. If there are two or
       more domains in the domains directory, the domain-name operand must be
       specified.

       This subcommand is supported in local or remote mode. If you specify a
       host name, the subcommand assumes you are operating in remote mode,
       which means you must correctly authenticate to the remote server. In
       local mode, you normally do not need to authenticate to the server as
       long as you are running the subcommand as the same user who started the
       server.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --domaindir
           Specifies the directory of the domain that is to be stopped. If
           specified, the path must be accessible in the file system. If not
           specified, the domain in the default as-install/domains directory
           is stopped.

       --force
           Specifies whether the domain is forcibly stopped immediately.

           Possible values are as follows:

           true
               The domain is forcibly stopped immediately (default).

           false
               The subcommand waits until all threads that are associated with
               the domain are exited before stopping the domain.

       --kill
           Specifies whether the domain is killed by using functionality of
           the operating system to terminate the domain process.

           Possible values are as follows:

           false
               The domain is not killed. The subcommand uses functionality of
               the Java platform to terminate the domain process (default).

           true
               The domain is killed. The subcommand uses functionality of the
               operating system to terminate the domain process.

OPERANDS
       domain-name
           The name of the domain you want to stop. Default is the name
           specified during installation, usually domain1.

EXAMPLES
       Example 1, Stopping a Domain
           This example stops the domain named sampleDomain in the default
           domains directory.

               asadmin> stop-domain sampleDomain
               Waiting for the domain to stop .................
               Command stop-domain executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-domain(1), list-domains(1), restart-domain(1), start-domain(1)

       asadmin(1M)

Java EE 7                         20 Dec 2010                   stop-domain(1)
Command stop-domain executed successfully.

Waiting for the domain to stop ..
Command stop-domain executed successfully.

Domain domain2 deleted.
Command delete-domain executed successfully.

Waiting for domain1 to start ................
Successfully started the domain : domain1
domain  Location: /home/cdctest/glassfish4_b80/glassfish/domains/domain1
Log File: /home/cdctest/glassfish4_b80/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command start-domain executed successfully.

backup-domain(1)          asadmin Utility Subcommands         backup-domain(1)

NAME
       backup-domain - performs a backup on the domain

SYNOPSIS
           backup-domain [--help]
           [--long[={false|true}]]
           [--description description-text]
           [--domaindir domain-root-dir]
           [--backupdir backup-directory]
           [--backupconfig backup-config-name]
           [domain_name]

DESCRIPTION
       The backup-domain subcommand backs up files under the named domain.

       This subcommand is supported in local mode only in GlassFish Server
       Open Source Edition, and is supported in local mode and remote mode in
       Oracle GlassFish Server.

       In GlassFish Server Open Source Edition, the domain to be backed up
       must be stopped.

       In Oracle GlassFish Server, the domain to be backed up must be stopped
       or be suspended using the () subcommand.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Displays detailed information about the backup operation.

           The default value is false.

       --description
           Specifies a description to store in the backup file. The
           description is displayed as part of the information about a backup
           file.

           The default value has this form:

               domain-name backup created on YYYY_MM_DD by user user-name

       --domaindir
           Specifies the domain root directory, the parent directory of the
           domain to back up.

           The default value is as-install/domains.

       --backupdir
           Specifies the directory under which the backup file is to be
           stored.

           The default value is as-install/domains/domain-dir/backups. If the
           domain is not in the default location, the location is
           domain-dir/backups.

       --backupconfig
           (Supported only in Oracle GlassFish Server.) The name of the domain
           backup configuration in the backup directory under which the backup
           file is to be stored.

OPERANDS
       domain-name
           Specifies the name of the domain to be backed up.

           This operand is optional if only one domain exists in the GlassFish
           Server installation.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       restore-domain(1), list-backups(1), (), ()

Java EE 7                         22 Dec 2010                 backup-domain(1)
Command backup-domain executed successfully.

Waiting for the domain to stop ...
Command stop-domain executed successfully.

Backed up domain1 at Wed Mar 20 02:22:05 EDT 2013.
Command backup-domain executed successfully.

Waiting for domain1 to start .................
Successfully started the domain : domain1
domain  Location: /home/cdctest/glassfish4_b80/glassfish/domains/domain1
Log File: /home/cdctest/glassfish4_b80/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command start-domain executed successfully.

list-backups(1)           asadmin Utility Subcommands          list-backups(1)

NAME
       list-backups - lists all backups

SYNOPSIS
           list-backups [--help]
           [--long[={false|true}]]
           [--domaindir domain-root-dir]
           [--backupdir backup-directory]
           [--backupconfig backup-config-name]
           [domain-name]

DESCRIPTION
       The list-backups subcommand displays information about domain backups.

       This subcommand is supported in local mode only in GlassFish Server
       Open Source Edition, and is support in local mode and remote mode in
       Oracle GlassFish Server.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Displays detailed information about each backup.

           The default value is false.

       --domaindir
           Specifies the domain root directory, the parent directory of the
           domain upon which the command will operate.

           The default value is as-install/domains.

       --backupdir
           Specifies the directory under which backup files are stored.

           The default value is as-install/domains/domain-dir/backups. If the
           domain is not in the default location, the location is
           domain-dir/backups.

       --backupconfig
           (Supported only in Oracle GlassFish Server.) Restricts the listing
           of backup files in the backup directory to those for the specified
           domain backup configuration.

OPERANDS
       domain-name
           Specifies the domain for which backups are listed.

           This operand is optional if only one domain exists in the GlassFish
           Server installation.

EXAMPLES
       Example 1, Listing Domain Backups
           This example provides detailed information about backups in the
           default domain.

               asadmin> list-backups --long
               Description               : domain1 backup created on 2010_12_01 by user adminuser
               GlassFish Version         : Oracle GlassFish Server 3.1
               Backup User               : adminuser
               Backup Date               : Wed Dec 01 09:22:45 PST 2010
               Domain Name               : domain1
               Backup Type               : full
               Backup Config Name        :
               Backup Filename (origin)  : /glassfish3/glassfish/domains/domain1/backups/domain1_2010_12_01_v00001.zip
               Domain Directory          : /glassfish3/glassfish/domains/domain1

               Description               : domain1 backup created on 2010_12_16 by user adminuser
               GlassFish Version         : Oracle GlassFish Server 3.1
               Backup User               : adminuser
               Backup Date               : Thu Dec 16 09:23:48 PST 2010
               Domain Name               : domain1
               Backup Type               : full
               Backup Config Name        :
               Backup Filename (origin)  : /glassfish3/glassfish/domains/domain1/backups/domain1_2010_12_16_v00001.zip
               Domain Directory          : /glassfish3/glassfish/domains/domain1

               Command list-backups executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       backup-domain(1), restore-domain(1)

Java EE 7                         22 Dec 2010                  list-backups(1)
Command list-backups executed successfully.

CONFIG  USER     BACKUP-DATE                   FILENAME                       
        cdctest  Wed Mar 20 02:08:16 EDT 2013  domain1_2013_03_20_v00001.zip  
        cdctest  Wed Mar 20 02:22:05 EDT 2013  domain1_2013_03_20_v00002.zip  
Command list-backups executed successfully.

restore-domain(1)         asadmin Utility Subcommands        restore-domain(1)

NAME
       restore-domain - restores files from backup

SYNOPSIS
           restore-domain [--help]
           [--long[={false|true}]]
           [--filename backup-filename]
           [--domaindir domain-root-dir]
           [--backupdirbackup-directory]
           [--backupconfigbackup-config-name]
           [--force[={false|true}]]
           [domain-name]

DESCRIPTION
       This command restores files under the domain from a backup directory.

       The restore-domain command is supported in local mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Displays detailed information about the restore operation.

           The default value is false.

       --filename
           Specifies the name of the backup file to use as the source.

       --domaindir
           Specifies the domain root directory, the parent directory of the
           domain to restore.

           The default value is as-install/domains.

       --backupdir
           Specifies the directory under which the backup file is stored.

           The default value is as-install/domains/domain-dir/backups. If the
           domain is not in the default location, the location is
           domain-dir/backups.

       --backupconfig
           (Supported only in Oracle GlassFish Server.) The name of the domain
           backup configuration in the backup directory under which the backup
           file is stored.

       --force
           Causes the restore operation to continue even when the name of the
           domain to restore does not match the name of the domain stored in
           the backup file.

           The default value is false.

OPERANDS
       domain-name
           Specifies the name of the domain to restore.

           This operand is optional if only one domain exists in the GlassFish
           Server installation.

           If the specified domain name does not match the domain name stored
           in the backup file, an error occurs unless the --force option is
           specified.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       backup-domain(1), list-backups(1)

Java EE 7                         22 Dec 2010                restore-domain(1)
Command restore-domain executed successfully.

Waiting for the domain to stop ..
Command stop-domain executed successfully.

Restored the domain (domain1) to /home/cdctest/glassfish4_b80/glassfish/domains/domain1
Command restore-domain executed successfully.

Waiting for domain1 to start .................
Successfully started the domain : domain1
domain  Location: /home/cdctest/glassfish4_b80/glassfish/domains/domain1
Log File: /home/cdctest/glassfish4_b80/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command start-domain executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-instance [options] ...
create-instance(1)        asadmin Utility Subcommands       create-instance(1)

NAME
       create-instance - creates a GlassFish Server instance

SYNOPSIS
           create-instance [--help] --node node-name
           [--config config-name | --cluster cluster-name]
           [--lbenabled={true|false}]
           [--portbase=port-number] [--checkports={true|false}]
           [--systemproperties (name=value)[:name=value]* ]
           instance-name

DESCRIPTION
       The create-instance subcommand creates a GlassFish Server instance.
       This subcommand requires the Distributed Component Object Model (DCOM)
       remote protocol or secure shell (SSH) to be configured on the host
       where the domain administration server (DAS) is running and on the host
       that is represented by the node where the instance is to reside.

           Note
           +----------------------------------------+
           |           DCOM or SSH is not required  |
           |           if the instance is to reside |
           |           on a node of type CONFIG     |
           |           that represents the local    |
           |           host. A node of type CONFIG  |
           |           is not enabled for remote    |
           |           communication over DCOM or   |
           |           SSH.                         |
           +----------------------------------------+

       You may run this command from any host that can contact the DAS.

       A GlassFish Server instance is a single Virtual Machine for the Java
       platform (Java Virtual Machine or JVM machine) on a single node in
       which GlassFish Server is running. A node defines the host where the
       GlassFish Server instance resides. The JVM machine must be compatible
       with the Java Platform, Enterprise Edition (Java EE).

       A GlassFish Server instance requires a reference to the following
       items:

       *   The node that defines the host where the instance resides. The node
           must be specified in the command to create the instance.

       *   The named configuration that defines the configuration of the
           instance. The configuration can be specified in the command to
           create the instance, but is not required. If no configuration is
           specified for an instance that is not joining a cluster, the
           subcommand creates a configuration for the instance. An instance
           that is joining a cluster receives its configuration from its
           parent cluster.

       Each GlassFish Server instance is one of the following types of
       instance:

       Standalone instance
           A standalone instance does not share its configuration with any
           other instances or clusters. A standalone instance is created if
           either of the following conditions is met:

           *   No configuration or cluster is specified in the command to
               create the instance.

           *   A configuration that is not referenced by any other instances
               or clusters is specified in the command to create the instance.

           When no configuration or cluster is specified, a copy of the
           default-config configuration is created for the instance. The name
           of this configuration is instance-name-config, where instance-name
           represents the name of an unclustered server instance.

       Shared instance
           A shared instance shares its configuration with other instances or
           clusters. A shared instance is created if a configuration that is
           referenced by other instances or clusters is specified in the
           command to create the instance.

       Clustered instance
           A clustered instance inherits its configuration from the cluster to
           which the instance belongs and shares its configuration with other
           instances in the cluster. A clustered instance is created if a
           cluster is specified in the command to create the instance.

           Any instance that is not part of a cluster is considered an
           unclustered server instance. Therefore, standalone instances and
           shared instances are unclustered server instances.

       By default, this subcommand attempts to resolve possible port conflicts
       for the instance that is being created. The subcommand also assigns
       ports that are currently not in use and not already assigned to other
       instances on the same node. The subcommand assigns these ports on the
       basis of an algorithm that is internal to the subcommand. Use the
       --systemproperties option to resolve port conflicts for additional
       instances on the same node. System properties of an instance can be
       manipulated by using the create-system-properties(1) subcommand and the
       delete-system-property(1) subcommand.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --node
           The name of the node that defines the host where the instance is to
           be created. The node must already exist. If the instance is to be
           created on the host where the domain administration server (DAS) is
           running, use the predefined node localhost-domain.

       --config
           Specifies the named configuration that the instance references. The
           configuration must exist and must not be named default-config or
           server-config. Specifying the --config option creates a shared
           instance.

           The --config option and the --cluster option are mutually
           exclusive. If both options are omitted, a standalone instance is
           created.

       --cluster
           Specifies the cluster from which the instance inherits its
           configuration. Specifying the --cluster option creates a clustered
           instance.

           The --config option and the --cluster option are mutually
           exclusive. If both options are omitted, a standalone instance is
           created.

       --lbenabled
           Specifies whether the instance is enabled for load balancing.
           Possible values are as follows:

           true
               The instance is enabled for load balancing (default).

               When an instance is enabled for load balancing, a load balancer
               sends requests to the instance.

           false
               The instance is disabled for load balancing.

               When an instance is disabled for load balancing, a load
               balancer does not send requests to the instance.

       --portbase
           Determines the number with which the port assignment should start.
           An instance uses a certain number of ports that are statically
           assigned. The portbase value determines where the assignment should
           start. The values for the ports are calculated as follows:

           *   Administration port: portbase + 48

           *   HTTP listener port: portbase + 80

           *   HTTPS listener port: portbase + 81

           *   JMS port: portbase + 76

           *   IIOP listener port: portbase + 37

           *   Secure IIOP listener port: portbase + 38

           *   Secure IIOP with mutual authentication port: portbase + 39

           *   JMX port: portbase + 86

           *   JPA debugger port: portbase + 9

           *   Felix shell service port for OSGi module management: portbase +
               66

           When the --portbase option is specified, the output of this
           subcommand includes a complete list of used ports.

       --checkports
           Specifies whether to check for the availability of the
           administration, HTTP, JMS, JMX, and IIOP ports. The default value
           is true.

       --systemproperties
           Defines system properties for the instance. These properties
           override property definitions for port settings in the instance's
           configuration. Predefined port settings must be overridden if, for
           example, two clustered instances reside on the same host. In this
           situation, port settings for one instance must be overridden
           because both instances share the same configuration.

           The following properties are available:

           ASADMIN_LISTENER_PORT
               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.

           HTTP_LISTENER_PORT
               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.

           HTTP_SSL_LISTENER_PORT
               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.

           IIOP_LISTENER_PORT
               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.

           IIOP_SSL_LISTENER_PORT
               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.

           IIOP_SSL_MUTUALAUTH_PORT
               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.

           JAVA_DEBUGGER_PORT
               This property specifies the port number of the port that is
               used for connections to the Java Platform Debugger Architecture
               (JPDA)
               (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)
               debugger. Valid values are 1-65535. On UNIX, creating sockets
               that listen on ports 1-1024 requires superuser privileges.

           JMS_PROVIDER_PORT
               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.

           JMX_SYSTEM_CONNECTOR_PORT
               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.

           OSGI_SHELL_TELNET_PORT
               This property specifies the port number of the port that is
               used for connections to the Apache Felix Remote Shell
               (http://felix.apache.org/site/apache-felix-remote-shell.html).
               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.

OPERANDS
       instance-name
           The name of the instance that is being created.

           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 GlassFish Server instance, a cluster, a named
               configuration, or a node.

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

EXAMPLES
       Example 1, Creating a Standalone GlassFish Server Instance
           This example creates the standalone GlassFish Server instance
           pmdsainst in the domain domain1 on the local host.

               asadmin> create-instance --node localhost-domain1 pmdsainst
               Port Assignments for server instance pmdsainst:
               JMX_SYSTEM_CONNECTOR_PORT=28688
               JMS_PROVIDER_PORT=27678
               ASADMIN_LISTENER_PORT=24850
               HTTP_LISTENER_PORT=28082
               IIOP_LISTENER_PORT=23702
               IIOP_SSL_LISTENER_PORT=23822
               HTTP_SSL_LISTENER_PORT=28183
               IIOP_SSL_MUTUALAUTH_PORT=23922

               Command create-instance executed successfully.

       Example 2, Creating a Standalone GlassFish Server Instance With Custom
       Port Assignments
           This example creates the standalone GlassFish Server instance
           pmdcpinst in the domain domain1 on the local host. Custom port
           numbers are assigned to the following ports:

           *   HTTP listener port

           *   HTTPS listener port

           *   IIOP connections port

           *   Secure IIOP connections port

           *   Secure IIOP connections port with mutual authentication

           *   JMX connector port

               asadmin> create-instance --node localhost-domain1
               --systemproperties HTTP_LISTENER_PORT=58294:
               HTTP_SSL_LISTENER_PORT=58297:
               IIOP_LISTENER_PORT=58300:
               IIOP_SSL_LISTENER_PORT=58303:
               IIOP_SSL_MUTUALAUTH_PORT=58306:
               JMX_SYSTEM_CONNECTOR_PORT=58309 pmdcpinst
               Port Assignments for server instance pmdcpinst:
               JMS_PROVIDER_PORT=27679
               ASADMIN_LISTENER_PORT=24851

               Command create-instance executed successfully.

       Example 3, Creating a Shared GlassFish Server Instance
           This example creates the shared GlassFish Server instance
           pmdsharedinst1 in the domain domain1 on the local host. The shared
           configuration of this instance is pmdsharedconfig.

               asadmin create-instance --node localhost-domain1 --config pmdsharedconfig
               pmdsharedinst1
               Port Assignments for server instance pmdsharedinst1:
               JMX_SYSTEM_CONNECTOR_PORT=28687
               JMS_PROVIDER_PORT=27677
               ASADMIN_LISTENER_PORT=24849
               HTTP_LISTENER_PORT=28081
               IIOP_LISTENER_PORT=23701
               IIOP_SSL_LISTENER_PORT=23821
               HTTP_SSL_LISTENER_PORT=28182
               IIOP_SSL_MUTUALAUTH_PORT=23921

               Command create-instance executed successfully.

       Example 4, Creating a Clustered GlassFish Server Instance
           This example creates the clustered GlassFish Server instance
           pmdinst1 in the domain domain1 on the local host. The instance is a
           member of the cluster pmdclust1.

               asadmin> create-instance --node localhost-domain1 --cluster pmdclust pmdinst1
               Port Assignments for server instance pmdinst1:
               JMX_SYSTEM_CONNECTOR_PORT=28686
               JMS_PROVIDER_PORT=27676
               HTTP_LISTENER_PORT=28080
               ASADMIN_LISTENER_PORT=24848
               IIOP_SSL_LISTENER_PORT=23820
               IIOP_LISTENER_PORT=23700
               HTTP_SSL_LISTENER_PORT=28181
               IIOP_SSL_MUTUALAUTH_PORT=23920

               Command create-instance executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-local-instance(1), create-node-config(1), create-node-dcom(1),
       create-node-ssh(1), create-system-properties(1), delete-instance(1),
       delete-system-property(1), list-instances(1), setup-ssh(1),
       start-instance(1), stop-instance(1)

       asadmin(1M)

Java EE 7                         08 Dec 2011               create-instance(1)
Command create-instance executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-instances [options] ...
list-instances(1)         asadmin Utility Subcommands        list-instances(1)

NAME
       list-instances - lists GlassFish Server instances in a domain

SYNOPSIS
           list-instances [--help] [--timeoutmsec timeout]
           [--long={false|true} | --nostatus={false|true}]
           [--standaloneonly={false|true} | target]

DESCRIPTION
       The list-instances subcommand lists GlassFish Server instances in a
       domain. The list can be filtered by cluster, instance, node, or
       configuration.

       The subcommand displays every GlassFish Server instance in the
       specified target, regardless of how each instance was created. For
       example, this subcommand lists instances that were created by using the
       create-instance(1) subcommand and by using the create-local-instance(1)
       subcommand.

       By default, the subcommand indicates whether each instance that is
       listed is running. Options of this subcommand control the information
       that is displayed for each instance.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --timeoutmsec
           The time limit in milliseconds for determining the status of
           instances. The default is 2,000, which is equivalent to 2 seconds.

       --long, -l
           Specifies whether detailed information is displayed for each
           instance that is listed.

           The --long option and --nostatus option are mutually exclusive. If
           both options are specified in the same command, an error occurs.

           Valid values are as follows:

           true
               The following details are displayed for each instance that is
               listed:

               *   The name of the instance

               *   The name of the host where the instance's node resides

               *   The HTTP port on which the instance listens for
                   administration requests

               *   The process identifier (PID) of the instance process or -1
                   if the instance is not running

               *   The name of the cluster of which the instance is a member,
                   if any

               *   The state of the instance, which is running or not running

                   When an instance is listed, some configuration changes in
                   the domain administration server (DAS) for the instance
                   might not have been applied to the instance itself. In this
                   situation, the commands that are required to apply the
                   changes are listed adjacent to the state of the instance.
                   The maximum number of commands that are listed for an
                   instance is 10.

           false
               Only the name of the instance and an indication of whether the
               instance is running are displayed (default). The length of time
               that the instance has been running is not displayed.

       --nostatus
           Specifies whether information about whether instances are running
           is suppressed.

           The --long option and --nostatus option are mutually exclusive. If
           both options are specified in the same command, an error occurs.

           Valid values are as follows:

           true
               Information about whether instances are running is suppressed.
               Only the name of each instance is displayed.

           false
               Information about whether instances are running is displayed
               (default).

       --standaloneonly
           Specifies whether only standalone instances are listed.

           The --standaloneonly option and the target operand and are mutually
           exclusive. If both the --standaloneonly option and the target
           operand are specified in the same command, an error occurs.

           Valid values are as follows:

           true
               Only standalone instances are listed.

           false
               All instances in the specified target are listed (default).

OPERANDS
       target
           Filters the list of GlassFish Server instances by specifying the
           target for which instances are listed.

           The target operand and the --standaloneonly option are mutually
           exclusive. If both the target operand and the --standaloneonly
           option are specified in the same command, an error occurs.

           Valid values are as follows:

           domain
               Lists all instances in the domain (default).

           cluster-name
               Lists the instances that are members of the specified cluster.

           instance-name
               Lists only the specified instance.

           node-name
               Lists the instances that reside on the specified node.

           configuration-name
               Lists all instances whose configuration is defined by the
               specified named configuration.

EXAMPLES
       Example 1, Listing Basic Information About All GlassFish Server
       Instances in a Domain
           This example lists the name and status of all GlassFish Server
           instances in the current domain.

               asadmin> list-instances
               pmd-i-sj02 running
               yml-i-sj02 running
               pmd-i-sj01 running
               yml-i-sj01 running
               pmdsa1 not running

               Command list-instances executed successfully.

       Example 2, Listing Detailed Information About All GlassFish Server
       Instances in a Domain
           This example lists detailed information about all GlassFish Server
           instances in the current domain.

               asadmin> list-instances --long=true
               NAME        HOST       PORT   PID    CLUSTER     STATE
               pmd-i-sj01  sj01       24848  31310  pmdcluster   running
               yml-i-sj01  sj01       24849  25355  ymlcluster   running
               pmdsa1      localhost  24848  -1     ---          not running
               pmd-i-sj02  sj02       24848  22498  pmdcluster   running
               yml-i-sj02  sj02       24849  20476  ymlcluster   running
               ymlsa1      localhost  24849  -1     ---          not running
               Command list-instances executed successfully.

       Example 3, Displaying the Status of an Instance
           This example displays status of the instance pmd-i-sj01, which is
           running.

               asadmin> list-instances pmd-i-sj01
               pmd-i-sj01 running
               Command list-instances executed successfully.

       Example 4, Listing Only Standalone Instances in a Domain
           This example lists only the standalone instances in the current
           domain.

               asadmin> list-instances --standaloneonly=true
               pmdsa1 not running
               Command list-instances executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-instance(1), create-local-instance(1)

       asadmin(1M)

Java EE 7                         10 Dec 2010                list-instances(1)
Command list-instances executed successfully.

ins2   not running  
Command list-instances executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help start-instance [options] ...
start-instance(1)         asadmin Utility Subcommands        start-instance(1)

NAME
       start-instance - starts a GlassFish Server instance

SYNOPSIS
           start-instance [--help]
           [--debug={false|true}] [--sync={normal|full|none}]
           instance-name

DESCRIPTION
       The start-instance subcommand starts a GlassFish Server instance. This
       subcommand requires the Distributed Component Object Model (DCOM)
       remote protocol or secure shell (SSH) to be configured on the machine
       where the domain administration server (DAS) is running and on the
       machine where the instance resides.

           Note
           +----------------------------------------+
           |           DCOM or SSH is not required  |
           |           if the instance resides on a |
           |           node of type CONFIG that     |
           |           represents the local host. A |
           |           node of type CONFIG is not   |
           |           enabled for remote           |
           |           communication over DCOM or   |
           |           SSH.                         |
           +----------------------------------------+

       You may run this subcommand from any machine that can contact the DAS.

       The subcommand can start any GlassFish Server instance, regardless of
       how the instance was created. For example, this subcommand can start an
       instance that was created by using the create-local-instance(1)
       subcommand.

       This command is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --debug
           Specifies whether the instance is started with Java Platform
           Debugger Architecture (JPDA)

           (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

           debugging enabled.

           Possible values are as follows:

           true
               The instance is started with JPDA debugging enabled and the
               port number for JPDA debugging is displayed.

           false
               The instance is started with JPDA debugging disabled (default).

       --sync
           The type of synchronization between the DAS and the instance's
           files when the instance is started.

           Possible values are as follows:

           none
               The DAS does not synchronize the instance's files with any
               changes. This type of synchronization minimizes the time that
               is required to start the instance.

           normal
               The DAS synchronizes the instance with changes since the last
               synchronization as follows:

               *   For the config directory, the DAS synchronizes the instance
                   with all changes.

               *   For the applications directory and docroot directory, only
                   a change to a top-level subdirectory causes the DAS to
                   synchronize all files under that subdirectory.

                   If a file below a top level subdirectory is changed without
                   a change to a file in the top level subdirectory, full
                   synchronization is required. In normal operation, files
                   below the top level subdirectories of these directories are
                   not changed. If an application is deployed and undeployed,
                   full synchronization is not necessary to update the
                   instance with the change.

               This value is the default.

           full
               The DAS synchronizes the instance with all of the instance's
               files, regardless of whether the files have changed since the
               last synchronization. This type of synchronization might delay
               the startup of the instance while the DAS updates all files in
               the instance's directories.

OPERANDS
       instance-name
           The name of the GlassFish Server instance to start.

EXAMPLES
       Example 1, Starting a GlassFish Server Instance
           This example starts the GlassFish Server instance pmdsa1.

               asadmin> start-instance pmdsa1
               Waiting for the server to start ..............................
               Successfully started the instance: pmdsa1
               instance Location: /export/glassfish3/glassfish/nodes/localhost/pmdsa1
               Log File: /export/glassfish3/glassfish/nodes/localhost/pmdsa1/logs/server.log
               Admin Port: 24848
               Command start-local-instance executed successfully.
               The instance, pmdsa1, was started on host localhost

               Command start-instance executed successfully.

       Example 2, Starting a GlassFish Server Instance With JPDA Debugging
       Enabled
           This example starts the GlassFish Server instance ymlsa1 with JPDA
           debugging enabled.

               asadmin> start-instance --debug=true ymlsa1
               Waiting for the server to start ...............................
               Successfully started the instance: ymlsa1
               instance Location: /export/glassfish3/glassfish/nodes/localhost/ymlsa1
               Log File: /export/glassfish3/glassfish/nodes/localhost/ymlsa1/logs/server.log
               Admin Port: 24849
               Debugging is enabled. The debugging port is: 29010
               Command start-local-instance executed successfully.
               The instance, ymlsa1, was started on host localhost

               Command start-instance executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-instance(1), create-local-instance(1), delete-instance(1),
       delete-local-instance(1), setup-ssh(1), start-domain(1),
       start-local-instance(1), stop-domain(1), stop-instance(1),
       stop-local-instance(1), validate-dcom(1)

       asadmin(1M)

       Java Platform Debugger Architecture (JPDA)
       (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

Java EE 7                         8 Dec 2011                 start-instance(1)
Command start-instance executed successfully.

Waiting for ins2 to start ....................
Successfully started the instance: ins2
instance Location: /home/cdctest/glassfish4_b80/glassfish/nodes/localhost-domain1/ins2
Log File: /home/cdctest/glassfish4_b80/glassfish/nodes/localhost-domain1/ins2/logs/server.log
Admin Port: 24848
Command start-local-instance executed successfully.
The instance, ins2, was started on host localhost
Command start-instance executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help stop-instance [options] ...
stop-instance(1)          asadmin Utility Subcommands         stop-instance(1)

NAME
       stop-instance - stops a running GlassFish Server instance

SYNOPSIS
           stop-instance [--help]
           [--force={false|true}] [--kill={false|true}]
           instance-name

DESCRIPTION
       The stop-instance subcommand stops a running GlassFish Server instance.

       The subcommand can stop any GlassFish Server instance, regardless of
       how the instance was created. For example, this subcommand can stop an
       instance that was created by using the create-local-instance(1)
       subcommand.

       This command is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --force
           Specifies whether the instance is forcibly stopped immediately.

           Possible values are as follows:

           true
               The instance is forcibly stopped immediately (default).

           false
               The subcommand waits until all threads that are associated with
               the instance are exited before stopping the instance.

       --kill
           Specifies whether the instance is killed by using functionality of
           the operating system to terminate the instance process.

           Possible values are as follows:

           false
               The instance is not killed. The subcommand uses functionality
               of the Java platform to terminate the instance process
               (default).

           true
               The instance is killed. The subcommand uses functionality of
               the operating system to terminate the instance process.

OPERANDS
       instance-name
           This is the name of the GlassFish Server instance to stop.

EXAMPLES
       This example stops the GlassFish Server instance yml-i-sj01.

       Example 1, Stopping a GlassFish Server Instance

               asadmin> stop-instance yml-i-sj01
               The instance, yml-i-sj01, was stopped.

               Command stop-instance executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-instance(1), create-local-instance(1), delete-instance(1),
       delete-local-instance(1), start-domain(1), start-instance(1),
       start-local-instance(1), stop-domain(1), stop-local-instance(1)

       asadmin(1M)

Java EE 7                         16 Dec 2010                 stop-instance(1)
Command stop-instance executed successfully.

The instance, ins2, is stopped.
Command stop-instance executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-instance [options] ...
delete-instance(1)        asadmin Utility Subcommands       delete-instance(1)

NAME
       delete-instance - deletes a GlassFish Server instance

SYNOPSIS
           delete-instance [--help] instance-name

DESCRIPTION
       The delete-instance subcommand deletes a GlassFish Server instance.
       This subcommand requires the Distributed Component Object Model (DCOM)
       remote protocol or secure shell (SSH) to be configured on the host
       where the domain administration server (DAS) is running and on the host
       that is represented by the node where the instance resides.

           Note
           +----------------------------------------+
           |           DCOM or SSH is not required  |
           |           if the instance resides on a |
           |           node of type CONFIG that     |
           |           represents the local host. A |
           |           node of type CONFIG is not   |
           |           enabled for remote           |
           |           communication over DCOM or   |
           |           SSH.                         |
           +----------------------------------------+

       You may run this subcommand from any host that can contact the DAS.

       The subcommand can delete any GlassFish Server instance, regardless of
       how the instance was created. For example, this subcommand can delete
       an instance that was created by using the create-local-instance(1)
       subcommand.

       The instance that is being deleted must not be running. Otherwise, an
       error occurs.

       The subcommand deletes an instance by performing the following actions:

       *   Removing the instance from the configuration of the domain
           administration server (DAS)

       *   Deleting the instance's files from file system

       If the instance that is being deleted is the only instance that is
       using the node directory, that directory is also removed.

       If a standalone instance is deleted, the instance's standalone
       configuration is also deleted. A standalone instance refers to a
       configuration that is named instance-name-config to which no other
       clusters or unclustered instances refer.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       instance-name
           The name of the instance to delete.

EXAMPLES
       Example 1, Deleting a GlassFish Server Instance
           This example deletes the GlassFish Server instance pmdsainst.

               asadmin> delete-instance pmdsainst

               Command delete-instance executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-instance(1), create-local-instance(1), delete-local-instance(1),
       setup-ssh(1), start-instance(1), start-local-instance(1),
       stop-instance(1), stop-local-instance(1), validate-dcom(1)

       asadmin(1M)

Java EE 7                         08 Dec 2011               delete-instance(1)
Command delete-instance executed successfully.

Command _delete-instance-filesystem executed successfully.
The instance, ins2, was deleted from host localhost
Command delete-instance executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-cluster [options] ...
create-cluster(1)         asadmin Utility Subcommands        create-cluster(1)

NAME
       create-cluster - creates a GlassFish Server cluster

SYNOPSIS
           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

DESCRIPTION
       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:

       *   create-instance(1)

       *   create-local-instance(1)

       To delete server instances from the cluster at any time, use one of the
       following subcommands:

       *   delete-instance(1)

       *   delete-local-instance(1)

       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.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --config
           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.

       --systemproperties
           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:

           ASADMIN_LISTENER_PORT
               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.

           HTTP_LISTENER_PORT
               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.

           HTTP_SSL_LISTENER_PORT
               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.

           IIOP_LISTENER_PORT
               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.

           IIOP_SSL_LISTENER_PORT
               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.

           IIOP_SSL_MUTUALAUTH_PORT
               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.

           JAVA_DEBUGGER_PORT
               This property specifies the port number of the port that is
               used for connections to the Java Platform Debugger Architecture
               (JPDA)

               (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

               debugger. Valid values are 1-65535. On UNIX, creating sockets
               that listen on ports 1-1024 requires superuser privileges.

           JMS_PROVIDER_PORT
               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.

           JMX_SYSTEM_CONNECTOR_PORT
               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.

           OSGI_SHELL_TELNET_PORT
               This property specifies the port number of the port that is
               used for connections to the Apache Felix Remote Shell

               (http://felix.apache.org/site/apache-felix-remote-shell.html) .
               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.

       --properties
           Defines properties for the cluster. The following properties are
           available:

           GMS_DISCOVERY_URI_LIST
               The locations of GlassFish Server instances in the cluster to
               use for discovering the cluster. This property is required only
               if the Group Management Service (GMS) is not using multicast
               for broadcasting messages.

               Valid values for this property are as follows:

               *   A comma-separated list of uniform resource identifiers
                   (URIs). Each URI must locate a GlassFish Server instance or
                   the DAS. This format is required if multiple GlassFish
                   Server instances are running on the same host.

                   The format of each URI in the list is as follows:

                   scheme://host-name-or -IP-address:port

                   *   scheme is the URI scheme, which is tcp.

                   *   host-name-or -IP-address is the host name or IP address
                       of the host on which the instance is running.

                   *   port is the port number of the port on which the
                       instance listens for messages from GMS. The system
                       property GMS_LISTENER_PORT-clustername must be set for
                       the instance. For information about how to set this
                       system property for an instance, see "Discovering a
                       Cluster When Multicast Transport Is Unavailable" in
                       Oracle GlassFish Server High Availability
                       Administration Guide.

               *   A comma-separated list of IP addresses or host names on
                   which the DAS or the instances are running. The list can
                   contain a mixture of IP addresses and host names. This
                   format can be used only if one clustered instance is
                   running on each host. The value of the GMS_LISTENER_PORT
                   property must be unique for each cluster in a domain.

               *   The keyword generate. This format can be used only if one
                   instance in a cluster is running on each host and the DAS
                   is running on a separate host. Multiple instances on the
                   same host cannot be members of the same cluster. The value
                   of the GMS_LISTENER_PORT property must be unique for each
                   cluster in a domain.

           GMS_LISTENER_PORT
               The port number of the port on which the cluster listens for
               messages from GMS.

               The default value is a reference to the
               GMS_LISTENER_PORT-cluster-name system property. By default,
               this system property is not set. In this situation, GMS selects
               a free port from the range that is defined by the properties
               GMS_TCPSTARTPORT and GMS_TCPENDPORT. By default, this range is
               9090-9200. In most situations, the default behavior should
               suffice.

               However, if GMS is not using multicast for broadcasting
               messages, the GMS_LISTENER_PORT property must specify a port
               number that is valid for all GlassFish Server instances in the
               cluster. To use the default value to meet this requirement, use
               a system property to set the port number individually for each
               instance.

               For example, use the create-system-properties subcommand to
               create the system property GMS_LISTENER_PORT-cluster-name for
               the DAS. Then, for each instance in the cluster, set the
               GMS_LISTENER_PORT-cluster-name system property to the port
               number on which the instance listens for messages from GMS. The
               default value of the GMS_LISTENER_PORT property for the cluster
               references this system property.

           GMS_LOOPBACK
               Specifies whether an instance may receive from itself
               application-level messages that the instance broadcasts to the
               cluster.

               Possible values are as follows:

               false
                   The instance may not receive messages from itself
                   (default).

               true
                   The instance may receive messages from itself. Use this
                   setting for testing an instance when the instance is the
                   only instance in a cluster.

           GMS_MULTICAST_TIME_TO_LIVE
               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.

           GMS_TCPENDPORT
               The highest port number in the range from which GMS selects a
               free port if the GMS_LISTENER_PORT-cluster-name system property
               is not set. The default is 9200.

           GMS_TCPSTARTPORT
               The lowest port number in the range from which GMS selects a
               free port if the GMS_LISTENER_PORT-cluster-name system property
               is not set. The default is 9090.

       --gmsenabled
           Specifies whether GMS is enabled for the cluster.

           Possible values are as follows:

           true
               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.

           false
               GMS is disabled for the cluster.

       --multicastaddress
           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.

       --multicastport
           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-49151. The default is an automatically generated value
           in this range.

       --bindaddress
           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.

       --hosts
           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.

       --haagentport
           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.

       --haadminpassword
           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.

       --haadminpasswordfile
           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.

       --devicesize
           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.

       --haproperty
           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.

       --autohadb
           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.

       --portbase
           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.

OPERANDS
       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 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.

           If the configure-jms-cluster(1) subcommand is to be used to
           configure a Message Queue cluster to provide JMS services to the
           GlassFish Server cluster, the length of the GlassFish Server
           cluster name is might be restricted:

           *   If clustertype is set to enhanced in the
               configure-jms-cluster(1) subcommand, the name can be no longer
               than n–21 characters, where n is the maximum table name length
               allowed by the database.

           *   If configstoretype is set to shareddb in the
               configure-jms-cluster(1) subcommand, the name can be no longer
               than n–19 characters, where n is the maximum table name length
               allowed by the database.

EXAMPLES
       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.

       Example 2, Creating a Cluster With a List of URIs for Discovering the
       Cluster
           This example creates a cluster that is named tcpcluster. In this
           example, GMS is not using multicast for broadcasting messages and
           multiple instances reside on the same host. Therefore, the
           GMS_DISCOVERY_URI_LIST property is set to the locations of the
           GlassFish Server instances to use for discovering the cluster.
           These instances reside on the host whose IP address is
           10.152.23.224 and listen for GMS events on ports 9090, 9091, and
           9092.

           To distinguish colon (:) characters in URIs from separators in a
           property list, colons in URIs are escaped with single quote
           characters (') and backslash (\) characters. For more information
           about escape characters in options for the asadmin utility, see the
           asadmin(1M) help page.

           This example assumes that the port on which each instance listens
           for GMS messages is set independently for the instance through the
           GMS_LISTENER_PORT-tcpcluster system property. For information about
           how to set the port on which an instance listens for GMS messages,
           see "Discovering a Cluster When Multicast Transport Is Unavailable"
           in Oracle GlassFish Server High Availability Administration Guide.

               asadmin> create-cluster --properties GMS_DISCOVERY_URI_LIST=
               tcp'\\:'//10.152.23.224'\\:'9090,
               tcp'\\:'//10.152.23.224'\\:'9091,
               tcp'\\:'//10.152.23.224'\\:'9092 tcpcluster
               Command create-cluster executed successfully.

       Example 3, Creating a Cluster With a List of IP Addresses for
       Discovering the Cluster
           This example creates a cluster that is named ipcluster. In this
           example, GMS is not using multicast for broadcasting messages and
           only one clustered instance resides on each host. Therefore, the
           GMS_DISCOVERY_URI_LIST property is set to the IP addresses of the
           hosts where instances to use for discovering the cluster are
           running. The cluster listens for messages from GMS on port 9090.

               asadmin> create-cluster --properties 'GMS_DISCOVERY_URI_LIST=
               10.152.23.225,10.152.23.226,10.152.23.227,10.152.23.228:
               GMS_LISTENER_PORT=9090' ipcluster
               Command create-cluster executed successfully.

       Example 4, Creating a Cluster With a Generated List of Instances for
       Discovering the Cluster
           This example creates a cluster that is named gencluster. In this
           example, GMS is not using multicast for broadcasting messages, one
           instance in the cluster is running on each host and the DAS is
           running on a separate host. Therefore, the GMS_DISCOVERY_URI_LIST
           property is set to the keyword generate to generate a list of
           instances to use for discovering the cluster. The cluster listens
           for messages from GMS on port 9090.

               asadmin> create-cluster --properties 'GMS_DISCOVERY_URI_LIST=generate:
               GMS_LISTENER_PORT=9090' gencluster
               Command create-cluster executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       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)

       asadmin(1M)

       "Discovering a Cluster When Multicast Transport Is Unavailable" in
       Oracle GlassFish Server High Availability Administration Guide

       Apache Felix Remote Shell
       (http://felix.apache.org/site/apache-felix-remote-shell.html), Java
       Platform Debugger Architecture (JPDA)
       (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

Java EE 7                         4 Jan 2012                 create-cluster(1)
Command create-cluster executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-clusters [options] ...
list-clusters(1)          asadmin Utility Subcommands         list-clusters(1)

NAME
       list-clusters - lists existing clusters in a domain

SYNOPSIS
           list-clusters [--help] [target]

DESCRIPTION
       The list-clusters subcommand lists existing clusters in a domain. The
       list can be filtered by cluster, instance, node, or configuration. For
       each cluster that is listed, the subcommand indicates whether the
       cluster is running.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       target
           Filters the list of clusters by specifying the target for which the
           clusters are to be listed. Valid values are as follows:

           domain
               Lists all clusters in the domain (default).

           cluster-name
               Lists only the specified cluster.

           instance-name
               Lists the cluster of which the specified instance is a member.

           node-name
               Lists the clusters that contain an instance that resides on the
               specified node. For example, if instance pmdi1 in cluster pmdc
               and instance ymli1 in cluster ymlc reside on node n1, pmdc and
               ymlc are listed.

           configuration-name
               Lists all clusters that contain instances whose configuration
               is defined by the named configuration.

EXAMPLES
       Example 1, Listing All Clusters in a Domain
           This example lists all clusters in the current domain.

               asadmin> list-clusters
               pmdclust not running
               ymlclust not running

               Command list-clusters executed successfully.

       Example 2, Displaying the Status of a Cluster
           This example displays status of the cluster ymlclust, which is not
           running.

               asadmin> list-clusters ymlclust
               ymlclust not running

               Command list-clusters executed successfully.

       Example 3, Listing All Clusters That Are Associated With a Node
           This example lists the clusters that contain an instance that
           resides on the node sj02.

               asadmin> list-clusters sj02
               ymlclust not running

               Command list-clusters executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-cluster(1), delete-cluster(1), start-cluster(1), stop-cluster(1)

       asadmin(1M)

Java EE 7                         9 Sep 2010                  list-clusters(1)
Command list-clusters executed successfully.

cluster2 not running
Command list-clusters executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-cluster [options] ...
delete-cluster(1)         asadmin Utility Subcommands        delete-cluster(1)

NAME
       delete-cluster - deletes a GlassFish Server cluster

SYNOPSIS
           delete-cluster [--help]
           [--autohadboverride={true|false}] [--node-agent=node-agent--name]
           cluster-name

DESCRIPTION
       The delete-cluster subcommand deletes a GlassFish Server cluster. A
       cluster can be deleted only if the cluster contains no GlassFish Server
       instances. If a cluster that you are deleting contains any instances,
       stop and delete the instances before deleting the cluster.

       If the cluster's named configuration was created automatically for the
       cluster and no other clusters or unclustered instances refer to the
       configuration, the configuration is deleted when the cluster is
       deleted. A configuration that is created automatically for a cluster is
       named cluster-name-config, where cluster-name is the name of the
       cluster.

       This command is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --autohadboverride
           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.

       --nodeagent
           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.

OPERANDS
       cluster-name
           The name of the cluster to delete.

EXAMPLES
       Example 1, Deleting a GlassFish Server Cluster
           This example deletes the GlassFish Server cluster adccluster.

               asadmin> delete-cluster adccluster
               Command delete-cluster executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-cluster(1), delete-instance(1), delete-local-instance(1),
       list-clusters(1), start-cluster(1), stop-instance(1),
       stop-local-instance(1), stop-cluster(1)

       asadmin(1M)

Java EE 7                         7 Dec 2010                 delete-cluster(1)
Command delete-cluster executed successfully.

Command delete-cluster executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-node-ssh [options] ...
create-node-ssh(1)        asadmin Utility Subcommands       create-node-ssh(1)

NAME
       create-node-ssh - creates a node that is enabled for communication over
       SSH

SYNOPSIS
           create-node-ssh [--help]
           --nodehost node-host
           [--installdir as-install-parent] [--nodedir node-dir]
           [--sshport ssh-port] [--sshuser ssh-user]
           [--sshkeyfile ssh-keyfile]
           [--force={false|true}]
           [--install={false|true}] [--archive archive]
           node-name

DESCRIPTION
       The create-node-ssh subcommand creates a node that is enabled for
       communication over secure shell (SSH).

       A node represents a host on which the GlassFish Server software is
       installed. A node must exist for every host on which GlassFish Server
       instances reside.

       The domain administration server (DAS) contacts an SSH node's host
       through the SSH connector to manage GlassFish Server instances that
       reside on the node. However, the DAS does not use the SSH connector to
       contact the host where the DAS is running because the DAS can run all
       asadmin subcommands locally.

       By default, the subcommand fails and the node is not created if the DAS
       cannot contact the node's host through SSH. To force the node to be
       created in the DAS configuration even if the host cannot be contacted
       through SSH, set the --force option to true.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --nodehost
           The name of the host that the node represents. The name of the host
           must be specified. Otherwise, an error occurs.

       --installdir
           The full path to the parent of the base installation directory of
           the GlassFish Server software on the host, for example,
           /export/glassfish3/. The default is the parent of the default base
           installation directory of the GlassFish Server software for the
           DAS. This default is useful only if GlassFish Server is installed
           in the same location on all hosts.

       --nodedir
           The path to the directory that is to contain GlassFish Server
           instances that are created on the node. The default is
           as-install/nodes, where as-install is the base installation
           directory of the GlassFish Server software on the host. If a
           relative path is specified, the path is relative to the as-install
           directory.

       --sshport
           The port to use for SSH connections to this node's host. The
           default is 22. If the --nodehost option is set to localhost-domain,
           the --sshport option is ignored.

       --sshuser
           The user on this node's host that is to run the process for
           connecting to the host through SSH. The default is the user that is
           running the DAS process. To ensure that the DAS can read this
           user's SSH private key file, specify the user that is running the
           DAS process. If the --nodehost option is set to localhost-domain,
           the --sshuser option is ignored.

       --sshkeyfile
           The absolute path to the SSH private key file for user that the
           --sshuser option specifies. This file is used for authentication to
           the sshd daemon on the node's host.

               Note
               +----------------------------------------+
               |GlassFish Server also supports password |
               |authentication through the              |
               |AS_ADMIN_SSHPASSWORD entry in the       |
               |password file. The password file is     |
               |specified in the --paswordfile option   |
               |of the asadmin(1M) utility.             |
               +----------------------------------------+
           If the SSH private key file is protected by a passphrase, the
           password file must contain the AS_ADMIN_SSHKEYPASSPHRASE entry.

           The path to the key file must be reachable by the DAS and the key
           file must be readable by the DAS.

           The default is the a key file in the user's .ssh directory. If
           multiple key files are found, the subcommand uses the following
           order of preference:

            1. id_rsa

            2. id_dsa

            3. identity

       --force
           Specifies whether the node is created in the DAS configuration even
           if validation of the node's parameters fails. To validate a node's
           parameters, the DAS must be able to contact the node's host through
           SSH. Possible values are as follows:

           false
               The node is not created if validation of the node's parameters
               fails (default).

           true
               The node is created even if validation of the node's parameters
               fails.

       --install
           Specifies whether the subcommand shall install the GlassFish Server
           software on the host that the node represents.

           Possible values are as follows:

           false
               The subcommand shall not install the GlassFish Server software
               on the host (default).

           true
               The subcommand shall install the GlassFish Server software on
               the host.

       --archive
           The absolute path to the archive file of the GlassFish Server
           software that is to be installed. If this option is omitted and the
           --install is true, the subcommand creates a ZIP archive of the
           GlassFish Server software from the installation where this
           subcommand is run. The archive does not contain the domains
           directory or the nodes directory.

OPERANDS
       node-name
           The name of the node.

           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 node, a cluster, a named configuration, or a
               GlassFish Server instance.

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

EXAMPLES
       Example 1, Creating a Node
           This example creates the node adc for the host adc.example.com. By
           default, the parent of the base installation directory of the
           GlassFish Server software is /export/glassfish3.

               asadmin> create-node-ssh
               --nodehost adc.example.com
               --installdir /export/glassfish3 adc

               Command create-node-ssh executed successfully.

       Example 2, Forcing the Creation of a Node
           This example forces the creation of node eg1 for the host
           eghost.example.com. The node is created despite the failure of the
           DAS to contact the host eghost.example.com to validate the node's
           parameters.

               asadmin> create-node-ssh --force --nodehost eghost.example.com eg1
               Warning: some parameters appear to be invalid.
               Could not connect to host eghost.example.com using SSH.
               There was a problem while connecting to eghost.example.com:22
               eghost.example.com
               Continuing with node creation due to use of --force.

               Command create-node-ssh executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-config(1), create-node-dcom(1), delete-node-ssh(1),
       install-node(1), install-node-ssh(1), list-nodes(1), ping-node-ssh(1),
       setup-ssh(1), uninstall-node(1), uninstall-node-ssh(1),
       update-node-ssh(1)

       asadmin(1M)

Java EE 7                         5 Jan 2012                create-node-ssh(1)
Command create-node-ssh executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-nodes [options] ...
list-nodes(1)             asadmin Utility Subcommands            list-nodes(1)

NAME
       list-nodes - lists all GlassFish Server nodes in a domain

SYNOPSIS
           list-nodes [--help] [--long={false|true}]

DESCRIPTION
       The list-nodes subcommand lists all GlassFish Server nodes in a domain.

       By default, the subcommand displays the following information for each
       node that is listed:

       *   The name of the node

       *   The type of the node, which is one of the following types:

           CONFIG
               The node does not support remote communication.

           DCOM
               The node supports communication over the Distributed Component
               Object Model (DCOM) remote protocol.

           SSH
               The node supports communication over secure shell (SSH).

       *   The name of the host that the node represents

       The --long option of the subcommand specifies whether the nodes are
       listed in long format. In long format, the following additional
       information about each node is displayed:

       *   The path to the parent of the base installation directory of
           GlassFish Server on the host that the node represents

       *   A comma-separated list of the names of the GlassFish Server
           instances that reside on the node

       If the --terse option of the asadmin(1M) utility is true and the --long
       option of the subcommand is false, the subcommand lists only the name
       of each node.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Specifies whether the nodes are listed in long format.

           Possible values are as follows:

           true
               The nodes are listed in long format.

           false
               The nodes are listed in short format (default).

EXAMPLES
       Example 1, Listing GlassFish Server Nodes
           This example displays the name, type, and host for all GlassFish
           Server nodes in the domain domain1.

               asadmin> list-nodes
               localhost-domain1  CONFIG  localhost
               sj02  SSH  sj02.example.com
               sj01  SSH  sj01.example.com
               devnode  CONFIG  localhost
               Command list-nodes executed successfully.

       Example 2, Listing Only the Names of GlassFish Server Nodes
           This example uses the --terse option of the asadmin utility to list
           only the names of the GlassFish Server nodes in the domain domain1.

               asadmin> list-nodes --terse=true
               localhost-domain1
               sj02
               sj01
               devnode

       Example 3, Listing GlassFish Server Nodes in Long Format
           This example lists the GlassFish Server nodes in the domain domain1
           in long format.

               asadmin> list-nodes --long=true
               NODE NAME           TYPE     NODE HOST          INSTALL DIRECTORY     REFERENCED BY
               localhost-domain1   CONFIG   localhost          /export/glassfish3
               sj02                SSH      sj02.example.com   /export/glassfish3    pmd-i2, yml-i2
               sj01                SSH      sj01.example.com   /export/glassfish3    pmd-i1, yml-i1
               devnode             CONFIG   localhost          /export/glassfish3    pmdsa1
               Command list-nodes executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-config(1), create-node-dcom(1), create-node-ssh(1),
       delete-node-config(1), delete-node-dcom(1), delete-node-ssh(1),
       list-nodes-config(1), list-nodes-dcom(1), list-nodes-ssh(1)

       asadmin(1M)

Java EE 7                         8 Dec 2011                     list-nodes(1)
Command list-nodes executed successfully.

localhost-domain1  CONFIG  localhost
node-ssh-1  SSH  localhost
Command list-nodes executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-node-ssh [options] ...
delete-node-ssh(1)        asadmin Utility Subcommands       delete-node-ssh(1)

NAME
       delete-node-ssh - deletes a node that is enabled for communication over
       SSH

SYNOPSIS
           delete-node-ssh [--help]
           [--uninstall={false|true}] [--force={false|true}]
           node-name

DESCRIPTION
       The delete-node-ssh subcommand deletes a node that is enabled for
       communication over secure shell (SSH) from the domain. This subcommand
       does not require SSH to be configured.

       This subcommand can delete only a node that is enabled for
       communication over SSH. The subcommand for deleting other types of
       nodes depends on the type of the node:

       *   A node that is enabled for communication over the Distributed
           Component Object Model (DCOM) remote protocol must be deleted by
           using the delete-node-dcom(1) subcommand.

       *   A node that is not enabled for remote communication must be deleted
           by using the delete-node-config(1) subcommand.

       To determine whether a node is enabled for communication over SSH, use
       the list-nodes(1) subcommand.

       No GlassFish Server instances must reside on the node that is being
       deleted. Otherwise, the subcommand fails. Before running this
       subcommand, delete any instances that reside on the node by using, for
       example, the delete-instance(1) subcommand or the
       delete-local-instance(1) subcommand.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --uninstall
           Specifies whether the GlassFish Server software is uninstalled from
           host that the node represents.

           Possible values are as follows:

           false
               The GlassFish Server software is not uninstalled from the host
               (default).

           true
               The GlassFish Server software is uninstalled from the host. By
               default, if any node except the predefined node
               localhost-domain resides on any host from which GlassFish
               Server software is being uninstalled, the subcommand fails. To
               uninstall the GlassFish Server software from a host on which
               user-defined nodes reside, set the --force option to true. If
               the --force option is true, the subcommand removes the entire
               content of the parent of the base installation directory.

       --force
           If --uninstall is true, specifies whether the subcommand uninstalls
           the GlassFish Server software from a host even if a user-defined
           node resides on the host. Possible values are as follows:

           false
               If a user-defined node resides on a host, the software is not
               uninstalled and the subcommand fails (default).

               If the --force option is false, the subcommand removes only the
               GlassFish Server software files. Other content if the parent of
               the base installation directory, such as configuration files,
               are not removed.

           true
               The subcommand uninstalls the GlassFish Server software from
               the host even if a user-defined node resides on the host.

               If the --force option is true, the subcommand removes the
               entire content of the parent of the base installation
               directory.

OPERANDS
       node-name
           The name of the node to delete. The node must enabled for
           communication over SSH. Otherwise, an error occurs.

EXAMPLES
       Example 1, Deleting a Node That Is Enabled for Communication Over SSH
           This example deletes the node eg1, which is enabled for
           communication over SSH.

               asadmin> delete-node-ssh eg1
               Command delete-node-ssh executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-dcom(1), create-node-ssh(1), delete-node-config(1),
       delete-node-dcom(1), delete-instance(1), delete-local-instance(1),
       install-node(1), install-node-dcom(1), install-node-ssh(1),
       list-nodes(1), uninstall-node(1), uninstall-node-dcom(1),
       uninstall-node-ssh(1), update-node-dcom(1), update-node-ssh(1)

       asadmin(1M)

Java EE 7                         8 Dec 2011                delete-node-ssh(1)
Command delete-node-ssh executed successfully.

Command delete-node-ssh executed successfully.

Can't find remote man page, looking locally...
list-http-lb-configs(1)   asadmin Utility Subcommands  list-http-lb-configs(1)

NAME
       list-http-lb-configs - lists load balancer configurations

SYNOPSIS
           list-http-lb-configs [--help] [target]

DESCRIPTION
       The list-http-lb-configs subcommand lists the load balancer
       configurations. List them all or list them by the cluster or server
       instance they reference.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       target
           Lists the load balancers by target. Valid values are:

           *   cluster_name- The name of a target cluster.

           *   instance_name- The name of a target server instance.

EXAMPLES
       Example 1, Listing Load Balancer Configurations Without a Target
           This example lists all load balancer configurations defined for all
           GlassFish Server clusters and instances.

               asadmin> list-http-lb-configs

               mycluster-http-lb-config
               serverinstlb
               Command list-http-lb-configs executed successfully.

       Example 2, Listing Load Balancer Configurations for a Specific Target
           This example lists the load balancer configuration defined for a
           cluster named mycluster.

               asadmin> list-http-lb-configs mycluster

               mycluster-http-lb-config
               Command list-http-lb-configs executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-http-lb-config(1), create-http-lb-config(1)

       asadmin(1M)

Java EE 7                         26 Aug 2010          list-http-lb-configs(1)
Command list-http-lb-configs executed successfully.

Command list-http-lb-configs executed successfully.

Can't find remote man page, looking locally...
create-http-lb(1)         asadmin Utility Subcommands        create-http-lb(1)

NAME
       create-http-lb - creates a load balancer

SYNOPSIS
           create-http-lb [--help] --devicehost device_host_or_IP_address --deviceport device_port
           [--sslproxyhost proxy_host]
           [--sslproxyport proxy_port] [--target target] [--lbpolicy lbpolicy] [--lbpolicymodule lb_policy_module] [--healthchec
kerurl url]
           [--healthcheckerinterval 10] [--healthcheckertimeout 10]
           [--lbenableallinstances=true] [--lbenableallapplications=true] [--lbweight instance=weight[:instance=weight]*] [--res
ponsetimeout 60] [--httpsrouting=false] [--reloadinterval60][--monitor=false][--routecookie=true]
           [--property (name=value)[:name=value]*
           ] load_balancer_name

DESCRIPTION
       Use the create-http-lb subcommand to create a load balancer, including
       the load balancer configuration, target reference, and health checker.
       A load balancer is a representation of the actual load balancer device,
       defined by its device host and port information. Once you've created
       the load balancer, you can automatically apply changes made to the load
       balancer configuration without running export-http-lb-config and
       manually copying the generated load balancer configuration file to the
       web server instance.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --devicehost
           The device host or the IP address of the load balancing device.
           This host or IP is where the physical load balancer will reside.

       --deviceport
           The port used to communicate with the load balancing device. It
           must be SSL enabled.

       --sslproxyhost
           The proxy host used for outbound HTTP.

       --sslproxyport
           The proxy port used for outbound HTTP.

       --target
           Specifies the target to which the load balancer applies.

           Valid values are:

           *   cluster_name- Specifies that requests for this cluster will be
               handled by the load balancer.

           *   stand-alone_instance_name- Specifies that requests for this
               stand-alone instance will be handled by the load balancer.

       --lbpolicy
           The policy the load balancer follows to distribute load to the
           server instances in a cluster. Valid values are round-robin,
           weighted-round-robin, and user-defined. If you choose user-defined,
           specify a load balancer policy module with the lbpolicymodule
           option. If you choose weighted-round-robin, assign weights to the
           server instances using the configure-lb-weight subcommand. The
           default is round-robin.

       --lbpolicymodule
           If your target is a cluster and the load balancer policy is
           user-defined, use this option to specify the full path and name of
           the shared library of your load balancing policy module. The shared
           library needs to be in a location accessible by the web server.

       --healthcheckerurl
           The URL to ping to determine whether the instance is healthy.

       --healthcheckerinterval
           The interval in seconds the health checker waits between checks of
           an unhealthy instance to see whether it has become healthy. The
           default value is 10 seconds. A value of 0 disables the health
           checker.

       --healthcheckertimeout
           The interval in seconds the health checker waits to receive a
           response from an instance. If the health checker has not received a
           response in this interval, the instance is considered unhealthy.
           The default value is 10 seconds.

       --lbenableallinstances
           Enables all instances in the target cluster for load balancing. If
           the target is a server instance, enables that instance for load
           balancing.

       --lbenableallapplications
           Enables all applications deployed to the target cluster or instance
           for load balancing.

       --lbweight
           The name of the instance and the weight you are assigning it. The
           weight must be an integer. The pairs of instances and weights are
           separated by colons. For example instance1=1:instance2=4 means that
           for every five requests, one goes to instance1 and four go to
           instance2. A weight of 1 is the default.

       --responsetimeout
           The time in seconds within which a server instance must return a
           response. If no response is received within the time period, the
           server is considered unhealthy. If set to a positive number, and
           the request is idempotent, the request is retried. If the request
           is not idempotent, an error page is returned. If set to 0 no
           timeout is used. The default is 60.

       --httpsrouting
           If set to true, HTTPS requests to the load balancer result in HTTPS
           requests to the server instance. If set to false, HTTPS requests to
           the load balancer result in HTTP requests to the server instance.
           The default is false.

       --reloadinterval
           The time, in seconds, that the load balancer takes to check for an
           updated configuration. When detected, the configuration file is
           reloaded. The default value is 60 seconds. A value of 0 disables
           reloading.

       --monitor
           If set to true, monitoring of the load balancer is switched on. The
           default value is false.

       --routecookie
           This option is deprecated. The value is always true.

       --property
           Optional attribute name/value pairs for configuring the load
           balancer.

OPERANDS
       lb_name
           The name of the new load balancer. This name must not conflict with
           any other load balancers in the domain.

EXAMPLES
       Example 1, Creating a Load Balancer
           This example creates a load balancer named mylb.

               asadmin> create-http-lb
               --devicehost host1 --deviceport 5555 mylb

               Command create-http-lb executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-http-lb(1), list-http-lbs(1), create-http-lb-config(1)

       asadmin(1M)

Java EE 7                         25 Aug 2010                create-http-lb(1)
Command create-http-lb executed successfully.

Command create-http-lb executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-http-lb-config [options] ...
NAME
     create-http-lb-config

SYNOPSIS
     Usage: create-http-lb-config
     	[--responsetimeout <responsetimeout(default:60)>]
     	[--monitor <monitor(default:false)>]
     	[--httpsrouting <httpsrouting(default:false)>]
     	[--property (name=value)[:name=value]*]
     	[--routecookie <routecookie(default:true)>]
     	[--reloadinterval <reloadinterval(default:60)>]
     	[-?|--help[=<help(default:false)>]] --target <target> | nam
     e

OPTIONS
     --responsetimeout

     --monitor

     --httpsrouting

     --target

     --property

     --routecookie

     --reloadinterval

OPERANDS
     name
Command create-http-lb-config executed successfully.

Command create-http-lb-config executed successfully.

Can't find remote man page, looking locally...
create-http-lb-ref(1)     asadmin Utility Subcommands    create-http-lb-ref(1)

NAME
       create-http-lb-ref - adds an existing cluster or server instance to an
       existing load balancer configuration or load balancer

SYNOPSIS
           create-http-lb-ref [--help] --config config_name | --lbname load_balancer_name
           [--lbpolicy round-robin] [--lbpolicymodule lb_policy_module]
           [--healthcheckerurl url] [--healthcheckerinterval 10]
           [--healthcheckertimeout 10] [--lbenableallinstances=true]
           [--lbenableallapplications=true] [--lbweight instance=weight[:instance=weight]*]
           target

DESCRIPTION
       Use the create-http-lb-ref subcommand to:

       *   Add an existing cluster or server instance to an existing load
           balancer configuration or load balancer. The load balancer forwards
           the requests to the clustered and standalone instances it
           references.

       *   Set the load balancing policy to round-robin, weighted round-robin,
           or to a user-defined policy.

       *   Configure a health checker for the load balancer. Any health
           checker settings defined here apply only to the target. If you do
           not create a health checker with this subcommand, use
           create-http-health-checker.

       *   Enable all instances in the target cluster for load balancing, or
           use enable-http-lb-server to enable them individually.

       *   Enable all applications deployed to the target for load balancing,
           or use enable-http-lb-application to enable them individually.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --config
           Specifies which load balancer configuration to which to add
           clusters and server instances. Specify either a load balancer
           configuration or a load balancer. Specifying both results in an
           error.

       --lbname
           Specifies the load balancer to which to add clusters and server
           instances. Specify either a load balancer configuration or a load
           balancer. Specifying both results in an error.

       --lbpolicy
           The policy the load balancer follows. Valid values are round-robin,
           weighted-round-robin, and user-defined. If you choose user-defined,
           specify a load balancer policy module with the lbpolicymodule
           option. If you choose weighted-round-robin assign weights to the
           server instances using the configure-lb-weight subcommand. The
           default is round-robin.

       --lbpolicymodule
           If your load balancer policy is user-defined, use this option to
           specify the full path and name of the shared library of your load
           balancing policy module. The shared library needs to be in a
           location accessible by the web server.

       --healthcheckerurl
           The URL to ping to determine whether the instance is healthy.

       --healthcheckerinterval
           The interval in seconds the health checker waits between checks of
           an unhealthy instance to see whether it has become healthy. The
           default value is 30 seconds. A value of 0 disables the health
           checker.

       --healthcheckertimeout
           The interval in seconds the health checker waits to receive a
           response from an instance. If the health checker has not received a
           response in this interval, the instance is considered unhealthy.
           The default is 10.

       --lbenableallinstances
           Enables all instances in the target cluster for load balancing. If
           the target is a server instance, enables that instance for load
           balancing. The default value is true.

       --lbenableallapplications
           Enables all applications deployed to the target cluster or instance
           for load balancing. The default value is true.

       --lbweight
           The name of the instance and the weight you are assigning it. The
           weight must be an integer. The pairs of instances and weights are
           separated by colons. For example instance1=1:instance2=4 means that
           for every five requests, one goes to instance1 and four go to
           instance2. A weight of 1 is the default.

OPERANDS
       target
           Specifies which cluster or instance to add to the load balancer.
           Valid values are:

           *   cluster_name- Specifies that requests for this cluster will be
               handled by the load balancer.

           *   stand-alone_instance_name- Specifies that requests for this
               standalone instance will be handled by the load balancer.

EXAMPLES
       Example 1, Adding a Cluster Reference to a Load Balancer Configuration
           This example adds a reference to a cluster named cluster2 to a load
           balancer configuration named mylbconfig.

               asadmin> create-http-lb-ref --config mylbconfig cluster2

               Command create-http-lb-ref executed successfully.

       Example 2, Adding a Cluster Reference to a Load Balancer
           This example adds a reference to a cluster named cluster2 to a load
           balancer named mylb.

               asadmin> create-http-lb-ref --lbname mylb cluster2

               Command create-http-lb-ref executed successfully.

       Example 3, Configuring a Health Checker and Load Balancer Policy
           This example configures a health checker and load balancing policy,
           and enables the load balancer for instances and applications.

               asadmin> create-http-lb-ref --config mylbconfig --lbpolicy weighted-round-robin
               --healthcheckerinterval 40 --healthcheckertimeout 20
               --lbenableallinstances=true --lbenableallapplications=true cluster2

               Command create-http-lb-ref executed successfully.

       Example 4, Setting a User-Defined Load Balancing Policy
           This example sets a user-defined load balancing policy.

               asadmin> create-http-lb-ref --lbpolicy user-defined --lbpolicymodule /user/modules/module.so
               --config mylbconfig cluster2

               Command create-http-lb-ref executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-http-lb-ref(1), create-http-health-checker(1),
       enable-http-lb-server(1), enable-http-lb-application(1),
       list-http-lb-configs(1), list-http-lbs(1) configure-lb-weight(1)

       asadmin(1M)

Java EE 7                         25 Aug 2010            create-http-lb-ref(1)
Command create-http-lb-ref executed successfully.

Command create-cluster executed successfully.

Command create-http-lb-ref executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-http-lb [options] ...
NAME
     delete-http-lb

SYNOPSIS
     Usage: delete-http-lb name 

OPTIONS
OPERANDS
     name
Command delete-http-lb executed successfully.

Command delete-http-lb executed successfully.

Can't find remote man page, looking locally...
delete-http-lb-ref(1)     asadmin Utility Subcommands    delete-http-lb-ref(1)

NAME
       delete-http-lb-ref - deletes the cluster or server instance from a load
       balancer

SYNOPSIS
           delete-http-lb-ref [--help] --config config_name | --lbname load_balancer_name
           [--force=false] target

DESCRIPTION
       Use the delete-http-lb-ref subcommand to remove a reference to a
       cluster or standalone server instance from a load balancer
       configuration or load balancer. So that you do not interrupt user
       requests, make sure the standalone server instance or all server
       instances in the cluster are disabled before you remove them from the
       load balancer configuration. If the force option is set to true, the
       references are deleted even if server instances or clusters are
       enabled.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --config
           Specifies which load balancer configuration to delete cluster and
           server instance references from.

           Specify either a load balancer configuration or a load balancer.
           Specifying both results in an error.

       --lbname
           Specifies the load balancer to delete cluster and server instance
           references from.

           Specify either a load balancer configuration or a load balancer.
           Specifying both results in an error.

       --force
           If force is set to true, then the references are deleted even if
           there are currently enabled applications or instances. The default
           is false.

OPERANDS
       target
           Specifies which cluster or instance to remove from the load
           balancer. Valid values are:

           *   cluster_name- The name of a target cluster.

           *   instance_name- The name of a target server instance.

EXAMPLES
       Example 1, Deleting a Cluster Reference from a Load Balancer
       Configuration
           This example deletes the reference to cluster named cluster2 from a
           load balancer configuration named mycluster-http-lb-config.

               asadmin> delete-http-lb-ref --config mycluster-http-lb-config cluster2

               Command delete-http-lb-ref executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-http-lb-ref(1), disable-http-lb-server(1)

       asadmin(1M)

Java EE 7                         25 Aug 2010            delete-http-lb-ref(1)
Command delete-http-lb-ref executed successfully.

Command _create-instance-filesystem executed successfully.
Port Assignments for server instance ins2: 
JMX_SYSTEM_CONNECTOR_PORT=28686
JMS_PROVIDER_PORT=27676
HTTP_LISTENER_PORT=28080
ASADMIN_LISTENER_PORT=24848
JAVA_DEBUGGER_PORT=29009
IIOP_SSL_LISTENER_PORT=23820
IIOP_LISTENER_PORT=23700
OSGI_SHELL_TELNET_PORT=26666
HTTP_SSL_LISTENER_PORT=28181
IIOP_SSL_MUTUALAUTH_PORT=23920
The instance, ins2, was created on host localhost
Command create-instance executed successfully.

Command configure-lb-weight executed successfully.

Command _delete-instance-filesystem executed successfully.
The instance, ins2, was deleted from host localhost
Command delete-instance executed successfully.

Command delete-http-lb-ref executed successfully.

Can't find remote man page, looking locally...
enable-http-lb-server(1)  asadmin Utility Subcommands enable-http-lb-server(1)

NAME
       enable-http-lb-server - enables a previously disabled sever or cluster
       managed by a load balancer

SYNOPSIS
           enable-http-lb-server [--help] target

DESCRIPTION
       The enable-http-lb-server subcommand enables a standalone server
       instance or cluster for load balancing. By default, load balancing is
       enabled for instances and clusters.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       target
           This operand specifies which server instances and clusters to
           enable. Valid values are:

           *   cluster_name- The name of a target cluster.

           *   instance_name- The name of a target server instance.

EXAMPLES
       Example 1, Enabling a Cluster for Load Balancing
           This example enables load balancing for a cluster named mycluster.

               asadmin> enable-http-lb-server mycluster

               Command enable-http-lb-server executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-http-lb-ref(1), disable-http-lb-server(1)

       asadmin(1M)

Java EE 7                         26 Aug 2010         enable-http-lb-server(1)
Command enable-http-lb-server executed successfully.

Command enable-http-lb-server executed successfully.

Can't find remote man page, looking locally...
disable-http-lb-server(1) asadmin Utility Subcommandsdisable-http-lb-server(1)

NAME
       disable-http-lb-server - disables a sever or cluster managed by a load
       balancer

SYNOPSIS
           disable-http-lb-server [--help] [--timeout 30]
            target

DESCRIPTION
       The disable-http-lb-server subcommand disables a standalone server or
       cluster of servers for load balancing. The disabled server instance or
       cluster goes offline for load balancing with a minimum impact to users.

       Once the target has been disabled and the changes have been applied to
       the load balancer, the load balancer stops assigning new requests to
       the target. Session requests with sessions created before disabling the
       target continue to be assigned to that target until the timeout is
       reached. This process is known as quiescing.

       Changes are applied the load balancer automatically. You can also
       manually export the configuration using export-http-lb-config and copy
       it to the load balancer.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --timeout
           The timeout (in minutes) to wait before disabling the specified
           target. This time allows for the graceful shutdown (quiescing) of
           the specified target. The default value is 30 minutes. The minimum
           value is 1 minute.

OPERANDS
       target
           This operand specifies which server instances and clusters to
           disable. Valid values are:

           *   cluster_name- The name of a target cluster.

           *   instance_name- The name of a target server instance.

EXAMPLES
       Example 1, Disabling a Cluster for Load Balancing
           This example disables load balancing for a cluster named mycluster.

               asadmin> disable-http-lb-server mycluster

               Command disable-http-lb-server executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-http-lb-ref(1), enable-http-lb-server(1)

       asadmin(1M)

Java EE 7                         26 Aug 2010        disable-http-lb-server(1)
Command disable-http-lb-server executed successfully.

Command disable-http-lb-server executed successfully.

Can't find remote man page, looking locally...
configure-lb-weight(1)    asadmin Utility Subcommands   configure-lb-weight(1)

NAME
       configure-lb-weight - sets load balancing weights for clustered
       instances

SYNOPSIS
           configure-lb-weight [--help] --cluster cluster_name
            instance-name=weight[:instance-name=weight]

DESCRIPTION
       The configure-lb-weight subcommand assigns weight to the server
       instances in a cluster. Weights can be used for HTTP, RMI/IIOP and JMS
       load balancing. For the HTTP load balancer, the weights are used only
       if the load balancer's policy is set to weighted-round-robin. The load
       balancer policy is set in the create-http-lb-ref subcommand or set
       subcommand.

       Use the weight to vary the load going to different instances in the
       cluster. For example, if an instance is on a machine with more
       capacity, give it a higher weight so that more requests are sent to
       that instance by the load balancer. The default weight is 100. If all
       instances have the default weight, the load balancer performs simple
       round robin load balancing.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --cluster
           The name of the cluster.

OPERANDS
       instance-name=weight
           The name of the instance and the weight you are assigning it. The
           weight must be an integer. The pairs of instances and weights are
           separated by colons. For example instance1=1:instance2=4 means that
           for every five requests, one goes to instance1 and four go to
           instance2. A weight of 1 is the default.

EXAMPLES
       Example 1, Assigning Load Balancer Weights to Cluster Instances
           The following subcommand assigns weights of 1, 1, and 2 to
           instances i1, i2, and i3 in the cluster1 cluster.

               asadmin> configure-lb-weight --cluster cluster1 i1=1:i2=1:i3=2
               Command configure-lb-weight executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-http-lb-ref(1)create-cluster(1)

       asadmin(1M)

Java EE 7                         25 Aug 2010           configure-lb-weight(1)
Command configure-lb-weight executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-http-lb-config [options] ...
NAME
     delete-http-lb-config

SYNOPSIS
     Usage: delete-http-lb-config name 

OPTIONS
OPERANDS
     name
Command delete-http-lb-config executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help validate-dcom [options] ...
validate-dcom(1)          asadmin Utility Subcommands         validate-dcom(1)

NAME
       validate-dcom - tests the connection over DCOM to a remote host

SYNOPSIS
           validate-dcom [--help]
           [--windowsuser windows-user] [--windowsdomain windows-domain]
           [--remotetestdir remote-test-directory]
           [--verbose={false|true}] host-name

DESCRIPTION
       The validate-dcom subcommand tests the connection over the Distributed
       Component Object Model (DCOM) remote protocol to the remote host that
       is specified as the operand of the subcommand. The DCOM protocol is
       available only on Windows systems.

       The prerequisites for running this subcommand are as follows:

       *   DCOM must be configured on the host where the domain administration
           server (DAS) is running and on the remote host that is specified as
           the operand of the subcommand.

       *   The following ports must be open on the remote host:

           *   DCOM port 135 or 139

           *   Windows Shares port 445

       *   The Server Windows Service is enabled on the remote host.

       This subcommand verifies whether the prerequisites for creating a DCOM
       node or creating a GlassFish Server instance on a DCOM node are met. If
       this subcommand fails, any attempt to create a DCOM node or create an
       instance on a DCOM node will also fail.

       You may run this command from any machine that can contact the DAS.

       The subcommand tests the connection over DCOM to the remote host by
       performing the following operations on the remote host:

       *   Resolving the host name

       *   Connecting to DCOM through port 135 or 139

       *   Connecting to Windows Shares through port 445

       *   Copying a script that is named delete_me.bat in the folder that is
           specified by the --remotetestdir option

       *   Running the script to obtain a listing of the folder in which the
           delete_me.bat was written

       By default, the subcommand displays no information about the operations
       that are performed to test the connection to the remote host. To
       display information about these operations, set the --verbose option to
       true.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --windowsuser, -w
           The user on the remote host that is to run the process for
           connecting to that host through DCOM. The default is the user that
           is running the DAS process.

       --windowsdomain, -d
           The name of the Windows domain that contains the user that the
           --windowsuser option specifies. The default is the name of the host
           on which the subcommand is run.

       --remotetestdir
           Specifies the folder on the remote host in which the subcommand
           creates the delete_me.bat file. The user that the --windowsuser
           option specifies must have write access to this folder. Otherwise
           an error occurs. The default is C:\

       --verbose, -v
           Specifies whether the subcommand displays information about the
           operations that are performed to test the connection to the remote
           host.

           Possible values are as follows:

           false
               No information about the operations that are performed to test
               the connection is displayed (default).

           true
               The subcommand displays information about the operations that
               are performed to test the connection.

               If the --verbose option is true and the AS_DEBUG environment
               variable is set, the subcommand also displays the command line
               for each process that is running on the remote host.

OPERANDS
       host-name
           The name of the host to which to test the connection over DCOM.

EXAMPLES
       Example 1, Testing the Connection Over DCOM to a Remote Host
           This example tests the connection over DCOM to the host wpmdl2.

               asadmin> validate-dcom --wpmdl2
               Command validate-dcom executed successfully.

       Example 2, Verbosely Testing the Connection Over DCOM to a Remote Host
           This example tests the connection over DCOM to the host wpmdl2 and
           displays information about the operations that are performed to
           test the connection to the remote host.

               asadmin> validate-dcom --verbose wpmdl2

               Successfully resolved host name to: wpmdl2/192.168.122.106
               Successfully connected to DCOM Port at port 135 on host wpmdl2.
               Successfully connected to NetBIOS Session Service at port 139 on host wpmdl2.
               Successfully connected to Windows Shares at port 445 on host wpmdl2.
               Successfully accessed C: on wpmdl2 using DCOM.
               Successfully wrote delete_me.bat to C: on wpmdl2 using DCOM.
               Successfully accessed WMI (Windows Management Interface) on wpmdl2. There are 40
               processes running on wpmdl2.
               Successfully ran the test script on wpmdl2 using DCOM.
               The script simply ran the DIR command. Here are the first few lines from the
               output of the dir command on the remote machine:

               C:\Windows\system32>dir C:\
                Volume in drive C has no label.
                Volume Serial Number is XXXX-XXX

                Directory of C:\

               12/05/2011  10:21 AM                63 .asadminpass
               02/15/2011  01:08 PM    <DIR>          aroot
               12/05/2011  04:43 PM                 8 delete_me.bat
               03/03/2011  10:36 AM    <DIR>          export

               Command validate-dcom executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-dcom(1), delete-node-dcom(1), list-nodes(1),
       ping-node-dcom(1), update-node-dcom(1)

       asadmin(1M)

Java EE 7                         5 Jan 2012                  validate-dcom(1)
Command validate-dcom executed successfully.

Deprecated syntax, instead use:
asadmin --help --user admin --passwordfile asadminpass create-node-dcom [options] ...
create-node-dcom(1)       asadmin Utility Subcommands      create-node-dcom(1)

NAME
       create-node-dcom - creates a node that is enabled for communication
       over DCOM

SYNOPSIS
           create-node-dcom [--help]
           --nodehost node-host
           [--installdir as-install-parent] [--nodedir node-dir]
           [--windowsuser windows-user] [--windowsdomain windows-domain]
           [--force={false|true}]
           [--install={false|true}] [--archive archive]
           node-name

DESCRIPTION
       The create-node-dcom subcommand creates a node that is enabled for
       communication over the Distributed Component Object Model (DCOM) remote
       protocol. The DCOM protocol is available only on Windows systems.

       A node represents a host on which the GlassFish Server software is
       installed. A node must exist for every host on which GlassFish Server
       instances reside.

       In a DCOM-enabled network, the domain administration server (DAS)
       contacts a node's host through the DCOM connector to manage GlassFish
       Server instances that reside on the node. DCOM is used only for
       communications between hosts. DCOM is never used for communications
       within a single host.

       By default, the subcommand fails and the node is not created if the DAS
       cannot contact the node's host through DCOM. To force the node to be
       created in the DAS configuration even if the host cannot be contacted
       through DCOM, set the --force option to true.

       The create-node-dcom subcommand cannot create a node that represents
       the local host, that is, the host on which the subcommand is run. The
       subcommand fails regardless of how the local host is specified, for
       example, by using the keyword localhost, the Internet Protocol (IP)
       address of the host, or the host name.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --nodehost
           The name of the host that the node represents. The name of the host
           must be specified. Otherwise, an error occurs.

       --installdir
           The full path to the parent of the base installation directory of
           the GlassFish Server software on the host, for example,
           C:\glassfish3. The default is the parent of the default base
           installation directory of the GlassFish Server software for the
           DAS. This default is useful only if GlassFish Server is installed
           in the same location on all hosts.

       --nodedir
           The path to the directory that is to contain GlassFish Server
           instances that are created on the node. The default is
           as-install\nodes, where as-install is the base installation
           directory of the GlassFish Server software on the host. If a
           relative path is specified, the path is relative to the as-install
           directory.

       --windowsuser, -w
           The user on this node's host that is to run the process for
           connecting to the host through DCOM. The default is the user that
           is running the DAS process. If the --nodehost option is set to
           localhost-domain, the --windowsuser option is ignored

       --windowsdomain, -d
           The name of the Windows domain that contains the user that the
           --windowsuser option specifies. The default is the name of the host
           on which the subcommand is run.

       --force
           Specifies whether the node is created in the DAS configuration even
           if validation of the node's parameters fails. To validate a node's
           parameters, the DAS must be able to contact the node's host through
           DCOM. Possible values are as follows:

           false
               The node is not created if validation of the node's parameters
               fails (default).

           true
               The node is created even if validation of the node's parameters
               fails.

       --install
           Specifies whether the subcommand shall install the GlassFish Server
           software on the host that the node represents.

           Possible values are as follows:

           false
               The subcommand shall not install the GlassFish Server software
               on the host (default).

           true
               The subcommand shall install the GlassFish Server software on
               the host.

       --archive
           The absolute path to the archive file of the GlassFish Server
           software that is to be installed. If this option is omitted and the
           --install is true, the subcommand creates a ZIP archive of the
           GlassFish Server software from the installation where this
           subcommand is run. The archive does not contain the domains
           directory or the nodes directory.

OPERANDS
       node-name
           The name of the node.

           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 node, a cluster, a named configuration, or a
               GlassFish Server instance.

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

EXAMPLES
       Example 1, Creating a Node
           This example creates the node wpmdl1 for the host
           wpmdl1.example.com. By default, the parent of the base installation
           directory of the GlassFish Server software is C:\glassfish3.

               asadmin> create-node-dcom
               --nodehost wpmdl1.example.com wpmdl1
               Command create-node-dcom executed successfully.

       Example 2, Creating a Node With a Specific Installation Directory
           This example creates the node wyml1 for the host wyml1.example.com.
           The parent of the base installation directory of the GlassFish
           Server software on this host is C:\middleware\glassfish3.

               asadmin> create-node-dcom --installdir C:\middleware\glassfish3
               --nodehost wyml1.example.com wyml1
               Command create-node-dcom executed successfully.

       Example 3, Forcing the Creation of a Node
           This example forces the creation of node xkyd for the host
           xkyd.example.com. The node is created despite the failure of the
           DAS to contact the host xkyd.example.com to validate the node's
           parameters.

               asadmin> create-node-dcom --force --nodehost xkyd.example.com xkyd
               Warning: some parameters appear to be invalid.
               com.sun.enterprise.universal.process.WindowsException: Connection in error
               Continuing with node creation due to use of --force.
               Command create-node-dcom executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-config(1), create-node-ssh(1), delete-node-dcom(1),
       install-node-dcom(1), list-nodes(1), uninstall-node-dcom(1),
       update-node-dcom(1)

       asadmin(1M)

Java EE 7                         5 Jan 2012               create-node-dcom(1)
Command create-node-dcom executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-nodes-dcom [options] ...
list-nodes-dcom(1)        asadmin Utility Subcommands       list-nodes-dcom(1)

NAME
       list-nodes-dcom - lists all GlassFish Server nodes that support
       communication over DCOM in a domain

SYNOPSIS
           list-nodes-dcom [--help] [--long={false|true}]

DESCRIPTION
       The list-nodes-dcom subcommand lists all GlassFish Server nodes that
       support communication over the Distributed Component Object Model
       (DCOM) remote protocol. The DCOM protocol is available only on Windows
       systems.

           Note
           +-------------------------------------+
           |           To list all nodes in a    |
           |           domain regardless of the  |
           |           type of the node, run the |
           |           list-nodes(1) subcommand. |
           +-------------------------------------+

       By default, the subcommand displays the following information for each
       node that is listed:

       *   The name of the node

       *   The type of the node, which is DCOM

       *   The name of the host that the node represents

       The --long option of the subcommand specifies whether the nodes are
       listed in long format. In long format, the following additional
       information about each node is displayed:

       *   The path to the parent of the base installation directory of
           GlassFish Server on the host that the node represents

       *   A comma-separated list of the names of the GlassFish Server
           instances that reside on the node

       If the --terse option of the asadmin(1M) utility is true and the --long
       option of the subcommand is false, the subcommand lists only the name
       of each node.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Specifies whether the nodes are listed in long format.

           Possible values are as follows:

           true
               The nodes are listed in long format.

           false
               The nodes are listed in short format (default).

EXAMPLES
       Example 1, Listing GlassFish Server Nodes
           This example displays the name, type, and host for all GlassFish
           Server nodes that support communication over DCOM in a domain.

               asadmin> list-nodes-dcom
               xkyd  DCOM  xkyd.example.com
               wpmdl2  DCOM  wpmdl2.example.com
               wpmdl1  DCOM  wpmdl1.example.com
               Command list-nodes-dcom executed successfully.

       Example 2, Listing Only the Names of GlassFish Server Nodes
           This example uses the --terse option of the asadmin utility to list
           only the names of the GlassFish Server nodes that support
           communication over DCOM in a domain.

               asadmin> list-nodes-dcom --terse=true
               xkyd
               wpmdl2
               wpmdl1

       Example 3, Listing GlassFish Server Nodes in Long Format
           This example lists the GlassFish Server nodes that support
           communication over DCOM in a domain in long format.

               asadmin> list-nodes-dcom --long=true
               NODE NAME    TYPE   NODE HOST            INSTALL DIRECTORY   REFERENCED BY
               xkyd         DCOM   xkyd.example.com     C:\glassfish3
               wpmdl2       DCOM   wpmdl2.example.com   C:\glassfish3       wdi2
               wpmdl1       DCOM   wpmdl1.example.com   C:\glassfish3       wdi1
               Command list-nodes-dcom executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-config(1), create-node-dcom(1), create-node-ssh(1),
       delete-node-config(1), delete-node-dcom(1), delete-node-ssh(1),
       list-nodes(1), list-nodes-config(1), list-nodes-dcom(1)

       asadmin(1M)

Java EE 7                         05 Dec 2011               list-nodes-dcom(1)
Command list-nodes-dcom executed successfully.

Command list-nodes-dcom executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-node-dcom [options] ...
delete-node-dcom(1)       asadmin Utility Subcommands      delete-node-dcom(1)

NAME
       delete-node-dcom - deletes a node that is enabled for communication
       over DCOM

SYNOPSIS
           delete-node-dcom [--help]
           [--uninstall={false|true}] [--force={false|true}]
           node-name

DESCRIPTION
       The delete-node-dcom subcommand deletes a node that is enabled for
       communication over the Distributed Component Object Model (DCOM) remote
       protocol from the domain. The DCOM protocol is available only on
       Windows systems. This subcommand does not require DCOM to be
       configured.

       This subcommand can delete only a node that is enabled for
       communication over DCOM. The subcommand for deleting other types of
       nodes depends on the type of the node:

       *   A node that is enabled for communication over secure shell (SSH)
           must be deleted by using the delete-node-ssh(1) subcommand.

       *   A node that is not enabled for communication must be deleted by
           using the delete-node-config(1) subcommand.

       To determine whether a node is enabled for communication over DCOM, use
       the list-nodes(1) subcommand.

       No GlassFish Server instances must reside on the node that is being
       deleted. Otherwise, the subcommand fails. Before running this
       subcommand, delete any instances that reside on the node by using, for
       example, the delete-instance(1) subcommand or the
       delete-local-instance(1) subcommand.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --uninstall
           Specifies whether the GlassFish Server software is uninstalled from
           host that the node represents.

           Possible values are as follows:

           false
               The GlassFish Server software is not uninstalled from the host
               (default).

           true
               The GlassFish Server software is uninstalled from the host. By
               default, if any node except the predefined node
               localhost-domain resides on any host from which GlassFish
               Server software is being uninstalled, the subcommand fails. To
               uninstall the GlassFish Server software from a host on which
               user-defined nodes reside, set the --force option to true. If
               the --force option is true, the subcommand removes the entire
               content of the parent of the base installation directory.

       --force
           If --uninstall is true, specifies whether the subcommand uninstalls
           the GlassFish Server software from a host even if a user-defined
           node resides on the host. Possible values are as follows:

           false
               If a user-defined node resides on a host, the software is not
               uninstalled and the subcommand fails (default).

               If the --force option is false, the subcommand removes only the
               GlassFish Server software files. Other content if the parent of
               the base installation directory, such as configuration files,
               are not removed.

           true
               The subcommand uninstalls the GlassFish Server software from
               the host even if a user-defined node resides on the host.

               If the --force option is true, the subcommand removes the
               entire content of the parent of the base installation
               directory.

OPERANDS
       node-name
           The name of the node to delete. The node must enabled for
           communication over DCOM. Otherwise, an error occurs.

EXAMPLES
       Example 1, Deleting a Node That Is Enabled for Communication Over DCOM
           This example deletes the node xkyd, which is enabled for
           communication over DCOM.

               asadmin> delete-node-dcom xkyd
               Command delete-node-dcom executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-dcom(1), delete-node-config(1), delete-node-ssh(1),
       delete-instance(1), delete-local-instance(1), install-node-dcom(1),
       list-nodes(1), uninstall-node-dcom(1), update-node-dcom(1)

       asadmin(1M)

Java EE 7                         05 Dec 2011              delete-node-dcom(1)
Command delete-node-dcom executed successfully.

asadmin(1M)                    Utility Commands                    asadmin(1M)

NAME
       asadmin - utility for performing administrative tasks for Oracle
       GlassFish Server

SYNOPSIS
           asadmin [--host host]
           [--port port]
           [--user admin-user]
           [--passwordfile filename]
           [--terse={true|false}]
           [--secure={false|true}]
           [--echo={true|false}]
           [--interactive={true|false}]
           [--detach={true|false}]
           [--help]
           [subcommand [options] [operands]]

DESCRIPTION
       Use the asadmin utility to perform administrative tasks for Oracle
       GlassFish Server. You can use this utility instead of the
       Administration Console interface.

   Subcommands of the asadmin Utility
       The subcommand identifies the operation or task that you are
       performing. Subcommands are case-sensitive. Each subcommand is either a
       local subcommand or a remote subcommand.

       *   A local subcommand can be run without a running domain
           administration server (DAS). However, to run the subcommand and
           have access to the installation directory and the domain directory,
           the user must be logged in to the machine that hosts the domain.

       *   A remote subcommand is always run by connecting to a DAS and
           running the subcommand there. A running DAS is required.

   asadmin Utility Options and Subcommand Options
       Options control the behavior of the asadmin utility and its
       subcommands. Options are also case-sensitive.

       The asadmin utility has the following types of options:

       *   asadmin utility options.  These options control the behavior of the
           asadmin utility, not the subcommand. The asadmin utility options
           may precede or follow the subcommand, but asadmin utility options
           after the subcommand are deprecated. All asadmin utility options
           must either precede or follow the subcommand. If asadmin utility
           options are specified both before and after the subcommand, an
           error occurs. For a description of the asadmin utility options, see
           the "Options" section of this help information.

       *   Subcommand options.  These options control the behavior of the
           subcommand, not the asadmin utility. Subcommand options must follow
           the subcommand. For a description of a subcommand's options, see
           the help information for the subcommand.

       A subcommand option may have the same name as an asadmin utility
       option, but the effects of the two options are different.

       The asadmin utility options and some subcommand options have a long
       form and a short form.

       *   The long form of an option has two dashes (--) followed by an
           option word.

       *   The short form of an option has a single dash (-) followed by a
           single character.

       For example, the long form and the short form of the option for
       specifying terse output are as follows:

       *   Long form: --terse

       *   Short form: -t

       Most options require argument values, except Boolean options, which
       toggle to enable or disable a feature.

   Operands of asadmin Subcommands
       Operands specify the items on which the subcommand is to act. Operands
       must follow the argument values of subcommand options, and are set off
       by a space, a tab, or double dashes (--). The asadmin utility treats
       anything that follows the subcommand options and their values as an
       operand.

   Escape Characters in Options for the asadmin Utility
       Escape characters are required in options of the asadmin utility for
       the following types of characters:

       *   Meta characters in the UNIX operating system.  These characters
           have special meaning in a shell. Meta characters in the UNIX
           operating system include: \/,.!$%^&*|{}[]"'`~;.

           To disable these characters, use the backslash (\) escape character
           or enclose the entire command-line argument in single quote (')
           characters.

           The following examples illustrate the effect of escape characters
           on the * character. In these examples, the current working
           directory is the domains directory.

           *   The following command, without the escape character, echoes all
               files in the current directory:

                   prompt% echo *
                   domain1 domain2

           *   The following command, in which the backslash (\) escape
               character precedes the * character, echoes the * character:

                   prompt% echo \*
                   *

           *   The following command, in which the * character is enclosed in
               single quote (') characters, echoes the * character:

                   prompt% echo '*'
                   *

           The escape character is also a special character in the UNIX
           operating system and in the Java language. Therefore, in the UNIX
           operating system and in multimode, you must apply an additional
           escape character to every escape character in the command line.
           This requirement does not apply to the Windows operating system.

           For example, the backslash (\) UNIX operating system meta character
           in the option argument Test\Escape\Character is specified on UNIX
           and Windows systems as follows:

           *   On UNIX systems, each backslash must be escaped with a second
               backslash:

                   Test\\Escape\\Character

           *   On Windows systems, no escape character is required:

                   Test\Escape\Character

               Note
               +----------------------------------------+
               |In contexts where meta characters in    |
               |the UNIX operating system are           |
               |unambiguous, these characters do not    |
               |require escape characters. For example, |
               |in the set(1) subcommand, the value     |
               |that is to be set is specified as       |
               |name=value. Because name can never      |
               |include an equals sign, no escape       |
               |character is required to disable the    |
               |equals sign. Therefore, everything      |
               |after the equals sign is an             |
               |uninterpreted string that the set       |
               |subcommand uses unchanged.              |
               +----------------------------------------+

       *   Spaces.  The space is the separator in the command-line interface.
           To distinguish a space in a command-line argument from the
           separator in the command-line interface, the space must be escaped
           as follows:

           *   For the UNIX operating system in single mode and multimode, and
               for all operating systems in multimode, use the backslash (\)
               escape character or enclose the entire command-line argument in
               single quote (') characters or double quote (") characters.

           *   For the Windows operating system in single mode, enclose the
               entire command-line argument in double quote (") characters.

       *   Option delimiters.  The asadmin utility uses the colon character
           (:) as a delimiter for some options. The backslash (\) escape
           character is required if the colon is part of any of the following
           items:

           *   A property

           *   An option of the Virtual Machine for the Java platform (Java
               Virtual Machine or JVM machine)The terms "Java Virtual Machine"
               and "JVM" mean a Virtual Machine for the Java platform.

           For example, the operand of the subcommand create-jvm-options(1)
           specifies JVM machine options in the following format:

               (jvm-option-name[=jvm-option-value])
               [:jvm-option-name[=jvm-option-value]]*
           Multiple JVM machine options in the operand of the
           create-jvm-options subcommand are separated by the colon (:)
           delimiter. If jvm-option-name or jvm-option-value contains a colon,
           the backslash (\) escape character is required before the colon.

           The backslash (\) escape character is also required before a single
           quote (') character or a double quote (") character in an option
           that uses the colon as a delimiter.

           When used without single quote (') characters, the escape character
           disables the option delimiter in the command-line interface.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the colon character and the
           backslash character in an option that uses the colon as a delimiter
           must be specified as follows:

           *   To pass a literal backslash to a subcommand, two backslashes
               are required. Therefore, the colon (:) must be escaped by two
               backslashes (\\).

           *   To prevent a subcommand from treating the backslash as a
               special character, the backslash must be escaped. As a result,
               two literal backslashes (\\) must be passed to the subcommand.
               To prevent the shell from interpreting these backslashes as
               special characters, each backslash must be escaped. Therefore,
               the backslash must be specified by a total of four backslashes
               (\\\\).

           For the Windows operating system in single mode, a backslash (\) is
           required to escape the colon (:) and the backslash (\) in an option
           that uses the colon as a delimiter.

       Instead of using the backslash (\) escape character, you can use the
       double quote (") character or single quote (') character. The effects
       of the different types of quote characters on the backslash (\)
       character are as follows:

       *   Between double quote (") characters, the backslash (\) character is
           a special character.

       *   Between single quote (') characters, the backslash (\) character is
           not a special character.

   Requirements for Using the --secure Option
       The requirements for using the --secure option are as follows:

       *   The domain that you are administering must be configured for
           security.

       *   The security-enabled attribute of the http-listener element in the
           DAS configuration must be set to true.

           To set this attribute, use the set subcommand.

   Server Restart After Creation or Deletion
       When you use the asadmin subcommands to create or delete a
       configuration item, you must restart the DAS for the change to take
       effect. To restart the DAS, use the restart-domain(1) subcommand.

   Help Information for Subcommands and the asadmin Utility
       To obtain help information for an asadmin utility subcommand, specify
       the subcommand of interest as the operand of the help subcommand. For
       example, to obtain help information for the start-domain(1) subcommand,
       type:

           asadmin help start-domain

       If you run the help subcommand without an operand, this help
       information for the asadmin utility is displayed.

       To obtain a listing of available asadmin subcommands, use the
       list-commands(1) subcommand.

OPTIONS
       --host, -H
           The machine name where the DAS is running. The default value is
           localhost.

       --port, -p
           The HTTP port or HTTPS port for administration. This port is the
           port in the URL that you specify in your web browser to manage the
           domain. For example, in the URL http://localhost:4949, the port is
           4949.

           The default port number for administration is 4848.

       --user, -u
           The user name of the authorized administrative user of the DAS.

           If you have authenticated to a domain by using the asadmin login
           command, you need not specify the --user option for subsequent
           operations on the domain.

       --passwordfile, -W
           Specifies the name, including the full path, of a file that
           contains password entries in a specific format.

           The entry for a password must have the AS_ADMIN_ prefix followed by
           the password name in uppercase letters, an equals sign, and the
           password.

           The entries in the file that are read by the asadmin utility are as
           follows:

           *   AS_ADMIN_PASSWORD=administration-password

           *   AS_ADMIN_MASTERPASSWORD=master-password

           The entries in this file that are read by subcommands are as
           follows:

           *   AS_ADMIN_NEWPASSWORD=new-administration-password (read by the
               start-domain(1) subcommand)

           *   AS_ADMIN_USERPASSWORD=user-password (read by the
               create-file-user(1) subcommand)

           *   AS_ADMIN_ALIASPASSWORD=alias-password (read by the
               create-password-alias(1) subcommand)

           *   AS_ADMIN_MAPPEDPASSWORD=mapped-password (read by the
               create-connector-security-map(1) subcommand)

           *   AS_ADMIN_WINDOWSPASSWORD=windows-password (read by the
               create-node-dcom(1), install-node-dcom(1), and
               update-node-dcom(1) subcommands)

           *   AS_ADMIN_SSHPASSWORD=sshd-password (read by the
               create-node-ssh(1), install-node(1), install-node-ssh(1), and
               update-node-ssh(1) subcommands)

           *   AS_ADMIN_SSHKEYPASSPHRASE=sshd-passphrase (read by the
               create-node-ssh(1), install-node(1), install-node-ssh(1), and
               update-node-ssh(1) subcommands)

           *   AS_ADMIN_JMSDBPASSWORD= jdbc-user-password (read by the
               configure-jms-cluster(1) subcommand)

           These password entries are stored in clear text in the password
           file. To provide additional security, the create-password-alias
           subcommand can be used to create aliases for passwords that are
           used by remote subcommands. The password for which the alias is
           created is stored in an encrypted form. If an alias exists for a
           password, the alias is specified in the entry for the password as
           follows:

               AS_ADMIN_password-name=${ALIAS=password-alias-name}
           For example:

               AS_ADMIN_SSHPASSWORD=${ALIAS=ssh-password-alias}
               AS_ADMIN_SSHKEYPASSPHRASE=${ALIAS=ssh-key-passphrase-alias}
           In domains that do not allow unauthenticated login, all remote
           subcommands must specify the administration password to
           authenticate to the DAS. The password can be specified by one of
           the following means:

           *   Through the --passwordfile option

           *   Through the login(1) subcommand

           *   Interactively at the command prompt

           The login subcommand can be used to specify only the administration
           password. For other passwords that remote subcommands require, use
           the --passwordfile option or specify them at the command prompt.

           After authenticating to a domain by using the asadmin login
           command, you need not specify the administration password through
           the --passwordfile option for subsequent operations on the domain.
           However, only the AS_ADMIN_PASSWORD option is not required. You
           still must provide the other passwords, for example,
           AS_ADMIN_USERPASSWORD, when required by individual subcommands,
           such as update-file-user(1).

           For security reasons, a password that is specified as an
           environment variable is not read by the asadmin utility.

           The master password is not propagated on the command line or an
           environment variable, but can be specified in the file that the
           --passwordfile option specifies.

           The default value for AS_ADMIN_MASTERPASSWORD is changeit.

       --terse, -t
           If true, output data is very concise and in a format that is
           optimized for use in scripts instead of for reading by humans.
           Typically, descriptive text and detailed status messages are also
           omitted from the output data. Default is false.

       --secure, -s
           If set to true, uses SSL/TLS to communicate with the DAS.

           The default is false.

       --echo, -e
           If set to true, the command-line statement is echoed on the
           standard output. Default is false.

       --interactive, -I
           If set to true, only the required options are prompted.

           The default depends on how the asadmin utility is run:

           *   If the asadmin utility is run from a console window, the
               default is true.

           *   If the asadmin utility is run without a console window, for
               example, from within a script, the default is false.

       --detach
           If set to true, the specified asadmin subcommand is detached and
           executed in the background in detach mode. The default value is
           false.

           The --detach option is useful for long-running subcommands and
           enables you to execute several independent subcommands from one
           console or script.

           The --detach option is specified before the subcommand. For
           example, in single mode, asadmin --detach subcommand.

           Job IDs are assigned to subcommands that are started using asadmin
           --detach. You can use the list-jobs(1) subcommand to view the jobs
           and their job IDs, the attach(1) subcommand to reattach to the job
           and view its status and output, and the configure-managed-jobs(1)
           subcommand to configure how long information about the jobs is
           kept.

       --help, -?
           Displays the help text for the asadmin utility.

EXAMPLES
       Example 1, Running an asadmin Utility Subcommand in Single Mode
           This example runs the list-applications(1) subcommand in single
           mode. In this example, the default values for all options are used.

           The example shows that the application hello is deployed on the
           local host.

               asadmin list-applications
               hello <web>

               Command list-applications executed successfully.

       Example 2, Specifying an asadmin Utility Option With a Subcommand
           This example specifies the --host asadmin utility option with the
           list-applications subcommand in single mode. In this example, the
           DAS is running on the host srvr1.example.com.

           The example shows that the applications basic-ezcomp, scrumtoys,
           ejb31-war, and automatic-timer-ejb are deployed on the host
           srvr1.example.com.

               asadmin --host srvr1.example.com list-applications
               basic-ezcomp <web>
               scrumtoys <web>
               ejb31-war <ejb, web>
               automatic-timer-ejb <ejb>

               Command list-applications executed successfully.

       Example 3, Specifying an asadmin Utility Option and a Subcommand Option
           This example specifies the --host asadmin utility option and the
           --type subcommand option with the list-applications subcommand in
           single mode. In this example, the DAS is running on the host
           srvr1.example.com and applications of type web are to be listed.

               asadmin --host srvr1.example.com list-applications --type web
               basic-ezcomp <web>
               scrumtoys <web>
               ejb31-war <ejb, web>

               Command list-applications executed successfully.

       Example 4, Escaping a Command-Line Argument With Single Quote
       Characters
           The commands in this example specify the backslash (\) UNIX
           operating system meta character and the colon (:) option delimiter
           in the property value c:\extras\pmdapp.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the backslash (\) is required
           to escape the backslash (\) meta character and the colon (:) option
           delimiter:

               asadmin deploy --property extras.home='c\:\\extras\\pmdapp' pmdapp.war
               Application deployed with name pmdapp.
               Command deploy executed successfully
           For the Windows operating system in single mode, the single quote
           (') characters eliminate the need for other escape characters:

               asadmin deploy --property extras.home='c:\extras\pmdapp' pmdapp.war
               Application deployed with name pmdapp.
               Command deploy executed successfully

       Example 5, Specifying a UNIX Operating System Meta Character in an
       Option
           The commands in this example specify the backslash (\) UNIX
           operating system meta character in the option argument
           Test\Escape\Character.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the backslash (\) is required
           to escape the backslash (\) meta character:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname sampleClassName
               --description Test\\Escape\\Character
               sampleJDBCConnectionPool
           For the Windows operating system in single mode, no escape
           character is required:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname sampleClassName
               --description Test\Escape\Character
               sampleJDBCConnectionPool

       Example 6, Specifying a Command-Line Argument That Contains a Space
           The commands in this example specify spaces in the operand
           C:\Documents and Settings\gfuser\apps\hello.war.

           For all operating systems in single mode or multimode, the entire
           operand can be enclosed in double quote (") characters:

               asadmin deploy "C:\Documents and Settings\gfuser\apps\hello.war"
               Application deployed with name hello.
               Command deploy executed successfully.
           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, the entire command-line
           argument can be enclosed in single quote (') characters:

               asadmin> deploy 'C:\Documents and Settings\gfuser\apps\hello.war'
               Application deployed with name hello.
               Command deploy executed successfully.
           Alternatively, for the UNIX operating system in single mode and
           multimode, and for all operating systems in multimode, the
           backslash (\) escape character can be used before each space in the
           operand. In this situation, the backslash (\) escape character is
           required before each backslash in the operand:

               asadmin> deploy C:\\Documents\ and\ Settings\\gfuser\\apps\\hello.war
               Application deployed with name hello.
               Command deploy executed successfully.

       Example 7, Specifying a Meta Character and an Option Delimiter
       Character in a Property
           The commands in this example specify the backslash (\) UNIX
           operating system meta character and the colon (:) option delimiter
           character in the --property option of the
           create-jdbc-connection-pool(1) subcommand.

           The name and value pairs for the --property option are as follows:

               user=dbuser
               passwordfile=dbpasswordfile
               DatabaseName=jdbc:derby
               server=http://localhost:9092
           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, a backslash (\) is required to
           escape the colon (:) and the backslash (\):

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property user=dbuser:passwordfile=dbpasswordfile:
               DatabaseName=jdbc\\:derby:server=http\\://localhost\\:9092 javadb-pool
           Alternatively, the entire argument to the --property option can be
           enclosed in single quote (') characters:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property 'user=dbuser:passwordfile=dbpasswordfile:
               DatabaseName="jdbc:derby":server="http://localhost:9092"' javadb-pool
           For the Windows operating system in single mode, a backslash (\) is
           required to escape only the colon (:), but not the backslash (\):

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property user-dbuser:passwordfile-dbpasswordfile:
               DatabaseName=jdbc\:derby:server=http\://localhost\:9092 javadb-pool
           For all operating systems, the need to escape the colon (:) in a
           value can be avoided by enclosing the value in double quote
           characters or single quote characters:

               asadmin --user admin --passwordfile gfpass create-jdbc-connection-pool
               --datasourceclassname com.derby.jdbc.jdbcDataSource
               --property user=dbuser:passwordfile=dbpasswordfile:
               DatabaseName=\"jdbc:derby\":server=\"http://localhost:9092\" javadb-pool

       Example 8, Specifying an Option Delimiter and an Escape Character in a
       JVM Machine Option
           The commands in this example specify the following characters in
           the -Dlocation=c:\sun\appserver JVM machine option:

           *   The colon (:) option delimiter

           *   The backslash (\) escape character

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, these characters must be
           specified as follows:

           *   To pass a literal backslash to a subcommand, two backslashes
               are required. Therefore, the colon (:) must be escaped by two
               backslashes (\\).

           *   To prevent the subcommand from treating the backslash as a
               special character, the backslash must be escaped. As a result,
               two literal backslashes (\\) must be passed to the subcommand.
               To prevent the shell from interpreting these backslashes as
               special characters, each backslash must be escaped. Therefore,
               the backslash must be specified by a total of four backslashes
               (\\\\).

           The resulting command is as follows:

               asadmin create-jvm-options --target test-server
               -e -Dlocation=c\\:\\\\sun\\\\appserver
           For the Windows operating system in single mode, a backslash (\) is
           required to escape the colon (:) and the backslash (\):

               asadmin create-jvm-options --target test-server
               -e -Dlocation=c\:\\sun\\appserver

       Example 9, Specifying an Option That Contains an Escape Character
           The commands in this example specify the backslash (\) character
           and the double quote (") characters in the
           "Hello\App"\authentication option argument.

           For the UNIX operating system in single mode and multimode, and for
           all operating systems in multimode, a backslash (\) is required to
           escape the double quote character (") and the backslash (\):

               asadmin set-web-env-entry --name="Hello User" --type=java.lang.String
               --value=techscribe --description=\"Hello\\App\"\\authentication hello
           For the Windows operating system in single mode, a backslash (\) is
           required to escape only the double quote ("), but not the backslash
           (\):

               asadmin set-web-env-entry --name="Hello User" --type=java.lang.String
               --value=techscribe --description=\"Hello\App\"\authentication hello

ENVIRONMENT VARIABLES
       Environment variables modify the default values of asadmin utility
       options as shown in the following table.

       +-----------------------------+------------------------+
       |       Environment           |        asadmin Utility |
       |       Variable              |        Option          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_TERSE        |        --terse         |
       +-----------------------------+------------------------+
       |       AS_ADMIN_ECHO         |        --echo          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_INTERACTIVE  |        --interactive   |
       +-----------------------------+------------------------+
       |       AS_ADMIN_HOST         |        --host          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_PORT         |        --port          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_SECURE       |        --secure        |
       +-----------------------------+------------------------+
       |       AS_ADMIN_USER         |        --user          |
       +-----------------------------+------------------------+
       |       AS_ADMIN_PASSWORDFILE |        --passwordfile  |
       +-----------------------------+------------------------+
       |       AS_ADMIN_HELP         |        --help          |
       +-----------------------------+------------------------+

ATTRIBUTES
       See attributes(5) for descriptions of the following attributes:

       +---------------------------+------------------------+
       |       ATTRIBUTE TYPE      |        ATTRIBUTE VALUE |
       +---------------------------+------------------------+
       |       Interface Stability |        Unstable        |
       +---------------------------+------------------------+

SEE ALSO
       attach(1), configure-jms-cluster(1), configure-managed-jobs(1),
       create-connector-security-map(1), create-file-user(1),
       create-jdbc-connection-pool(1), create-jvm-options(1),
       create-node-dcom(1), create-node-ssh(1), create-password-alias(1),
       deploy(1), install-node(1), install-node-dcom(1), install-node-ssh(1),
       list-applications(1), list-commands(1), list-jobs(1), login(1),
       restart-domain(1), set(1), set-web-env-entry(1), start-domain(1),
       update-file-user(1), update-node-dcom(1), update-node-ssh(1)

       attributes(5)

Java EE 7                         12 Feb 2013                      asadmin(1M)
Command help executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help attach [options] ...
attach(1)                 asadmin Utility Subcommands                attach(1)

NAME
       attach - attaches to a subcommand that was started using asadmin
       --detach

SYNOPSIS
           attach  [--help]
           jobid

DESCRIPTION
       The attach subcommand attaches to a subcommand that was started using
       the asadmin utility option --detach, which detaches long-running
       subcommands and executes them in the background in detach mode. Job IDs
       are assigned to subcommands (jobs) that are started using asadmin
       --detach. The attach subcommand enables you to view the status of a job
       and its output.

       You can use the list-jobs(1) subcommand to view the jobs and their job
       IDs, and the configure-managed-jobs(1) subcommand to configure how long
       information about the jobs is kept.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       jobid
           The ID of the job for which you want to view status and output.

EXAMPLES
       Example 1, Attaching to a Subcommand and Checking Its Status
           This example attaches to the deploy subcommand with a job ID of 20
           and shows that the job has completed. If a subcommand is still in
           progress, the output displays the current status, for example, 64%:
           Uploading bits.

               asadmin> attach 20
               Finished execution of deploy
               Command attach executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-jobs(1), configure-managed-jobs(1)

       asadmin(1M)

Java EE 7                         12 Jan 2013                        attach(1)
Command attach executed successfully.

asadmin --host localhost --port 4848 --user admin --passwordfile /home/cdctest/JavaEE7/cmdant/asadminpass --interactive=false --
echo=true --terse=false list-jobs
Job ID: 1
Command list-jobs started successfully

Command list-jobs executed with status SUCCESS.
Command attach executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help configure-managed-jobs [options] ...
configure-managed-jobs(1) asadmin Utility Subcommandsconfigure-managed-jobs(1)

NAME
       configure-managed-jobs - configures how long information about
       subcommands (jobs) started using asadmin --detach is kept

SYNOPSIS
           configure-managed-jobs [--help]
           [--in-memory-retention-period in-memory-retention-period]
           [--job-retention-period job-retention-period]
           [--cleanup-initial-delay cleanup-initial-delay]
           [--cleanup-poll-interval cleanup-poll-interval]

DESCRIPTION
       The configure-managed-jobs subcommand configures how long information
       about subcommands (jobs) that are started using the asadmin utility
       option --detach is kept. Job information includes subcommand progress
       and status.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       in-memory-retention-period
           Specifies how long a completed job is kept in memory after the job
           is finished. The default is 1 hour.

       --job-retention-period
           Specifies how long a job is stored. The default is 24 hours.

       --cleanup-initial-delay
           After server startup, specifies the initial delay after which the
           cleanup service starts purging jobs. The default is 5 minutes.

       --cleanup-poll-interval
           Specifies the time interval after which the cleanup service polls
           for expired jobs. The default is 20 minutes.

EXAMPLES
       Example 1, Configuring the Job Retention Period
           This example sets the job retetion period to 36 hours. Time periods
           can be specified in Hh|Mm|Ss for hours, minutes, or seconds.

               asadmin> configure-managed-jobs --job-retention-period=36h
               Command configure-managed-jobs executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-jobs(1)

       asadmin(1M)

Java EE 7                         06 Feb 2013        configure-managed-jobs(1)
Command configure-managed-jobs executed successfully.

Command configure-managed-jobs executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-context-service [options] ...
create-context-service(1) asadmin Utility Subcommandscreate-context-service(1)

NAME
       create-context-service - creates a context service resource

SYNOPSIS
           create-context-service [--help]
           [--enabled[={false|true}]]
           [--contextinfo contextinfo]
           [--description description]
           [--property property]
           [--target target]
           jndi_name

DESCRIPTION
       The create-context-service subcommand creates a context service
       resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       ----enabled
           Specifies whether the context service is enabled at runtime.

           The default value is true.

       --contextinfo
           A comma separated string specifying a list of context types to be
           propagated. The context types are Security, Classloader, JNDI, and
           WorkArea. If omitted, all context types are propagated.

       --description
           Descriptive details about the context service instance.

       --property
           Optional attribute name/value pairs for configuring the context
           service instance.

       --target
           The target for which the context service resource is being created.

OPERANDS
       jndi_name
           The JNDI name to look up the context service instance.

EXAMPLES
       Example 1, Creating a Context Service Resource
           This example creates a context service resource.

               asadmin> create-context-service concurrent/SampleContextService
               Context service concurrent/SampleContextService created successfully.
               Command create-context-service executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-context-service(1), list-context-services(1)

       asadmin(1M)

Java EE 7                         09 Feb 2013        create-context-service(1)
Command create-context-service executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-login-module-config [options] ...
Can't find remote man page, looking locally...
Command create-login-module-config failed.
Cannot find man page for command: create-login-module-config

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-managed-executor-service [options] ...
create-managed-executor-seasadmin)Utility Sucreate-managed-executor-service(1)

NAME
       create-managed-executor-service - creates a managed executor service
       resource

SYNOPSIS
           create-managed-executor-service [--help]
           [--enabled[={false|true}]]
           [--contextinfo contextinfo]
           [--threadpriority threadpriority]
           [--longrunningtasks[={false|true}]]]
           [--hungafterseconds hungafterseconds]
           [--corepoolsize corepoolsize]
           [--maximumpoolsize maximumpoolsize]
           [--keepaliveseconds keepaliveseconds]
           [--threadlifetimeseconds threadlifetimeseconds]
           [--taskqueuecapacity taskqueuecapacity]
           [--description description]
           [--property property]
           [--target target]
           jndi_name

DESCRIPTION
       The create-managed-executor-service subcommand creates a managed
       executor service resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --enabled
           Specifies whether the managed executor service resource is enabled
           at runtime.

           The default value is true.

       --contextinfo
           A comma separated text string specifying the context types to be
           propagated. Context types are Security, Classloader, JNDI, and
           WorkArea. If omitted, all context types are propagated.

       --threadpriority
           Specifies the priority of threads to be created for the managed
           executor service instance.

           The default value is 5.

       --longrunningtasks
           Specifies how a container should handle threads.If set to true,
           stuck threads will not be reported and shutdown of the managed
           executor service will not be blocked waiting for long-running
           tasks. The default value is false.

       --hungafterseconds
           Specifies the time in seconds that a task can execute before it is
           considered hung. If omitted, tasks are never considered hung.

       --corepoolsize
           Specifies the number of threads to keep in a thread pool.

           The default value is 0.

       ---maximumpoolsize
           Specifies the maximum number of threads a thread pool can contain.

           The default value is 2147483647.

       --keepaliveseconds
           Specifies the time in seconds threads can remain idle when the
           number of threads is greater than core size.

           The default value is 60.

       --threadlifetimeseconds
           Specifies the time in seconds each thread remains in a thread pool
           before it is purged, regardless of whether the number of threads is
           greater than core size or whether the thread is idle. Threads are
           not interrupted while executing requests. Threads exceeding the
           thread-lifetime-seconds value are not returned to the thread pool
           after the current request completes.

           The default value is 0.

       --taskqueuecapacity
           Specifies the size of the queue holding submitted tasks waiting to
           be executed.

           The default value is 2147483647.

       --description
           Text providing descriptive details about the managed executor
           service resource.

       --property
           Optional attribute name/value pairs for configuring the managed
           executor service instance.

       --target
           The target for which the managed executor service resource is being
           created.

OPERANDS
       jndi_name
           The JNDI name to look up the managed executor service instance.

EXAMPLES
       Example 1, Creating a Managed Executor Service Resource
           This example creates a managed executor service resource.

               asadmin> create-managed-executor-service concurrent/SampleExecutor
               Managed executor service concurrent/SampleExecutor created successfully.
               Command create-managed-executor-service executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-managed-executor-service(1), list-managed-executor-services(1)

       asadmin(1M)

Java EE 7                         09 Feb 201create-managed-executor-service(1)
Command create-managed-executor-service executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-managed-scheduled-executor-service [options] ...
create-managed-scheduled-easadmin-create-managed-scheduled-executor-service(1)

NAME
       create-managed-scheduled-executor-service - creates a managed scheduled
       executor service resource

SYNOPSIS
           create-managed-scheduled-executor-service [--help]
           [--enabled[={false|true}]]
           [--contextinfo contextinfo]
           [--threadpriority threadpriority]
           [--longrunningtasks[={false|true}]]
           [--hungafterseconds hungafterseconds]
           [--corepoolsize corepoolsize]
           [--maximumpoolsize maximumpoolsize]
           [--keepaliveseconds keepaliveseconds]
           [--threadlifetimeseconds threadlifetimeseconds]
           [--taskqueuecapacity taskqueuecapacity]
           [--description description]
           [--property property]
           [--target target]
           jndi_name

DESCRIPTION
       The create-managed-scheduled-executor-service subcommand creates a
       managed scheduled executor service resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --enabled
           Specifies whether the managed scheduled executor service resource
           is enabled at runtime.

           The default value is true.

       --contextinfo
           A comma separated string specifying a list of context types to be
           propagated. Context types are Security, Classloader, JNDI, and
           WorkArea. If omitted, all context types are propagated.

       --threadpriority
           Specifies the priority of threads to be created for the managed
           scheduled executor service instance.

           The default value is 5.

       --longrunningtasks
           Specifies how a container should handle threads.If set to true,
           stuck threads will not be reported and shutdown of the managed
           scheduled executor service will not be blocked waiting for
           long-running tasks. The default value is false.

       --hungafterseconds
           Specifies the amount of time in seconds that a task can execute
           before it is considered hung. If omitted, tasks will never be
           considered hung.

       --corepoolsize
           Specifies the number of threads to keep in a thread pool.

           The default value is 0.

       ---maximumpoolsize
           Specifies the maximum number of threads a thread pool can contain.

           The default value is 2147483647.

       --keepaliveseconds
           Specifies the time in seconds threads can remain idle when the
           number of threads is greater than core size.

           The default value is 60.

       --threadlifetimeseconds
           Specifies the time in seconds each thread remains in a thread pool
           before it is purged, regardless of whether the number of threads is
           greater than core size or whether the thread is idle. Threads are
           not interrupted while executing requests. Threads exceeding the
           thread-lifetime-seconds value are not returned to the thread pool
           after the current request completes.

           The default value is 0.

       --taskqueuecapacity
           Specifies the size of the queue holding submitted tasks waiting to
           be executed.

           The default value is 2147483647.

       --description
           Text providing descriptive details about the managed scheduled
           executor service.

       --property
           Optional attribute name/value pairs for configuring the managed
           executor service instance.

       --target
           The target for which the managed scheduled executor service
           resource is being created.

OPERANDS
       jndi_name
           The JNDI name to look up the managed scheduled executor service
           instance.

EXAMPLES
       Example 1, Creating a Managed Scheduled Executor Service Resource
           This example creates a managed scheduled executor service resource.

               asadmin> create-managed-scheduled-executor-service concurrent/SampleScheduledExecutor
               Managed scheduled executor service concurrent/SampleScheduledExecutor created successfully.
               Command create-managed-scheduled-executor-service executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-managed-scheduled-executor-service(1),
       list-managed-scheduled-executor-services(1)

       asadmin(1M)

Java EE 7                         create-managed-scheduled-executor-service(1)
Command create-managed-scheduled-executor-service executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-managed-thread-factory [options] ...
create-managed-thread-factasadmin Utility Subccreate-managed-thread-factory(1)

NAME
       create-managed-thread-factory - creates a managed thread factory
       resource

SYNOPSIS
           create-managed-thread-factory [--help]
           [--enabled[={false|true}]]
           [--contextinfo contextinfo]
           [--threadpriority threadpriority]
           [--description description]
           [--property property]
           [--target target]
           jndi_name

DESCRIPTION
       The create-managed-thread-factory subcommand creates a managed thread
       factory resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --enabled
           Specifies whether the managed thread factory is enabled at runtime.

           The default value is true.

       --contextinfo
           A comma separated text string specifying the context types to be
           propagated. Context types are Security, Classloader, JNDI, and
           WorkArea. If omitted, all context types are propagated.

       --threadpriority
           Specifies the priority of threads to be created for the managed
           thread factory instance.

           The default value is 5.

       --description
           Text providing descriptive details about the managed thread
           factory.

       --property
           Optional attribute name/value pairs for configuring the managed
           thread factory instance.

       --target
           The target for which the managed thread factory resource is being
           created.

OPERANDS
       jndi_name
           The JNDI name to look up the managed thread factory instance.

EXAMPLES
       Example 1, Creating a Managed Thread Factory Resource
           This example creates a managed thread factory resource.

               asadmin> create-managed-thread-factory concurrent/SampleThreadFactory
               Managed thread factory concurrent/SampleThreadFactory created successfully.
               Command create-managed-thread-factory executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-managed-thread-factory(1), list-managed-thread-factories(1)

       asadmin(1M)

Java EE 7                         09 Feb 2013 create-managed-thread-factory(1)
Command create-managed-thread-factory executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-module-config [options] ...
create-module-config(1)   asadmin Utility Subcommands  create-module-config(1)

NAME
       create-module-config - adds the default configuration of a module to
       domain.xml

SYNOPSIS
           create-module-config [--help]
           [--dryrun[={false|true}]]
           [--all[={false|true}]]
           [--target target]
           servicename

DESCRIPTION
       The create-module-config subcommand adds the default configuration of a
       module to domain.xml.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --dryrun
           Displays the default configuration of a module but does not add it
           to domain.xml.

           The default value is false.

       --all
           Adds all default configurations of modules to domain.xml if they
           are not already in it.

           The default value is false.

       --target
           Specifies the target for which the default configuration of the
           module will be added.

           Possible values are as follows:

           server
               Adds the default configuration of a module to the domain.xml
               for the default server instance. This is the default value.

           domain
               Adds the default configuration of a module to the domain.xml
               for the default domain.

           cluster-name
               Adds the default configuration of a module to the domain.xml
               for the specified cluster.

           instance-name
               Adds the default configuration of a module to the domain.xml
               for the specified instance.

OPERANDS
       servicename
           The name of the module. The default configuration of the module
           will be added to the domain.xml of the target.

EXAMPLES
       Example 1, Adding a Default Configuration to domain.xml
           This example adds the default configuration of the web container
           module to the domain.xml file of domain1 in server-config (the
           default configuration). To preview the configuration before it is
           added to domain.xml, use the --dryrun option.

               asadmin> create-module-config web-container
               Command create-module-config executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-module-config(1), get-active-module-config(1)

       asadmin(1M)

Java EE 7                         06 Feb 2013          create-module-config(1)
Command create-module-config executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-security-provider [options] ...
Can't find remote man page, looking locally...
Cannot find man page for command: create-security-provider
Command create-security-provider failed.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-security-service [options] ...
Can't find remote man page, looking locally...
Cannot find man page for command: create-security-service
Command create-security-service failed.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-context-service [options] ...
delete-context-service(1) asadmin Utility Subcommandsdelete-context-service(1)

NAME
       delete-context-service - deletes a context service resource

SYNOPSIS
           delete-context-service [--help]
           [--target target]
           context_service_name

DESCRIPTION
       The delete-context-service subcommand deletes a context service
       resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           The target for which the context service resource is being deleted.

OPERANDS
       context_service_name
           The name of the context service resource to be deleted.

EXAMPLES
       Example 1, Deleting a Context Service Resource
           This example deletes the named context service resource.

               asadmin> delete-context-service

               Command delete-context-service executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-context-service(1), list-context-services(1)

       asadmin(1M)

Java EE 7                         09 Feb 2013        delete-context-service(1)
Command delete-context-service executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-managed-executor-service [options] ...
delete-managed-executor-seasadmin)Utility Sudelete-managed-executor-service(1)

NAME
       delete-managed-executor-service - deletes a managed executor service
       resource

SYNOPSIS
           delete-managed-executor-service [--help]
           [--target target]
           managed_executor_service_name

DESCRIPTION
       The delete-managed-executor-service subcommand deletes a managed
       executor service resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           The target for which the managed executor service resource is being
           deleted.

OPERANDS
       managed_executor_service_name
           The name of the managed executor service resource to be deleted.

EXAMPLES
       Example 1, Deleting a Managed Executor Service Resource
           This example deletes the named managed executor service resource.

               asadmin> delete-managed-executor-service

               Command delete-managed-executor-service executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-managed-executor-service(1), list-managed-executor-services(1)

       asadmin(1M)

Java EE 7                         09 Feb 201delete-managed-executor-service(1)
Command delete-managed-executor-service executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-managed-scheduled-executor-service [options] ...
delete-managed-scheduled-easadmin-delete-managed-scheduled-executor-service(1)

NAME
       delete-managed-scheduled-executor-service - deletes a managed scheduled
       executor service resource

SYNOPSIS
           delete-managed-scheduled-executor-service [--help]
           [--target target]
           managed_scheduled_executor_service_name

DESCRIPTION
       The delete-managed-scheduled-executor-service subcommand deletes a
       managed scheduled executor service resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           The target for which the managed scheduled executor service
           resource is being deleted.

OPERANDS
       managed_scheduled_executor_service_name
           The name of the managed scheduled executor service resource to be
           deleted.

EXAMPLES
       Example 1, Deleting a Managed Scheduled Executor Service Resource
           This example deletes the named managed scheduled executor service
           resource.

               asadmin> delete-managed-scheduled-executor-service

               Command delete-managed-scheduled-executor-service executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-managed-scheduled-executor-service(1),
       list-managed-scheduled-executor-services(1)

       asadmin(1M)

Java EE 7                         delete-managed-scheduled-executor-service(1)
Command delete-managed-scheduled-executor-service executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-managed-thread-factory [options] ...
delete-managed-thread-factasadmin Utility Subcdelete-managed-thread-factory(1)

NAME
       delete-managed-thread-factory - deletes a managed thread factory
       resource

SYNOPSIS
           delete-managed-thread-factory [--help]
           [--target target]
           managed_thread_factory_name

DESCRIPTION
       The delete-managed-thread-factory subcommand deletes a managed thread
       factory resource.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           The target for which the managed thread factory resource is being
           deleted.

OPERANDS
       managed_thread_factory_name
           The name of the managed thread factory resource to be deleted.

EXAMPLES
       Example 1, Deleting a Managed Thread Factory Resource
           This example deletes the named managed thread factory resource.

               asadmin> delete-managed-thread-factory

               Command delete-managed-thread-factory executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-managed-thread-factory(1), list-managed-thread-factories(1)

       asadmin(1M)

Java EE 7                         09 Feb 2013 delete-managed-thread-factory(1)
Command delete-managed-thread-factory executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help delete-module-config [options] ...
delete-module-config(1)   asadmin Utility Subcommands  delete-module-config(1)

NAME
       delete-module-config - deletes the default configuration of a module
       from domain.xml

SYNOPSIS
           delete-module-config [--help]
           [--target target]
           servicename

DESCRIPTION
       The delete-module-config subcommand deletes the default configuration
       of a module from domain.xml and causes the module to use the default
       configuration included in the module.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           Specifies the target from which the default configuration of the
           module will be deleted.

           Possible values are as follows:

           server
               Deletes the default configuration of a module from the
               domain.xml for the default server instance. This is the default
               value.

           domain
               Deletes the default configuration of a module from the
               domain.xml for the default domain.

           cluster-name
               Deletes the default configuration of a module to the domain.xml
               from the specified cluster.

           instance-name
               Deletes the default configuration of a module from the
               domain.xml for the specified instance.

OPERANDS
       servicename
           The name of the module. The default configuration of the module
           will be deleted from the domain.xml of the target.

EXAMPLES
       Example 1, Deleting a Default Configuration From domain.xml
           This example deletes the default configuration of the web container
           module from the domain.xml file of domain1 in server-config (the
           default configuration).

               asadmin> delete-module-config web-container
               Command delete-module-config executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-module-config(1), get-active-module-config(1)

       asadmin(1M)

Java EE 7                         06 Feb 2013          delete-module-config(1)
Command delete-module-config executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help generate-rest-client [options] ...
NAME
     generate-rest-client

SYNOPSIS
     Usage: generate-rest-client --outputdir=outputdir [--languag
     es=java] 

OPTIONS
     --outputdir

     --languages
      -lang

Command generate-rest-client executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help get-active-module-config [options] ...
get-active-module-config(1asadmin Utility Subcommanget-active-module-config(1)

NAME
       get-active-module-config - displays the current active configuration of
       a service or instance

SYNOPSIS
           get-active-module-config [--help]
           [--target target]
           [--all[={false|true}]]
           [servicename]

DESCRIPTION
       The get-active-module-config subcommand displays the current active
       configuration of a service or instance.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           Specifies the target for the subcommand.

           Possible values are as follows:

           server
               Displays the current active configuration of a service for the
               default server instance. This is the default value.

           domain
               Displays the current active configuration of a service for the
               default domain.

           cluster-name
               Displays the current active configuration of a service for the
               specified cluster.

           instance-name
               Displays the current active configuration of a service for the
               specified instance.

       --all
           Displays all current active configurations.

           The default value is false.

OPERANDS
       servicename
           The name of the module.

EXAMPLES
       Example 1, Displaying the Current Active Configuration
           This example displays the current active configuration for the JMS
           service in server-config (the default configuration).

               asadmin> get-active-module-config
               At location: domain/configs/config[server-config]
               <jms-service default-jms-host="default_JMS_host" type="EMBEDDED"
                 <jms-host port="7676" host="localhost" name="default_JMS_host"/>
               </jms-service>
               Command get-active-module-config executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-module-config(1), delete-module-config(1)

       asadmin(1M)

Java EE 7                         06 Feb 2013      get-active-module-config(1)
Command get-active-module-config executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-batch-jobs [options] ...
list-batch-jobs(1)        asadmin Utility Subcommands       list-batch-jobs(1)

NAME
       list-batch-jobs - lists batch jobs

SYNOPSIS
           list-batch-jobs [--help]
           [--job-name job-name]
           [--instance-id instance-id]
           [--execution-id execution-id]
           [--long[={false|true}]]
           [--output output]
           [--header[={false|true}]]

DESCRIPTION
       The list-batch-jobs subcommand lists batch jobs and job details. A job
       represents the entire batch process.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --job-name, -j
           Specifies the name of a job.

       --instance-id, -i
           Specifies the instance ID of a job.

       --execution-id, -e
           Specifies the execution ID of a job.

       --long, -l
           Displays detailed information about the jobs. The default value is
           false.

       --output, -o
           Displays specific details about each job. Use a comma-separated
           list to specify the details you want to display and their order.
           The values are case-insensitive. The job-name and instance-count
           column headings are displayed by default.

           Possible values are as follows:

           job-name
               Displays the name of the job.

           instance-count
               Displays the number of job instances that are running.

           execution-id
               Displays the execution ID of a particular job instance.

           status
               Displays the status of the job.

           exit-status
               Displays the exit status of the job.

           start-time
               Displays the start time of the job.

           end-time
               Displays the finish time of the job.

           job-parameters
               Displays the job parameters.

       --header, -h
           Specifies whether column headings are displayed when the --long
           option is used. The default value is true. To suppress the
           headings, set the --header option to false.

EXAMPLES
       Example 1, List Batch Jobs
           The following example lists the batch jobs.

               asadmin> list-batch-jobs

               Command list-batch-jobs executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-batch-runtime-configuration(1)

       asadmin(1M)

Java EE 7                         13 Feb 2013               list-batch-jobs(1)
Command list-batch-jobs executed successfully.

JOBNAME  INSTANCECOUNT  
Command list-batch-jobs executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-batch-runtime-configuration [options] ...
list-batch-runtime-configuasadmin1Utility Slist-batch-runtime-configuration(1)

NAME
       list-batch-runtime-configuration - displays the configuration of the
       batch runtime

SYNOPSIS
           list-batch-runtime-configuration [--help]
           [--long[={false|true}]]
           [--output output]
           [--header[={false|true}]]

DESCRIPTION
       The list-batch-runtime-configuration subcommand displays the
       configuration of the batch runtime. Batch runtime configuration data is
       stored in the config element in domain.xml.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Displays detailed information about the batch runtime. The default
           value is false.

       --output, -o
           Displays specific details about the batch runtime. Use a
           comma-separated list to specify the details you want to display and
           their order. The values are case-insensitive. The
           min-thread-pool-size, max-thread-pool-size, max-queue-size, and
           data-source-name column headings are displayed by default.

           Possible values are as follows:

           min-thread-pool-size
               The minimum thread pool size.

           max-thread-pool-size
               The maximum thread pool size.

           max-idle-thread-timeout-in-seconds
               The maximum idle time before the thread is destroyed.

           max-queue-size
               The maximum queue size for holding jobs.

           data-source-name
               The name of the datasource where data about jobs is persisted
               by the job runtime.

           max-data-retention-time-in-seconds
               The maximum amount of time completed jobs are retained in the
               job repository.

       --header, -h
           Specifies whether column headings are displayed when the --long
           option is used. The default value is true. To suppress the
           headings, set the --header option to false.

EXAMPLES
       Example 1, List Batch Runtime Configuration
           The following example lists the configuration of the batch runtime.

               asadmin> list-batch-runtime-configuration
               MIN-THREAD-POOL-SIZE  MAX-THREAD-POOL-SIZE  DATA-SOURCE-NAME  4                     16                    jdbc/__
TimerPool
               Command list-batch-runtime-configuration executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-batch-jobs(1)

       asadmin(1M)

Java EE 7                         13 Feb 20list-batch-runtime-configuration(1)
Command list-batch-runtime-configuration executed successfully.

DATA-SOURCE-LOOKUP-NAME  EXECUTOR-SERVICE-LOOKUP-NAME             
jdbc/__TimerPool         java:comp/DefaultManagedExecutorService  
Command list-batch-runtime-configuration executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-context-services [options] ...
list-context-services(1)  asadmin Utility Subcommands list-context-services(1)

NAME
       list-context-services - lists the context service resources

SYNOPSIS
           list-context-services [--help]
           [target]

DESCRIPTION
       The list-context-services subcommand lists the context service
       resources.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       target
           The target for which the context service resources are being
           listed.

EXAMPLES
       Example 1, Listing the Context Service Resources
           This example lists the context service resources.

               asadmin> list-context-services

               Command list-context-services executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-context-service(1), delete-context-service(1)

       asadmin(1M)

Java EE 7                         09 Feb 2013         list-context-services(1)
Command list-context-services executed successfully.

concurrent/__defaultContextService
Command list-context-services executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-jobs [options] ...
list-jobs(1)              asadmin Utility Subcommands             list-jobs(1)

NAME
       list-jobs - lists information about subcommands started using asadmin
       --detach

SYNOPSIS
           list-jobs [--help]
           [jobid]

DESCRIPTION
       The list-jobs subcommand lists information about subcommands that were
       started using asadmin --detach, including job IDs.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       jobid
           The ID of the job for which you want to list information.

EXAMPLES
       Example 1, Checking Job Status
           This example provides information about subcommands that were
           started using asadmin --detach.

               asadmin> list-jobs
               JOB ID     COMMAND           STATE       EXIT CODE TIME OF COMPLETION
               1          load-sdp          COMPLETED   SUCCESS   2013-02-15 16:16:16 PST
               2          deploy            COMPLETED   FAILURE   2013-02-15 18:26:30 PST
               Command list-jobs executed successfully

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       configure-managed-jobs(1), attach(1)

       asadmin(1M)

Java EE 7                         06 Feb 2013                     list-jobs(1)
Command list-jobs executed successfully.

Nothing to list.
Command list-jobs executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-loggers [options] ...
list-loggers(1)           asadmin Utility Subcommands          list-loggers(1)

NAME
       list-loggers - lists existing loggers

SYNOPSIS
           list-loggers [--help]

DESCRIPTION
       The list-loggers subcommand lists the existing GlassFish Server
       loggers. Internal loggers are not listed. The list-loggers subcommand
       lists the logger name, subsystem, and description.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

EXAMPLES
       Example 1, Listing the Loggers
           This example lists the logger name, subsystem, and description for
           each logger. Some lines of output are omitted from this example for
           readability.

               asadmin> list-loggers
               Logger Name                            Subsystem         Logger Description
               ...
               javax.enterprise.monitoring            Monitoring        Monitoring Logger
               javax.enterprise.system.core.ee        AS-CORE           Java EE Core Kernel
               javax.enterprise.system.jmx            JMX               JMX System Logger
               javax.enterprise.system.tools.admin    ADMIN             Administration Services
               ...
               Command list-loggers executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-log-levels(1), set-log-file-format(1)

       asadmin(1M)

Java EE 7                         06 Feb 2013                  list-loggers(1)
Command list-loggers executed successfully.

Logger Name                                                 Subsystem         Logger Description                          
com.sun.enterprise.config                                   CONFIG-API        Configuration API                           
javax.enterprise.admin.rest                                 REST              Main REST Logger                            
javax.enterprise.admin.rest.client                          REST              REST Client Logger                          
javax.enterprise.admin.rest.connector                       RSTCN             REST Connector Logger                       
javax.enterprise.bootstrap                                  BOOTSTRAP         Main bootstrap logger.                      
javax.enterprise.cluster.gms                                CLSTR             Group Management Service Adapter Logger     
javax.enterprise.cluster.gms.admin                          CLSTR             Group Management Service Admin Logger       
javax.enterprise.cluster.gms.bootstrap                      CLSTR             Group Management Service Logger             
javax.enterprise.connector.work                             connector         logger for connector work manager module    
javax.enterprise.ejb.container                              GlassFish-EJB     GlassFish EJB Container Logger              
javax.enterprise.inject.spi                                 AS-CDI            CDI                                         
javax.enterprise.launcher                                   Launcher          Launcher Logger                             
javax.enterprise.logging                                    Logging           Main logger for core logging component.     
javax.enterprise.monitoring                                 Monitoring        Monitoring Logger                           
javax.enterprise.system.core                                CORE              Core Kernel                                 
javax.enterprise.system.core.ee                             AS-CORE           Java EE Core Kernel                         
javax.enterprise.system.jmx                                 JMX               JMX System Logger                           
javax.enterprise.system.tools.admin                         ADMIN             Administration Services                     
javax.enterprise.system.tools.admin.security                ADMSEC            Admin security                              
javax.enterprise.system.tools.admin.security.authorization  ADMSECAUTHZ       Admin security authorization                
javax.enterprise.system.tools.amx                           COMMON            AMX Services                                
javax.enterprise.system.tools.amxee                         AMX-JAVAEE        AMX Services                                
javax.enterprise.system.tools.deployment.autodeploy         DEPLOYMENT        Deployment System Logger                    
javax.enterprise.system.tools.deployment.client             DEPLOYMENT        Deployment System Logger                    
javax.enterprise.system.tools.deployment.common             DEPLOYMENT        Deployment System Logger                    
javax.enterprise.system.tools.deployment.dol                DEPLOYMENT        Deployment System Logger                    
javax.enterprise.system.tools.deployment.javaee             DEPLOYMENT        Deployment System Logger                    
javax.enterprise.system.tools.monitor                       MON               Flashlight Services                         
javax.enterprise.system.tools.util                          COMMON            Internal API                                
javax.enterprise.system.util                                COMMON            Common Utilities                            
javax.enterprise.web                                        WEB               Main WEB Logger                             
javax.enterprise.web.admin                                  WEB               WEB Admin Logger                            
javax.enterprise.web.core                                   WEB               WEB Core Logger                             
javax.enterprise.web.ha                                     WEB               WEB HA Logger                               
javax.enterprise.web.naming                                 WEB               WEB Naming Logger                           
javax.enterprise.web.util                                   WEB               WEB Util Logger                             
javax.enterprise.webservices                                WEBSERVICES       JSR-109 Implementation Logger               
javax.enterprise.webservices.connector                      WEBSERVICES       Web Services Connector Logger               
javax.enterprise.webservices.metroglue                      WEBSERVICES       Metro Glue Main Logger                      
javax.enterprise.webservices.transport.tcp                  WEBSERVICES       SOAP/TCP Transport Logger                   
org.glassfish.naming                                        glassfish-naming  logger for GlassFish appserver naming       
org.glassfish.orb                                           orb               logger for GlassFish appserver orb modules  

Command list-loggers executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-managed-executor-services [options] ...
list-managed-executor-servasadmin Utility Sublist-managed-executor-services(1)

NAME
       list-managed-executor-services - lists the managed executor service
       resources

SYNOPSIS
           list-managed-executor-services [--help]
           [target]

DESCRIPTION
       The list-managed-executor-services subcommand lists the managed
       executor service resources.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       target
           The target for which the managed executor service resources are
           being listed.

EXAMPLES
       Example 1, Listing the Managed Executor Service Resources
           The following example lists the managed executor service resources.

               asadmin> list-managed-executor-services

               Command list-managed-executor-services executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-managed-executor-service(1), delete-managed-executor-service(1)

       asadmin(1M)

Java EE 7                         09 Feb 2013list-managed-executor-services(1)
Command list-managed-executor-services executed successfully.

concurrent/__defaultManagedExecutorService
concurrent/__defaultManagedScheduledExecutorService
Command list-managed-executor-services executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-managed-scheduled-executor-services [options] ...
list-managed-scheduled-exeasadmineUlist-managed-scheduled-executor-services(1)

NAME
       list-managed-scheduled-executor-services - lists the managed scheduled
       executor service resources

SYNOPSIS
           list-managed-scheduled-executor-services [--help]
           [target]

DESCRIPTION
       The list-managed-scheduled-executor-services subcommand lists the
       managed scheduled executor service resources.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       target
           The target for which the managed scheduled executor service
           resources are being listed.

EXAMPLES
       Example 1, Listing the Managed Scheduled Executor Service Resources
           The following example lists the managed scheduled executor service
           resources.

               asadmin> list-managed-scheduled-executor-services

               Command list-managed-scheduled-executor-services executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-managed-scheduled-executor-service(1),
       delete-managed-scheduled-executor-service(1)

       asadmin(1M)

Java EE 7                         0list-managed-scheduled-executor-services(1)
Command list-managed-scheduled-executor-services executed successfully.

concurrent/__defaultManagedScheduledExecutorService
Command list-managed-scheduled-executor-services executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-managed-thread-factories [options] ...
list-managed-thread-factorasadmin Utility Subclist-managed-thread-factories(1)

NAME
       list-managed-thread-factories - lists the managed thread factory
       resources

SYNOPSIS
           list-managed-thread-factories [--help]
           [target]

DESCRIPTION
       The list-managed-thread-factories subcommand lists the managed thread
       factory resources.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       target
           The target for which the managed thread factory resources are being
           listed.

EXAMPLES
       Example 1, Listing the Managed Thread Factory Resources
           The following example lists the managed thread factory resources.

               asadmin> list-managed-thread-factories

               Command list-managed-thread-factories executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-managed-thread-factory(1), delete-managed-thread-factory(1)

       asadmin(1M)

Java EE 7                         09 Feb 2013 list-managed-thread-factories(1)
Command list-managed-thread-factories executed successfully.

concurrent/__defaultManagedThreadFactory
Command list-managed-thread-factories executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help osgi [options] ...
osgi(1)                   asadmin Utility Subcommands                  osgi(1)

NAME
       osgi - executes asadmin subcommands in the OSGi shell

SYNOPSIS
           osgi [--help]
           [--session session]
           [--session-id session-id]
           [--instance instance]
           [command-line ...]

DESCRIPTION
       The osgi subcommand executes asadmin subcommands in the OSGi shell

       This subcommand is supported in the remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       command-line ...
           TBD

EXAMPLES
       Example 1, TBD
           TBD

               asadmin> osgi

               Command osgi executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       asadmin(1M)

Java EE 7                         06 Feb 2013                          osgi(1)
Command osgi executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help set-log-file-format [options] ...
set-log-file-format(1)    asadmin Utility Subcommands   set-log-file-format(1)

NAME
       set-log-file-format - sets the formatter to be used for the server log
       file

SYNOPSIS
           set-log-file-format [--help]
           [--target target]
           [formatter]

DESCRIPTION
       The set-log-file-format subcommand sets the formatter to be used for
       the server log file for the specified target.

       GlassFish Server provides the ULF (UniformLogFormatter) and ODL (Oracle
       Diagnostics Logging) formatters. A custom formatter can also be used by
       specifying the fully qualified name of a class that extends
       java.util.logging.

       The custom formatter class can be packaged in a JAR file and placed in
       domain/lib/ext, or implemented as an HK2 service and the JAR containing
       the formatter implementation installed in glassfish/modules.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --target
           Specifies the target for which the formatter is being set. Specify
           the name of the server domain, instance, or cluster. If this option
           is omitted, logger attributes are set for the default server.

OPERANDS
       formatter
           Specifies the fomatter to be used for the server log file. Valid
           values are ULF, ODL, or the fully qualified name of the custom
           formatter class to be used to render the log files. The default
           value is ODL.

EXAMPLES
       Example 1, Setting the Log File Format
           This example sets the server log file format to ULF for server1.

               asadmin> set-log-file-format --target server1 ULF
               Command set-log-file-format executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-loggers(1)

       asadmin(1M)

Java EE 7                         06 Feb 2013           set-log-file-format(1)
Command set-log-file-format executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help setup-local-dcom [options] ...
setup-local-dcom(1)       asadmin Utility Subcommands      setup-local-dcom(1)

NAME
       setup-local-dcom - sets up DCOM on a host

SYNOPSIS
           setup-local-dcom [--help] [--verbose={false|true}]
           --force={false|true}

DESCRIPTION
       The setup-local-dcom subcommand sets up the Distributed Component
       Object Model (DCOM) remote protocol on the host where the subcommand is
       run. The DCOM remote protocol is available only on Windows systems.

       This subcommand must be run by the operating-system-level administrator
       user on the host where DCOM is being set up. Before running this
       command, ensure that items in the Windows operating system are set as
       described in "Windows Operating System Settings" in Oracle GlassFish
       Server High Availability Administration Guide.

       Setting up DCOM on a host ensures that scripts can be run on the host
       from a remote host. To run scripts on the host from a remote host, the
       Windows user must be allowed full control over some Windows registry
       keys.

       In some versions of Windows, only the user NT SERVICE\TrustedInstaller
       has full control over these Windows registry keys. If the version of
       Windows on a host is configured in this way, this subcommand modifies
       these keys to allow full control over them for the Windows user.

           Caution
           +----------------------------------------+
           |           This subcommand might modify |
           |           the permissions of some keys |
           |           in the Windows registry.     |
           |           Before running this command, |
           |           back up the Windows          |
           |           registry.                    |
           +----------------------------------------+

       By default, the subcommand prompts you to confirm that you want to
       update the Windows registry. To run the subcommand without being
       prompted, set the --force option to true.

       This subcommand is supported in local mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --verbose, -v
           Specifies whether the subcommand displays information about the
           operations that are performed to set up DCOM on the host.

           Possible values are as follows:

           false
               No information about the operations that are performed to set
               up DCOM is displayed (default).

           true
               The subcommand displays information about the operations that
               are performed to set up DCOM on the host.

       --force, -f
           Specifies whether the subcommand prompts you to confirm that you
           want to update the Windows registry.

           Possible values are as follows:

           false
               You are prompted to confirm that you want to update the Windows
               registry (default).

           true
               The subcommand forcibly updates the Windows registry without
               prompting you.

EXAMPLES
       Example 1, Setting Up DCOM on a Host
           This example sets up DCOM on the host where the subcommand is run.

               asadmin> setup-local-dcom
               Caution: This command might modify the permissions of some keys in the Windows
               registry.
               Before running this command, back up the Windows registry.
               The modification allows the Windows user full control over these keys.

               Are you sure that you want to edit the Windows registry? If so, type yes in full: yes
               Command setup-local-dcom executed successfully.

       Example 2, Forcibly Setting Up DCOM on a Host
           This example sets up DCOM without prompting for confirmation that
           the user wants to update the Windows registry.

               asadmin> setup-local-dcom --force=true
               Command setup-local-dcom executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       asadmin(1M)

       "Windows Operating System Settings" in Oracle GlassFish Server High
       Availability Administration Guide

Java EE 7                         10 Feb 2012              setup-local-dcom(1)
Command setup-local-dcom executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-jms-host [options] ...
create-jms-host(1)        asadmin Utility Subcommands       create-jms-host(1)

NAME
       create-jms-host - creates a JMS host

SYNOPSIS
           create-jms-host [--help]
           --mqhost mq-host --mqport mq-port
           --mquser mq-user --mqpassword mq-password
           [--target target]
           [--force[={false|true}]]
           jms_host_name

DESCRIPTION
       Creates a Java Message Service (JMS) host within the JMS service.

       This subcommand is supported in remote mode only. Remote asadmin
       subcommands require a running domain administration server (DAS).

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --mqhost
           The host name for the JMS service.

       --mqport
           The port number used by the JMS service.

       --mquser
           The user name for the JMS service.

       --mqpassword
           The password for the JMS service.

       --target
           Creates the JMS host only for the specified target. Valid values
           are as follows:

           server
               Creates the JMS host for the default server instance. This is
               the default value.

           configuration-name
               Creates the JMS host in the specified configuration.

           cluster-name
               Creates the JMS host for every server instance in the specified
               cluster.

           instance-name
               Creates the JMS host for the specified server instance.

       --force
           Specifies whether the subcommand overwrites the existing JMS host
           of the same name. The default value is false.

OPERANDS
       jms_host_name
           A unique identifier for the JMS host to be created.

EXAMPLES
       Example 1, Creating a JMS host using a non-default port
           The following command creates a JMS host named MyNewHost on the
           system pigeon.

               asadmin> create-jms-host --mqhost pigeon.example.com --mqport 7677
               --mquser admin --mqpassword admin MyNewHost
               Jms Host MyNewHost created.
               Command create-jms-host executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list-jms-hosts(1), delete-jms-host(1), jms-ping(1)

       asadmin(1M)

Java EE 7                         12 Feb 2013               create-jms-host(1)
Command create-jms-host executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-jms-resource [options] ...
create-jms-resource(1)    asadmin Utility Subcommands   create-jms-resource(1)

NAME
       create-jms-resource - creates a JMS resource

SYNOPSIS
           create-jms-resource [--help]
           --restype type
           [--target target]
           [--enabled={true|false}]
           [--description text]
           [--property (name=value)[:name=value]*]
           [--force[={false|true}]]
           jndi_name

DESCRIPTION
       The create-jms-resource subcommand creates a Java Message Service (JMS)
       connection factory resource or a JMS destination resource.

       This subcommand is supported in remote mode only. Remote asadmin
       subcommands require a running domain administration server (DAS).

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --restype
           The JMS resource type, which can be javax.jms.Topic,
           javax.jms.Queue, javax.jms.ConnectionFactory,
           javax.jms.TopicConnectionFactory, or
           javax.jms.QueueConnectionFactory.

       --target
           Creates the JMS resource only for the specified target. Valid
           values are as follows:

               Note
               +----------------------------------------+
               |The resource is always created for the  |
               |domain as a whole, but the              |
               |<resource-ref> element for the resource |
               |is only created for the specified       |
               |--target. This means that although the  |
               |resource is defined at the domain       |
               |level, it is only active at the         |
               |specified --target.                     |
               +----------------------------------------+

           server
               Creates the JMS resource for the default server instance. This
               is the default value.

           domain
               Creates the JMS resource for the domain.

           cluster-name
               Creates the JMS resource for every server instance in the
               specified cluster.

           instance-name
               Creates the JMS resource for the specified server instance.

       --enabled
           If set to true (the default), the resource is enabled at runtime.

       --description
           Text providing details about the JMS resource.

       --property
           Optional attribute name/value pairs for configuring the JMS
           resource.

           You can specify the following properties for a connection factory
           resource:

           ClientId
               A client ID for a connection factory that will be used by a
               durable subscriber.

           AddressList
               A comma-separated list of message queue addresses that specify
               the host names (and, optionally, port numbers) of a message
               broker instance or instances with which your application will
               communicate. For example, the value could be earth or
               earth:7677. Specify the port number if the message broker is
               running on a port other than the default (7676). composed from
               the JMS hosts defined in the server's JMS service
               configuration. The default value is localhost and the default
               port number is 7676. The client will attempt a connection to a
               broker on port 7676 of the local host.

           UserName
               The user name for the connection factory. The default value is
               guest.

           Password
               The password for the connection factory. The default value is
               guest.

           ReconnectEnabled
               A value of true indicates that the client runtime attempts to
               reconnect to a message server (or the list of addresses in the
               AddressList) when a connection is lost. The default value is
               false.

           ReconnectAttempts
               The number of attempts to connect (or reconnect) for each
               address in the AddressList before the client runtime tries the
               next address in the list. A value of -1 indicates that the
               number of reconnect attempts is unlimited (the client runtime
               attempts to connect to the first address until it succeeds).
               The default value is 6.

           ReconnectInterval
               The interval in milliseconds between reconnect attempts. This
               applies to attempts on each address in the AddressList and for
               successive addresses in the list. If the interval is too short,
               the broker does not have time to recover. If it is too long,
               the reconnect might represent an unacceptable delay. The
               default value is 30,000 milliseconds.

           AddressListBehavior
               Specifies whether connection attempts are in the order of
               addresses in the AddressList (PRIORITY) or in a random order
               (RANDOM).  PRIORITY means that the reconnect will always try to
               connect to the first server address in the AddressList and will
               use another one only if the first broker is not available. If
               you have many clients attempting a connection using the same
               connection factory, specify RANDOM to prevent them from all
               being connected to the same address. The default value is the
               AddressListBehavior value of the server's JMS service
               configuration.

           AddressListIterations
               The number of times the client runtime iterates through the
               AddressList in an effort to establish (or re-establish) a
               connection). A value of -1 indicates that the number of
               attempts is unlimited. The default value is -1.

           Additionally, you can specify connector-connection-pool attributes
           as connector resource properties. For a list of these attributes,
           see "connector-connection-pool" in Oracle GlassFish Server
           Application Deployment Guide.

           You can specify the following properties for a destination
           resource:

           Name
               The name of the physical destination to which the resource will
               refer. The physical destination is created automatically when
               you run an application that uses the destination resource. You
               can also create a physical destination with the create-jmsdest
               subcommand. If you do not specify this property, the JMS
               service creates a physical destination with the same name as
               the destination resource (replacing any forward slash in the
               JNDI name with an underscore).

           Description
               A description of the physical destination.

       --force
           Specifies whether the subcommand overwrites the existing JMS
           resource of the same name. The default value is false.

OPERANDS
       jndi_name
           The JNDI name of the JMS resource to be created.

EXAMPLES
       Example 1, Creating a JMS connection factory resource for durable
       subscriptions
           The following subcommand creates a connection factory resource of
           type javax.jms.ConnectionFactory whose JNDI name is
           jms/DurableConnectionFactory. The ClientId property sets a client
           ID on the connection factory so that it can be used for durable
           subscriptions. The JNDI name for a JMS resource customarily
           includes the jms/ naming subcontext.

               asadmin> create-jms-resource --restype javax.jms.ConnectionFactory
               --description "connection factory for durable subscriptions"
               --property ClientId=MyID jms/DurableConnectionFactory
               Connector resource jms/DurableConnectionFactory created.
               Command create-jms-resource executed successfully.

       Example 2, Creating a JMS destination resource
           The following subcommand creates a destination resource whose JNDI
           name is jms/MyQueue. The Name property specifies the physical
           destination to which the resource refers.

               asadmin> create-jms-resource --restype javax.jms.Queue
               --property Name=PhysicalQueue jms/MyQueue
               Administered object jms/MyQueue created.
               Command create-jms-resource executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       delete-jms-resource(1), list-jms-resources(1)

       asadmin(1M)

Java EE 7                         12 Feb 2013           create-jms-resource(1)
Command create-jms-resource executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help create-jmsdest [options] ...
create-jmsdest(1)         asadmin Utility Subcommands        create-jmsdest(1)

NAME
       create-jmsdest - creates a JMS physical destination

SYNOPSIS
           create-jmsdest [--help]
           --desttype dest_type
           [--property (name=value)[:name=value]*]
           [--target target]
           [--force[={false|true}]]
           dest_name

DESCRIPTION
       The create-jmsdest subcommand creates a Java Message Service (JMS)
       physical destination. Typically, you use the create-jms-resource
       subcommand to create a JMS destination resource that has a Name
       property that specifies the physical destination. The physical
       destination is created automatically when you run an application that
       uses the destination resource. Use the create-jmsdest subcommand if you
       want to create a physical destination with non-default property
       settings.

       This subcommand is supported in remote mode only. Remote asadmin
       subcommands require a running domain administration server (DAS).

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --desttype
           The type of the JMS destination. Valid values are topic and queue.

       --property
           Optional attribute name/value pairs for configuring the physical
           destination. You can specify the following properties for a
           physical destination.

           maxNumMsgs
               The maximum number of unconsumed messages permitted for the
               destination. A value of -1 denotes an unlimited number of
               messages. The default value is -1. For the dead message queue,
               the default value is 1000.

               If the limitBehavior property is set to FLOW_CONTROL, it is
               possible for the specified message limit to be exceeded because
               the broker cannot react quickly enough to stop the flow of
               incoming messages. In such cases, the value specified for
               maxNumMsgs serves as merely a hint for the broker rather than a
               strictly enforced limit.

           maxBytesPerMsg
               The maximum size, in bytes, of any single message. Rejection of
               a persistent message is reported to the producing client with
               an exception; no notification is sent for non-persistent
               messages.

               The value may be expressed in bytes, kilobytes, or megabytes,
               using the following suffixes:

               b
                   Bytes

               k
                   Kilobytes (1024 bytes)

               m
                   Megabytes (1024 x 1024 = 1,048,576 bytes)

               A value with no suffix is expressed in bytes; a value of -1
               denotes an unlimited message size. The default value is -1.

           maxTotalMsgBytes
               The maximum total memory, in bytes, for unconsumed messages.
               The default value is -1. The syntax is the same as for
               maxBytesPerMsg. For the dead message queue, the default value
               is 10m.

           limitBehavior
               The behavior of the message queue broker when the memory-limit
               threshold is reached. Valid values are as follows.

               REJECT_NEWEST
                   Reject newest messages and notify the producing client with
                   an exception only if the message is persistent. This is the
                   default value.

               FLOW_CONTROL
                   Slow the rate at which message producers send messages.

               REMOVE_OLDEST
                   Throw out the oldest messages.

               REMOVE_LOW_PRIORITY
                   Throw out the lowest-priority messages according to age,
                   with no notification to the producing client.

               If the value is REMOVE_OLDEST or REMOVE_LOW_PRIORITY and the
               useDMQ property is set to true, excess messages are moved to
               the dead message queue. For the dead message queue itself, the
               default limit behavior is REMOVE_OLDEST, and the value cannot
               be set to FLOW_CONTROL.

           maxNumProducers
               The maximum number of message producers for the destination.
               When this limit is reached, no new producers can be created. A
               value of -1 denotes an unlimited number of producers. The
               default value is 100. This property does not apply to the dead
               message queue.

           consumerFlowLimit
               The maximum number of messages that can be delivered to a
               consumer in a single batch. A value of -1 denotes an unlimited
               number of messages. The default value is 1000. The client
               runtime can override this limit by specifying a lower value on
               the connection factory object.

               In load-balanced queue delivery, this is the initial number of
               queued messages routed to active consumers before load
               balancing begins.

           useDMQ
               If set to true, dead messages go to the dead message queue. If
               set to false, dead messages are discarded. The default value is
               true.

           validateXMLSchemaEnabled
               If set to true, XML schema validation is enabled for the
               destination. The default value is false.

               When XML validation is enabled, the Message Queue client
               runtime will attempt to validate an XML message against the
               specified XSDs (or against the DTD, if no XSD is specified)
               before sending it to the broker. If the specified schema cannot
               be located or the message cannot be validated, the message is
               not sent, and an exception is thrown.

               This property should be set when a destination is inactive:
               that is, when it has no consumers or producers and when there
               are no messages in the destination. Otherwise the producer must
               reconnect.

           XMLSchemaURIList
               A space-separated list of XML schema document (XSD) URI
               strings. The URIs point to the location of one or more XSDs to
               use for XML schema validation, if validateXMLSchemaEnabled is
               set to true. The default value is null.

               Use double quotes around this value if multiple URIs are
               specified, as in the following example:

                   "http://foo/flap.xsd http://test.com/test.xsd"
               If this property is not set or null and XML validation is
               enabled, XML validation is performed using a DTD specified in
               the XML document. If an XSD is changed as a result of changing
               application requirements, all client applications that produce
               XML messages based on the changed XSD must reconnect to the
               broker.

           To modify the value of these properties, you can use the
           as-install/mq/bin/imqcmd command. See "Physical Destination
           Property Reference" in Oracle GlassFish Server Message Queue
           Administration Guide for more information.

       --target
           Creates the physical destination only for the specified target.
           Although the create-jmsdest subcommand is related to resources, a
           physical destination is created using the JMS Service (JMS Broker),
           which is part of the configuration. A JMS Broker is configured in
           the config section of domain.xml. Valid values are as follows:

           server
               Creates the physical destination for the default server
               instance. This is the default value.

           configuration-name
               Creates the physical destination in the specified
               configuration.

           cluster-name
               Creates the physical destination for every server instance in
               the specified cluster.

           instance-name
               Creates the physical destination for the specified server
               instance.

       --force
           Specifies whether the subcommand overwrites the existing JMS
           physical destination of the same name. The default value is false.

OPERANDS
       dest_name
           A unique identifier for the JMS destination to be created.

EXAMPLES
       Example 1, Creating a JMS physical destination
           The following subcommand creates a JMS physical queue named
           PhysicalQueue with non-default property values.

               asadmin> create-jmsdest --desttype queue
               --property maxNumMsgs=1000:maxBytesPerMsg=5k PhysicalQueue
               Command create-jmsdest executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-jms-resource(1), delete-jmsdest(1), list-jmsdest(1),
       flush-jmsdest(1)

       asadmin(1M)

Java EE 7                         12 Feb 2013                create-jmsdest(1)
Command create-jmsdest executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help deploy [options] ...
deploy(1)                 asadmin Utility Subcommands                deploy(1)

NAME
       deploy - deploys the specified component

SYNOPSIS
           deploy [--help]
           [--force={false|true}]
           [--virtualservers virtual_servers]
           [--contextroot context_root]
           [--precompilejsp={false|true}]
           [--verify={false|true}]
           [--name component_name]
           [--upload={true|false}]
           [--retrieve local_dirpath]
           [--dbvendorname dbvendorname]
           [--createtables={true|false}|--dropandcreatetables={true|false}]
           [--uniquetablenames={true|false}]
           [--deploymentplan deployment_plan]
           [--altdd alternate_deploymentdescriptor]
           [--runtimealtdd runtime_alternate_deploymentdescriptor]
           [--deploymentorder deployment_order]
           [--enabled={true|false}]
           [--generatermistubs={false|true}]
           [--availabilityenabled={false|true}]
           [--asyncreplication={true|false}]
           [--lbenabled={true|false}]
           [--keepstate={false|true}]
           [--libraries jar_file[,jar_file]*]
           [--target target]
           [--type pkg-type]
           [--properties(name=value)[:name=value]*]
           [file_archive|filepath]

DESCRIPTION
       The deploy subcommand deploys applications to the server. Applications
       can be enterprise applications, web applications, Enterprise JavaBeans
       (EJB) modules, connector modules, and application client modules. If
       the component is already deployed or already exists, it is forcibly
       redeployed if the --force option is set to true (default is false).

       The --createtables and --dropandcreatetables options are boolean flags
       and therefore can take the values of true or false. These options are
       only used during deployment of CMP beans that have not been mapped to a
       database (that is, no sun-cmp-mappings.xml descriptor is provided in
       the module's META-INF directory). They are ignored otherwise.

       The --createtables and --dropandcreatetables options are mutually
       exclusive; only one should be used. If drop and/or create tables fails,
       the deployment does not fail; a warning message is provided in the log
       file.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --force
           If set to true, redeploys the component even if the specified
           component has already been deployed or already exists. Default is
           false.

       --virtualservers
           One or more virtual server IDs. Multiple IDs are separated by
           commas.

       --contextroot
           Valid only if the archive is a web module. It is ignored for other
           archive types; defaults to filename without extension.

       --precompilejsp
           By default this option does not allow the JSP to be precompiled
           during deployment. Instead, JSPs are compiled during runtime.
           Default is false.

       --verify
           If set to true and the required verifier packages are installed
           from the Update Tool, the syntax and semantics of the deployment
           descriptor is verified. Default is false.

       --name
           Name of the deployable component.

           The name can include an optional version identifier, which follows
           the name and is separated from the name by a colon (:). The version
           identifier must begin with a letter or number. It can contain
           alphanumeric characters plus underscore (_), dash (-), and period
           (.) characters. For more information about module and application
           versions, see "Module and Application Versions" in Oracle GlassFish
           Server Application Deployment Guide.

       --upload
           Specifies whether the subcommand uploads the file to the DAS. In
           most situations, this option can be omitted.

           Valid values are as follows:

           false
               The subcommand does not upload the file and attempts to access
               the file through the specified file name. If the DAS cannot
               access the file, the subcommand fails.

               For example, the DAS might be running as a different user than
               the administration user and does not have read access to the
               file. In this situation, the subcommand fails if the --upload
               option is false.

           true
               The subcommand uploads the file to the DAS over the network
               connection.

           The default value depends on whether the DAS is on the host where
           the subcommand is run or is on a remote host.

           *   If the DAS is on the host where the subcommand is run, the
               default is false.

           *   If the DAS is on a remote host, the default is true.

           If a directory filepath is specified, this option is ignored.

       --retrieve
           Retrieves the client stub JAR file from the server machine to the
           local directory.

       --dbvendorname
           Specifies the name of the database vendor for which tables are
           created. Supported values include db2, mssql, mysql, oracle, derby,
           javadb, postgresql, and sybase. These values are case-insensitive.
           If not specified, the value of the database-vendor-name attribute
           in glassfish-ejb-jar.xml is used. If no value is specified, a
           connection is made to the resource specified by the jndi-name
           subelement of the cmp-resource element in the glassfish-ejb-jar.xml
           file, and the database vendor name is read. If the connection
           cannot be established, or if the value is not recognized, SQL-92
           compliance is presumed.

       --createtables
           If specified as true, creates tables at deployment of an
           application with unmapped CMP beans. If specified as false, tables
           are not created. If not specified, the value of the
           create-tables-at-deploy entry in the cmp-resource element of the
           glassfish-ejb-jar.xml file determines whether or not tables are
           created. No unique constraints are created for the tables.

       --dropandcreatetables
           If specified as true when the component is redeployed, the tables
           created by the previous deployment are dropped before creating the
           new tables. Applies to deployed applications with unmapped CMP
           beans. Preexisting tables will not be dropped on the initial
           deployment of an application or on a deployment that follows an
           explicit undeploy. If specified as false, tables are neither
           dropped nor created. If not specified, the tables are dropped if
           the drop-tables-at-undeploy entry in the cmp-resource element of
           the glassfish-ejb-jar.xml file is set to true, and the new tables
           are created if the create-tables-at-deploy entry in the
           cmp-resource element of the glassfish-ejb-jar.xml file is set to
           true.

       --uniquetablenames
           Guarantees unique table names for all the beans and results in a
           hash code added to the table names. This is useful if you have an
           application with case-sensitive bean names. Applies to applications
           with unmapped CMP beans.

       --deploymentplan
           Deploys the deployment plan, which is a JAR file that contains
           GlassFish Server descriptors. Specify this option when deploying a
           pure EAR file. A pure EAR file is an EAR without GlassFish Server
           descriptors.

       --altdd
           Deploys the application using a Java EE standard deployment
           descriptor that resides outside of the application archive. Specify
           an absolute path or a relative path to the alternate deployment
           descriptor file. The alternate deployment descriptor overrides the
           top-level deployment descriptor packaged in the archive. For
           example, for an EAR, the use of --altdd overrides application.xml.
           For a standalone module, the use of --altdd overrides the top-level
           module descriptor such as web.xml.

       --runtimealtdd
           Deploys the application using a GlassFish Server runtime deployment
           descriptor that resides outside of the application archive. Specify
           an absolute path or a relative path to the alternate deployment
           descriptor file. The alternate deployment descriptor overrides the
           top-level deployment descriptor packaged in the archive. For
           example, for an EAR, the use of --runtimealtdd overrides
           glassfish-application.xml. For a standalone module, the use of
           --runtimealtdd overrides the top-level module descriptor such as
           glassfish-web.xml. Applies to GlassFish Server deployment
           descriptors only (glassfish-*.xml); the name of the alternate
           deployment descriptor file must begin with glassfish-. Does not
           apply to sun-*.xml deployment descriptors, which are deprecated.

       --deploymentorder
           Specifies the deployment order of the application. This is useful
           if the application has dependencies and must be loaded in a certain
           order at server startup. The deployment order is specified as an
           integer. The default value is 100. Applications with a lower number
           are loaded before applications with a higher number. For example,
           an application with a deployment order of 102 is loaded before an
           application with a deployment order of 110. If a deployment order
           is not specified, the default value of 100 is assigned. If two
           applications have the same deployment order, the first application
           to be deployed is the first application to be loaded at server
           startup.

           The deployment order is typically specified when the application is
           first deployed but can also be specified or changed after initial
           deployment using the set subcommand. You can view the deployment
           order of an application using the get subcommand.

       --enabled
           Allows users to access the application. If set to false, users will
           not be able to access the application. This option enables the
           application on the specified target instance or cluster. If you
           deploy to the target domain, this option is ignored, since
           deploying to the domain doesn't deploy to a specific instance or
           cluster. The default is true.

       --generatermistubs
           If set to true, static RMI-IIOP stubs are generated and put into
           the client.jar. If set to false, the stubs are not generated.
           Default is false.

       --availabilityenabled
           This option controls whether high-availability is enabled for web
           sessions and for stateful session bean (SFSB) checkpointing and
           potentially passivation. If set to false (default) all web session
           saving and SFSB checkpointing is disabled for the specified
           application, web application, or EJB module. If set to true, the
           specified application or module is enabled for high-availability.
           Set this option to true only if high availability is configured and
           enabled at higher levels, such as the server and container levels.

       --asyncreplication
           This option controls whether web session and SFSB states for which
           high availability is enabled are first buffered and then replicated
           using a separate asynchronous thread. If set to true (default),
           performance is improved but availability is reduced. If the
           instance where states are buffered but not yet replicated fails,
           the states are lost. If set to false, performance is reduced but
           availability is guaranteed. States are not buffered but immediately
           transmitted to other instances in the cluster.

       --lbenabled
           This option controls whether the deployed application is available
           for load balancing. The default is true.

       --keepstate
           This option controls whether web sessions, SFSB instances, and
           persistently created EJB timers are retained between redeployments.

           The default is false. This option is supported only on the default
           server instance, named server. It is not supported and ignored for
           any other target.

           Some changes to an application between redeployments prevent this
           feature from working properly. For example, do not change the set
           of instance variables in the SFSB bean class.

           For web applications, this feature is applicable only if in the
           glassfish-web-app.xml file the persistence-type attribute of the
           session-manager element is file.

           For stateful session bean instances, the persistence type without
           high availability is set in the server (the sfsb-persistence-type
           attribute) and must be set to file, which is the default and
           recommended value.

           If any active web session, SFSB instance, or EJB timer fails to be
           preserved or restored, none of these will be available when the
           redeployment is complete. However, the redeployment continues and a
           warning is logged.

           To preserve active state data, GlassFish Server serializes the data
           and saves it in memory. To restore the data, the class loader of
           the newly redeployed application deserializes the data that was
           previously saved.

       --libraries
           A comma-separated list of library JAR files. Specify the library
           JAR files by their relative or absolute paths. Specify relative
           paths relative to domain-dir/lib/applibs. The libraries are made
           available to the application in the order specified.

       --target
           Specifies the target to which you are deploying. Valid values are:

           server
               Deploys the component to the default server instance server and
               is the default value.

           domain
               Deploys the component to the domain. If domain is the target
               for an initial deployment, the application is deployed to the
               domain, but no server instances or clusters reference the
               application. If domain is the target for a redeployment (the
               --force option is set to true), and dynamic reconfiguration is
               enabled for the clusters or server instances that reference the
               application, the referencing clusters or server instances
               automatically get the new version of the application. If
               redeploying, and dynamic configuration is disabled, the
               referencing clusters or server instances do not get the new
               version of the application until the clustered or standalone
               server instances are restarted.

           cluster_name
               Deploys the component to every server instance in the cluster.

           instance_name
               Deploys the component to a particular stand-alone sever
               instance.

       --type
           The packaging archive type of the component that is being deployed.
           Possible values are as follows:

           car
               The component is packaged as a CAR file.

           ear
               The component is packaged as an EAR file.

           ejb
               The component is an EJB packaged as a JAR file.

           osgi
               The component is packaged as an OSGi bundle.

           rar
               The component is packaged as a RAR file.

           war
               The component is packaged as a WAR file.

       --properties or --property
           Optional keyword-value pairs that specify additional properties for
           the deployment. The available properties are determined by the
           implementation of the component that is being deployed or
           redeployed. The --properties option and the --property option are
           equivalent. You can use either option regardless of the number of
           properties that you specify.

           You can specify the following properties for a deployment:

           jar-signing-alias
               Specifies the alias for the security certificate with which the
               application client container JAR file is signed. Java Web Start
               will not run code that requires elevated permissions unless it
               resides in a JAR file signed with a certificate that the user's
               system trusts. For your convenience, GlassFish Server signs the
               JAR file automatically using the certificate with this alias
               from the domain's keystore. Java Web Start then asks the user
               whether to trust the code and displays the GlassFish Server
               certificate information. To sign this JAR file with a different
               certificate, add the certificate to the domain keystore, then
               use this property. For example, you can use a certificate from
               a trusted authority, which avoids the Java Web Start prompt, or
               from your own company, which users know they can trust. Default
               is s1as, the alias for the self-signed certificate created for
               every domain.

           java-web-start-enabled
               Specifies whether Java Web Start access is permitted for an
               application client module. Default is true.

           compatibility
               Specifies the GlassFish Server release with which to be
               backward compatible in terms of JAR visibility requirements for
               applications. The only allowed value is v2, which refers to Sun
               GlassFish Enterprise Server version 2 or Sun Java System
               Application Server version 9.1 or 9.1.1. The Java EE 6 platform
               specification imposes stricter requirements than Java EE 5 did
               on which JAR files can be visible to various modules within an
               EAR file. In particular, application clients must not have
               access to EJB JAR files or other JAR files in the EAR file
               unless references use the standard Java SE mechanisms
               (extensions, for example) or the Java EE library-directory
               mechanism. Setting this property to v2 removes these Java EE 6
               restrictions.

           keepSessions={false|true}
               Superseded by the --keepstate option.

               If the --force option is set to true, this property can by used
               to specify whether active sessions of the application that is
               being redeployed are preserved and then restored when the
               redeployment is complete. Applies to HTTP sessions in a web
               container. Default is false.

               false
                   Active sessions of the application are not preserved and
                   restored (default).

               true
                   Active sessions of the application are preserved and
                   restored.

                   If any active session of the application fails to be
                   preserved or restored, none of the sessions will be
                   available when the redeployment is complete. However, the
                   redeployment continues and a warning is logged.

                   To preserve active sessions, GlassFish Server serializes
                   the sessions and saves them in memory. To restore the
                   sessions, the class loader of the newly redeployed
                   application deserializes any sessions that were previously
                   saved.

           preserveAppScopedResources
               If set to true, preserves any application-scoped resources and
               restores them during redeployment. Default is false.

           Other available properties are determined by the implementation of
           the component that is being redeployed.

OPERANDS
       file_archive|filepath
           The path to the archive that contains the application that is being
           deployed. This path can be a relative path or an absolute path.

           The archive can be in either of the following formats:

           *   An archive file, for example, /export/JEE_apps/hello.war.

               If the --upload option is set to true, this is the path to the
               deployable file on the local client machine. If the --upload
               option is set to false, this is the path to the file on the
               server machine.

           *   A directory that contains the exploded format of the deployable
               archive. This is the path to the directory on the server
               machine.

               If you specify a directory, the --upload option is ignored.

EXAMPLES
       Example 1, Deploying an Enterprise Application
           This example deploys the enterprise application packaged in the
           Cart.ear file to the default server instance server. You can use
           the --target option to deploy to a different server instance or to
           a cluster.

               asadmin> deploy Cart.ear
               Application deployed successfully with name Cart.
               Command deploy executed successfully

       Example 2, Deploying a Web Application With the Default Context Root
           This example deploys the web application in the hello.war file to
           the default server instance server. You can use the --target option
           to deploy to a different server instance or to a cluster.

               asadmin> deploy hello.war
               Application deployed successfully with name hello.
               Command deploy executed successfully

       Example 3, Forcibly Deploying a Web Application With a Specific Context
       Root
           This example forcibly deploys the web application in the hello.war
           file. The context root of the deployed web application is
           greetings. If the application has already been deployed, it is
           redeployed.

               asadmin> deploy --force=true --contextroot greetings hello.war
               Application deployed successfully with name hello.
               Command deploy executed successfully

       Example 4, Deploying an Enterprise Bean
           This example deploys a component based on the EJB specification
           (enterprise bean) with CMP and creates the database tables used by
           the bean.

           This example uses the --target option. The target in this example
           is an existing cluster, cluster1.

               asadmin> deploy --createtables=true --target cluster1 EmployeeEJB.jar
               Application deployed successfully with name EmployeeEJB.
               Command deploy executed successfully

       Example 5, Deploying a Connector Module
           This example deploys a connector module that is packaged in a RAR
           file.

           This example uses the --target option. The target in this example
           is an existing standalone server instance that does not belong to a
           cluster.

               asadmin> deploy --target myinstance jdbcra.rar
               Application deployed successfully with name jdbcra.
               Command deploy executed successfully

       Example 6, Specifying the Deployment Order for an Application
           This example specifies the deployment order for two applications.
           The cart application is loaded before the horse application at
           server startup.

               asadmin> deploy --deploymentorder 102 --name cart cart.war
               asadmin> deploy --deploymentorder 110 --name horse horse.war

       Example 7, Deploying an Application Using an Alternate Java EE 7
       Deployment Descriptor File
           This example deploys an application using a Java EE standard
           deployment descriptor file that resides outside of the application
           archive.

               asadmin> deploy --altdd path_to_alternate_descriptor cart.ear

       Example 8, Deploying an Application Using an Alternate GlassFish Server
       Deployment Descriptor File
           This example deploys an application using a GlassFish Server
           runtime deployment descriptor file that resides outside of the
           application archive.

               asadmin> deploy --runtimealtdd path_to_alternate_runtime_descriptor horse.ear

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       redeploy(1), list-components(1), undeploy(1), get(1), set(1)

       asadmin(1M)

       Oracle GlassFish Server Application Deployment Guide

Java EE 7                         12 Feb 2013                        deploy(1)
Command deploy executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help deploydir [options] ...
deploydir(1)              asadmin Utility Subcommands             deploydir(1)

NAME
       deploydir - deploys an exploded format of application archive

SYNOPSIS
           deploydir [--help]
           [--force={false|true}]
           [--virtualservers virtual_servers]
           [--contextroot context_root]
           [--verify={false|true}]
           [--precompilejsp={false|true}]
           [--name component-name]
           [--retrieve local_dirpath]
           [--uniquetablenames={true|false}]
           [--dbvendorname dbvendorname]
           [--createtables={false|true}|--dropandcreatetables={false|true}]
           [--deploymentplan deployment_plan]
           [--altdd alternate_deploymentdescriptor]
           [--runtimealtdd runtime_alternate_deploymentdescriptor]
           [--deploymentorder deployment_order]
           [--enabled={true|false}]
           [--generatermistubs={false|true}]
           [--availabilityenabled={false|true}]
           [--asyncreplication={true|false}]
           [--lbenabled={true|false}]
           [--keepstate={false|true}]
           [--libraries jar_file[,jar_file]*]
           [--target target]
           [--type pkg-type]
           [--properties(name=value)[:name=value]*]
           dirpath

DESCRIPTION
           Note
           +---------------------------------------+
           |           The deploydir subcommand is |
           |           deprecated. Use the deploy  |
           |           subcommand instead.         |
           +---------------------------------------+

       The deploydir subcommand deploys an application directly from a
       development directory. The appropriate directory hierarchy and
       deployment descriptors conforming to the Java EE specification must
       exist in the deployment directory.

       Directory deployment is for advanced developers only. Do not use
       deploydir in production environments. Instead, use the deploy
       subcommand. Directory deployment is only supported on localhost, that
       is, the client and server must reside on the same machine. For this
       reason, the only values for the --host option are:

       *   localhost

       *   The value of the $HOSTNAME environment variable

       *   The IP address of the machine

       If the --uniquetablenames, --createtables, and --dropandcreatetables
       options are not specified, the entries in the deployment descriptors
       are used.

       The --force option makes sure the component is forcefully (re)deployed
       even if the specified component has already been deployed or already
       exists. Set the --force option to false for an initial deployment. If
       the specified application is running and the --force option is set to
       false, the subcommand fails.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --force
           If set to true, redeploys the component even if the specified
           component has already been deployed or already exists. Default is
           false.

       --virtualservers
           One or more virtual server IDs. Multiple IDs are separated by
           commas.

       --contextroot
           Valid only if the archive is a web module. It is ignored for other
           archive types; defaults to filename without extension.

       --precompilejsp
           By default this option does not allow the JSP to be precompiled
           during deployment. Instead, JSPs are compiled during runtime.
           Default is false.

       --verify
           If set to true and the required verifier packages are installed
           from the Update Tool, the syntax and semantics of the deployment
           descriptor is verified. Default is false.

       --name
           Name of the deployable component.

           The name can include an optional version identifier, which follows
           the name and is separated from the name by a colon (:). The version
           identifier must begin with a letter or number. It can contain
           alphanumeric characters plus underscore (_), dash (-), and period
           (.) characters. For more information about module and application
           versions, see "Module and Application Versions" in Oracle GlassFish
           Server Application Deployment Guide.

       --retrieve
           Retrieves the client stub JAR file from the server machine to the
           local directory.

       --dbvendorname
           Specifies the name of the database vendor for which tables are
           created. Supported values include db2, mssql, mysql, oracle, derby,
           javadb, postgresql, and sybase. These values are case-insensitive.
           If not specified, the value of the database-vendor-name attribute
           in glassfish-ejb-jar.xml is used. If no value is specified, a
           connection is made to the resource specified by the jndi-name
           subelement of the cmp-resource element in the glassfish-ejb-jar.xml
           file, and the database vendor name is read. If the connection
           cannot be established, or if the value is not recognized, SQL-92
           compliance is presumed.

       --createtables
           If specified as true, creates tables at deployment of an
           application with unmapped CMP beans. If specified as false, tables
           are not created. If not specified, the value of the
           create-tables-at-deploy entry in the cmp-resource element of the
           glassfish-ejb-jar.xml file determines whether or not tables are
           created. No unique constraints are created for the tables.

       --dropandcreatetables
           If specified as true when the component is redeployed, the tables
           created by the previous deployment are dropped before creating the
           new tables. Applies to deployed applications with unmapped CMP
           beans. Preexisting tables will not be dropped on the initial
           deployment of an application or on a deployment that follows an
           explicit undeploy. If specified as false, tables are neither
           dropped nor created. If not specified, the tables are dropped if
           the drop-tables-at-undeploy entry in the cmp-resource element of
           the glassfish-ejb-jar.xml file is set to true, and the new tables
           are created if the create-tables-at-deploy entry in the
           cmp-resource element of the glassfish-ejb-jar.xml file is set to
           true.

       --uniquetablenames
           Guarantees unique table names for all the beans and results in a
           hash code added to the table names. This is useful if you have an
           application with case-sensitive bean names. Applies to applications
           with unmapped CMP beans.

       --deploymentplan
           Deploys the deployment plan, which is a JAR file that contains
           GlassFish Server descriptors. Specify this option when deploying a
           pure EAR file. A pure EAR file is an EAR without GlassFish Server
           descriptors.

       --altdd
           Deploys the application using a Java EE standard deployment
           descriptor that resides outside of the application archive. Specify
           an absolute path or a relative path to the alternate deployment
           descriptor file. The alternate deployment descriptor overrides the
           top-level deployment descriptor packaged in the archive. For
           example, for an EAR, the use of --altdd overrides application.xml.
           For a standalone module, the use of --altdd overrides the top-level
           module descriptor such as web.xml.

       --runtimealtdd
           Deploys the application using a GlassFish Server runtime deployment
           descriptor that resides outside of the application archive. Specify
           an absolute path or a relative path to the alternate deployment
           descriptor file. The alternate deployment descriptor overrides the
           top-level deployment descriptor packaged in the archive. For
           example, for an EAR, the use of --runtimealtdd overrides
           glassfish-application.xml. For a standalone module, the use of
           --runtimealtdd overrides the top-level module descriptor such as
           glassfish-web.xml. Applies to GlassFish Server deployment
           descriptors only (glassfish-*.xml); the name of the alternate
           deployment descriptor file must begin with glassfish-. Does not
           apply to sun-*.xml deployment descriptors, which are deprecated.

       --deploymentorder
           Specifies the deployment order of the application. This is useful
           if the application has dependencies and must be loaded in a certain
           order at server startup. The deployment order is specified as an
           integer. The default value is 100. Applications with a lower number
           are loaded before applications with a higher number. For example,
           an application with a deployment order of 102 is loaded before an
           application with a deployment order of 110. If a deployment order
           is not specified, the default value of 100 is assigned. If two
           applications have the same deployment order, the first application
           to be deployed is the first application to be loaded at server
           startup.

           The deployment order is typically specified when the application is
           first deployed but can also be specified or changed after initial
           deployment using the set subcommand. You can view the deployment
           order of an application using the get subcommand

       --enabled
           Allows users to access the application. If set to false, users will
           not be able to access the application. This option enables the
           application on the specified target instance or cluster. If you
           deploy to the target domain, this option is ignored, since
           deploying to the domain doesn't deploy to a specific instance or
           cluster. The default is true.

       --generatermistubs
           If set to true, static RMI-IIOP stubs are generated and put into
           the client.jar. If set to false, the stubs are not generated.
           Default is false.

       --availabilityenabled
           This option controls whether high-availability is enabled for web
           sessions and for stateful session bean (SFSB) checkpointing and
           potentially passivation. If set to false (default) all web session
           saving and SFSB checkpointing is disabled for the specified
           application, web application, or EJB module. If set to true, the
           specified application or module is enabled for high-availability.
           Set this option to true only if high availability is configured and
           enabled at higher levels, such as the server and container levels.

       --asyncreplication
           This option controls whether web session and SFSB states for which
           high availability is enabled are first buffered and then replicated
           using a separate asynchronous thread. If set to true (default),
           performance is improved but availability is reduced. If the
           instance where states are buffered but not yet replicated fails,
           the states are lost. If set to false, performance is reduced but
           availability is guaranteed. States are not buffered but immediately
           transmitted to other instances in the cluster.

       --lbenabled
           This option controls whether the deployed application is available
           for load balancing. The default is true.

       --keepstate
           This option controls whether web sessions, SFSB instances, and
           persistently created EJB timers are retained between redeployments.

           The default is false. This option is supported only on the default
           server instance, named server. It is not supported and ignored for
           any other target.

           Some changes to an application between redeployments prevent this
           feature from working properly. For example, do not change the set
           of instance variables in the SFSB bean class.

           For web applications, this feature is applicable only if in the
           glassfish-web-app.xml file the persistence-type attribute of the
           session-manager element is file.

           For stateful session bean instances, the persistence type without
           high availability is set in the server (the sfsb-persistence-type
           attribute) and must be set to file, which is the default and
           recommended value.

           If any active web session, SFSB instance, or EJB timer fails to be
           preserved or restored, none of these will be available when the
           redeployment is complete. However, the redeployment continues and a
           warning is logged.

           To preserve active state data, GlassFish Server serializes the data
           and saves it in memory. To restore the data, the class loader of
           the newly redeployed application deserializes the data that was
           previously saved.

       --libraries
           A comma-separated list of library JAR files. Specify the library
           JAR files by their relative or absolute paths. Specify relative
           paths relative to domain-dir/lib/applibs. The libraries are made
           available to the application in the order specified.

       --target
           Specifies the target to which you are deploying. Valid values are:

           server
               Deploys the component to the default server instance server and
               is the default value.

           domain
               Deploys the component to the domain. If domain is the target
               for an initial deployment, the application is deployed to the
               domain, but no server instances or clusters reference the
               application. If domain is the target for a redeployment (the
               --force option is set to true), and dynamic reconfiguration is
               enabled for the clusters or server instances that reference the
               application, the referencing clusters or server instances
               automatically get the new version of the application. If
               redeploying, and dynamic configuration is disabled, the
               referencing clusters or server instances do not get the new
               version of the application until the clustered or standalone
               server instances are restarted.

           cluster_name
               Deploys the component to every server instance in the cluster.

           instance_name
               Deploys the component to a particular stand-alone server
               instance.

       --type
           The packaging archive type of the component that is being deployed.
           Possible values are as follows:

           car
               The component is packaged as a CAR file.

           ear
               The component is packaged as an EAR file.

           ejb
               The component is an EJB packaged as a JAR file.

           osgi
               The component is packaged as an OSGi bundle.

           rar
               The component is packaged as a RAR file.

           war
               The component is packaged as a WAR file.

       --properties or --property
           Optional keyword-value pairs that specify additional properties for
           the deployment. The available properties are determined by the
           implementation of the component that is being deployed or
           redeployed. The --properties option and the --property option are
           equivalent. You can use either option regardless of the number of
           properties that you specify.

           You can specify the following properties for a deployment:

           jar-signing-alias
               Specifies the alias for the security certificate with which the
               application client container JAR file is signed. Java Web Start
               will not run code that requires elevated permissions unless it
               resides in a JAR file signed with a certificate that the user's
               system trusts. For your convenience, GlassFish Server signs the
               JAR file automatically using the certificate with this alias
               from the domain's keystore. Java Web Start then asks the user
               whether to trust the code and displays the GlassFish Server
               certificate information. To sign this JAR file with a different
               certificate, add the certificate to the domain keystore, then
               use this property. For example, you can use a certificate from
               a trusted authority, which avoids the Java Web Start prompt, or
               from your own company, which users know they can trust. Default
               is s1as, the alias for the self-signed certificate created for
               every domain.

           java-web-start-enabled
               Specifies whether Java Web Start access is permitted for an
               application client module. Default is true.

           compatibility
               Specifies the GlassFish Server release with which to be
               backward compatible in terms of JAR visibility requirements for
               applications. The only allowed value is v2, which refers to Sun
               GlassFish Enterprise Server version 2 or Sun Java System
               Application Server version 9.1 or 9.1.1. The Java EE 6 platform
               specification imposes stricter requirements than Java EE 5 did
               on which JAR files can be visible to various modules within an
               EAR file. In particular, application clients must not have
               access to EJB JAR files or other JAR files in the EAR file
               unless references use the standard Java SE mechanisms
               (extensions, for example) or the Java EE library-directory
               mechanism. Setting this property to v2 removes these Java EE 6
               restrictions.

           keepSessions={false|true}
               Superseded by the --keepstate option.

               If the --force option is set to true, this property can by used
               to specify whether active sessions of the application that is
               being redeployed are preserved and then restored when the
               redeployment is complete. Applies to HTTP sessions in a web
               container. Default is false.

               false
                   Active sessions of the application are not preserved and
                   restored (default).

               true
                   Active sessions of the application are preserved and
                   restored.

                   If any active session of the application fails to be
                   preserved or restored, none of the sessions will be
                   available when the redeployment is complete. However, the
                   redeployment continues and a warning is logged.

                   To preserve active sessions, GlassFish Server serializes
                   the sessions and saves them in memory. To restore the
                   sessions, the class loader of the newly redeployed
                   application deserializes any sessions that were previously
                   saved.

           preserveAppScopedResources
               If set to true, preserves any application-scoped resources and
               restores them during redeployment. Default is false.

           Other available properties are determined by the implementation of
           the component that is being redeployed.

OPERANDS
       dirpath
           Path to the directory containing the exploded format of the
           deployable archive. This is the path to the directory on the server
           machine.

EXAMPLES
       Example 1, Deploying an Application From a Directory
           In this example, the exploded application to be deployed is in the
           /home/temp/sampleApp directory. Because the --force option is set
           to true, if an application of that name already exists, the
           application is redeployed.

               asadmin> deploydir --force=true --precompilejsp=true /home/temp/sampleApp
               Application deployed successfully with name sampleApp.
               WARNING : deploydir command deprecated. Please use deploy command instead.
               Command deploydir executed successfully

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       deploy(1), , redeploy(1), undeploy(1), get(1), set(1)

       asadmin(1M)

       Oracle GlassFish Server Application Deployment Guide

Java EE 7                         12 Feb 2013                     deploydir(1)
Command deploydir executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help export-http-lb-config [options] ...
export-http-lb-config(1) asadmin Utility Subcommands; export-http-lb-config(1)

NAME
       export-http-lb-config - exports the load balancer configuration or load
       balancer to a file

SYNOPSIS
           export-http-lb-config [--help] --config config_name | --lbname load_balancer_name [--target target] [--retrievefile=f
alse] [file_name]

DESCRIPTION
       The export-http-lb-config subcommand exports a load balancer
       configuration or load balancer into a file that the load balancer
       plug-in can use. The default file name is loadbalancer.xml, but you can
       specify a different name. Once exported, you manually copy the exported
       file to the load balancer plug-in location before configuration changes
       are applied. The --target option makes it possible to generate a
       loadbalancer.xml for clusters or standalone instances without having to
       manually create lb-config or load-balancer elements in the target's
       domain.xml.

       To apply changes to the load balancer without manually copying the
       configuration file, configure the load balancer to automatically apply
       changes with create-http-lb. If you use the create-http-lb subcommand,
       you do not need to use export-http-lb-config.

           Note
           +----------------------------------------+
           |           This subcommand is only      |
           |           applicable to Oracle         |
           |           GlassFish Server. This       |
           |           subcommand is not applicable |
           |           to GlassFish Server Open     |
           |           Source Edition.              |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --config
           Specifies which load balancer configuration to export.

           Specify either a load balancer configuration or a load balancer.
           Specifying both results in an error.

       --lbname
           Specifies the load balancer to export.

           Specify either a load balancer configuration or a load balancer.
           Specifying both results in an error.

       --retrievefile
           If set to true, retrieves the loadbalancer.xml file from the remote
           machine. The default is false.

       --target
           Specifies the target to which the load balancer configuration will
           be exported. If a target is not specified, the load balancer
           configuration is exported to the location specified with file_name.

OPERANDS
       file_name
           Specifies the file name and location of the exported configuration.

           *   If you specify a directory (relative or absolute) but not a
               file name, the file named
               loadbalancer.xml.load_balancer_config_name is created in the
               specified directory. On Microsoft Windows systems the path must
               be in quotes.

           *   If you specify a file name in a relative or absolute path, the
               file is created with the name you specify in the directory you
               specify.

           *   If you specify a file name but do not specify a directory, the
               file is created with that name in the current working
               directory.

           *   If you do not specify this operand, the default value is a file
               named loadbalancer.xml.load_balancer_config_name created in the
               domain-dir/generated directory.

       target
           Specifies the target to which the configuration will be exported.

           Valid values are:

           *   cluster_name- Specifies a cluster and its server instances.

           *   stand-alone_instance_name- Specifies a specific server
               instance.

EXAMPLES
       Example 1, Exporting a Load Balancer Configuration on UNIX
           The following example exports a load balancing configuration named
           mycluster-http-lb-config to a file named loadbalancer.xml in the
           /Sun/AppServer directory .

               asadmin> export-http-lb-config --config mycluster-http-lb-config /Sun/AppServer/loadbalancer.xml
               Command export-http-lb-config executed successfully.

       Example 2, Exporting a Load Balancer Configuration on Windows
           The following example exports a load balancing configuration named
           mycluster-http-lb-config to a file named loadbalancer.xml in the
           C:\Sun\AppServer directory on a Microsoft Windows system.

               asadmin> export-http-lb-config --config mycluster-http-lb-config "C:\Sun\AppServer\loadbalancer.xml"
               Command export-http-lb-config executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-http-lb(1), create-http-lb-config(1), list-http-lb-configs(1)

       asadmin(1M)

Java EE 7                         26 Aug 2010         export-http-lb-config(1)
Command export-http-lb-config executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help get [options] ...
get(1)                    asadmin Utility Subcommands                   get(1)

NAME
       get - gets the values of configurable or monitorable attributes

SYNOPSIS
           get [--help]
           [--monitor[={true|false}]]
           [--aggregatedataonly[={true|false}]]
           (dotted-attribute--name)+

DESCRIPTION
       The get subcommand uses dotted names to get the names and values of
       configurable or monitorable attributes for GlassFish Server elements.

       You can use the list(1) subcommand to display the dotted names that
       represent individual server components and subsystems. For example, a
       dotted name might be server.applications.web-module. Attributes from
       the monitoring hierarchy are read-only, but configuration attributes
       can be modified using the set(1) subcommand. For more detailed
       information on dotted names, see the dotted-names(5ASC) help page.

           Note
           +----------------------------------------+
           |           Characters that have special |
           |           meaning to the shell or      |
           |           command interpreter, such as |
           |           * (asterisk), should be      |
           |           quoted or escaped as         |
           |           appropriate to the shell,    |
           |           for example, by enclosing    |
           |           the argument in quotes. In   |
           |           multimode, quotes are needed |
           |           only for arguments that      |
           |           include spaces, quotes, or   |
           |           backslash.                   |
           +----------------------------------------+

       The following list shows common usage of the get subcommand with the *
       (asterisk):

       get * or get *.*
           Gets all values on all dotted name prefixes.

       get domain* or get domain*.*
           Gets all values on the dotted names that begin with domain.

       get *config*.*.*
           Gets all values on the dotted names that match *config*.*.

       get domain.j2ee-applications.*.ejb-module.*.*
           Gets all values on all EJB modules of all applications.

       get *web-modules.*.*
           Gets all values on all web modules whether in an application or
           standalone.

       get *.*.*.*
           Gets all values on all dotted names that have four parts.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --monitor, -m
           Defaults to false. If set to false, the configurable attribute
           values are returned. If set to true, the monitorable attribute
           values are returned.

       --aggregatedataonly, -c
           Aggregates monitoring data for all GlassFish Server instances in a
           cluster. The default value is false.

OPERANDS
       dotted-attribute-name
           Identifies the attribute name in the dotted notation. At least one
           dotted name attribute is required. The dotted notation is the
           syntax used to access attributes of configurable entities.

EXAMPLES
       Example 1, Getting the Attributes of a Configurable Element
           This example gets the attributes of listener.http-listener-1.

               asadmin> get server.http-service.http-listener.http-listener-1.*
               server.http-service.http-listener.http-listener-1.acceptor-threads = 1
               server.http-service.http-listener.http-listener-1.address = 0.0.0.0
               server.http-service.http-listener.http-listener-1.blocking-enabled = false
               server.http-service.http-listener.http-listener-1.default-virtual-server = server
               server.http-service.http-listener.http-listener-1.enabled = true
               server.http-service.http-listener.http-listener-1.external-port =
               server.http-service.http-listener.http-listener-1.family = inet
               server.http-service.http-listener.http-listener-1.id = http-listener-1
               server.http-service.http-listener.http-listener-1.port = 8080
               server.http-service.http-listener.http-listener-1.redirect-port =
               server.http-service.http-listener.http-listener-1.security-enabled = false
               server.http-service.http-listener.http-listener-1.server-name =
               server.http-service.http-listener.http-listener-1.xpowered-by = true
               Command get executed successfully.

       Example 2, Getting Monitorable Objects
           This example gets the configuration attributes for setting the
           monitoring level and shows whether they are enabled (LOW or HIGH)
           or disabled (OFF). The jvm component is enabled for monitoring.

               asadmin> get server.monitoring-service.module-monitoring-levels.*
               server.monitoring-service.module-monitoring-levels.connector-connection-pool=OFF
               server.monitoring-service.module-monitoring-levels.connector-service=OFF
               server.monitoring-service.module-monitoring-levels.d-trace=OFF
               server.monitoring-service.module-monitoring-levels.ejb-container=OFF
               server.monitoring-service.module-monitoring-levels.http-service=OFF
               server.monitoring-service.module-monitoring-levels.jdbc-connection-pool=OFF
               server.monitoring-service.module-monitoring-levels.jms-service=OFF
               server.monitoring-service.module-monitoring-levels.jvm=HIGH
               server.monitoring-service.module-monitoring-levels.orb=OFF
               server.monitoring-service.module-monitoring-levels.thread-pool=OFF
               server.monitoring-service.module-monitoring-levels.transaction-service=OFF
               server.monitoring-service.module-monitoring-levels.web-container=OFF
               Command get executed successfully.

       Example 3, Getting Attributes and Values for a Monitorable Object
           This example gets all attributes and values of the jvm monitorable
           object.

               asadmin> get --monitor server.jvm.*
               server.jvm.HeapSize_Current = 45490176
               server.jvm.HeapSize_Description = Describes JvmHeapSize
               server.jvm.HeapSize_HighWaterMark = 45490176
               server.jvm.HeapSize_LastSampleTime = 1063217002433
               server.jvm.HeapSize_LowWaterMark = 0
               server.jvm.HeapSize_LowerBound = 0
               server.jvm.HeapSize_Name = JvmHeapSize
               server.jvm.HeapSize_StartTime = 1063238840055
               server.jvm.HeapSize_Unit = bytes
               server.jvm.HeapSize_UpperBound = 531628032
               server.jvm.UpTime_Count = 1063238840100
               server.jvm.UpTime_Description = Describes JvmUpTime
               server.jvm.UpTime_LastSampleTime = 1-63238840070
               server.jvm.UpTime_Name = JvmUpTime
               server.jvm.UpTime_StartTime = 1063217002430
               server.jvm.UpTime_Unit = milliseconds
               Command get executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       list(1), set(1)

       dotted-names(5ASC)

       asadmin(1M)

       Oracle GlassFish Server Administration Guide

Java EE 7                         12 Feb 2013                           get(1)
Command get executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-domains [options] ...
list-domains(1)           asadmin Utility Subcommands          list-domains(1)

NAME
       list-domains - lists the domains in the specified directory

SYNOPSIS
           list-domains [--help]
           [--domaindir domaindir]
           [--long[={false|true}]]
           [--header[={false|true}]]

DESCRIPTION
       The list-domains subcommand lists the domains in the specified domains
       directory. If the domains directory is not specified, the domains in
       the default directory are listed. If there is more that one domains
       directory, the --domaindir option must be specified. The status of each
       domain is included.

       This subcommand is supported in local mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --domaindir
           The directory where the domains are to be listed. If specified, the
           path must be accessible in the files stem. If not specified, the
           domains in the domain root directory are listed. The default
           location of the domain root directory is as-install/domains.

       --long, -l
           Displays detailed information about the administration servers in
           the listed domains, including host names and port numbers. The
           default value is false.

       --header, -h
           Specifies whether a header is displayed when the --long option is
           used. The default value is true. To suppress the header, set the
           --header option to false.

EXAMPLES
       Example 1, Listing Domains
           This example lists the domains in the default directory.

               asadmin> list-domains
               Name: domain1 Status: Running
               Name: domain2 Status: Not running
               Name: domain4 Status: Running, restart required to apply configuration changes
               Command list-domains executed successfully

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-domain(1), delete-domain(1), start-domain(1), stop-domain(1),

       asadmin(1M)

Java EE 7                         12 Feb 2013                  list-domains(1)
Command list-domains executed successfully.

domain1 running
Command list-domains executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-http-lbs [options] ...
NAME
     list-http-lbs

SYNOPSIS
     Usage: list-http-lbs [--output=output] [--long=false] [--hea
     der=true] [name] 

OPTIONS
     --output
      -o

     --long
      -l

     --header
      -h

OPERANDS
     name
Command list-http-lbs executed successfully.

Command list-http-lbs executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-secure-admin-internal-users [options] ...
list-secure-admin-internalasadmin1Utility Slist-secure-admin-internal-users(1)

NAME
       list-secure-admin-internal-users - lists the user names that the
       GlassFish Server DAS and instances use to authenticate with each other
       and to authorize admin operations.

SYNOPSIS
           list-secure-admin-internal-users [--help]
           [--long[={false|true}]]
           [--output output]
           [--header[={false|true}]]
           [name]

DESCRIPTION
       The list-secure-admin-internal-users subcommand lists the user names
       that the GlassFish Server DAS and instances use to authenticate with
       each other and to authorize admin operations.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Displays detailed information about each internal user. The default
           value is false.

       --output, -o
           Displays specific details about each internal user. Use a
           comma-separated list to specify the details you want to display and
           their order. The values are case-insensitive.

           Possible values are as follows:

           username
               Displays the user name for the internal user.

           password-alias
               Displays the password alias for the internal user.

       --header, -h
           Specifies whether column headings are displayed when the --long
           option is used. The default value is true. To suppress the
           headings, set the --header option to false.

OPERANDS
       name
           The user name for the internal user for which you want to display
           details.

EXAMPLES
       Example 1, List the user name for secure admin
           The following example lists the user names that the GlassFish
           Server DAS and instances use to authenticate with each other and to
           authorize admin operations.

               asadmin> list-secure-admin-internal-users

               Command list-secure-admin-internal-users executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       enable-secure-admin(1)

       enable-secure-admin-internal-user(1)

       asadmin(1M)

Java EE 7                         13 Feb 20list-secure-admin-internal-users(1)
Command list-secure-admin-internal-users executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help list-secure-admin-principals [options] ...
list-secure-admin-principaasadmin Utility Subcolist-secure-admin-principals(1)

NAME
       list-secure-admin-principals - lists the certificates for which
       GlassFish Server accepts admin requests from clients.

SYNOPSIS
           list-secure-admin-principals [--help]
           [--long[={false|true}]]
           [--output output]
           [--header[={false|true}]]
           [name]

DESCRIPTION
       The list-secure-admin-principals subcommand lists the certificates for
       which GlassFish Server accepts admin requests from clients.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --long, -l
           Displays detailed information about the certificates for which
           GlassFish Server accepts admin requests from clients. The default
           value is false.

       --output, -o
           Displays specific details about the certificates for which
           GlassFish Server accepts admin requests from clients. Use a
           comma-separated list to specify the details you want to display and
           their order. The values are case-insensitive.

           Possible values are as follows:

           DN
               Displays the distinguished name (DN) of each certificate.

       --header, -h
           Specifies whether column headings are displayed when the --long
           option is used. The default value is true. To suppress the
           headings, set the --header option to false.

OPERANDS
       name
           The distinguished name of the certificate, specified as a
           comma-separated list in quotes. For example:
           "CN=system.amer.oracle.com,OU=GlassFish,O=Oracle
           Corporation,L=Santa Clara,ST=California,C=US".

EXAMPLES
       Example 1, List the certificates
           The following example shows how to list the certificates for which
           GlassFish Server accepts admin requests from clients.

               asadmin> list-secure-admin-principals
               CN=localhost,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US
               CN=localhost-instance,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US
               Command list-secure-admin-principals executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       enable-secure-admin(1)

       enable-secure-admin-principal(1)

       asadmin(1M)

Java EE 7                         13 Feb 2013  list-secure-admin-principals(1)
Command list-secure-admin-principals executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help login [options] ...
login(1)                  asadmin Utility Subcommands                 login(1)

NAME
       login - logs you into a domain

SYNOPSIS
           login [--help]

DESCRIPTION
       The purpose of the login subcommand is to ease domain administration by
       letting you log into a particular domain. If GlassFish Server domains
       are created on various machines (locally), you can run the asadmin
       utility from any of these machines and manage domains located elsewhere
       (remotely). This is especially useful when a particular machine is
       chosen as an administration client that manages multiple domains and
       servers.

       The login subcommand prompts you for the administrator user name and
       password. After successful login, the .asadminpass file is created in
       your home directory. (This is the same file that is modified when you
       run the create-domain subcommand with the --savelogin option.) The
       literal host name is stored, and no resolution with the DNS is
       attempted. If a domain is being administered from other machines, it is
       sufficient to run the login subcommand once. You do not need to specify
       the asadmin utility options --user and --passwordfile when you run
       additional remote subcommands on that domain. After you have logged
       into a domain, you still need to provide the host and port for any
       subsequent remote subcommands unless you chose the default values for
       --host (localhost) and --port (4848) options.

       Subsequent use of same subcommand with the same parameters will result
       in overwriting the contents of the .asadminpass file for the given
       administration host and port. You can decide to overwrite the file or
       to reject such a login.

       Login information is saved permanently and can be used across multiple
       domain restarts.

       There is no logout subcommand. If you want to log in to another domain,
       run the login subcommand and specify new values for the asadmin utility
       options --host and --port.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

EXAMPLES
       Example 1, Logging Into a Domain on a Remote Machine
           This example logs into a domain located on another machine. Options
           are specified before the login subcommand.

               asadmin --host foo --port 8282 login
               Please enter the admin user name>admin
               Please enter the admin password>

               Trying to authenticate for administration of server at host [foo]
               and port [8282] ...
               Login information relevant to admin user name [admin] for host [foo]
               and admin port [8282] stored at [/.asadminpass] successfully.
               Make sure that this file remains protected. Information stored in this
               file will be used by asadmin commands to manage associated domain.

       Example 2, Logging Into a Domain on the Default Port of Localhost
           This example logs into a domain on mylhost on the default port.
           Options are specified before the login subcommand.

               asadmin --host myhost login
               Please enter the admin user name>admin
               Please enter the admin password>
               Trying to authenticate for administration of server
               at host [myhost] and port [4848] ...
               An entry for login exists for host [myhost] and port [4848], probably
               from an earlier login operation.
               Do you want to overwrite this entry (y/n)?y
               Login information relevant to admin user name [admin] for host [myhost]
               and admin port [4848] stored at [/home/joe/.asadminpass] successfully.
               Make sure that this file remains protected. Information stored in this
               file will be used by asadmin commands to manage associated domain.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-domain(1), delete-domain(1)

       asadmin(1M)

Java EE 7                         9 Oct 2009                          login(1)
Command login executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help redeploy [options] ...
redeploy(1)               asadmin Utility Subcommands              redeploy(1)

NAME
       redeploy - redeploys the specified component

SYNOPSIS
           redeploy [--help]
           --name component_name
           [--upload={true|false}]
           [--retrieve local_dirpath]
           [--dbvendorname dbvendorname]
           [--createtables={true|false}|--dropandcreatetables={true|false}]
           [--uniquetablenames={true|false}]
           [--deploymentplan deployment_plan]
           [--altdd alternate_deploymentdescriptor]
           [--runtimealtdd runtime_alternate_deploymentdescriptor]
           [--deploymentorder deployment_order]
           [--enabled={true|false}]
           [--generatermistubs={false|true}]
           [--contextroot context_root]
           [--precompilejsp={true|false}]
           [--verify={false|true}]
           [--virtualservers virtual_servers]
           [--availabilityenabled={false|true}]
           [--asyncreplication={true|false}]
           [--lbenabled={true|false}]
           [--keepstate={false|true}]
           [--libraries jar_file[,jar_file]*]
           [--target target]
           [--type pkg-type]
           [--properties(name=value)[:name=value]*]
           [file_archive|filepath]

DESCRIPTION
       The redeploy subcommand redeploys an enterprise application, web
       application, module based on the Enterprise JavaBeans ( EJB)
       specification (EJB module), connector module, or application client
       module that is already deployed or already exists. The redeploy
       subcommand preserves the settings and other options with which the
       application was originally deployed. The application must already be
       deployed. Otherwise, an error occurs.

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --virtualservers
           One or more virtual server IDs. Multiple IDs are separated by
           commas.

       --contextroot
           Valid only if the archive is a web module. It is ignored for other
           archive types; defaults to filename without extension.

       --precompilejsp
           By default this option does not allow the JSP to be precompiled
           during deployment. Instead, JSPs are compiled during runtime.
           Default is false.

       --verify
           If set to true and the required verifier packages are installed
           from the Update Tool, the syntax and semantics of the deployment
           descriptor is verified. Default is false.

       --name
           Name of the deployable component.

           The name can include an optional version identifier, which follows
           the name and is separated from the name by a colon (:). The version
           identifier must begin with a letter or number. It can contain
           alphanumeric characters plus underscore (_), dash (-), and period
           (.) characters. For more information about module and application
           versions, see "Module and Application Versions" in Oracle GlassFish
           Server Application Deployment Guide.

       --upload
           Specifies whether the subcommand uploads the file to the DAS. In
           most situations, this option can be omitted.

           Valid values are as follows:

           false
               The subcommand does not upload the file and attempts to access
               the file through the specified file name. If the DAS cannot
               access the file, the subcommand fails.

               For example, the DAS might be running as a different user than
               the administration user and does not have read access to the
               file. In this situation, the subcommand fails if the --upload
               option is false.

           true
               The subcommand uploads the file to the DAS over the network
               connection.

           The default value depends on whether the DAS is on the host where
           the subcommand is run or is on a remote host.

           *   If the DAS is on the host where the subcommand is run, the
               default is false.

           *   If the DAS is on a remote host, the default is true.

           If a directory filepath is specified, this option is ignored.

       --retrieve
           Retrieves the client stub JAR file from the server machine to the
           local directory.

       --dbvendorname
           Specifies the name of the database vendor for which tables are
           created. Supported values include db2, mssql, oracle, derby,
           javadb, postgresql, and sybase, case-insensitive. If not specified,
           the value of the database-vendor-name attribute in
           glassfish-ejb-jar.xml is used. If no value is specified, a
           connection is made to the resource specified by the jndi-name
           subelement of the cmp-resource element in the glassfish-ejb-jar.xml
           file, and the database vendor name is read. If the connection
           cannot be established, or if the value is not recognized, SQL-92
           compliance is presumed.

       --createtables
           If specified as true, creates tables at deployment of an
           application with unmapped CMP beans. If specified as false, tables
           are not created. If not specified, the value of the
           create-tables-at-deploy entry in the cmp-resource element of the
           glassfish-ejb-jar.xml file determines whether or not tables are
           created. No unique constraints are created for the tables.

       --dropandcreatetables
           If specified as true when the component is redeployed, the tables
           created by the previous deployment are dropped before creating the
           new tables. Applies to deployed applications with unmapped CMP
           beans. If specified as false, tables are neither dropped nor
           created. If not specified, the tables are dropped if the
           drop-tables-at-undeploy entry in the cmp-resource element of the
           glassfish-ejb-jar.xml file is set to true, and the new tables are
           created if the create-tables-at-deploy entry in the cmp-resource
           element of the glassfish-ejb-jar.xml file is set to true.

       --uniquetablenames
           Guarantees unique table names for all the beans and results in a
           hash code added to the table names. This is useful if you have an
           application with case-sensitive bean names. Applies to applications
           with unmapped CMP beans.

       --deploymentplan
           Deploys the deployment plan, which is a JAR file that contains
           GlassFish Server descriptors. Specify this option when deploying a
           pure EAR file. A pure EAR file is an EAR without GlassFish Server
           descriptors.

       --altdd
           Deploys the application using a Java EE standard deployment
           descriptor that resides outside of the application archive. Specify
           an absolute path or a relative path to the alternate deployment
           descriptor file. The alternate deployment descriptor overrides the
           top-level deployment descriptor packaged in the archive. For
           example, for an EAR, the use of --altdd overrides application.xml.
           For a standalone module, the use of --altdd overrides the top-level
           module descriptor such as web.xml.

       --runtimealtdd
           Deploys the application using a GlassFish Server runtime deployment
           descriptor that resides outside of the application archive. Specify
           an absolute path or a relative path to the alternate deployment
           descriptor file. The alternate deployment descriptor overrides the
           top-level deployment descriptor packaged in the archive. For
           example, for an EAR, the use of --runtimealtdd overrides
           glassfish-application.xml. For a standalone module, the use of
           --runtimealtdd overrides the top-level module descriptor such as
           glassfish-web.xml. Applies to GlassFish Server deployment
           descriptors only (glassfish-*.xml); the name of the alternate
           deployment descriptor file must begin with glassfish-. Does not
           apply to sun-*.xml deployment descriptors, which are deprecated.

       --deploymentorder
           Specifies the deployment order of the application. This is useful
           if the application has dependencies and must be loaded in a certain
           order at server startup. The deployment order is specified as an
           integer. The default value is 100. Applications with a lower number
           are loaded before applications with a higher number. For example,
           an application with a deployment order of 102 is loaded before an
           application with a deployment order of 110. If a deployment order
           is not specified, the default value of 100 is assigned. If two
           applications have the same deployment order, the first application
           to be deployed is the first application to be loaded at server
           startup.

           The deployment order is typically specified when the application is
           first deployed but can also be specified or changed after initial
           deployment using the set subcommand. You can view the deployment
           order of an application using the get subcommand.

       --enabled
           Allows users to access the application. If set to false, users will
           not be able to access the application. This option enables the
           application on the specified target instance or cluster. If you
           deploy to the target domain, this option is ignored, since
           deploying to the domain doesn't deploy to a specific instance or
           cluster. The default is true.

       --generatermistubs
           If set to true, static RMI-IIOP stubs are generated and put into
           the client.jar. If set to false, the stubs are not generated.
           Default is false.

       --availabilityenabled
           This option controls whether high-availability is enabled for web
           sessions and for stateful session bean (SFSB) checkpointing and
           potentially passivation. If set to false (default) all web session
           saving and SFSB checkpointing is disabled for the specified
           application, web application, or EJB module. If set to true, the
           specified application or module is enabled for high-availability.
           Set this option to true only if high availability is configured and
           enabled at higher levels, such as the server and container levels.

       --asyncreplication
           This option controls whether web session and SFSB states for which
           high availability is enabled are first buffered and then replicated
           using a separate asynchronous thread. If set to true (default),
           performance is improved but availability is reduced. If the
           instance where states are buffered but not yet replicated fails,
           the states are lost. If set to false, performance is reduced but
           availability is guaranteed. States are not buffered but immediately
           transmitted to other instances in the cluster.

       --lbenabled
           This option controls whether the deployed application is available
           for load balancing. The default is true.

       --keepstate
           This option controls whether web sessions, SFSB instances, and
           persistently created EJB timers are retained between redeployments.

           The default is false. This option is supported only on the default
           server instance, named server. It is not supported and ignored for
           any other target.

           Some changes to an application between redeployments prevent this
           feature from working properly. For example, do not change the set
           of instance variables in the SFSB bean class.

           For web applications, this feature is applicable only if in the
           glassfish-web-app.xml file the persistence-type attribute of the
           session-manager element is file.

           For stateful session bean instances, the persistence type without
           high availability is set in the server (the sfsb-persistence-type
           attribute) and must be set to file, which is the default and
           recommended value.

           If any active web session, SFSB instance, or EJB timer fails to be
           preserved or restored, none of these will be available when the
           redeployment is complete. However, the redeployment continues and a
           warning is logged.

           To preserve active state data, GlassFish Server serializes the data
           and saves it in memory. To restore the data, the class loader of
           the newly redeployed application deserializes the data that was
           previously saved.

       --libraries
           A comma-separated list of library JAR files. Specify the library
           JAR files by their relative or absolute paths. Specify relative
           paths relative to domain-dir/lib/applibs. The libraries are made
           available to the application in the order specified.

       --target
           Specifies the target to which you are deploying. Valid values are:

           server
               Deploys the component to the default server instance server and
               is the default value.

           domain
               Deploys the component to the domain. If domain is the target
               for an initial deployment, the application is deployed to the
               domain, but no server instances or clusters reference the
               application. If domain is the target for a redeployment, and
               dynamic reconfiguration is enabled for the clusters or server
               instances that reference the application, the referencing
               clusters or server instances automatically get the new version
               of the application. If redeploying, and dynamic configuration
               is disabled, the referencing clusters or server instances do
               not get the new version of the application until the clustered
               or standalone server instances are restarted.

           cluster_name
               Deploys the component to every server instance in the cluster.

           instance_name
               Deploys the component to a particular stand-alone server
               instance.

       --type
           The packaging archive type of the component that is being deployed.
           Possible values are as follows:

           car
               The component is packaged as a CAR file.

           ear
               The component is packaged as an EAR file.

           ejb
               The component is an EJB packaged as a JAR file.

           osgi
               The component is packaged as an OSGi bundle.

           rar
               The component is packaged as a RAR file.

           war
               The component is packaged as a WAR file.

       --properties or --property
           Optional keyword-value pairs that specify additional properties for
           the deployment. The available properties are determined by the
           implementation of the component that is being deployed or
           redeployed. The --properties option and the --property option are
           equivalent. You can use either option regardless of the number of
           properties that you specify.

           You can specify the following properties for a deployment:

           jar-signing-alias
               Specifies the alias for the security certificate with which the
               application client container JAR file is signed. Java Web Start
               will not run code that requires elevated permissions unless it
               resides in a JAR file signed with a certificate that the user's
               system trusts. For your convenience, GlassFish Server signs the
               JAR file automatically using the certificate with this alias
               from the domain's keystore. Java Web Start then asks the user
               whether to trust the code and displays the GlassFish Server
               certificate information. To sign this JAR file with a different
               certificate, add the certificate to the domain keystore, then
               use this property. For example, you can use a certificate from
               a trusted authority, which avoids the Java Web Start prompt, or
               from your own company, which users know they can trust. Default
               is s1as, the alias for the self-signed certificate created for
               every domain.

           java-web-start-enabled
               Specifies whether Java Web Start access is permitted for an
               application client module. Default is true.

           compatibility
               Specifies the GlassFish Server release with which to be
               backward compatible in terms of JAR visibility requirements for
               applications. The only allowed value is v2, which refers to Sun
               Java System Application Server version 2 or Sun Java System
               Application Server version 9.1 or 9.1.1. The Java EE 6 platform
               specification imposes stricter requirements than Java EE 5 did
               on which JAR files can be visible to various modules within an
               EAR file. In particular, application clients must not have
               access to EJB JAR files or other JAR files in the EAR file
               unless references use the standard Java SE mechanisms
               (extensions, for example) or the Java EE library-directory
               mechanism. Setting this property to v2 removes these Java EE 6
               restrictions.

           keepSessions={false|true}
               Superseded by the --keepstate option.

               This property can by used to specify whether active sessions of
               the application that is being redeployed are preserved and then
               restored when the redeployment is complete. Applies to HTTP
               sessions in a web container. Default is false.

               false
                   Active sessions of the application are not preserved and
                   restored (default).

               true
                   Active sessions of the application are preserved and
                   restored.

                   If any active session of the application fails to be
                   preserved or restored, none of the sessions will be
                   available when the redeployment is complete. However, the
                   redeployment continues and a warning is logged.

                   To preserve active sessions, GlassFish Server serializes
                   the sessions and saves them in memory. To restore the
                   sessions, the class loader of the newly redeployed
                   application deserializes any sessions that were previously
                   saved.

           preserveAppScopedResources
               If set to true, preserves any application-scoped resources and
               restores them during redeployment. Default is false.

           Other available properties are determined by the implementation of
           the component that is being redeployed.

OPERANDS
       file_archive|filepath
           The path to the archive that contains the application that is being
           redeployed. This path can be a relative path or an absolute path.

           The archive can be in either of the following formats:

           *   An archive file, for example, /export/JEE_apps/hello.war.

               If the --upload option is set to true, this is the path to the
               deployable file on the local client machine. If the --upload
               option is set to false, this is the absolute path to the file
               on the server machine.

           *   A directory that contains the exploded format of the deployable
               archive. This is the absolute path to the directory on the
               server machine.

               If you specify a directory, the --upload option is ignored.

           Whether this operand is required depends on how the application was
           originally deployed:

           *   If the application was originally deployed from a file, the
               archive-path operand is required. The operand must specify an
               archive file.

           *   If the application was originally deployed from a directory,
               the archive-path operand is optional.

               The operand can specify a directory or an archive file.

EXAMPLES
       Example 1, Redeploying a Web Application From a File
           This example redeploys the web application hello from the hello.war
           file in the current working directory. The application was
           originally deployed from a file. Active sessions of the application
           are to be preserved and then restored when the redeployment is
           complete.

               asadmin> redeploy --name hello --properties keepSessions=true hello.war
               Application deployed successfully with name hello.
               Command redeploy executed successfully

       Example 2, Redeploying a Web Application From a Directory
           This example redeploys the web application hellodir. The
           application was originally deployed from a directory.

               asadmin> redeploy --name hellodir
               Application deployed successfully with name hellodir.
               Command redeploy executed successfully

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       deploy(1), undeploy(1), list-components(1), get(1), set(1)

       asadmin(1M)

       Oracle GlassFish Server Application Deployment Guide

Java EE 7                         12 Feb 2013                      redeploy(1)
Command redeploy executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help start-domain [options] ...
start-domain(1)           asadmin Utility Subcommands          start-domain(1)

NAME
       start-domain - starts the DAS of the specified domain

SYNOPSIS
           start-domain [--help]
           [--debug={true|false}] [--domaindir domain-dir]
           [--dry-run={true|false}] [--upgrade={true|false}]
           [--verbose={true|false}] [--watchdog={true|false}]
           [domain-name]

DESCRIPTION
       The start-domain subcommand starts the domain administration server
       (DAS) of the specified domain. If a domain is not specified, the
       default domain is assumed. If the domains directory contains two or
       more domains, the domain-name operand must be specified.

           Note
           +----------------------------------------+
           |           On the Windows platform,     |
           |           processes can bind to the    |
           |           same port. To avoid this     |
           |           problem, do not start        |
           |           multiple domains with the    |
           |           same port number at the same |
           |           time.                        |
           +----------------------------------------+

       This subcommand is supported in local mode only.

           Note
           +----------------------------------------+
           |           In Oracle GlassFish Server,  |
           |           the start-domain subcommand  |
           |           prompts for a new admin user |
           |           password if no password has  |
           |           been set for the admin user. |
           |           Additionally, the admin user |
           |           password must not be blank   |
           |           if secure administration is  |
           |           enabled; otherwise, the      |
           |           start-domain subcommand      |
           |           fails.                       |
           |           To provide the new admin     |
           |           user password, you can use   |
           |           the --passwordfile utility   |
           |           option of the asadmin(1M)    |
           |           command after adding the     |
           |           entry AS_ADMIN_NEWPASSWORD   |
           |           to the password file.        |
           +----------------------------------------+

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --debug
           Specifies whether the domain is started with Java Platform Debugger
           Architecture (JPDA)

           (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

           debugging enabled.

           Possible values are as follows:

           true
               The instance is started with JPDA debugging enabled and the
               port number for JPDA debugging is displayed.

           false
               The instance is started with JPDA debugging disabled (default).

       --dry-run, -n
           Suppresses actual starting of the domain. Instead, start-domain
           displays the full java command that would be used to start the
           domain, including all options. Reviewing this command can be useful
           to confirm JVM options and when troubleshooting startup issues.

           The default value is false.

       --domaindir
           The domain root directory, which contains the directory of the
           domain that is to be restarted. If specified, the path must be
           accessible in the file system. The default location of the domain
           root directory is as-install/domains.

       --upgrade
           Specifies whether the configuration of the domain administration
           server (DAS) is upgraded to the current release. Normally, if the
           subcommand detects that the configuration is from an older release
           of GlassFish Server, the configuration is upgraded automatically
           before being started. You should not need to use this option
           explicitly.

           Possible values are as follows:

           true
               When the domain is started, the configuration is modified to be
               compatible with this release of GlassFish Server, and the
               GlassFish Server process stops.

           false
               The configuration of the DAS is not updated (default).

       --verbose, -v
           Specifies whether detailed information about the domain is
           displayed in the console window where the subcommand is run.

           Possible values are as follows:

           true
               Detailed startup messages and log messages about the domain are
               displayed in the console window where the subcommand is run. If
               the domain is later restarted by running the restart-domain(1)
               subcommand from a different console window, messages continue
               to be displayed in the original console window.

               You can kill the GlassFish Server process by typing CTRL-C in
               the console window.

               You can kill the GlassFish Server process and obtain a thread
               dump for the server by typing one of the following key
               combinations in the console window:

               *   CTRL-\ on UNIX systems

               *   CTRL-Break on Windows systems

           false
               Detailed information is not displayed (default).

       --watchdog, -w
           Specifies whether limited information about the domain is displayed
           in the console window where the subcommand is run. The --watchdog
           option is similar to --verbose but does not display the detailed
           startup messages and log messages. This option is useful when
           running the asadmin utility in the background or with no attached
           console.

           Possible values are as follows:

           true
               Limited information is displayed in the console window.

           false
               Limited information is not displayed in the console window
               (default).

OPERANDS
       domain-name
           The unique name of the domain you want to start.

           This operand is optional if only one domain exists in the GlassFish
           Server installation.

EXAMPLES
       Example 1, Starting a Domain
           This example starts mydomain4 in the default domains directory.

               asadmin> start-domain mydomain4
               Waiting for DAS to start. ...........
               Started domain: mydomain4
               Domain location: /myhome/glassfishv3/glassfish/domains/mydomain4
               Log file: /myhome/glassfishv3/glassfish/domains/mydomain4/logs/server.log
               Admin port for the domain: 4848
               Command start-domain executed successfully.

EXIT STATUS
       0
           subcommand executed successfully

       1
           error in executing the subcommand

SEE ALSO
       create-domain(1), delete-domain(1), list-domains(1), restart-domain(1),
       stop-domain(1)

       asadmin(1M)

       Java Platform Debugger Architecture (JPDA)
       (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

Java EE 7                         13 Feb 2013                  start-domain(1)
Command start-domain executed successfully.

Command delete-cluster executed successfully.

Deprecated syntax, instead use:
asadmin --user admin --passwordfile asadminpass --help start-local-instance [options] ...
start-local-instance(1)   asadmin Utility Subcommands  start-local-instance(1)

NAME
       start-local-instance - starts a GlassFish Server instance on the host
       where the subcommand is run

SYNOPSIS
           start-local-instance [--help]
           [--nodedir node-dir] [--node node]
           [--debug={false|true}] [--dry-run={false|true}] [--sync={normal|full|none}]
           [--verbose={false|true}] [--watchdog={false|true}]
           [instance-name]

DESCRIPTION
       The start-local-instance subcommand starts a GlassFish Server instance
       on the host where the subcommand is run. This subcommand does not
       require the Distributed Component Object Model (DCOM) remote protocol
       or secure shell (SSH) to be configured. You must run this command from
       the host where the instance resides.

       The subcommand can start any GlassFish Server instance, regardless of
       how the instance was created. For example, this subcommand can start an
       instance that was created by using the create-instance(1) subcommand.

       The start-local-instance subcommand does not contact the domain
       administration server (DAS) to determine the node on which the instance
       resides. To determine the node on which the instance resides, the
       subcommand searches the directory that contains the node directories.
       If multiple node directories exist, the node must be specified as an
       option of the subcommand.

       This subcommand is supported in local mode. However, to synchronize the
       instance with the DAS, this subcommand must be run in remote mode.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

       --nodedir
           Specifies the directory that contains the instance's node
           directory. The instance's files are stored in the instance's node
           directory. The default is as-install/nodes.

       --node
           Specifies the node on which the instance resides. This option may
           be omitted only if the directory that the --nodedir option
           specifies contains only one node directory. Otherwise, this option
           is required.

       --debug
           Specifies whether the instance is started with Java Platform
           Debugger Architecture (JPDA)

           (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

           debugging enabled.

           Possible values are as follows:

           true
               The instance is started with JPDA debugging enabled and the
               port number for JPDA debugging is displayed.

           false
               The instance is started with JPDA debugging disabled (default).

       --dry-run, -n
           Suppresses actual starting of the instance. Instead,
           start-local-instance displays the full java command that would be
           used to start the instance, including all options. Reviewing this
           command can be useful to confirm JVM options and when
           troubleshooting startup issues.

           The default value is false.

       --sync
           The type of synchronization between the DAS and the instance's
           files when the instance is started.

           Possible values are as follows:

           none
               The DAS does not synchronize the instance's files with any
               changes. This type of synchronization minimizes the time that
               is required to start the instance.

           normal
               The DAS synchronizes the instance with changes since the last
               synchronization as follows:

               *   For the config directory, the DAS synchronizes the instance
                   with all changes.

               *   For the applications directory and docroot directory, only
                   a change to a top-level subdirectory causes the DAS to
                   synchronize all files under that subdirectory.

                   If a file below a top level subdirectory is changed without
                   a change to a file in the top level subdirectory, full
                   synchronization is required. In normal operation, files
                   below the top level subdirectories of these directories are
                   not changed. If an application is deployed and undeployed,
                   full synchronization is not necessary to update the
                   instance with the change.

               This value is the default.

           full
               The DAS synchronizes the instance with all of the instance's
               files, regardless of whether the files have changed since the
               last synchronization. This type of synchronization might delay
               the startup of the instance while the DAS updates all files in
               the instance's directories.

                   Caution
                   +----------------------------------------+
                   |If the DAS is not running or is         |
                   |unreachable from the host where you are |
                   |running this subcommand, do not set the |
                   |--sync option to full. To perform a     |
                   |full synchronization, the subcommand    |
                   |removes the instance's cache. If the    |
                   |DAS cannot be contacted to replace the  |
                   |cache, the subcommand fails and the     |
                   |instance cannot be restarted until it   |
                   |is resynchronized with the DAS.         |
                   +----------------------------------------+

       --verbose, -v
           Specifies whether detailed information about the instance is
           displayed in the console window where the subcommand is run.

           Possible values are as follows:

           true
               Detailed startup messages and log messages about the instance
               are displayed in the console window where the subcommand is
               run. If the instance is later restarted by running the
               restart-local-instance(1) subcommand from a different console
               window, messages continue to be displayed in the original
               console window.

               You can kill the GlassFish Server process by typing CTRL-C in
               the console window.

               You can kill the GlassFish Server process and obtain a thread
               dump for the server by typing one of the following key
               combinations in the console window:

               *   CTRL-\ on UNIX systems

               *   CTRL-Break on Windows systems

           false
               Detailed information is not displayed (default).

       --watchdog, -w
           Specifies whether limited information about the instance is
           displayed in the console window where the subcommand is run. The
           --watchdog option is similar to --verbose but does not display the
           detailed startup messages and log messages. This option is useful
           when running the asadmin utility in the background or with no
           attached console.

           Possible values are as follows:

           true
               Limited information is displayed in the console window.

           false
               Limited information is not displayed in the console window
               (default).

OPERANDS
       instance-name
           The name of the instance to start.

EXAMPLES
       Example 1, Starting an Instance Locally
           This example starts the instance yml-i-sj01 on the host where the
           subcommand is run.

               asadmin> start-local-instance --node sj01 yml-i-sj01
               Waiting for the server to start .................................
               Successfully started the instance: yml-i-sj01
               instance Location: /export/glassfish3/glassfish/nodes/sj01/yml-i-sj01
               Log File: /export/glassfish3/glassfish/nodes/sj01/yml-i-sj01/logs/server.log
               Admin Port: 24849
               Command start-local-instance executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-instance(1), create-local-instance(1), delete-instance(1),
       delete-local-instance(1), restart-instance(1),
       restart-local-instance(1), start-domain(1), start-instance(1),
       stop-domain(1), stop-instance(1), stop-local-instance(1)

       asadmin(1M)

       Java Platform Debugger Architecture (JPDA)
       (http://java.sun.com/javase/technologies/core/toolsapis/jpda/)

Java EE 7                         13 Feb 2013          start-local-instance(1)
Command start-local-instance executed successfully.