Deploying a J2EE application file consists of installing the application file on a server configured to hold installable J2EE modules. Before installing an enterprise application or other installable module on an application server, develop the module, assemble the module, and configure the target server or cluster. Before choosing a deployment target for the module, ensure that the target version is compatible with your module.
The topics in this section describe how to deploy and administer applications or modules using the administrative console. You can also use scripting or administrative programs (JMX).
If a changed application or module is deployed on a cluster, click Rollout Update on the Enterprise Applications page to propagate the changed configuration on all cluster members of the cluster on which the application or module is deployed. Rollout Update sequentially updates the configuration on the nodes that contain cluster members.
Use Rollout Update if the application is deployed on one or more clusters spread across multiple nodes. This action reduces the amount of time that any single cluster member is unavailable to serve requests to the smallest interval possible. Pending IIOP transactions will complete before a cluster member stops; in-flight HTTP and JMS transactions might be lost while the cluster member is stopping. If the administrative console session times out during a rollout updating, ensure that the changed configuration was propagated to each node. For an application server without clusters, use Update and then save and synchronize the node instead. For a standalone application server, simply update and save.
After making
changes to administrative configurations of your applications in the administrative
console, ensure that you save the changes.