WLS 10.3.5 : upload a Deployment Plan Archive

hi
Please consider the WebLogic Server 10.3.5 console "Summary of Deployments" page, where an "Install" button takes you to the first page of the "Install Application Assistant" which says "... If you cannot find your deployment files, upload your file(s) ..."
with a link to the page where you can select and upload a "Deployment Archive" and a "Deployment Plan Archive",
a shown in the screenshot at http://www.consideringred.com/files/oracle/img/2011/WLS1035-DeploymentPlanArchive.png
For this "Deployment Plan Archive" the page has a description that says
"A deployment plan is a configuration which can supplement the descriptors included in the deployment archive. A deployment will work without a deployment plan, but you can also upload a deployment plan archive now. This deployment plan archive will be a directory of configuration information packaged as a .jar file. See related links for additional information about deployment plans. "
So, there seems to be a difference between a deployment plan file (plan.xml) and a deployment plan archive (JAR file).
- (q1) Where can I find documentation on what such deployment plan archive (JAR file) should look like?
many thanks
Jan Vervecken

fyi
In the context of service request 3-4667732128 I got this feedback:
"Deployment Plan Archive" Option that we have in WebLogic Console at Deployment Service is new feature added from 11G and currently not under full fledged implementation, so that's the reason its not documented in any of the Oracle Documentation.regards
Jan

Similar Messages

Weblogic deployment plan will not override variables (Weblogic 10.3.5).

I am having some trouble trying to adjust the deployment settings of our application in weblogic. I feel what I'm trying to do ought to be quite simple, but it's not working as expected.
I am just trying to override the context-root in weblogic.xml and the JNDI name for the data source, so these can both be configured at deployment time.
I have removed the application.xml from the ear file, so that shouldn't be affecting the overrides.
What I have so far:
weblogic.xml:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
<context-root>mosaic</context-root>
<resource-description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<jndi-name>LogicalDS</jndi-name>
</resource-description>
web.xml
<?xml version='1.0' encoding='UTF-8'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<resource-ref>
<description>A logical reference to the datasource - mapped in deployment plan</description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
plan.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:deployment-plan xmlns:wls="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd" global-variables="true">

<wls:application-name>mosaic.ear</wls:application-name>
<wls:variable-definition>
<wls:variable>
<wls:name>datasource_name</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>The name of the datasource to map to the mosaic application</wls:description>
</wls:variable>
<wls:variable>
<wls:name>new_context_root</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>URL to deploy Mosaic at</wls:description>
</wls:variable>
</wls:variable-definition>
<wls:module-override>
<wls:module-name>mosaic.war</wls:module-name>
<wls:module-type>war</wls:module-type>
<wls:module-descriptor>
<wls:root-element>weblogic-web-app</wls:root-element>
<wls:uri>WEB-INF/weblogic.xml</wls:uri>
<wls:variable-assignment>
<wls:name>new_context_root</wls:name>
<wls:xpath>/weblogic-web-app/context-root</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:description>Data source for mosaic application</wls:description>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-env-description/resource-env-ref-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-description/[res-ref-name="jdbc/LogicalDS"]/jndi-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
</wls:module-descriptor>
</wls:module-override>
</wls:deployment-plan>
Nothing happens when I use the deployment plan, and neither of the variables appear under the Deployment Plan configuration screens in the admin console. From what I understand, I should at least be asked for these variables, since I have specified that they are null in the deployment plan.
When I use WLST to browse the tree, I find that the runtime configuration just stays as the values in the deployment descriptors.
I have verified the deployment plan is being used in the general tab of the admin console.
Can anyone help me find out what I am doing wrong here? If I don't create a data source called LogicalDS, I get errors about this, suggesting it is not correctly overriding. I am puzzled to why I do not see any variables to specify though..

The documentation implies that this is not the case - see:
http://docs.oracle.com/cd/E24329_01/web.1211/e24443/export.htm#autoId13
'Assigning Null Variables to Require Administrator Input'.
However, require administrator input where? My thoughts were that this option would appear in the admin console under 'deployment plan'. However, although I have specified resource dependencies in the deployment descriptors, and the plan, nothing appears under 'resource dependencies' for the application.
Is the only way to change the context-root deployment URL by actually manually editing an XML file?
To me that seems primitive and will cause us support issues when distributing our application - is there any other way I can enable the ability to specify the data source name and context-root through the web console prior to/during deployment?
Edited by: user12032953 on 11-Jun-2012 07:20

Remote deploys from Windows to Linux fail with deployment plans on WLS 10.0

