5-4 Deploying Applications to Oracle WebLogic Server
2.
Create \app and \plan subdirectories: mkdir c:\exportapps\myApplication\app
mkdir c:\exportapps\myApplication\plan
3.
Copy the complete application to be exported into the \app subdirectory. The application can be either in archive or exploded archive form:
cp -r c:\dev\myApplication c:\exportapps\myApplication\app The \app directory must include the full application distribution, and can include
the WebLogic Server descriptor files that you use for deployment to your development environment.
If you choose not to use an installation directory when exporting an application, Oracle recommends using the -plan option to weblogic.PlanGenerator to
specify the location and filename of the generated plan. By default, weblogic.PlanGenerator stores generated files in the
TEMP
weblogic-installapplication_nameconfig directory, where TEMP is the temporary directory for your environment. For Windows platforms, this means
generated configuration files are stored in C:\Documents and Settings\username\Local
Settings\Temp\weblogic\install\myApplication.ear\config. Use the -plan option to place generated files in a known location.
5.5 Generating a Template Deployment Plan using weblogic.PlanGenerator
The weblogic.PlanGenerator tool provides a quick and easy way to generate a template deployment plan with null variables for an entire category such as
declaration or configurable properties of deployment descriptors. Oracle recommends using weblogic.PlanGenerator to generate a new deployment plan with null
variables for all of an applications dependencies. This ensures that all global resources required for an application can be easily configured by administrators who must
deploy the application in a new environment.
When using an application staged in an installation root directory, the basic syntax for using weblogic.PlanGenerator is:
java weblogic.PlanGenerator -root install_root category where:
install_root specifies the fully qualified name of the root directory for the
application and plan. category
specifies the category of WebLogic Server deployment descriptors for which you want to create variables. See
Section 5.2, Understanding Deployment Property Classifications
for a description of each category. For the purposes of generating a template deployment plan, you should usually use only the
-dependencies option, which is the default option, as this limits variables to external resources required by the application.
Exporting an Application for Deployment to New Environments 5-5
For example: java weblogic.PlanGenerator -root c:\exportapps\myApplication -dependencies
java weblogic.PlanGenerator -root c:\exportapps\myApplication With the above commands, which are synonymous because -dependencies is the
default option so you are not required to specify it in your weblogic.PlanGenerator command, weblogic.PlanGenerator inspects all
J2EE deployment descriptors in the selected application, and creates a deployment plan with null variables for all relevant WebLogic Server deployment properties that
configure external resources for the application. Using this template deployment plan, an administrator using the Administration Console is directed to assign valid resource
names and tuning properties for each null variable before the application can be deployed.
5.6 Customizing the Deployment Plan Using the Administration Console
