Changing context root

I know how to change context root inside Jdeveloper but I couldnt find any way to modify it outside Jdeveloper. like I changed application.xml and weblogic.xml but not successful.
I am using Jdev 11.1.2.2 and Ojdeploy for creating ear file

Hi,
Try changing in uiProjectName.jpr
you will find tag like <value n="contextRoot" v="SampleApp"/>
Edited by: Naresh on Mar 21, 2013 8:00 AM

Similar Messages

  • Help me! Change Context root in weblogic portal 10.3.2

    I has a desktop in weblogic portal with path is: http://localhost:7001/ABC/appmanager/t1/home , I want to change the string ABC => Portal with new is the path: http://localhost:7001/Portal/appmanager/ v1/home How to configuration? I need config file? .The users help to resolve the problem this
    Thanks you very much! Hoping to replay soon!!!

    Thanks Sanjeev Kumar has replay topic!
    I have followed your instructions by: replace <display-name>Portal</display-name> in web.xml and <wls:context-root>Portal</wls:context-root> in weblogic.xml , then I redeploy up server portal weblogic then runing path new is http://localhost:7001/Portal/appmanager/t1/home , throw error:
    Resource /t1/home could not be resolved for locale null. I think problem related to database when I create desktop. I view database see context root ABC resource in PF_Desktop_instance and PF_Desktop_Defination.How to update name colum WebApp in two table?
    Thanks you very much! Hoping to replay soon!!!
    Edited by: 890028 on Feb 15, 2012 11:12 PM

  • Deploy given EAR file having application.xml and change context-root

    hi
    Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
    For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
    Given documentation appendix B section "context-root" [3] saying
    "... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
    and documentation section "Typical Deployment Configuration Workflows" [4] saying
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
    Some observed behaviour:
    - scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
    - scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
    The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
    "Remove the META-INF/application.xml DD from the EAR"
    - scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
    - scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
    One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
    Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
    So ...
    - (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
    - (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
    Seems like a simple goal, but I must be missing something that is required to achieve it.
    - [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
    - [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
    many thanks
    Jan Vervecken

    Thanks for your reply René van Wijk.
    René van Wijk wrote:
    You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
    Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
    "/application/module/web[web-uri/text()="WebProject.war"]/context-root"
    But, that didn't work.
    Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
    "/application/module[id="WebProject"]/web/context-root"
    - scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
    So, it does not seem to work.
    ... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
    ... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
    Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
    "java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
    Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
    - [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
    regards
    Jan Vervecken

  • 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
    &lt;?xml version='1.0' encoding='UTF-8'?&gt;
    &lt;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"&gt;
    &lt;application-name&gt;BrowserR08.003&lt;/application-name&gt;
    *&lt;variable-definition&gt;*
    * &lt;variable&gt;*
    * &lt;name&gt;CONTEXTROOT&lt;/name&gt;*
    * &lt;value&gt;BrowserWeb/servlet/BrowserServlet&lt;/value&gt;*
    * &lt;/variable&gt;*
    * &lt;/variable-definition&gt;*
    &lt;module-override&gt;
    &lt;module-name&gt;BrowserWeb.war&lt;/module-name&gt;
    &lt;module-type&gt;war&lt;/module-type&gt;
    &lt;module-descriptor external="true"&gt;
    &lt;root-element&gt;weblogic-web-app&lt;/root-element&gt;
    &lt;uri&gt;WEB-INF/weblogic.xml&lt;/uri&gt;
    &lt;hash-code&gt;1231953167814&lt;/hash-code&gt;
    *&lt;variable-assignment&gt;*
    * &lt;name&gt;CONTEXTROOT&lt;/name&gt;*
    * &lt;xpath&gt;/weblogic-web-app/context-root&lt;/xpath&gt;*
    * &lt;operation&gt;add&lt;/operation&gt;*
    * &lt;/variable-assignment&gt;*
    &lt;/module-descriptor&gt;
    &lt;module-descriptor external="false"&gt;
    &lt;root-element&gt;web-app&lt;/root-element&gt;
    &lt;uri&gt;WEB-INF/web.xml&lt;/uri&gt;
    &lt;/module-descriptor&gt;
    &lt;module-descriptor external="true"&gt;
    &lt;root-element&gt;wldf-resource&lt;/root-element&gt;
    &lt;uri&gt;META-INF/weblogic-diagnostics.xml&lt;/uri&gt;
    &lt;/module-descriptor&gt;
    &lt;/module-override&gt;
    &lt;config-root&gt;/export/home1/tecapp/BrowserR08.003/plan&lt;/config-root&gt;
    &lt;/deployment-plan&gt;
    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 --&gt; MyApp --&gt; 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 &lt;-- 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 :)

  • How to change data source name and context root during deployment

    Hi,
    Env:
    WLS 10.1.3
    JDev 11.1.1.6
    Hudson
    I need to deploy two instances of my ADF application on the same development enviroment. We are using Hudson to deploy. My question is how to change data source name and application context root before second deployment.
    Kuba

    I don't believe there is an inbuilt facility to do this.
    Previously how I've done this is when checking files out using Hudson jovs, before the build I then use an Ant extension called XmlTask (http://www.oopsconsultancy.com/software/xmltask/) to modify the required XML files.
    Can I ask why you're doing this in the first place please? Multi-tenancy? 2 versions of the same app?
    CM.

  • Change the integrated deployment context root

    How do I change the context root of applications deployed with the integrated WLS instance? I created my own application.xml and put it in project_root/META-INF but this gets overwritten when the application is deployed.

    Hi,
    Ok, we know that it is easy to change the context-root as you explained from within jdev.
    My question is if I want to set the context-root to default "/ how can I do?
    Jdev dosen't accept to set the context-root to "/" (context root invalid) and if there is a valid context root it overwrites my application.xml when I deploy to ear.
    Any solution other that this workarround:
    after deploying to ear unzip it and change the application.xml to <context-root>/</context-root>
    Thanks
    Jamil
    Edited by: Jamil Nour on Feb 23, 2010 12:19 AM

  • Is it possible to change portal context root?

    Hi,
    how I can change portal context root from /portal to / ?
    Thanks.

    Do you use the webserver or the appserver?
    For the webserver: (assuming default paths)
    You probably can do this by editing:
    /opt/SUNWwbsvr/https-YOURSERVER/config/server.xml
    Try to add something along the following:
    <WEBAPP uri="/" path="/var/opt/SUNWps/https-YOURSERVER/portal/web-apps" enabled="true"/>
    For the appserver it is probably something similiar, please let me know if it works!

  • Changing Forms 11.1.2 context root

    Hello,
    We are currently planning a deployment that will end up with 6 physical servers running Forms 11.1.2 on them. We would like to make access to these servers available through a single url (ie www.something.com). We have tested and plan to use the nginx reverse proxy to serve up the 6 forms servers (we found it has much better performance than webcache). Now the problem we are facing is that each forms app is deployed under the /forms/ context root. This of course won't work for us since we need to differentiate each of the 6 servers. Our idea is to move the context root for each forms server to a something like /forms1/, /forms2/, etc.
    Basically each server will be under a different path on the same hostname
    http://www.something.com/forms1/frmservlet <- server 1
    http://www.something.com/forms2/frmservlet <- server 2
    http://www.something.com/forms3/frmservlet <- server 3
    http://www.something.com/forms4/frmservlet <- server 4
    http://www.something.com/forms5/frmservlet <- server 5
    http://www.something.com/forms6/frmservlet <- server 6
    So the question is what would be the simplest and most ideal way to change the context root of the forms application?
    Thanks in advance

    Well I work for a NASA contractor and with the downsizing of the space program I have to work with the hardware I have not what I'd like to have. I re-installed 11.1.2 just to make sure I hadn't done something wrong and I still don't have access to the Fusion Middleware Control (http://host:7001/em) I get a Error 404 so it may be the Windows XP issue that was mentioned. The strange thing is that I had installed 11.1.1.4 on a Windows XP PC about 6 months ago and it worked fine but due to the forementioned downsizing that PC was excessed so I had to start over and thought I'd use the current version.

  • How change programmatically war context root inside ear

    Hi,
    We have an ear application containing a war.
    We need to specify by code at runtime the war application context root WITHOUT specifiy it in web.xml or application.xml deployment descriptor.
    Is it possibile?
    thanks in advance for help

    I found it. It is in the edit descriptor of the ear file, not war file. Sorry about that. My mistake.

  • How to access static resources in ear without specifing context-root

    Hello, i have a problem with my ear.
    The war's structure is like this:
    ---/jsp
    ---/css
    ---/images/ViewRisposte.gif
    ---/xsl/Request.xsl
    ---/Common/data.xsl
    /error.xsl
    /input.xsl
    xsl files reference css and images files that are contained in css and images dir.
    I can't use the "../" to specify css and images path into xsl and jsp due to security policy setting on the Http server (and I can't change this policy).
    In the ear's application.xml is specified the context root of the module web with the name SABEARWeb
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <application>
    <display-name>SABEARWeb module</display-name>
    <module>
    <web>
              <web-uri>SABEARWeb.war</web-uri>
              <context-root>SABEARWeb</context-root>
         </web>
    </module>
    </application>
    For example with this following code (Request.xsl), how can i replace the "../" notation to access xsl and image resouces without write the context root? How i can insert the images and css references into xsl and jsp files?
    <xsl:import href="../Common/data.xsl" />
    <img align="center" width="20" src="../images/ViewRisposte.gif" id="viewXslRisp" title="Visualizza Risposta">...</img>
    Thanks a lot

    >>As I understand I should change View1 by handling command of button “Edit”, and then View 2 should be displayed, then I change data and then View1 should be updated. How to do it?
    For information about how to handle a command, please refer to my blog post:
    http://blog.magnusmontin.net/2013/06/30/handling-events-in-an-mvvm-wpf-application/
    You could bind the Command property of the edit button to an ICommand property of VMMain. When this command is executed you could then send a message using an event aggregator or some kind of messenger. Please refer to my blog post for more information about
    how to for example use Prism's event aggregator class to pass events between view model classes:
    http://blog.magnusmontin.net/2014/02/28/using-the-event-aggregator-pattern-to-communicate-between-view-models/
    Andy has written an example of how to use MvvmLight's Messenger class:
    http://social.technet.microsoft.com/wiki/contents/articles/26070.communicating-between-classes.aspx
    The concepts are the same but you will have to download and reference either Prism:
    https://www.nuget.org/packages/Prism/
    ...or MvvmLight: https://www.nuget.org/packages/MvvmLight/
    You then subcribe to this event or message in the main view model and change the value of the CurrentPageViewModel property whenever you recieve an event. Note that the class must implement the INotifyPropertyChanged interface and raise its PropertyChanged
    interface for this to work:
    https://msdn.microsoft.com/en-us/library/system.componentmodel.inotifypropertychanged%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396
    This is how you are supposed to communicate between different view model classes.
    Hope that helps.
    Please remember to close your threads by marking helpful as answer and then start a new thread if you have a new question.

  • HowTo: deploy an j2ee app using "/" as context root on iAS 6.5

    Hi all iAS expert
    It is highly appreciated one can teach me how to get around below problem
    l deployed an app using "/" as context root. But the iAS could respond to any HTTP request.
    However, as l changed the context root to sth other than root. iAS responded properly.
    Can someone help me get around this problem ?
    thank you a lot
    fox

    I deployed the same EJB on WLS 6.1+sp3 and WLS 7.0.
    These both work. Looks like there is some problem with WLS6.0+sp2. I have opened
    a case with BEA customer support.
    --Latha

  • Multiple war with same context root

    Dear all,
    I would like to know if it's possible to have several war in an EAR file with a same context root?
    I know that it is possible to have several war but I don't know if it's possible to share the same context root.
    The problem here is that the application on which we work is provided by another company, hence we have an original EAR containing the company war as well as the company EJB. As new versions of the application are delivered to us quite frequently, it's impossible to store the code developped by us in the EAR, as it is replaced in each delivery.
    Concerning our custom code, it is not a problem as we develop this code in a separated project which is included as a jar in the APP-INF/lib directory of the EAR file.
    But concerning the war it's an other problem. Indeed, we develop custom JSFs pages or javascript. These files are placed in the application war file which changes for each delivery.
    Thus, we would like to create an other war file which will contain all our custom pages and javascripts in order to be able, in each delivery, to fully replace the other war containing the company pages and javascripts. This would allow us to save time each time a new delivery is done.
    The important thing would be to keep the same context root for the two wars, enabling transparency for the application.
    Thanks for your help,
    Citrouille57

    Hello,
    this is possible in IBM Websphere via custom extension: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tprs_sharing_data.html
    I don't know if it's possible somewhere else.
    k.

  • Context-root ignored? (and documentation 404?)

    Hello,
    Q: How can I rename the webapp to 'testapp' if the webapp is in exploded
    format in a directory called 'test' ?
    (WLS always calls the webapp 'html' which I can't use because all of my
    webapps are in 'html' directories in CVS)
    I would like to use the context-root element of weblogic.xml.
    The online docs found here:
    http://e-docs.bea.com/wls/docs70/webapp/weblogic_xml.html#1037343
    contain 2 links (Two-Phase deployment and deloying WebLogic Server
    Applications). Both of these links are 404.
    Simply creating a simple weblogic.xml like this fails:
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA
    Systems, Inc.//DTD Web Application 7.0//EN"
    "http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd">
    <weblogic-web-app>
    <context-root>testapp</context-root>
    </weblogic-web-app>
    Because when I start WebLogic 7.0sp1 it ignores the context-root.
    WLS uses the URI instead and names the webapp as 'test'.
    (the webapp is in the test directory)

    you can try this command :
    java -jar admin.jar ormi://[host] [user admin] [password] -bindWebApp [application-deployment-name] [web-app-name] [web-site-name] [context-root]
    [application-deployment-name] is the name of your J2EE application (without extension .ear)
    [web-app-name] is the name of your war (without extension)
    [web-site-name] is generally http-web-site
    [context-root] =&gt; your new context root
    you have to do this command only once.
    admin.jar is located in j2ee/home directory of oc4j.
    PS: You can change manually the config file http-web-site.xml, located in j2ee/home/config :
    Just add this line
    &lt;web-app application="ear-name" name="war-name" root="/context-root" /&gt;

  • Context-root Problem

    The project I'm working on has just recently changed the context-root of the webapp from / to /grp. As the UI developer for this project, this seemingly small change has had a huge impact on my workload. All of the images, stylesheets and JavaScript files have absolute paths. For example, an image on the site would have the path
    /i/t.gif
    I'd like to know if there's a way to map /i to /grp/i without having to change every JSP in the webapp (~3000 files).
    I read about virtual-directory-mapping at http://e-docs.bea.com/wls/docs81/webapp/weblogic_xml.html#1039396 but that only seems to apply to a directory on the server and not within the WAR file itself.

    one solution for that is use a web server such i-planet that manage the static content.
    the location of static content must be independent of application.

  • Deploying 2 application of same context root

    Recently I deployed 2 applications in weblogic7 and weblogic8
    /usr2/applns_one --> dev
    /usr3/applns_one --> staging
    Here "applns_one" are the same in "/usr2 and /usr3" where "/usr2" is for dev and "/usr3" is for staging.
    I deployed both on the same instance or managed server of weblogic.
    first deployed app (/usr2) had a context root "/applns_one-1"
    Second deplyed app (/usr3) had a context root "/applns_one"
    After deployment I see 404 error for the URL which is accessing "/usr2" appln since its context root is "/applns_one-1".
    My issue is how can I deploy "/usr2/applns_one" and /usr3/applns_two" on the same managed server.
    Is there any workaround for this in weblogic.
    Thanks,

    If you're asking how can you deploy two applications to the same weblogic instance with the same context root, you just can't do that. There would be no point to that, as you'd only ever be able to access one of them. You'll need to change one of them.

Maybe you are looking for