The Applications page opens.
The Deploy Applications or Modules page opens.
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.
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.
If you specified either a Packaged File to Be Uploaded to the Server or a Local Packaged File That Is Accessible From the Enterprise Server, the application type is detected automatically. If you specified a Directory That Is Accessible From the Enterprise Server, you must specify the type manually.
The default name appears if you chose to upload a file. The application name must be unique.
This option is selected by default. If this option is disabled, the application is unavailable.
If this option is disabled, JSP files are compiled at runtime when they are first accessed. This option is disabled by default.
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.
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.
This option is disabled by default.
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.