To deploy an enterprise application, choose .ear from the Type drop-down list and continue with step 2.
To deploy a web application, follow the instructions in To deploy a web application.
To deploy an EJB module, follow the instructions in To view, deploy, and manage EJB modules.
To deploy a connector module, follow the instructions in To view, deploy, and manage connector modules.
To deploy a lifecycle module, follow the instructions in To view, deploy, and manage lifecycle modules.
To deploy an application client module, follow the instructions in To deploy an application client module.
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.
Click Browse to browse to the file, or type the full path to the file.
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.
The default name appears if you chose to upload a file. The application name must be unique.
To view the available virtual servers, in the tree component select Configuration -> HTTP Service -> Virtual Servers.
By default, an application is available as soon as it is deployed.
Java Web Start provides browser-independent Deploy Enterprise Applications/Modules page of Java client applications that run directly in a Java VM.
Verification of large applications can be time-consuming. Verify the file if you suspect it is corrupt or non-portable.
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, select this option for best performance in a production environment.
The libraries must be accessible on the server.