WebLogic 11g Deployment: Exporting an Application for Deployment

* To expose the external resources requirements of the application, e.g. JNDI names, as null variables in a deployment plan.
* To expose additional configurable properties, such as tuning parameters (e.g. EJB caching), as variables in a deployment plan.

* weblogic.PlanGenerator:
– Creates a template deployment plan with null variables for selected categories of WebLogic Server deployment descriptors.
– You typically need to manually modify the deployment plan created by weblogic.PlanGenerator, either manually or using the Administration Console, to delete extraneous variable definitions or add variables for individual properties.
* Admin Console:
– Generate a new deployment plan .
– Or add/override variables in an existing plan.
– More flexible than weblogic.PlanGenerator. It allow interactively add/edit individual deployment descriptor properties in the plan, rather than export entire categories of descriptor properties.

* Non-configurable properties:
– ejb-name
* Dependency properties:
– datasource name used within EJB code.
* Declaration properties:
– JNDI name of an EJB
* Configurable properties: rest of properties, e.g. tuning properties.
– Dynamic properties: do not require server restart.
– Non-dynamic properties: do require server restart.

1. Create a top-level installation directory for your application:

mkdir c:\exportapps\myApplication

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.
* Use -plan option for weblogic.PlanGenerator to specify the location and file name of the generated plan.
– Otherwise, the plan is generated in TEMP/weblogic-install/application_name/config directory, where TEMP is the temporary directory for your environment. For example, C:\Documents and Settings\username\Local Settings\Temp\weblogic\install\myApplication.ear\config.

* Syntax:

java weblogic.PlanGenerator -root install_root category

– install_root: fully qualified name of the root directory for the application and plan.
– category: defaults to -dependencies.
* Example:

java weblogic.PlanGenerator -root c:\exportapps\myApplication

* Install the Exported Application and Template Deployment Plan.
* Add Variables for Selected Tuning Properties.
* Retrieve the Customized Deployment Plan.

* Following two operations can not be done in Admin Console:
– Remove an existing deployment plan variable.
– Assign a null value to a generated variable in the plan to require Admin input.

...
  <variable-definition>
    <variable>
      <name>SessionDescriptor_InvalidationIntervalSecs_11029744771850</name>
      <value>80</value>
    </variable>
  </variable-definition>
...
 
to:
 
...
  <variable-definition>
    <variable>
      <name>SessionDescriptor_InvalidationIntervalSecs_11029744771850</name>
      <value xsi:nil="true"></value>
    </variable>
  </variable-definition>
...

* On the Summary of Deployments page, select the name of the application or module that you installed.
* Select the Deployment Plan > Dependencies tab.
* Verify that the dependencies configured for the deployed module are valid for the selected target servers.

[mv_include id=”3569″]
* Exporting an Application for Deployment to New Environments