Admin Console Tasks for Listing, Undeploying, and Enabling Applications

• To list deployed applications

• To list subcomponents

• To view module descriptors of deployed applications

• To undeploy an application or module

• To enable or disable an application or module

• To configure dynamic reloading

To list deployed applications

1. In the tree component, expand the Applications node.

2. Expand the node for the application or module type.

   To view the details of a deployed application or module either:

   • In the tree component, select the node of the application or module.

   • On the page, select an entry in the Application Name column.

Equivalent asadmin command

list-components

To list subcomponents

Enterprise and Web applications, EJB Modules and Connector Modules contain subcomponents. For example, a web application might contain one or more servlets.

1. In the tree component, expand the Applications node.

2. Expand the node for the type of application or module for which to view descriptors.

3. Select the node for the deployed application or module.

4. On the Application or Module page, note the contents of the Sub Components table.

Equivalent asadmin command

list-sub-components

To view module descriptors of deployed applications

For Enterprise Applications, Web Applications, EJB Modules, Connector Modules, and App Client Modules, you can view the module deployment descriptors.

1. In the tree component, expand the Applications node.

2. Select the node for the type of application or module for which to view descriptors.

3. Select the node for the deployed application or module.

4. Select the Descriptor tab.

5. To see the text of the descriptor file, click the file name.

   The page displays the file contents. This information is read-only.

To undeploy an application or module

Undeploying an application or module uninstalls it.

1. In the tree component, expand the Applications node.

2. Select the node for the type of application or module want to undeploy.

3. In the table listing the deployed applications, select the checkbox for the application or module you want to undeploy.

4. Click Undeploy.

Equivalent asadmin command

undeploy

To enable or disable an application or module

If a deployed application or module is enabled, it is accessible by clients. If it is disabled, it is still deployed but is not accessible by clients. By default, when you deploy an application or module, it is enabled because the Enable on All Targets radio button is selected by default.

1. In the tree component, expand the Applications node.

2. Expand the node for the application type.

3. To enable a deployed application or module, select the checkbox next to the deployed application or module.

4. Click Enable or Disable.

Equivalent asadmin commands

enable and disable

To configure dynamic reloading

If dynamic reloading is enabled, the server periodically checks for changes in a deployed application and automatically reloads the application with the changes. Changes are signaled by a date change to a file called .reload that you create manually. The applications must be installed in domain-dir/applications/j2ee-modulesmodule-name or domain-dir/applications/j2ee-apps/app-name

For example:

/opt/SUNWappserver/domain/domain1/applications/j2ee-modules/webapps-simple

Dynamic reloading is useful in a development environment because it allows code changes to be tested quickly. In a production environment, however, dynamic reloading may degrade performance.

1. In the tree component, select Application Server.

2. Click Advanced.

3. On the Applications Configuration page, configure the following:

   • Reload: Enable or disable dynamic reloading with the Enabled checkbox.

   • Reload Poll Interval: Specify how often the server checks for changes in the deployed applications.

   • Admin Session Timeout: Specify the amount of time before the Admin Session times out and you have to log in again.

Next Steps

After configuring the system to use dynamic reloading, for every application to be reloaded dynamically, create a file called .reload and put it in the application’s directory. The file does not have any content. When you change the application, change the date of the file (for example, using the UNIX touch command), and the changes are reloaded automatically.