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

- Previous: To create a new resource type
- Next: Instance Specific Configuration Properties

## Administration Server Advanced Settings

The Administration Server Advanced settings allow you to set general properties for deploying applications. These properties enable you to ensure and monitor that changes to deployed applications are detected and the modified classes reloaded.

### Setting Applications Configurations

If dynamic reloading is enabled, the server periodically checks for changes in the files of the deployed application and automatically reloads the application with the changes. 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.

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

Note –

Dynamic reloading is only available for the default server instance.

To configure dynamic reloading from 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.

### To configure auto deploy settings

The auto deploy feature enables you to deploy a prepackaged application or module by copying it to the domain-dir`/autodeploy` directory.

For example, copy a file named `hello.war` to the domain-dir`/autodeploy` directory. To undeploy the application, remove the `hello.war` file from the `autodeploy` directory.

The auto deploy feature is intended for development environments. It is incompatible with session persistence, a production environment feature. Do not enable session persistence if auto deploy is enabled.

Note –

Auto deploy is only available for the default server instance.

1. Go to the Applications Configuration page.

2. Enable or disable auto deploy by selecting or deselecting the Enabled checkbox.

3. In the Auto Deploy Poll Interval field, specify how often the server checks the auto deploy directory for application or module files.

   Changing the poll interval does not affect the amount of time it takes to deploy an application or module.

4. In the Auto Deploy directory, if you specify the directory where you build your application, then you won’t have to copy the file to the default auto deploy directory.

   By default a variable is used to eliminate the need to manually change the directory for multiple server instances.

5. To run the verifier before deployment, select the Verifier Enabled checkbox.

   The verifier examines the structure and content of the file. Verification of large applications is often time-consuming.

6. To precompile JSP pages, select the JSPs checkbox.

   If you do not select this checkbox, the JSP pages are compiled at runtime when they are first accessed. Because compilation is often time-consuming, in a production environment select this checkbox.

7. Click the Add Property button to specify additional settings.

### Setting Domain Attributes

The following domain attributes properties are available.

Table 1–1 Domain Attributes values

Property | Definition
--- | ---
`com.sun.aas.installRoot` | Directory where the application server is installed.
`com.sun.aas.instanceRoot` | Top level directory for a server instance.
`com.sun.aas.hostName` | Name of the host (machine).
`com.sun.aas.javaRoot` | .J2SE installation directory.
`com.sun.aas.imqLib` | Library directory of the Sun Java System Message Queue software.
`com.sun.aas.configName` | Name of the configuration being used by a server instance.
`com.sun.aas.instanceName` | Name of the server instance. This property is not available for the default-config but can be used for customized configurations.
`com.sun.aas.clusterName` | Name of the cluster. This property is only set on the clustered server instances. This property is not available for the default-config but can be used for customized configurations.
`com.sun.aas.domainName` | Name of the domain. This property is not available for the default-config but can be used for customized configurations.

- Previous: To create a new resource type
- Next: Instance Specific Configuration Properties

- © 2010, Oracle Corporation and/or its affiliates