Plan.xml

I am getting plan.xml not found in c:\oracle\middleware\oracle_soa1\soa\dbplan\
I have checked the directory and plan.xml is there. also, not able to store xADataSourceName. Tried so many times and getting the same error
I'm using the weblogic 11.1.1.4.0 and trying to create simple dbadaptor example
thanks
Jith

Is this a windows 7 box? Make sure your user has full permissions on the directoy. When starting weblogic server, make sure to run it as Administrator.

Similar Messages

How to create a Plan.xml file for modification

Hi,
I am trying to create a plan.xml file. Is there any way, I can generate a plan.xml file.
I see a tab in Admin Console in deployments and plan. but there is nothing there. what it has to do with plan.
Thanks
regards
Amir riaz

You can find the steps here.
http://weblogic-wonders.com/weblogic/2009/11/29/plan-xml-usage-for-message-driven-bean/
http://weblogic-wonders.com/weblogic/2009/12/16/invalidation-interval-secs/

JMS Adapter Config issues with Plan.xml

Hi All,
I'm learning how to configure JMS Resources in WLS to use within a JMS adapter in my application. My approach so far has been :
1. Configure Outbound Connection in JMS Adapter : eis/wls/Queue. I used the weblogic.jms.XAConnectionFactory as the Connection Factory.
2. Create Queue within SOAJMSModule : jms/MyQueue and target - soa managed server.
Updated the JMSAdapter.rar deployment and restarted the SOA server as well as the JMS module.
3. Create JMS Adapter within JDeveloper to use jms/MyQueue as the destination and eis/wls/Queue as the JNDI source.
On deployment and running, I see this following error. Apologies it is a bit difficult to trawl through. I did have a look in the Plan.xml and it definitely has an entry for this Adapter and the jndi-name. Any other approach?
Oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) 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:597) at com.sun.el.parser.AstValue.invoke(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:765) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:305) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:276) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source) at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:992) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 81 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1012) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:803) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 84 more
The deployment plan reads as follows :
<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" global-variables="false">
<application-name>connectors</application-name>
<variable-definition>
<variable>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<value>eis/wls/Queue</value>
</variable>
<variable>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<value>weblogic.jms.XAConnectionFactory</value>
</variable>
</variable-definition>
<module-override>
<module-name>JmsAdapter.rar</module-name>
<module-type>rar</module-type>
<module-descriptor external="false">
<root-element>weblogic-connector</root-element>
<uri>META-INF/weblogic-ra.xml</uri>
<variable-assignment>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/jndi-name</xpath>
<origin>planbased</origin>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/connection-properties/properties/property/[name="ConnectionFactoryLocation"]/value</xpath>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>connector</root-element>
<uri>META-INF/ra.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>E:\oracle\product\middleware\11.1.1\soa_11.1\soa\connectors\plan</config-root>
</deployment-plan>
Thanks
JB
Edited by: 939260 on Jun 20, 2012 5:13 AM

Hi JB,
Please follow the below steps from beginning...
1. Create the JMS Server in the Admin Console, the target server for the same should be the soa server
2. create new JMS Module.
3. Create new Connection factory in resources, give your JNDI names, the target servers should be the admin and the soa.
4. create new queue, give the JNDI names, the target server should be the JMS Server which you have created in the step 1 above.
5. Now go to deployments, slect the JMS adapter, click update, and say redeploy with the location of JMS-plan.xml given below...
6. Now inside the composite while configuring the JMS adapter, select the queue which you have created above.
If you have followed the abpve steps correctly, you should not face any problem.
Hope this helps,
N

Namespaces in plan.xml - can't override weblogic.xml

