In the tree component, expand the Applications node.
Select the Web Applications node.
On the Web Applications page, click Deploy.
On the Deployment page, specify the location of the WAR 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.
Click Next to display the Deploy Web Application page.
On the Deploy Web Application page, specify the settings for the application.
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.
In the Context Root field, enter a string that identifies the Web application.
In the URL of the Web application, the context root immediately follows the port number (http://host:port/context-root/...). Make sure that the context root starts with a forward slash, for example: /hello.
To disable the application so that is unavailable after deployment, select the Disabled radio button.
By default, an application is available as soon as it is deployed.
If the application 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.
To verify the structure and contents of the file before deployment, select the Verifier checkbox.
Verification of large applications is often time-consuming. Verify the file if you suspect it is corrupt or non-portable.
To precompile JSP pages, select the JSPs checkbox.
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, in a production environment select this checkbox.
Choose a high availability setting.
To enable high availability for the application, select the Availability checkbox. If availability is enabled for an application, it must also be enabled at all higher levels (named configuration and web container or EJB container) as well.
Choose the targets to which to deploy the application.
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 application 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 application automatically references the new, redeployed application if dynamic reconfiguration is enabled for the cluster or stand-alone instance. For more information about how to redeploy applications without interruption of service, see “About Rolling Upgrades.”
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.
Click OK to deploy the application.