Hi Everyone,

I noticed that in weblogic 10 version, from the console we can not assign default web application to a server. This was there in 8.1 console ( server configuration-general tab). If my war or ear file is ready and released into prod but I do not want to untar it again to add <context-root> into the DD. I thought I can do it from console but I am able to set default web application from WLS 10 console.

Appreciate help if anybody knows how to do it from WLS 10 console.

thanks.

James, really appreciate your time. I created Plan.xml and added the tag <context-root>/</context-root>. When I tried to deploy the application archive file, I get the exception :

J2EE:160174ERROR: Failed to parse deployment plan 'C:\deployments\production\myApp\plan\Plan.xml': VALIDATION PROBLEMS WERE FOUND C:\deployments\production\myApp\plan\Plan.xml:17:5:17:5: problem: cvc-complex-type.2.4b: Element not allowed: context-root@http://www.bea.com/ns/weblogic/90 in element deployment-plan@http://www.bea.com/ns/weblogic/90:

I am not sure should I use ns declaration for weblogic 10 instead of 9.0.

Also, there is caution mentioned by Oracle in http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/config.html#wp1065363

Caution: Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file.

thanks

Maybe I'll blog this because it didn't work when I tried it as exploded (deployed directly from the IDE), but it did once I tried an EAR outside of the IDE (OEPE in this case).

Thanks to Edmond for helpful clues on this:
http://biemond.blogspot.com/2009/04/using-weblogic-deployment-plan-to.html

First export the EAR to a directory
Then go to your domain's bin dir with a shell and call setDomainEnv
Then call a command like this from the dir where the EAR is with that same shell:
java weblogic.PlanGenerator -all -plan Plan.xml PlanEAR.ear

That should generate a Plan.xml file.

The original weblogic.xml actually had the name of the context root explicitly defined for me like this:
<wls:context-root>PlanWEB</wls:context-root>

So firstly, we have to set the variable assignment in Plan.xml, where "FooPlan" is the value I want for my new context root.

Original:
<variable>
<name>WeblogicWebApp_ContextRoots_12482790756401</name>
<value xsi:nil="true"></value>
</variable>

New:
<variable>
<name>WeblogicWebApp_ContextRoots_12482790756401</name>
<value>FooPlan</value>
</variable>

So in order to override the context root we need to do a replace instead of a variable assignment since the element already exists. Edit Plan.xml again.

Original:
<variable-assignment>
<name>WeblogicWebApp_ContextRoots_12482790756401</name>
<xpath>/weblogic-web-app/context-root</xpath>
</variable-assignment>

New:
<variable-assignment>
<name>WeblogicWebApp_ContextRoots_12482790756401</name>
<xpath>/weblogic-web-app/context-root</xpath>
<operation>replace</operation>
</variable-assignment>

Now we can do a redeployment with this new deployment plan provided the EAR and Plan.xml and I can now access the application at http://locahost:7001/FooPlan/.
java weblogic.Deployer -adminurl t3://localhost:7001 -user weblogic -password welcome1 -redeploy -name PlanEAR -source PlanEAR.ear -targets AdminServer -plan Plan.xml

I found an easier way, you can do it from the console and it will auto-gen the deployment plan for you. Both methods are described in my blog entry:
http://blogs.oracle.com/jamesbayer/2009/07/11gr1_update_and_a_deployment.html

Cheers