So, we've tried every combination we can think of, but we can't seem to get a plan.xml that successfully overrides items in weblogic.xml. It seems to be an issue around namespaces:
<May 19, 2009 10:40:57 AM MDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor /nas/scart/domain_tmps/tcatshopDomain/servers/tcatshop1/tmp/_WL_user/MasterEar/v99i42/MasterWebPortal.war/WEB-INF/weblogic.xml of module MasterWebPortal.war. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
/nas/scart0/prod_ecom2/local/apps/apps92/tcatshop/THUNDER_01.09.06.004/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected elements 'description@http://www.bea.com/ns/weblogic/90 weblogic-version@http://www.bea.com/ns/weblogic/90 security-role-assignment@http://www.bea.com/ns/weblogic/90 run-as-role-assignment@http://www.bea.com/ns/weblogic/90 resource-description@http://www.bea.com/ns/weblogic/90 resource-env-description@http://www.bea.com/ns/weblogic/90 ejb-reference-description@http://www.bea.com/ns/weblogic/90 service-reference-description@http://www.bea.com/ns/weblogic/90 message-destination-descriptor@http://www.bea.com/ns/weblogic/90 session-descriptor@http://www.bea.com/ns/weblogic/90 jsp-descriptor@http://www.bea.com/ns/weblogic/90 auth-filter@http://www.bea.com/ns/weblogic/90 container-descriptor@http://www.bea.com/ns/weblogic/90 charset-params@http://www.bea.com/ns/weblogic/90 virtual-directory-mapping@http://www.bea.com/ns/weblogic/90 url-match-map@http://www.bea.com/ns/weblogic/90 security-permission@http://www.bea.com/ns/weblogic/90 context-root@http://www.bea.com/ns/weblogic/90 wl-dispatch-policy@http://www.bea.com/ns/weblogic/90 servlet-descriptor@http://www.bea.com/ns/weblogic/90 work-manager@http://www.bea.com/ns/weblogic/90 logging@http://www.bea.com/ns/weblogic/90 library-ref@http://www.bea.com/ns/weblogic/90' instead of *'session-descriptor@http://www.w3.org/2001/XMLSchema-instance' here in element weblogic-web-app@http://www.bea.com/ns/weblogic/90:<nullplan.xml>*
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:229)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:216)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
This is in WLP 9.2...
Plan:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/90">
<application-name>MasterEar.ear</application-name>
<variable-definition>
<variable>
<name>ThundercatCookieName</name>
<value>JSESSIONID_THUNDERCAT_PLAN_XML</value>
</variable>
<variable>
<name>ThundercatCookieDomain</name>
<value>.qwest.com</value>
</variable>
</variable-definition>
<module-override>
<module-name>MasterWebPortal.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>ThundercatCookieName</name>
 <xpath>/weblogic-web-app/session-descriptor/cookie-name</xpath>
</variable-assignment>
<variable-assignment>
 <name>ThundercatCookieDomain</name>
 <xpath>/weblogic-web-app/session-descriptor/cookie-domain</xpath>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
We've tried a lot of combinations of namespaces and such to try and get it to work, and it always spits out the same error....
Thanks,
Tim

Hi Folks -
Below is the weblogic.xml (or at least one version of it).
We're trying to override the session-descriptor cookie-name and cookie-domain ...
Thanks!!
Tim
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
<context-root>home</context-root>
<jsp-descriptor>
<page-check-seconds>-1</page-check-seconds>
<precompile>true</precompile>
<precompile-continue>true</precompile-continue>
<verbose>false</verbose>
<print-nulls>false</print-nulls>
</jsp-descriptor>
<session-descriptor>
 <cookie-name>JSESSIONID_THUNDERCAT</cookie-name>
 <cookie-domain>.tservicesq.com</cookie-domain>
</session-descriptor>
<library-ref>
<library-name>wlp-tools-visitor-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-commonui-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-services-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-framework-full-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>p13n-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>beehive-controls-1.0-war</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>weblogic-controls-1.0-war</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-wsrp-producer-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-lookandfeel-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-light-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-framework-common-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>wlp-framework-struts-1.2-web-lib</library-name>
<specification-version>9.2.0</specification-version>
<implementation-version>9.2.1</implementation-version>
</library-ref>
<library-ref>
<library-name>struts-1.2</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>wls-commonslogging-bridge-war</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>jstl</library-name>
<specification-version>1.1</specification-version>
<implementation-version>1.1.2</implementation-version>
</library-ref>
<library-ref>
<library-name>beehive-netui-resources-1.0</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>beehive-netui-1.0</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.0</implementation-version>
</library-ref>
<library-ref>
<library-name>QwestCmsLibrary</library-name>
<specification-version>1.0</specification-version>
<implementation-version>1.3.4.2</implementation-version>
</library-ref>
<library-ref>
<library-name>SIWebPortal.war</library-name>
</library-ref>
<library-ref>
<library-name>StylesWebPortal.war</library-name>
<specification-version>2.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>ShopWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>ProfileWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>CommonsWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>EBillWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>EPayWebPortal.war</library-name>
<specification-version>1.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
<library-ref>
<library-name>AdminWebPortal.war</library-name>
<specification-version>2.0.0</specification-version>
<implementation-version>1.0.0</implementation-version>
</library-ref>
</weblogic-web-app>

