Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide

- Previous: Admin Console Tasks for Deploying Applications
- Next: Deployment Methods for Developers

# 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 from the domain and removes references to it from all instances.

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.

   To enable an application on a single target:

   1. Select the node for the application.

   2. Click the Targets tab.

   3. Select the checkbox next to the deployed application or module.

4. Click Enable or Disable.

   These buttons enable or disable the application on all targets.

##### Equivalent asadmin commands

`enable` and `disable`

## To manage application targets

After deploying an application or module, manage the server instances and clusters that reference it by managing targets.

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

2. Expand the node for the application type.

3. Select the node for the deployed application.

4. Select the Targets tab.

5. To enable or disable an application on a specific target instance or cluster, click the checkbox next to the target and click Enable or Disable.

6. To add or delete targets for the application, choose Manage Targets.

7. Add or remove targets and click OK.

   The application is now available on the revised list of targets.

##### Equivalent asadmin commands

`create-application-ref` and `delete-application-ref`

## To deploy on additional virtual servers

After deploying an application or module to a target server instances or clusters, you can associate it with additional virtual servers.

1. From the deployed application or module’s Target page, click the Manage Virtual Servers link next to the target.

2. Add or remove virtual server targets from the list of available virtual servers.

3. Click OK.

## Redeploying to Multiple Targets

If an application is deployed to multiple targets (stand-alone server instances or clusters), you have two ways of redeploying to multiple targets. Use one of the following methods to make sure all server instances that reference an application receive the most recent version.

### Development Environment

In a development environment, simply redeploy the application. The application is redeployed to the domain, and all targets that reference it automatically receive the new version if dynamic reconfiguration is enabled for the target server instances. Dynamic reconfiguration is enabled by default. If dynamic reconfiguration is not enabled for a server instance, it continues to use the old version until the server instance is restarted.

### Production Environment

In a production environment, follow the steps detailed in “About Rolling Upgrades.”

## 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-modules` module-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.

Note –

Dynamic reloading is only available for the default server instance.

Dynamic reloading is intended for development environments. It is incompatible with session persistence, a production environment feature. Do not enable session persistence if dynamic reloading is enabled.

1. In the tree component, expand the Stand-Alone Instances node.

2. Click server (Admin Server).

3. Click Advanced.

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

- Previous: Admin Console Tasks for Deploying Applications
- Next: Deployment Methods for Developers

- © 2010, Oracle Corporation and/or its affiliates