en.help.task-deployentapp.html Maven / Gradle / Ivy
To Deploy an Enterprise Application
- In the navigation tree, select the Applications node.
The Applications page opens.
- In the Deployed Applications table, click the Deploy button.
The Deploy Applications or Modules page opens.
- 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.
- From the Type drop-down list, select Enterprise Application.
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.
- 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.
- From the Virtual Servers drop-down list, select the virtual server to be associated
with this application.
- Select the Status Enabled checkbox to enable the application.
This option is selected by default. If this option is disabled, the application
is unavailable.
- Select the Precompile JSPs checkbox to precompile JavaServer Pages (JSP) files.
If this option is disabled, JSP files are compiled at runtime when they
are first accessed. This option is disabled by default.
- 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.
- 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.
- Select the Java Web Start checkbox to enable Java Web Start access for
an application client.
This option is disabled by default.
- 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.
- In the Description field, type a description for this application.
- Click OK.
See Also