Hi there,
We're using WLS 10.0.1 running in a RHEL environment (actually CentOS release 4.7 for development), and attempting to perform remote deploys from Windows work stations using the weblogic.Deployer ant task.
It works fine when not using deployment plans, or when performing a remote deploy from a unix based work station such as a Mac. However, introducing a deployment plan causes a failure only when run from Windows.
The log trace follows:
weblogic.Deployer -debug -remote -verbose -upload -noexit -name obpservices -source C:\work\obf\ver4.0\services\target\obpservices.war -targets obEnterpriseServer -adminurl t3://wlsdev:7001 -user weblogic -password ******** -redeploy -plan C:\work\obf\ver4.0\services/src/runtime/deployment-plans/steves-deployment-plan.xml
weblogic.Deployer invoked with options: -debug -remote -verbose -upload -noexit -name obpservices -source C:\work\obf\ver4.0\services\target\obpservices.war -targets obEnterpriseServer -adminurl t3://wlsdev:7001 -user weblogic -redeploy -plan C:\work\obf\ver4.0\services/src/runtime/deployment-plans/steves-deployment-plan.xml
[WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
[WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at wlsdev:7001, as user weblogic
[ServerConnectionImpl.getEnvironment():288] : setting environment
[ServerConnectionImpl.getEnvironment():291] : getting context using t3://wlsdev:7001
[ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://wlsdev:7001/jndi/weblogic.management.mbeanservers.domainruntime
[ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://wlsdev:7001/jndi/weblogic.management.mbeanservers.runtime
[DomainManager.resetDomain():36] : Getting new domain
[DomainManager.resetDomain():39] : Using pending domain: false
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@359df4
[MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@359df4
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@375edb
[MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@375edb
[ServerConnectionImpl.initialize():171] : Connected to WLS domain: obportal_domain
[ServerConnectionImpl.setRemote():482] : Running in remote mode
[ServerConnectionImpl.init():161] : Initializing ServerConnection : [email protected]9a
[BasicOperation.dumpTmids():691] : Incoming tmids:
[BasicOperation.dumpTmids():693] : {Target=obEnterpriseServer, WebLogicTargetType=server, Name=obpservices}, targeted=true
[RedeployOperation.setupPaths():86] : in place redeploy: false from moduleArchive: C:\work\obf\ver4.0\services\target\obpservices.war
[RedeployOperation.setupPaths():95] : redeploy src path: C:\work\obf\ver4.0\services\target\obpservices.war
[BasicOperation.deriveAppName():140] : appname established as: obpservices
<20/10/2009 10:47:57 AM EST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, obpservices [archive: C:\work\obf\ver4.0\services\target\obpservices.war], to obEnterpriseServer .>
[ServerConnectionImpl.upload():658] : Uploaded app to /opt/bea/user_projects/domains/obportal_domain/servers/AdminServer/upload/obpservices
[BasicOperation.dumpTmids():691] : Incoming tmids:
[BasicOperation.dumpTmids():693] : {Target=obEnterpriseServer, WebLogicTargetType=server, Name=obpservices}, targeted=true
[BasicOperation.loadGeneralOptions():608] : Delete Files:false
Timeout :3600000
Targets:
obEnterpriseServer
ModuleTargets={}
SubModuleTargets={}
Files:
null
Deployment Plan: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan\steves-deplo
yment-plan.xml
App root: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices
App config: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan
Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=obpservices,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0}
[BasicOperation.execute():425] : Initiating redeploy operation for app, obpservices, on targets:
[BasicOperation.execute():427] : obEnterpriseServer
[RedeployOperation.initializeTask():55] : Starting task with path: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\app\obpservices.war
java.io.FileNotFoundException: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan\steves-deployment-plan.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at weblogic.deploy.internal.adminserver.operations.AbstractOperation.parsePlan(AbstractOperation.java:1027)
at weblogic.deploy.internal.adminserver.operations.AbstractOperation.execute(AbstractOperation.java:133)
at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run(DeployerRuntimeImpl.java:816)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.internal.DeployerRuntimeImpl.performDeployerActions(DeployerRuntimeImpl.java:810)
at weblogic.management.deploy.internal.DeployerRuntimeImpl.redeploy(DeployerRuntimeImpl.java:568)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:443)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:248)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:153)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:63)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:153)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:377)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:375)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:310)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
[ServerConnectionImpl.close():334] : Closing DM connection
[ServerConnectionImpl.close():354] : Unregistered all listeners
[ServerConnectionImpl.closeJMX():374] : Closed JMX connection
[ServerConnectionImpl.closeJMX():386] : Closed Runtime JMX connection
[ServerConnectionImpl.closeJMX():398] : Closed Edit JMX connection
Note the file path that cannot be found: "\opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan\steves-deployment-plan.xml ".
Of course this file does actually exist when the correct path separators are used.
Is this a bug? Is there anything we can do about it? The chances of us upgrading WLS are very remote unfortunately.
Thanks in advance,
Steve C

This is something you should definitely file an Oracle support ticket for. It's entirely possible there's a patch for this.

Working with xpath attribute values in WLS 12c deployment plans

I'm trying to use a deployment plan to adjust the hibernate.dialect property in persistence.xml
persistence.xml
<property name="hibernate.dialect" value="org.hibernate.dialect.DerbyDialect" />
but whenever I attempt to refer to attributes in xpath using the usual @ sign, I get an XPathLexer barf.
plan.xml
<variable>
 <name>dialect</name>
 <value xsi:nil="false">org.hibernate.dialect.Oracle10gDialect</value>
</variable>
 <variable-assignment>
 <name>dialect</name>
 <xpath>/persistence/persistence-unit[@name="DPLV1PU"]/properties/property[@name="hibernate.dialect"]/@value</xpath>
 <operation>replace</operation>
 </variable-assignment>