Env-entry from web.xml not in generated plan.xml

Hello,
Recently I migrated a JDeveloper 10.1.3.4 project to 11.1.1.3 and from there to 11.1.2.4. When I deploy this project to an 10.3.5. weblogic server then the 'env-entry' entires in the web.xml are not available on the application server.
Even when i use weblogic.PlanGenerator with the -all option to create a plan.xml from the WAR-file the env-enties are not found.
The web.xml is like this:
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
id="WebApp_ID" version="2.5">
<listener>
<listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
</listener>
<servlet>
<servlet-name>jaxrpc</servlet-name>
<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>VersionServlet</servlet-name>
<servlet-class>nl.deltalloyd.alfa.keten.version.VersionServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>VersionServlet</servlet-name>
<url-pattern>/version</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>jaxrpc</servlet-name>
<url-pattern>/RelatieSoapHttpPort</url-pattern>
</servlet-mapping>
<jsp-config/>
<security-role>
<role-name>Administrators</role-name>
</security-role>
<resource-ref>
<res-ref-name>jdbc/AlfaDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<env-entry>
<env-entry-name>appl/version</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>2013.06</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/releasedate</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>13-06-2013</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/loglevel</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>INFO</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>appl/omgeving</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
<env-entry>
<env-entry-name>service/case</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>http://test.services.intranet.company.nl/GixoCaseWeb/services/CaseServiceHttp</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>mqueue/rc/host</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>nl001wwavm058.ad.intra</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>mqueue/rc/port</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>1414</env-entry-value>
</env-entry>
</web-app>
Maybe I missed something in the migration path. Can someone please help me.
With kind regard,
Martin

Let me describe my case in few more words...
I have some kind of client-server app. Clients have OC4J installed and they download myApp.ear and myApp_plan.dat files and by using script (Windows CMD batch file) clients install those files with admin_client.jar, OC4J's admin utility. The problem is that I have 2 different types of clients and I have client specific settings set in web.xml file and each time I compile myApp.ear I have to uncomment/comment some lines in web.xml.
So, to make a long story short, I need a way to deploy those settings separated from (outside of) myApp.ear. By following you link, I have read that orion-web.xml should reside inside WEB-INF folder of myApp.ear, which is not good for me.

Oracle BAM Deployment Plan XML

Hi All,
The BAM adapter is not properly deployed on the WebLogic Server. It is showing status as prepared. I checked the BAM Adapter properties and found that the Plan.xml it was referencing is not present in the speified location. My question are
1) How will I generate a new Plan.xml for the BAM Adapter and will it contain all the configurations in it.
2) Also, can I copy the Plan.xml for OracleBAMAdapter.rar from some other WebLogic server and just change the connection details. Will it work?
Regards
Thomas

Hi,
Please find my responses below
1) How will I generate a new Plan.xml for the BAM Adapter and will it contain all the configurations in it.
When you create a new connection factory or modify the existing connection factory then the weblogic console creates the plan.xml to store your configurations. The configuration is effective after you restart the server.
2) Also, can I copy the Plan.xml for OracleBAMAdapter.rar from some other WebLogic server and just change the connection details. Will it work?
It may not work if you have not linked the OracleBAMAdapter with plan.xml that gets generated in step 1. After the plan.xml gets generated then you can compare and ensure to try out if you can replace with some other file. I have not done this before.
Thanks,
Ritesh

Plan.xml download

Hi,
The plan.xml got deleted from the server by mistake. Is there any place I can download the file and place it in the server required location?
Regards,
Aasta.

which version of soa suite??
redeploy the rar file and update to generate a plan.xml
and remember if you are using a clustered environment.Plan.xml does not get automatically copied to other managed servers you have to manually copy it to other managed servers.
for now i suggest you to redeploy and update

Overriding web.xml using Plan.xml

Hi,
I want to override certain values (MAX_ROW_FETCH_SIZE) in web.xml using Plan.xml for a servlet deployed on weblogic server.
My web.xml looks like this.
<?xml version = '1.0' encoding = 'windows-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
 version="2.5">
