Deploying and administering enterprise applications

Deploying an enterprise application file consists of installing an application file on a server configured to hold installable Java™ Platform, Enterprise Edition (Java EE) modules.

Before you begin

Before installing an enterprise application or other installable module on an application server, you must 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.

About this task

During installation, you can configure the module enough to enable it to run on the server. After installation, you can configure the module further, start or stop the application, and otherwise manage its activity.

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).

Procedure

Install Java EE application files on an application server.
Edit the administrative configuration for an application.
Optional: View the deployment descriptor for an application or module.
Start and stop enterprise applications.
Export enterprise applications.
Export a file in a Java EE application or module.
Export DDL files.
Update a Java EE application or module.
Uninstall enterprise applications using the console.
Uninstall enterprise applications by removing them from a monitored directory.
Remove a file from a Java EE application or module.

What to do next

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 Java Message Service (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 stand-alone 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.