I receive:
Error loading the persistence descriptor META-INF/persistence.xml from the module DPLV1EJB.jar. See the following stack trace for nested errors: weblogic.application.descriptor.DeploymentPlanException: [Munger:2156213]An error occurred while parsing the specifed XPath "/persistence/persistence-unit[@name="DPLV1PU"]/properties/property[@name="hibernate.dialect"]/@value" : line 1:31: unexpected char: '@'.
line 1:31: unexpected char: '@'
at weblogic.application.descriptor.parser.XPathLexer.nextToken(XPathLexer.java:148)
It seems wrong that I can't use a basic xpath feature like the @ to refer to an attribute here. Nor does the alternative axis syntax attribute:: work.
It's almost like there isn't a real XPath implementation under there.

Hi Chris,
I remember an earlier discussion along these lines... I haven't tested this myself, but the docs do say this:
Generic File Loading Overrides
This feature allows you to place application-specific files to be overridden into a new optional subdirectory (named /AppFileOverrides) in the existing plan directory structure. The presence or absence of this new optional subdirectory controls whether file overrides are enabled for the deployment. If this subdirectory is present, an internal ClassFinder is added to the front of the application and module classloaders for the deployment. As a result, the file override hierarchy rules follow the existing classloader and resource loading rules and behaviors for applications. For more information on WebLogic Server application classloading, see WebLogic Server Application Classloading in Developing Applications for Oracle WebLogic Server.
It seems to me that this would be the way to customise the bc4j.xcfg in the deployment plan. In the 10g days, I did this by building my EARs using ANT - I had several bc4j.xcfg files sitting in a separate directory, and each of my targets (dev/test/qa/prod) used the appropriate bc4j.xcfg to build the EAR. I did do a bit of research, and I didn't find anything obvious that would let you use a deployment plan directly for changing bc4j.xcfg - you cannot use the WLS console to change any of the properties (if you could do it via a deployment plan directly, I would expect to find the option there).
Sorry for the rambling post which doesn't give you any definitive answers, but it's just a brain dump at this point.
John

Configure dispatch-policy in deployment plan, wls 9.2

Hello,
We are planning to use deployment plans to configure applications post-compile time, such as assigning it a particular work manager which is defined globally. The problem is that weblogic seems to ignore the dispatch-policy configured in the plan, at least there is no evidence that the ejb is actually using specified work manager, even though it merges the plan with the descriptor.
The sections in my deployment plan looks as follows:
<variable-definition>
<variable>
<name>dispatch-policy_0</name>
<value>wm02</value>
</variable>
<variable-assignment>
<name>dispatch-policy_0</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="xx.xx.xx.myejb"\]/dispatch-policy</xpath>
</variable-assignment>

Hi,
I ran a quick test where I removed the work manager i referenced in the deployment plan, and behold, the server whined about referring to a missing work manager, so it "worked" all the time, there was just no way to test it.
Anyway, than you for the help, it was really appreciated. :)
Another thing I'm wondering about is XPath functions, and whether weblogic supports them in deployment plans. If I for example would like to insert the dispatch policy for some ejb with a name partially matching a string, I thought the XPath */weblogic-ejb-jar/weblogic-enterprise-bean[ejb-name/dispatch-policy* would do the trick, however this is not liked by weblogic since it requires name value pairs. Is there another way to use the contains()-function according to this requirement?
Regards
Olov

How do I change the context-root of a web app with a deployment plan?

I've been trying to figure this out for several hours.
I'm deploying a .ear file which sets the context root for the single web application it deploys in its application.xml deployment descriptor:
<application>
<display-name>MyApp</display-name>
<module>
<web>
<web-uri>MyAppViewControler.war</web-uri>
<context-root>MyApp</context-root>
</web>
</module>
</application>
I want to change the context-root from /MyApp to something else when deploying the ear file. It seemed to me that using a deployment plan was the way to do this. But when I use this plan:
<deployment-plan>
<application-name>MyApp<application-name>
<variable-definition>
<variable>
<name>NEWCONTEXTROOT</name>
<value>foobar</value>
</variable>
</variable-definition>
<module-override>
<module-name>MyApp</module-name>
<module-type>ear</module-type>
<module-descriptor external="false">
<root-element>application</root-element>
<uri>META-INF/application.xml</uri>
<variable-assignment>
<name>NEWCONTEXTROOT</name>
<xpath>/application/module/web/context-root</xpath>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
I get an error:
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
/bea/user_projects/domains/devod1/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected element 'web-uri@http://java.sun.com/xml/ns/javaee' instead of 'context-root@http://java.sun.com/xml/ns/javaee' here in element web@http://java.sun.com/xml/ns/javaee:<nullplan.xml>
I looked at http://e-docs.bea.com/wls/docs103/pdf/deployment.pdf which says:
"You cannot use 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."
I don't understand what this means. I'm not deploying my application as a library.
Does anyone know how to change the context-root for an application?
Any help would be greatly appreciated!

