### To Deploy an Enterprise Application

1. Select Deploy an Enterprise Application from the right panel of the console.

   You can also access the Enterprise Application Deploy page by selecting the Enterprise Applications node and clicking on the Deploy button.

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

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

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

   Caution - Deploying from an exploded directory is for advanced developers and is not recommended for production environments.

4. Select Next to proceed to the next page of the deployment.

5. Specify the settings for the application as follows:

   - Application Name: 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.

   - Virtual Servers: Identify the desired virtual server. To view the available virtual servers, select Configuration --> HTTP Service -->Virtual Servers in the navigation tree.

   - Status: By default, an application is available as soon as it is deployed. To disable the application so that is unavailable after deployment, uncheck the Enabled checkbox.

   - Java Web Start: By default, the Java Web Start technology is disabled. To enable Java Web Start and provide browser-independent deployment of Java client application that run directly in a Java virtual machine, check the Enabled checkbox.

   - Run: To verify the structure and contents of the file before deployment, select the Verifier checkbox. Verification of large applications can be time-consuming. Verify the file if you suspect it is corrupt or non-portable.

   - Precompile: Select the JSPs checkbox to precompile JSP pages. 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.

   - Libraries: Enter the path to any libraries (JAR files) that the application requires. The libraries must be accessible on the server.

   - Description: Provide a meaningful description of the component.

6. In the Advanced section of the deployment page, you can choose 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.