Using a Deployment Plan

This feature
is for advanced developers.

A deployment plan is an JAR file that contains only the deployment descriptors
that are specific to the Application Server. These deployment descriptors, for example sun-application.xml, are described in the Application Server Developer’s
Guide. The deployment plan is part of the implementation of JSR 88: J2EE Application Deployment. Use a deployment plan to deploy
an application or module that does not contain the deployment descriptors that are
specific to the Application Server.

To deploy using a deployment plan, specify the --deploymentplan option
of the asadmin deploy command. The following command, for example,
deploys the enterprise application in the myrosterapp.ear file
according to the plan specified by the mydeployplan.jar file.

In the deployment plan file for an enterprise application (EAR), the sun-application.xml file is located at the root. The deployment descriptor
for each module is stored according to this syntax: module-name.sun-dd-name, where the sun-dd-name depends on the module
type. If a module contains a CMP mappings file, the file is named module-name.sun-cmp-mappings.xml. A .dbschema file
is stored at the root level with each forward slash character (/) replaced by a pound
sign (#). The following listing shows the structure of the deployment plan file for
an enterprise application (EAR).

In the deployment plan for a web application or a module file, the deployment
descriptor that is specific to the Application Server is at the root level. If a stand-alone
EJB module contains a CMP bean, the deployment plan includes the sun-cmp-mappings.xml and .dbschema files at the root level. In the following
listing, the deployment plan describes a CMP bean.