Hi James,
I am quite new to Welogic if i am wrong please correct me.I have re-deployed my application (.war) with this Plan.xml
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>BrowserR08.003</application-name>
*<variable-definition>*
* <variable>*
* <name>CONTEXTROOT</name>*
* <value>BrowserWeb/servlet/BrowserServlet</value>*
* </variable>*
* </variable-definition>*
<module-override>
<module-name>BrowserWeb.war</module-name>
<module-type>war</module-type>
<module-descriptor external="true">
<root-element>weblogic-web-app</root-element>
<uri>WEB-INF/weblogic.xml</uri>
<hash-code>1231953167814</hash-code>
*<variable-assignment>*
* <name>CONTEXTROOT</name>*
* <xpath>/weblogic-web-app/context-root</xpath>*
* <operation>add</operation>*
* </variable-assignment>*
</module-descriptor>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>/export/home1/tecapp/BrowserR08.003/plan</config-root>
</deployment-plan>
I do not know wether i will require the other module descriptor definition in this Plzn.xml. Now when I go to following link.
Deployments --> MyApp --> Testing
It gives me following url as a test page:
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
as soon as i click on to the above link it redirects me to following.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet/servlet/BrowserServlet
Same if i remove these context-root part my normal Testing menu shows me following link as my webapp access path
http://localhost:7001/BrowserWeb <-- My war file name is BrowserWeb.war so it is default name of my deployed application if i am not wrong
and as soon as i click on above link it redirects me to the following one.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
It means application server know that my full web access page is with '*servlet/BrowserServlet*' because its adding it in both the cases.
What I want is a constant URL whcih does not change?
Hope this helps :)

Using deployment plan to change virtual directory mapping

