WebLogic 11g Deployment: Configuring Applications for Production Deployment

* Deployer should configure deployment plans not deployment descriptors.

* Programmer creates:
– JEE deployment descriptors
– WebLogic deployment descriptors

* Programmer creates:
– Deployment plan

* Admin or Deployer:
– Config application to be deployed

* Admin or Deployer:
– Reconfig application by redeploy with new deployment plan.
– Using Admin Console to update and redeploy an existing deployment plan.

* Owned by Dev team.
* One master plan for all environments.
* Generated by programmers.
* Deployers make changes for specific environment.

* Owned by Deployer team.
* One plan for each environment.
* Generated by Deployers for a specific environment.
* Recommended.

* Use Admin Console.
* Use weblogic.PlanGenerator.
* Steps:
– Prepare Deployment Files

mkdir c:\sample_root
mkdir c:\sample_root\app
mkdir c:\sample_root\plan
cp jspExpressionEar.ear c:\sample_root\app

– Install application archive (e.g. jspExpressionEar.ear) using Admin Console.
– Save config changes to a deployment plan (default to Plan.xml in the plan directory).
* See deployment-plan.xsd

* Allows application file overrides.
* Place application-specific files to be overridden in this directory.
* Overrides only classloader.getResourceAsStream() resources not ServletContext.getResourceAsStream() resources.
* To use:
– Specify a deployment plan.
– Specify the config-root within in the plan.
– Provide a config-root/AppFileOverrides subdirectory.

install-root/plan/AppFileOverrides
install-root/plan/AppFileOverrides/WebApp1.war/...
install-root/plan/AppFileOverrides/WebApp2.war/...

Properties myAppProps = new Properties();
InputStream iostream =
Thread.currentThread().getContextClassLoader().getResourceAsStream("myCfg/myApp.properties");
myAppProps.load(iostream);

[mv_include id=”3569″]
* Configuring Applications for Production Deployment