<servlet>
 <servlet-name>trial</servlet-name>
 <servlet-class>oracle.apps.cmi.sv.fwk.webui.trial</servlet-class>
 <init-param>
 <param-name>MAX_ROW_FETCH_SIZE</param-name>
 <param-value>50</param-value>
 </init-param>
 <init-param>
 <param-name>JDBC_MAX_FETCH_SIZE</param-name>
 <param-value>20</param-value>
 </init-param>
</servlet>
<servlet-mapping>
 <servlet-name>trial</servlet-name>
 <url-pattern>/trial</url-pattern>
</servlet-mapping>
</web-app>
My Plan.xml looks 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>SPUF</application-name>
<variable-definition>
 <variable>
 <name>SessionDescriptor_timeoutSecs_13708393894780</name>
 <value>3602</value>
 </variable>
 <variable>
 <name>MAX_ROW_FETCH_SIZE</name>
 <value>3</value>
 </variable>
 <variable>
 <name>JDBC_MAX_FETCH_SIZE</name>
 <value>2</value>
 </variable>
</variable-definition>
<module-override>
 <module-name>SPUF.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>SessionDescriptor_timeoutSecs_13708393894780</name>
 <xpath>/weblogic-web-app/session-descriptor/timeout-secs</xpath>
 </variable-assignment>
 </module-descriptor>
 <module-descriptor external="false">
 <root-element>web-app</root-element>
 <uri>WEB-INF/web.xml</uri>
 <variable-assignment>
 <name>MAX_ROW_FETCH_SIZE</name>
 <xpath>/web-app/servlet/init-param/[param-name="MAX_ROW_FETCH_SIZE"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
 <variable-assignment>
 <name>JDBC_MAX_FETCH_SIZE</name>
 <xpath>/web-app/servlet/init-param/[param-name="JDBC_MAX_FETCH_SIZE"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
 </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>/home/oracle/ebssdk2</config-root>
</deployment-plan>
I can see new value reflected for "Session TimeOut" for service configuration.
However when I use service to query certain data while considering "MAX_ROW_FETCH_SIZE" parameter, It is still querying 50 rows (Value in web.xml) at a time instead of 3 (As defined in Plan.xml)
I am using servlet init method to get init parameters in my java file.
Can someone help me to overcome from this issue or have any suggestion?

You could use Apache Ant and create 2 separate WAR files , one for development and one for production.
Normally I don't create a WAR file for the development environment. WAR file is made only for production.
This is how my Ant task runs currently.
1) For the development environment the ant task runs only to compile Java classes and nothing else, web.xml is that for development environment.
2) When the app is ready for production , I run Ant to copy all files from my dev folder to a temporary build folder - during this copy I filter out the .java files (since there's no longer a need for them in production) only class files are moved.
3) Then I treat the above temporary folder as the source folder, and run the Jasper pre-compiler which significantly alters the web.xml file .
But the good part is that my original development web.xml stays unaltered since it is in it's own folder.
4) Then finally I run a WAR task on the processed contents of the temporary build folder which contains the modified web.xml
This way each environment has it's own web.xml .

Defining application-scoped work manager in Plan.xml

I am having trouble getting my MDBs to recognize work managers that I have defined in my deployment plan using the admin console.
The work managers show up properly when I click the deployed application and go to the Deployments->myapp.ear->Configuration->Workload tab. They do not show up, however on the Deployments->myapp.ear->Monitoring->Workload tab.
Also, when the server boots, I get a log message like this:
<BEA-002919> <Unable to find a WorkManager with name FaxErrorQueue. Dispatch policy FaxErrorQueue will map to the default WorkManager for the application care360-backend-app-2008>even though FaxErrorQueue shows up under Configuration->Workload.
BACKGROUND
I am upgrading an 8.1 wls to 10MP1. Our MDBs are deployed as a single jar, included in 2 separate ears, which are deployed to 2 separate clusters. So, if we have 2 clusters with 2 managed servers in each cluster, we deploy each MDB to all 4 servers. We control the Execute Queues for each server in 8.1 with different values so that MDB#1 might have a single thread in one managed server and zero execute threads on another. Using the deployment plan is the only way I can think of to implement this. We would prefer not to use the 8.1 emulation, as the deprecated execution queues will have to be dealt with eventually. I am open to any other approaches to accomplish this as well.
Thanks,
Joe

