#### To deploy an application

1. In the Deploy Enterprise Applications/Modules page, from the Type drop-down list, select the type of the archive file corresponding to the application that you want to deploy. Do one of the following:

   - To deploy an enterprise application, choose .ear from the Type drop-down list and continue with step 2.

   - To deploy a web application, follow the instructions in To deploy a web application.

   - To deploy an EJB module, follow the instructions in To view, deploy, and manage EJB modules.

   - To deploy a connector module, follow the instructions in To view, deploy, and manage connector modules.

   - To deploy a lifecycle module, follow the instructions in To view, deploy, and manage lifecycle modules.

   - To deploy an application client module, follow the instructions in To deploy an application client module.

2. On the Deploy Enterprise Applications/Modules page, specify the location of the EAR file to deploy.

   The server machine is the host that is running the application server domain administration server. The client machine is the host on which you are viewing the Admin Console through a browser.

   - If the file resides on or is accessible from the client machine, click the radio button to specify a package file to upload to the Application Server.

     Click Browse to browse to the file, or type the full path to the file.

   - If the file resides on the server machine, or to deploy an un-packaged application from an exploded directory, click the radio button to specify a package file or a directory path accessible from the server.

     Type the full path name to the file or directory. Deploying from an exploded directory is for advanced developers and is not recommended for production environments.

3. Specify the settings for the application.
   1. In the Application Name field, either retain the default name, which is the prefix of the file name, or type another name.

      The default name appears if you chose to upload a file. The application name must be unique.

   2. To disable the application so that is unavailable after Deploy Enterprise Applications/Modules page, deselect the Status: Enabled check box.

      By default, an application is available as soon as it is deployed.

   3. To enable the application to use Java Web Start, select the Java Web Start: Enabled check box.

      Java Web Start provides browser-independent Deploy Enterprise Applications/Modules page of Java client applications that run directly in a Java VM.

   4. To verify the structure and contents of the file before Deploy Enterprise Applications/Modules page, select the Run: Verifier checkbox.

      Verification of large applications can be time-consuming. Verify the file if you suspect it is corrupt or non-portable.

   5. To precompile JSP pages, select the Precompile: 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, select this option for best performance in a production environment.

   6. Enter the path to any libraries (JAR files) that the application requires.

      The libraries must be accessible on the server.

   7. Optionally enter a brief text description of the application.
   8. Choose a high availability setting.

      To enable high availability for the application, select the Availability checkbox. If availability is enabled for an application, it must also be enabled at all higher levels (named configuration and web container or EJB container) as well.

   9. Choose the targets to which to deploy the application.

      From the list of available targets, choose the target or targets and click Add. Targets can be clusters or stand-alone server instances. If you do not select a target, the application is deployed to the default server instance `server`.

      If you are redeploying, don’t select targets. Anything you select here is ignored. Any target clustered or stand-alone server instance that references the deployed application automatically references the new, redeployed application if dynamic reconfiguration is enabled for the cluster or standalone instance.

4. Click OK to deploy the application.