### To deploy an enterprise application

An enterprise application is packaged in an EAR file, a type of archive file that contains any type of Java stand-alone modules, such as WAR and EJB JAR files.

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

2. Select the Enterprise Applications node.

3. On the Enterprise Applications page, click Deploy.

4. On the Deployment 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.

5. Click Next to display the Deploy Enterprise Application page.

6. On the Deploy Enterprise Application page, 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. In the Virtual Servers field, you can replace the default `server`.

      To view the available virtual servers, in the tree component select Configuration -> HTTP Service -> Virtual Servers.

   3. To disable the application so that is unavailable after deployment, deselect the Status: Enabled check box.

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

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

      Java Web Start provides browser-independent deployment of Java client applications that run directly in a Java VM.

   5. To verify the structure and contents of the file before deployment, 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.

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

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

      The libraries must be accessible on the server.

   8. Optionally enter a brief text description of the application.

   9. Select the Generate: RMI stubs to generate RMI stubs.

      If you choose to generate RMI stubs, static RMI-IIOP stubs are generated and put into the client JAR file.

7. Click OK to deploy the application.

##### More Information
To redeploy an enterprise application

To redeploy your application, click Redeploy. In the next page, provide the path to the EAR file and click OK.

##### Equivalent asadmin command

`deploy`

##### See Also

- To deploy an enterprise application

- To edit a deployed enterprise application

- To deploy a web application

- To launch a deployed web application

- To edit a deployed web application

- To deploy an EJB module

- To edit a deployed EJB module

- To deploy a connector module

- To edit a deployed connector module

- To create a lifecycle module

- To edit a lifecycle module

- To deploy an application client module

- To edit a deployed application client module

- To specify an archive file for deployment