Hello Fred,
Thank you very much for reply.
I totally agree with you but in my scenario, I have multiple domains on a single box.
and I am afraid that there could be a situation where one bad application of a particular domain may take most of the CPU usages.
What I can do is: I can define max thread constrain to all the applications of all the domains but it is not acceptable bcz we have hundreds of applications per domain.
So what I want is: to define some kind of thread constrain at the domain level [so that I can have CPU usages allocated to every domain] as well as some kind of thread constrain to few applications [non prioritize].
I tried this by defining Global Work Managers & Application-scoped Work Managers but I found that applications only respect to Application-scoped Work Managers.
or if I have some kind of way that make sure certain percentage of CPU usages is allocated to a particular domain?
hope I have made my self clear.
Thanks,
Qumar

Plan.xml instead manifest.mf

Hi. prompt, how use plan.xmk instead manifest.mf for numbering application version?

Not sure that is possible as the version is a part of the manifest file. However, you may use the plan to modify it.
Timo

Replacing web.xml values with a deployment plan. Not working on WL 10.3.2

Hi All-
I am trying to replace a value from web.xml with one in a weblogic deployment plan. I deployed the application on WL 10.3.2 and used the deployment plan below. No matter what I do it doesn't seem to want to take the value.
web.xml:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<context-param>
<param-name>TokenGroup</param-name>
<param-value>oldvalue</param-value>
</context-param>
</web-app>
Deployment Plan:
<?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"
global-variables="false">
<application-name>APPName</application-name>
<variable-definition>
<variable>
<name>TokenGroup</name>
<value>Key123456</value>
</variable>
</variable-definition>
<module-override>
<module-name>APPName.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>TokenGroup</name>
<xpath>/web-app/context-param/[param-name="TokenGroup"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
I've also tried other formats for the xpath such as:
/web-app/context-param/{param-name="TokenGroup"}/param-value
/web-app/context-param[param-name="TokenGroup"]/param-value
Any ideas why this doesnt work?
Thanks,
Joe

"web.xml"
<?xml version='1.0' encoding='WINDOWS-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<context-param>
<param-name>name</param-name>
<param-value>Joe</param-value>
</context-param>
<context-param>
<param-name>password</param-name>
<param-value>password</param-value>
</context-param>
<servlet>
<servlet-name>ParameterServlet</servlet-name>
<servlet-class>ParameterServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ParameterServlet</servlet-name>
<url-pattern>/ParameterServlet</url-pattern>
</servlet-mapping>
</web-app>
ParameterServlet
import java.io.IOException;
import javax.servlet.ServletConfig;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.ServletOutputStream;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class ParameterServlet extends HttpServlet {
private String dbName = "";
private String dbPassword = "";
public void init(ServletConfig config) throws ServletException {
super.init(config);
ServletContext context = getServletContext();
dbName = context.getInitParameter("name");
dbPassword = context.getInitParameter("password");
public void doGet(HttpServletRequest req, HttpServletResponse res)
throws IOException {
ServletOutputStream out = res.getOutputStream();
res.setContentType("text/html");
out.println("<html><head><title>Basic Servlet</title></head>");
out.println("<body>Database username is " + dbName);
out.println(" Database password is " + dbPassword + "");
out.println("</body></html>");
"Plan.xml"
<?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" global-variables="false">
<application-name>virtual</application-name>
<variable-definition>
<variable>
 <name>name</name>
 <value>akshay1</value>
 </variable>
 <variable>
 <name>password</name>
 <value>koul1</value>
 </variable>
</variable-definition>
<module-override>
<module-name>virtual</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
 <variable-assignment>
 <name>name</name>
 <xpath>/web-app/context-param/[param-name="name"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
 <variable-assignment>
 <name>password</name>
 <xpath>/web-app/context-param/[param-name="password"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
</module-descriptor>
</module-override>
<config-root>C:\DOCUME~1\user\LOCALS~1\Temp\user\.\config\deployments\virtual\plan</config-root>
</deployment-plan>
It works for me... I think your "web.xml" is causing the issue.
Try replacing
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
with
<?xml version='1.0' encoding='WINDOWS-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Hope this helps.
-Akshay

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)

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 :)

Need to generate a Index xml file for corresponding Report PDF file.

Need to generate a Index xml file for corresponding Report PDF file.
Currently in fusion we are generating a pdf file using given Rtf template and dataModal source through Ess BIPJobType.xml .
This is generating pdf successfully.
As per requirement from Oracle GSI team, they need index xml file of corresponding generated pdf file for their own business scenario.
Please see the following attached sample file .
PDf file : https://kix.oraclecorp.com/KIX/uploads1/Jan-2013/354962/docs/BPA_Print_Trx-_output.pdf
Index file : https://kix.oraclecorp.com/KIX/uploads1/Jan-2013/354962/docs/o39861053.out.idx.txt
In R12 ,
 We are doing this through java API call to FOProcessor and build the pdf. Here is sample snapshot :
 xmlStream = PrintInvoiceThread.generateXML(pCpContext, logFile, outFile, dbCon, list, aLog, debugFlag);
 OADocumentProcessor docProc = new OADocumentProcessor(xmlStream, tmpDir);
 docProc.process();
 PrintInvoiceThread :
 out.println("<?xml version=\"1.0\" encoding=\"UTF-8\" ?>");
 out.print("<xapi:requestset ");
 out.println("<xapi:filesystem output=\"" + outFile.getFileName() + "\"/>");
 out.println("<xapi:indexfile output=\"" + outFile.getFileName() + ".idx\">");
 out.println(" <totalpages>${VAR_TOTAL_PAGES}</totalpages>");
 out.println(" <totaldocuments>${VAR_TOTAL_DOCS}</totaldocuments>");
 out.println("</xapi:indexfile>");
 out.println("<xapi:document output-type=\"pdf\">");
out.println("<xapi:customcontents>");
XMLDocument idxDoc = new XMLDocument();
idxDoc.setEncoding("UTF-8");
((XMLElement)(generator.buildIndexItems(idxDoc, am, row)).getDocumentElement()).print(out);
idxDoc = null;
out.println("</xapi:customcontents>");
 In r12 we have a privilege to use page number variable through oracle.apps.xdo.batch.ControlFile
 public static final String VAR_BEGIN_PAGE = "${VAR_BEGIN_PAGE}";
 public static final String VAR_END_PAGE = "${VAR_END_PAGE}";
 public static final String VAR_TOTAL_DOCS = "${VAR_TOTAL_DOCS}";
 public static final String VAR_TOTAL_PAGES = "${VAR_TOTAL_PAGES}";
Is there any similar java library which do the same thing in fusion .
Note: I checked in the BIP doc http://docs.oracle.com/cd/E21764_01/bi.1111/e18863/javaapis.htm#CIHHDDEH
 Section 7.11.3.2 Invoking Processors with InputStream .
But this is not helping much to me. Is there any other document/view-let which covers these thing .
Appreciate any help/suggestions.
-anjani prasad
I have attached these java file in kixs : https://kix.oraclecorp.com/KIX/display.php?labelId=3755&articleId=354962
PrintInvoiceThread
InvoiceXmlBuilder
Control.java

You can find the steps here.
http://weblogic-wonders.com/weblogic/2009/11/29/plan-xml-usage-for-message-driven-bean/
http://weblogic-wonders.com/weblogic/2009/12/16/invalidation-interval-secs/

Catching an error from the component level in a plan?

I have components that installs a software package (using the LINUX rpm install plugin). These components are called in sequence from an SPS
"Plan". If any one of the rpm's to be installed by the plan might already have been installed, the rpm exits with an error message and a "1" exit code.
That exit, causes the whole install to stop dead in its tracks.
I have tried a "try and catch" to be allow the installation to continue
when that situation exists. Howvever, at the "Plan" level all I can catch is
any error. If a bad error; that is one that is not an "Exit 1" because the
rpm was already installed, but rather something that needs to stop the
entire plan ... the "catch" will ignore those errors as well.
Without modification of the SUN component install plugin, how in XML does one know what the exit code is from the install plugin
(a) within the component that calls the install plugin
(b) insde the plan XML that calls the component XML that calls the plugin
Are there global variables, passed return codes, inherited parameters or something that facilitates the passing of exit codes from plug-in to XML component to XML plan?

Hi,
Hope you have gone through the mentioned Notes for the pre-requisites. I checked the second Note which shows New and can not be implemented.
You can check whether the similar Notes have already been implemented in your system. Check with your BASIS team
Regards,
Suman
Edited by: Suman Chakravarthy on Sep 11, 2011 11:59 AM

Plan.xml

Similar Messages

Maybe you are looking for