The following topics are addressed here:
Use the version subcommand in remote mode to display information about the GlassFish Server version for a particular server. If the subcommand cannot communicate with the server by using the specified login (user/password) and target (host/port) information, then the local version is displayed along with a warning message.
Ensure that the server is running.
Remote subcommands require a running server.
Display the version by using the version(1) subcommand.
This example displays the version of GlassFish Server on the local host.
asadmin> version Version = Oracle GlassFish Server 3.0.1 (build 19) Command version executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help version at the command line.
Use the list-applications subcommand in remote mode to list the deployed Java applications. If the --type option is not specified, all applications are listed.
Ensure that the server is running.
Remote subcommands require a running server.
List applications by using the list-applications(1) subcommand.
This example lists the web applications on localhost.
asadmin> list-applications --type web hellojsp <web> Command list-applications executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help list-applications at the command line.
Use the list-containers subcommand in remote mode to list application containers.
Ensure that the server is running.
Remote subcommands require a running server.
List containers by using the list-containers(1) subcommand.
This example lists the containers on localhost.
asadmin> list-containers List all known application containers Container : grizzly Container : ejb Container : webservices Container : ear Container : appclient Container : connector Container : jpa Container : web Container : jruby Container : security Container : webbeans Command list-containers executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help list-containers at the command line.
Use the list-modules subcommand in remote mode to list the modules that are accessible to the GlassFish Server module subsystem. The status of each module is included. Possible statuses include NEW and READY.
Ensure that the server is running.
Remote subcommands require a running server.
List modules by using the list-modules(1) subcommand.
This example lists the accessible modules.
asadmin> list-modules |
Information similar to the following is displayed (partial output):
List Of Modules Module : org.glassfish.web.jstl-connector:10.0.0.b28 properties=(visibility=public,State=READY,Sticky=true) Module Characteristics : List of Jars implementing the module Jar : file:/C:/Preview/v3_Preview_release/distributions/web/target/glass fish/modules/web/jstl-connector.jar Module Characteristics : List of imported modules Module Characteristics : Provides to following services Module : org.glassfish.admingui.console-common:10.0.0.b28 properties=(visibility=public,State=NEW,Sticky=true) Module : org.glassfish.admin.launcher:10.0.0.b28 properties=(visibility=public,State=NEW,Sticky=true) Module : org.glassfish.external.commons-codec-repackaged:10.0.0.b28 properties=(visibility=public,State=NEW,Sticky=true) Module : com.sun.enterprise.tiger-types-osgi:0.3.32.Preview-b28 properties=(visibility=public,State=READY,Sticky=true) Module Characteristics : List of imported modules Module Characteristics : Provides to following services Module Characteristics : List of Jars implementing the module Jar : file:/C:/Preview/v3_Preview_release/distributions/web/target/glass fish/modules/tiger-types-osgi.jar. ... Command list-modules executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help list-modules at the command line.
Use the list-commands subcommand in remote mode to list the deployed asadmin subcommands. You can specify that only remote subcommands or only local subcommands are listed. By default, this subcommand displays a list of local subcommands followed by a list of remote subcommands.
Ensure that the server is running.
Remote subcommands require a running server.
List subcommands by using the list-commands(1) subcommand.
This example lists only local subcommands.
asadmin> list-commands --localonly create-domain delete-domain list-commands list-domains login monitor start-database start-domain stop-domain stop-database version Command list-commands executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help list-commands at the command line.
The timer service is a persistent and transactional notification service that is provided by the enterprise bean container and is used to schedule notifications or events used by enterprise beans. All enterprise beans except stateful session beans can receive notifications from the timer service. Persistent timers set by the service are not destroyed when the server is shut down or restarted.
Use the list-timers subcommand in remote mode to list the persistent timers owned by a specific server instance. You can use this information to decide whether to do a timer migration, or to verify that a migration has been completed successfully.
Ensure that the server is running.
Remote subcommands require a running server.
List timers by using thelist-timers(1) subcommand.
This example lists the timers in a particular standalone server instance. There is one currently active timer set.
asadmin> list-timers server 1 The list-timers command was executed successfully. |
Use the show-component-status subcommand in remote mode to get the status (either enabled or disabled) of the specified deployed component.
Ensure that the server is running.
Remote subcommands require a running server.
Show component status by using the show-component-status(1) subcommand.
This example shows the status of the MEjbApp component.
asadmin> show-component-status MEjbApp Status of MEjbApp is enabled Command show-component-status executed successfully. |