All Downloads are FREE. Search and download functionalities are using the official Maven repository.
  • Log In
  • Register

    • en.help.task-appdeployejb.html Maven / Gradle / Ivy

    



    To Deploy an EJB Jar
      

    1. In the navigation tree, select the Applications node.
      The Applications page opens.
      2. 

    2. In the Deployed Applications table, click the Deploy button.
      The Deploy Applications or Modules page opens.
      3. 

    3. Specify the location of the application to deploy.
        

      • If the application is an archive file that resides on or is accessible
from the client machine, select the option Packaged File to Be Uploaded to
the Server.
        The client machine is the host on which you are viewing the Administration
Console through a browser.
        Click Browse to browse to the file, or type the full path
to the file.
        • 

      • If the application is an archive file that resides on the server machine,
or is an unpackaged application from an exploded directory, select the option Local
Packaged File or Directory That Is Accessible From the GlassFish Server.
        The server machine is the host that is running the domain administration server
(DAS). 
        Click Browse Files to browse to a file, or Browse Folders to browse
to a directory. Alternatively, 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.
      4. 

    4. From the Type drop-down list, select EJB Jar.
      If you specified either a Packaged File to Be Uploaded to the Server or
a Local Packaged File That Is Accessible From the GlassFish Server, the application
type is detected automatically. If you specified a Directory That Is Accessible From
the GlassFish Server, you must specify the type manually.
      5. 

    5. In the Application Name field, retain the default name, which is the directory
name or 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.
      The name can include an optional version identifier, which follows the name and is
separated from the name by a colon (:). The version identifier must begin
with a letter or number. It can contain alphanumeric characters plus underscore (_), dash
(-), and period (.) characters. For more information about module and application versions,
see the Module and Application Versions in Oracle GlassFish Server 3.1 Application Deployment Guide.
      6. 

    6. Select the Status Enabled checkbox to enable the application.
      This option is selected by default. If this option is disabled, the application
is unavailable.
      7. 

    7. Select the Availability Enabled checkbox to enable SFSB checkpointing for the application.
      If the Enabled checkbox is selected, high-availability is enabled for stateful session bean
(SFSB) checkpointing and potentially passivation. If set to false (default) all SFSB checkpointing is
disabled for the specified EJB module. If set to true, the specified EJB
module is enabled for high-availability. Set this option to true only if high
availability is configured and enabled at higher levels, such as the server and
container levels.
      8. 

    8. Select the Run Verifier checkbox to run the verifier before deployment.
      If this option is selected and if verification fails, deployment is not performed.
The verifier examines the structure and content of the file. Verification of large
applications is often time-consuming. This option is disabled by default.
      9. 

    9. Select the Force Redeploy checkbox to force redeployment if the application is already
deployed.
      If this option is not selected, an attempt to deploy an application that
is already deployed results in an error. This option is disabled by default.
      10. 

    10. In the Libraries field, type a comma-separated list of library JAR files specific
to this application.
      The paths may be absolute or relative. A relative path is relative to
domain-dir/lib/applibs. If the path is absolute, the path must be accessible to the
domain administration server (DAS), which means it must be under domain-dir. The libraries
are made available to the application in the order in which they are
specified.
      11. 

    11. In the Description field, type a description for this application.
      12. 

    12. To add target server instances and clusters on which to deploy the module or
application, select them from the Available Targets list and use the Add button
to move them to the Selected Targets list.
      The Target option appears if clusters or stand-alone server instances aside from the default
server instance (server) exist. By default, the module or application is deployed to
the default server instance, named server. Use the Add All button to deploy to
all targets. Use the Remove and Remove All buttons to remove targets from
the Selected Targets list.
      13. 

    13. Click OK.
    See Also
    



Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices




    © 2015 - 2025 Weber Informatics LLC | Privacy Policy