Sun Java System Application Server Platform Edition 8.2 Administration Guide

ProcedureTo deploy an enterprise application

An enterprise application is packaged in an EAR file, a type of archive file that contains any type of J2EE 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 unpackaged application from an exploded directory, click the radio button to specify a package file or a directory path that must be 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, select the Disabled radio button.

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

    4. If the application has already been deployed, select the Redeploy checkbox to redeploy it; otherwise you see an error.

      You can also choose a different application name and deploy it under a new name.

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

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

Equivalent asadmin command