An enterprise application is packaged in an EAR file, a type of archive file that contains any type of J2EE stand-alone modules, such as WAR and EJB JAR files.
To deploy (install) an enterprise application:
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.
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.
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".
If you choose to generate RMI stubs, static RMI-IIOP stubs are generated and put into the client.jar.
Equivalent asadmin
command: deploy
See Also: