Tool Mentor: Deploying J2EE Modules and Applications Using Rational XDE Developer - Java Platform Edition
This tool mentor describes how Rational XDE supports the deployment of stand-alone J2EE Modules and J2EE Applications.
Tool: Rational XDE Developer
Main Description

Purpose

This tool mentor describes how Rational XDE supports the deployment of stand-alone J2EE Modules and J2EE Applications. The details of deployment vary depending on the application and the environment, and usually requires the use of vendor-specific tools. However, this tool mentor describes the ways in which Rational XDE supports the installing, configuring, and launching of the application. For more information, see Guideline: Deploying J2EE Modules and Applications.

Overview

XDE provides automation for configuring J2EE modules and applications that are to be deployed to a specific environment.

This tool mentor assumes that the archives and their containing XDE deployment models have already been created, and that the decision as to what archives are deployed to what nodes has already been made. For more information, see Tool Mentor: Assembling J2EE Modules and Applications Using Rational XDE Developer - Java Platform Edition.

The following steps are performed in this tool mentor:

Links to topics in the Rational XDE™ online Help are marked with helpbook icon.

Deploying the J2EE Application

Some pre-install configuration (like adjusting the deployment descriptors) may be done in the XDE deployment models (either creating new models, so the originals aren't changed, or editing the original). For more information on using the XDE deployment models to refine the properties of the deployment descriptors, see Tool Mentor: Assembling J2EE Modules and Applications Using Rational XDE Developer - Java Platform Edition.

Once you have setup your deployment models, you can deploy the application from the EAR deployment model. You can deploy a specific EAR, or deploy all EARs mapped to a specific node. For more information, see helpbook iconDeploying Java Applications .

From any deployment model, you can export a deployment descriptor or an archive. Exporting a deployment descriptor is useful for understanding how the model maps to the descriptor and for debugging. Exporting an archive allows you to deploy standalone archives, as well as supports the use of deployment tools of application servers that are not supported by XDE. For more information, see helpbook iconJava Application Deployment . See also helpbook iconCreating EJB Deployment Descriptors .

Configuring the J2EE Application

Some additional configuration of your application server may be required for your application to run correctly, such as database mapping, access to common libraries that aren't part of the EAR, etc. Use the server's administrator console to make the necessary changes.

Launching the J2EE Application

Once the application is deployed, follow the server vendor's instructions for starting the application. In many cases, servers running in a debug or testing configuration will automatically detect the installation of a new application and make it immediately available for testing.