Deploying Applications to WebLogic Server
weblogic.PlanGenerator is a Java-based deployment configuration tool. It is primarily intended for developers who want to export portions of a WebLogic Server deployment configuration into an XML deployment plan. weblogic.PlanGenerator
also enables you to generate a basic WebLogic Server configuration for applications that have only J2EE deployment descriptors.
See also WebLogic Scripting Tool for information about performing deployment configuration operations using the WebLogic Scripting Tool (WLST).
The following sections describe using the weblogic.PlanGenerator
utility:
weblogic.PlanGenerator
generates WebLogic Server deployment configuration files for an application or stand-alone module. weblogic.PlanGenerator
provides two primary functions:
By default, weblogic.PlanGenerator
writes an application's deployment plan to a file named plan.xml
in the application's root directory. If your application is not in an application root directory, weblogic.PlanGenerator
writes plan.xml
to <
your_dir
>/config/deployments/<
user
>/<
application_name
>/plan
where:
your_dir
is your TEMP
directory if it is specified in the property java.io.tmpdir
. If the property java.io.tmpdir
is not specified, your_dir
is the WebLogic Server domain directory.user
is your user name.application
is the name of the application.
To set up your environment to use the weblogic.PlanGenerator utility:
PATH
. You can use the setWLSEnv.sh or setWLSEnv.cmd
script, located in the server/bin subdirectory of the WebLogic Server installation directory, to set the environment.
java weblogic.PlanGenerator [Options] [
filespec
]
-root
option as described in Options when you issue a weblogic.PlanGenerator command.In all cases, the application identified with the filespec
must contain valid J2EE deployment descriptor files.
If you do not specify an application root directory with the -root
option or a deployment plan path and name with the -plan
option, by default, weblogic.PlanGenerator
writes an application's deployment plan to a file named plan.xml
in the application's root directory. If it cannot locate an application root directory, weblogic.PlanGenerator
writes plan.xml
to <
your_dir
>/config/deployments/<
user
>/<
application_name
>/plan
where:
your_dir
is your TEMP
directory if it is specified in the property java.io.tmpdir
. If the property java.io.tmpdir
is not specified, your_dir
is the WebLogic Server domain directory.user
is your user name.application
is the name of the application.The following table describes each weblogic.PlanGenerator
option.
Figure 7-2 weblogic.PlanGenerator Options
The following sections describe common configuration and export scenarios, with examples examples of weblogic.PlanGenerator
syntax.
If you store your application using an installation root directory, and you specify the root directory with the -root
option, generated deployment plan files are automatically stored in the root directory's plan
subdirectory.
java weblogic.PlanGenerator -root /appRelease/MyApplication
In the above example, the plan.xml
file is automatically stored in /appRelease/MyApplication/plan
.
The following command uses an existing plan as input and generates a new plan in the /plan
subdirectory of the application root directory:
java weblogic.PlanGenerator -useplan /plans/MyApplication_template.xml
-root /appRelease/MyApplication
You can use the -all
, -configurables
, -dependencies
, -declarations
, -dynamics
, and -none
options to specify the WebLogic Server deployment descriptor components that are exported to a template deployment plan. The following command exports all configurable properties to null variables in a template deployment plan:
java weblogic.PlanGenerator -root /appRelease/MyApplication -all
See Exporting an Application for Deployment to New Environments for more information about exporting a deployment configuration.