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

ProcedureTo deploy an EJB module

An EJB module, also called an EJB JAR file, contains enterprise beans.

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

  2. Select the EJB Modules node.

  3. On the EJB Module page, click Deploy.

  4. On the Deployment page, specify the location of the JAR 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 EJB Module page.

  6. On the Deploy EJB Module page, specify the settings for the module.

    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 module so that is unavailable after deployment, select the Disabled radio button.

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

    3. If the module 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.

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

    5. Choose a high availability setting.

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

    6. Choose the targets to which to deploy the module.

      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 module 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 module automatically references the new, redeployed module if dynamic reconfiguration is enabled for the cluster or stand-alone instance. For more information about how to redeploy modules without interruption of service, see “About Rolling Upgrades.”

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

Equivalent asadmin command