Hi all,
Have anyone tried this before?
I have a deployment plan to add virtual directory to my weblogic descriptors as follow:
Inside <variable-definitions> tag:
<variable>
 <name>LocalPath</name>
 <value>C:/</value>
 </variable>
 <variable>
 <name>VirtualPath</name>
 <value>/Temp/*</value>
 </variable> Then in to add the virtual directory to weblogic.xml:
<module-descriptor external="false">
 <root-element>weblogic-web-app</root-element>
 <uri>WEB-INF/weblogic.xml</uri>
 <variable-assignment>
 <name>LocalPath</name>
 <xpath>/weblogic-web-app/virtual-directory-mapping/local-path</xpath>
 </variable-assignment>
 <variable-assignment>
 <name>VirtualPath</name>
 <xpath>/weblogic-web-app/virtual-directory-mapping/url-pattern</xpath>
 <operation>add</operation>
 </variable-assignment>
 </module-descriptor>But I have this error:
Error VALIDATION PROBLEMS WERE FOUND C:\Users\Napoleon\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain\servers\DefaultServer\upload\ReviewApp\app\planplan.xml:0: problem: cvc-complex-type.2.4c: Expected element 'url-pattern@http://xmlns.oracle.com/weblogic/weblogic-web-app' before the end of the content in element virtual-directory-mapping@http://xmlns.oracle.com/weblogic/weblogic-web-app:<C:\Users\Napoleon\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain\servers\DefaultServer\upload\ReviewApp\app\planplan.xml>
I also tried using the xpath for url-pattern as followed:
<xpath>/weblogic-web-app/virtual-directory-mapping/[local-path="C:/"]/url-pattern</xpath>
But I have the same error. The <url-patter> element is not added correctly to the virtual directory mapping tag.
It is supposed to work. Anyone has done this before ? or is this a bug of deployment plan.
Thank you very much.
Regards
K.

Hi Jay,
I have looked at your link and modified my plan.xml accordingly ( the original plan is automatically generated by weblogic ). But I still get the same error. Could you have a look and tell me what's wrong?
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd">
<application-name>app</application-name>
<variable-definition>
 <variable>
 <name>SessionDescriptor_timeoutSecs_12786382366650</name>
 <value>3601</value>
 </variable>
 <variable>
 <name>firstNode</name>
 <value></value>
 </variable>
 <variable>
 <name>LocalPath</name>
 <value>C:\</value>
 </variable>
 <variable>
 <name>VirtualPath</name>
 <value>/Temp/*</value>
 </variable>
</variable-definition>
<module-override>
 <module-name>ReviewApp.ear</module-name>
 <module-type>ear</module-type>
 <module-descriptor external="false">
 <root-element>weblogic-application</root-element>
 <uri>META-INF/weblogic-application.xml</uri>
 <variable-assignment>
 <name>SessionDescriptor_timeoutSecs_12786382366650</name>
 <xpath>/weblogic-application/session-descriptor/timeout-secs</xpath>
 </variable-assignment>
 </module-descriptor>
 <module-descriptor external="false">
 <root-element>application</root-element>
 <uri>META-INF/application.xml</uri>
 </module-descriptor>
 <module-descriptor external="true">
 <root-element>wldf-resource</root-element>
 <uri>META-INF/weblogic-diagnostics.xml</uri>
 </module-descriptor>
</module-override>
<module-override>
 <module-name>ReviewUI.war</module-name>
 <module-type>war</module-type>
 <module-descriptor external="false">
 <root-element>weblogic-web-app</root-element>
 <uri>WEB-INF/weblogic.xml</uri>
 <variable-assignment>
 <name>firstNode</name>
 <xpath>/weblogic-web-app/virtual-directory-mapping</xpath>
 <operation>add</operation>
 </variable-assignment>
 <variable-assignment>
 <name>LocalPath</name>
 <xpath>/weblogic-web-app/virtual-directory-mapping/local-path</xpath>
 <operation>add</operation>
 </variable-assignment>
 <variable-assignment>
 <name>VirtualPath</name>
 <xpath>/weblogic-web-app/virtual-directory-mapping/[local-path="C:\"]/url-pattern</xpath>
 <operation>add</operation>
 </variable-assignment>
 </module-descriptor>
 <module-descriptor external="false">
 <root-element>web-app</root-element>
 <uri>WEB-INF/web.xml</uri>
 </module-descriptor>
</module-override>
<config-root>C:\Users\Napoleon\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain\servers\DefaultServer\upload\ReviewApp\app\plan</config-root>
</deployment-plan>

Update deployment plan definition with WLST

Hello,
I would like to write a script in order to get the existing deployemnt plan of my deployed application (Deployement plan is yet modified, I don't want to use loadApplication). Then I would to update my deployement plan (update/add work manager constraints).
I can't find any WLST api to do that. The Weblogic console doesn't record the actions when I do it through the console.
I would like top the the same as this link http://download.oracle.com/docs/cd/E15051_01/wls/docs103/config_scripting/updateplan.html
But with a deploymenPlan got from the server and not from the filesystem
The only way I see is to use a Java parser un Jython to update the existing deployemnt plan and then, redeploy the application but This solution is very heavy in term of developpment. It should be more efficient when a built in parser
Could you please help me giving me some information about how to update deployement plans of a yet deployed application with WLST ?
Thank you !
C.

Thank you for answering.
In fact, I have found the solution for my use case according to the previous html link
The WLST plan seems to be accessible only by file system.
If your application is yet deployed with a deployment plan and you want to update this plan, you have to login on the admin server via WLST,get the application absolute path and the plan absoluth path :
cd ("AppDeployments/" + INTERNAL_APP_NAME)
appPath = cmo.getAbsoluteSourcePath()
planPath = cmo.getAbsolutePlanPath()and then, load the existing plan :
plan = loadApplication(appPath, planPath)after that, you can use the api described at the following link http://download.oracle.com/docs/cd/E15051_01/wls/docs103/config_scripting/updateplan.html to update the plan.
Then, you have to redeploy the application :
redeploy(APP_NAME)Thank you for helping !
C.

Q: Changing login-config with a deployment plan

Hi everybody,
I have an application for which the developer sets the login-config in web.xml as follows:
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>Sec_Con-Realm</realm-name>
</login-config>
But I need it to be
<login-config>
<auth-method>CLIENT-CERT</auth-method>
<realm-name>myrealm</realm-name>
</login-config>
So I defined a deployment plan like this:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd">
<application-name>AppTest</application-name>
<variable-definition>
<variable>
 <name>LoginConfig_AuthMethod</name>
 <value>CLIENT-CERT</value>
</variable>
<variable>
 <name>LoginConfig_RealmName</name>
 <value>myrealm</value>
</variable>
 </variable-definition>
<module-override>
<module-name>AppTest.ear</module-name>
<module-type>ear</module-type>
<module-descriptor external="true">
<root-element>weblogic-application</root-element>
<uri>META-INF/weblogic-application.xml</uri>
</module-descriptor>
<module-descriptor external="false">
<root-element>application</root-element>
<uri>META-INF/application.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<module-override>
<module-name>AppTest.war</module-name>
<module-type>war</module-type>
<module-descriptor external="true">
<root-element>weblogic-web-app</root-element>
<uri>WEB-INF/weblogic.xml</uri>
</module-descriptor>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
 <name>LoginConfig_AuthMethod</name>
 <xpath>/web-app/login-config/auth-method</xpath>
 <operation>replace</operation>
 </variable-assignment>
<variable-assignment>
 <name>LoginConfig_RealmName</name>
 <xpath>/web-app/login-config/realm-name</xpath>
 <operation>replace</operation>
 </variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
But apparently my deployment plan doesn't work. If I set web.xml manually to have CLIENT-CERT/myrealm the application works. When I leave it at BASIC/Sec_Con-Realm it doesn't and asks to enter user/passwd. It seams as if the deployment plan were ignored. I don't get any errors or such, just the wrong behavior.
I use this WLST clause to deploy the EAR:
deploy('AppTest', 'dist/AppTest.ear', targets='node4', planPath='config/plan.xml', timeout=600)
The target WLS version is 10.3.4. Any clues?
Regards
Slawo.

Ivan, I don't know if this will work or not, but if you look at Edwin's example here http://biemond.blogspot.com/2009/04/using-weblogic-deployment-plan-to.html he uses the following syntax xpath so that you know which context-param needs to be replaced:
<variable-assignment>
<name>org.mytests.env</name>
<xpath>/web-app/context-param/[param-name="org.mytests.env"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
Give that a shot

Best practice: Deployment plan for cluster environment

Hi All,
I want to know, which way is the best practice for preparing and deploying new configuration for WLS-cluster environment. How can I plan a simultan deployment of ALL of nodes, with out single point of failure?
Regards,
Moh

Hi All,
I get the Answer as followed:
When you deploy an application OR redeploy an application, the deployment is initiated from the Admin Server and it it initiated on all targets (managed servers in the cluster) at the same time based on targets (which is expected to be cluster).
We recommend that applications should be targeted to a cluster instead of individual servers whenever a cluster configuration is available.
So, as long as you target the application to the cluster, the admin server will initiate the deployment on all the servers in a cluster at the same type, so application is in sync on all servers.
Hope that answers your queries. If not, please let me know what exactly you mean by synchronization.
Regards,
Moh

AIA FP 11.1.1.3 - Deployment Plan Generation for migrating from Dev to Test

Hi All,
Can you please validate the following from a Deployment from Dev to Test perspective. We have almost completed the development for an interface using AIA 11g, and are in the process of moving the interface from one instnace to another, and any help is highly appreciated.
Let us the take Purchase Order Integration between a legacy application and Oracle Purchasing, File Adapter-> Requester ABCS -> EBS -> Provider ABCS -> DB Adapter, which is a classical flow.
1. The Functional person defines a project in the Project Life Cycle Workbench
2. Functional decomposition done through Purchase Prder Business Task, and Service Solution components for each composite in the classical flow
3. The ABCSs are created by linking the corresponding Service Solution Components from the LCW using Service Contructor. These composite.xmls will have the annotation populated by the Service Constructor. It is okay for these composites to have concrete wsdls during development phase, but the concreate ones have to be replaced with abstract ones before geenrating deployment plans.
4. The EBS is not changed, it will have the annotations prepopulated, and there is no need to add any annoations to them
5. The File Adapter and DB Adapters (Transport Adapters?) have to be annotated based on the developer guide
6. The xsds and wsdl go into the mds based using the scripts provided. Any other common components can also be placed into MDS.
7. Once the development is done, Harvest the composites using the AIA Harvester.
8. After harvesting, from the AIA LCW, Generate the BOM. If we harvest all the 5 composites for the Business Task together, and do Generate BOM, does it capture all the composites? Or do they capture only the composites created using the Service Constructor? Or we have to add all the compistes manually to the Business Task?
9. Add Harvested Contents by Editing the BOM -> "Search and Add Existing Composite" option. We couldnt locate the "Add Harvested Composite" option while right clicking the Business Task.
10. Once all the harvested composites have been added to the BOM, export as XML
11. Using the BOM, generate the DeploymentPlan. The deployment plan will have references to the xsds and wsdls in the MDS
12. Using the Deployment Plan and AID, deploy the composites into a new instanec.
These are the questions I have,
1. Is the above understanding correct?
2. Since the MDS is in the Dev database, a pre-requisite for AID seems to be deployment of xsds and wsdls into the Test MDS schema. Can you please validate?
3. What happens to the bpels, xsls, mplans etc? How do they move from one instance to another?
Regards,
Anish

Hi Anish,
Following are the responses -
These are the questions I have,
1. Is the above understanding correct?
1. The Functional person defines a project in the Project Life Cycle Workbench - Yes
2. Functional decomposition done through Purchase Prder Business Task, and Service Solution components for each composite in the classical flow - Yes
3. The ABCSs are created by linking the corresponding Service Solution Components from the PLWB using Service Contructor. These composite.xmls will have the annotation populated by the Service Constructor. It is okay for these composites to have concrete wsdls during development phase, but the concreate ones have to be replaced with abstract ones before geenrating deployment plans.-Yes but location attribute in binding.ws section of composite.xml should always have concrete WSDL location.Use <replaceToken> in DeploymentPlan to replace the ip and port.
4. The EBS is not changed, it will have the annotations prepopulated, and there is no need to add any annoations to them - Yes
5. The File Adapter and DB Adapters (Transport Adapters?) have to be annotated based on the developer guide-Yes
6. The xsds and wsdl go into the mds based using the scripts provided. Any other common components can also be placed into MDS.- Yes
7. Once the development is done, Harvest the composites using the AIA Harvester.-Yes
8. After harvesting, from the AIA PLWB, Generate the BOM. If we harvest all the 5 composites for the Business Task together, and do Generate BOM, does it capture all the composites? Or do they capture only the composites created using the Service Constructor? Or we have to add all the compistes manually to the Business Task?-The 5 composites created by you should have a corresponding service solution component defined.When you define a service solution component in PLWB then a GUID is generated in the database table.You need to retrieve that value and manually enter in the annotation section of composite.xml except for ABCS.Then only the BOM will contain information on all the composites.
9. Add Harvested Contents by Editing the BOM -> "Search and Add Existing Composite" option. We couldnt locate the "Add Harvested Composite" option while right clicking the Business Task.*-Once you harvest it will be visible.*
10. Once all the harvested composites have been added to the BOM, export as XML - Yes
11. Using the BOM, generate the DeploymentPlan. The deployment plan will have references to the xsds and wsdls in the MDS - Yes
12. Using the Deployment Plan and AID, deploy the composites into a new instance.-Yes
2. Since the MDS is in the Dev database, a pre-requisite for AID seems to be deployment of xsds and wsdls into the Test MDS schema. Can you please validate?
Yes the 'UpdateMetaData' section under 'Configurations' in the DeploymentPlan will upload XSDs, WSDLs, DVM,Xrefs into MDS.
3. What happens to the bpels, xsls, mplans etc? How do they move from one instance to another?
The 'Deployments' section will deploy the project into server and write the information into MDS.
Rgds,
Mandrita

Deployment plan fails for weblogic-ejb-jar.xml

FILE FOR PLAN TO ACT ON:
application.ear\ReferenceTableSession.jar\META-INF\weblogic-ejb-jar.xml
<?xml version="1.0" encoding="utf-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>referencetablesession</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>150</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>XYZ_ejb/ProviderMaintSvc/referencetablesession</jndi-name>
</weblogic-enterprise-bean>
<transaction-isolation>
<isolation-level>TransactionReadCommitted</isolation-level>
<method>
<ejb-name>referencetablesession</ejb-name>
<method-name>*</method-name>
</method>
</transaction-isolation>
</weblogic-ejb-jar>
DEPLOYMENT PLAN:
<?xml version='1.0' encoding='utf-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd">
<application-name>application.ear</application-name>
<variable-definition>
<variable>
<name>VAR_referencetablesession</name>
<value>ejb/ProviderClaimOnlineSvc/referencetablesession</value>
</variable>
</variable-definition>
<module-override>
<module-name>ReferenceTableSession.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>META-INF/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>VAR_referencetablesession</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="referencetablesession"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<config-root>servers/AdminServer/upload</config-root>
</deployment-plan>
ERROR FROM CONSOLE:
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error Exception preparing module: EJBModule(ReferenceTableSession.jar) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Unmarshaller failed.
Message icon - Error Bean already exists: "[email protected]f2(/WeblogicEnterpriseBeans[referencetablesession])"
ERROR FROM LOG:
<Oct 2, 2009 1:08:25 PM CDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor servers/ms34/tmp/_WL_user/ProviderClaimOnlineSvc/y1anoa/ReferenceTableSession.jar/META-INF/weblogic-ejb-jar.xml of module ReferenceTableSession.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.mergeDescriptorBeanWithPlan(AbstractDescriptorLoader2.java:703)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:776)
at weblogic.ejb.spi.EjbJarDescriptor.parseWeblogicEjbJarBean(EjbJarDescriptor.java:160)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLEjbJarXMLWithSchema(EjbDescriptorReaderImpl.java:719)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:541)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:380)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:191)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:122)
Thanks,
Rob
Edited by: user11337024 on Oct 5, 2009 2:31 PM

FILE FOR PLAN TO ACT ON:
application.ear\ReferenceTableSession.jar\META-INF\weblogic-ejb-jar.xml
<?xml version="1.0" encoding="utf-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>referencetablesession</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>150</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>XYZ_ejb/ProviderMaintSvc/referencetablesession</jndi-name>
</weblogic-enterprise-bean>
<transaction-isolation>
<isolation-level>TransactionReadCommitted</isolation-level>
<method>
<ejb-name>referencetablesession</ejb-name>
<method-name>*</method-name>
</method>
</transaction-isolation>
</weblogic-ejb-jar>
DEPLOYMENT PLAN:
<?xml version='1.0' encoding='utf-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd">
<application-name>application.ear</application-name>
<variable-definition>
<variable>
<name>VAR_referencetablesession</name>
<value>ejb/ProviderClaimOnlineSvc/referencetablesession</value>
</variable>
</variable-definition>
<module-override>
<module-name>ReferenceTableSession.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>META-INF/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>VAR_referencetablesession</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="referencetablesession"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<config-root>servers/AdminServer/upload</config-root>
</deployment-plan>
ERROR FROM CONSOLE:
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error Exception preparing module: EJBModule(ReferenceTableSession.jar) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Unmarshaller failed.
Message icon - Error Bean already exists: "[email protected]f2(/WeblogicEnterpriseBeans[referencetablesession])"
ERROR FROM LOG:
<Oct 2, 2009 1:08:25 PM CDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor servers/ms34/tmp/_WL_user/ProviderClaimOnlineSvc/y1anoa/ReferenceTableSession.jar/META-INF/weblogic-ejb-jar.xml of module ReferenceTableSession.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.mergeDescriptorBeanWithPlan(AbstractDescriptorLoader2.java:703)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:776)
at weblogic.ejb.spi.EjbJarDescriptor.parseWeblogicEjbJarBean(EjbJarDescriptor.java:160)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLEjbJarXMLWithSchema(EjbDescriptorReaderImpl.java:719)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:541)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:380)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:191)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:122)
Thanks,
Rob
Edited by: user11337024 on Oct 5, 2009 2:31 PM

How to edit deployment plan through Administration Console in weblogic 9.0?

hi, 
I need to edit the deployment plan through console. But i'm not able to do so.Everytime i upload an ear file and tired to edit the environment variables or deployment plan through console it gives the message
"This module is defined with DTD based descriptors and cannot be edited using the console. " 
I have been manually editing the deployment plan file so far. 
In earlier versions of weblogic , there was an option to edit the environmental variables. Does weblogic 9.0 support the same? 
I'm not able to find a solution soo far. 
Please guide me. 
Thanks 
Smita

Hi.
I'm experiencing the same problem, using Weblogic 9.1.
I have an ear file that contains a war file.
Previously, the files were in servlet api 2.3 format (with a DTD). I used the DDConverter tool to update the files, and now I can use the console to change parameters for the web application, but I still can't change paramters for the main application: "This module is defined with DTD based descriptors and cannot be edited using the console.".
Here is the content of the META-INF/application.xml contained in mey ear file:
<?xml version='1.0' encoding='utf-8'?>
<application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4">
<description>Application xxx</description>
<display-name>xxx</display-name>
<module>
<web>
<web-uri>xxx.war</web-uri>
<context-root>xxx</context-root>
</web>
</module>
</application>
Thank you very much for your help.

WebLogic 10.2 Annotation Override/Deployment Plan Issue

We're migrating applications from WLS 9.2.1 over to 10.2. When we create the deployment plan and configure the overrides we find that some of the web service controls overrides are ignored and the defaults are used.
This was not an issue for 9.2.1 and I've not been able to find any information about this.
Has anyone experienced this before?
Chris

This issue turned out to be a missing target during the ant build process.

Deployment plan to update web.xml

Hello,
Is it possible to use a deployement plan to update the web.xml file of an war inside an ear ?
I would like to map a servlet on a new URI using a new workmanager by configuration (I mean once my application is built) I suppose it is possible to use the deployment plan to add a section inside the web.xml.
For example, I would like to add the folowing section :
<servlet>
<servlet-name>DummyServlet</servlet-name>
<servlet-class>com.company.servlets.DummyServlet</servlet-class>
<init-param>
<param-name>wl-dispatch-policy</param-name>
<param-value>DummyWorkManager</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>DummyServlet</servlet-name>
<url-pattern>/myDummyServlet</url-pattern>
</servlet-mapping>
Thank you for helping me on this point
Best Regards,
C.

To my knowledge you can not add elements to your deployment descriptors, but you can change them, for example
say we have the following ejb-jar.xml
<ejb-jar ...>
 <enterprise-beans>
 <session>
 <ejb-name>Bedrijf</ejb-name>
 <env-entry>
 <env-entry-name>something</env-entry-name>
 <env-entry-type>java.lang.String</env-entry-type>
 <env-entry-value>iets</env-entry-value>
 </env-entry>
 </session>
 </enterprise-beans>
</ejb-jar>and we want to change the value of something. Now we can generate a plan.xml (for example by using weblogic.Plangenerator
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/deployment/wlplangenerator.html). When we do this for an EAR
file we get something like the following:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd">
<application-name>test</application-name>
<variable-definition>
 <variable>
 <name>SessionDescriptor_timeoutSecs_12870427304900</name>
 <value>1800</value>
 </variable>
 <variable>
 <name>something</name>
 <value>anders</value>
 </variable>
</variable-definition>
<module-override>
 <module-name>EJBSessionBeans.ear</module-name>
 <module-type>ear</module-type>
 <module-descriptor external="true">
 <root-element>weblogic-application</root-element>
 <uri>META-INF/weblogic-application.xml</uri>
 <variable-assignment>
 <name>SessionDescriptor_timeoutSecs_12870427304900</name>
 <xpath>/weblogic-application/session-descriptor/timeout-secs</xpath>
 </variable-assignment>
 </module-descriptor>
 <module-descriptor external="false">
 <root-element>application</root-element>
 <uri>META-INF/application.xml</uri>
 </module-descriptor>
 <module-descriptor external="true">
 <root-element>wldf-resource</root-element>
 <uri>META-INF/weblogic-diagnostics.xml</uri>
 </module-descriptor>
</module-override>
<module-override>
 <module-name>Model.jar</module-name>
 <module-type>ejb</module-type>
 <module-descriptor external="true">
 <root-element>weblogic-ejb-jar</root-element>
 <uri>META-INF/weblogic-ejb-jar.xml</uri>
 </module-descriptor>
 <module-descriptor external="false">
 <root-element>ejb-jar</root-element>
 <uri>META-INF/ejb-jar.xml</uri>
 <variable-assignment>
 <name>something</name>
 <xpath>/ejb-jar/enterprise-beans/session/[ejb-name="Bedrijf"]/env-entry/[env-entry-name="something"]/env-entry-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
 </module-descriptor>
</module-override>
<module-override>
 <module-name>Userinterface.war</module-name>
 <module-type>war</module-type>
 <module-descriptor external="true">
 <root-element>weblogic-web-app</root-element>
 <uri>WEB-INF/weblogic.xml</uri>
 <hash-code>1287042734068</hash-code>
 </module-descriptor>
 <module-descriptor external="false">
 <root-element>web-app</root-element>
 <uri>WEB-INF/web.xml</uri>
 </module-descriptor>
</module-override>
<config-root>...</config-root>
</deployment-plan>To this plan.xml we added a variable definition
<variable-definition>
 <variable>
 <name>something</name>
 <value>anders</value>
 </variable>
</variable-definition>To change the contents of the variable something we add the following to the ejb-jar module section
<module-descriptor external="false">
 <variable-assignment>
 <name>something</name>
 <xpath>/ejb-jar/enterprise-beans/session/[ejb-name="Bedrijf"]/env-entry/[env-entry-name="something"]/env-entry-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
 </module-descriptor>The same steps can be followed when you want to change the contents of your web.xml (but note that the elements must be present
otherwise the xpath assignment will not work)

WLS 10.3.5 : upload a Deployment Plan Archive

Similar Messages

Maybe you are looking for