Multiple context root

I would like to deploy the same application on 2 different context roots.
          Example: http://localhost/context1 and http://localhost/context2.
          Is there a way to do that in weblogic without redeploying the whole application?

Hi,
Yes, it can be done without redeploying the application again. You can changes the URL for the application and then run again.
Regards
Nitin Sarna

Similar Messages

How to configure multiple virtual hosts for the same context root /

Hi,
I am using Glassfish V1 U1 - b14 on Solaris.
I am trying to configure two applications to be mapped to the / root context, each one in its own virtual host.
Two things I have noticed:
1. I have to manually add virtual-hosts="hostId" in domain.xml/application-ref ... looks like just simply deploying the app does not do that although the application is set as default for its particular virtual host. Is this a bug?
2. Although I have set for each virtual host the default web-app correctly, and they both respond fine, I cannot map both of them to the / context. The second application (chronologically deployed) does not respond when called with the / context ....
Any ideas? Is this a bug again?
Regards,
Rares
Message was edited by:
raresp

Wow, that's a shame. All mighty Application Server and two different apps on two different virtual hosts are considered ambiguous to have the same context root definition.... Fair play to Tomcat and 90% of the rest of servlet containers!
In my case I have the same EAR we are planning to deploy to many (up to 30) virtual hosts. Faking different context roots for each deployment will bring unnecessary overheads...
Should I file a bug or feature request?
Thanks again for your answer, although you're basically saying it is not possible I will wait and look a while for a possible solution before bringing this topic to a conclusion.

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.

WebLogic 10.3 , ear file, application.xml only finds first context root

I just can't find out what this is. I have two web service projects (JAX-WS) and am trying to put them in an .ear file to deploy to WebLogic 10. Normally, this is done by creating an .ear with both projects .war files in it and an application.xml file in the META-INF directory that defines the context-root for each .war file. However, nothing I do for WebLogic 10 seems to work, it only see's the first context-root and sets that same context-root for both web services. I have verified this by switching the order in the application.xml file. Also, this exact same .ear file deploys to the Sun Enterprise Server (Glassfish) and acts correctly. Using a weblogic.xml file in each .war and deploying them individually they end up having the correct context root, just not from an .ear using application.xml. I even tried deleting the application.xml file and just having the weblogic.xml files in each .war define the context root and it still only came up with one context root for both. It's as if only one context root is allowed in an .ear for WebLogic 10, which can't be correct as we are doing this on WebLogic 9.2 (JAX-RPC) with multiple .war files in an ear.

Hi,
Try to increase severity of the server logging to avoid more logging.
Avoid Debugs and and info and better select the severity to notice which will avoid more logging.
Regards,
Kal

Same context root conflict.

I'm try to run multiple instances of an application running on the same box (each on their own managed server) but use the same context root (/servlet)
e.g.
server1 -> /app -> /servlet
server2 -> /app2 -> /servlet
Currently how I do it is give each of them their own servlet name, e.g
server1 -> /app -> /servlet
server2 -> /app2 -> /servlet2
I'm trying to make the urls for each instance as simple as possible. I can already see potential instances where the server#, app#, and servlet# would all be different numbers.
If I set them to both servlet weblogic throws me this error:
Exception:weblogic.management.ApplicationException: prepare failed for app2 Module: app2 Error: Context path '/servlet/' is already in use by the module: app application: app
* [Deployer:149033]preparing application app2 on server2
* [Deployer:149033]failed application app2 on server2
* [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application app2 on server2.: Exception:weblogic.management.ApplicationException: prepare failed for app2 Module: app2 Error: Context path '/servlet/' is already in use by the module: app application: app.
Any help that you can provide will be greatly appreciated.

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.

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

ASA5540 in multiple-context SNMP/icmp doesn´t work

Hi there,
     I need some help in order to understante what´s going on with an asa540 configure in multiple-context mode.
     I Have a cacti server on my lan and now I´m try to monitoring the interface with snmp. When I try to get this information returns the error message:
     CISCOASA/CONTEXTA#
     JUN 11 2013 01:52:00: %ASA-1-1-6021: Deny UDP reverse path check from 10.6.6.6 to IP_SRV_CACTI on interface inside
    JUN 11 2013 01:52:01: %ASA-1-1-6021: Deny UDP reverve path check from 10.6.6.6 to IP_SRV_CACTI on interface inside
     If I try to ping returns the same error:
     CISCOASA/CONTEXTA#
     JUN 11 2013 01:56:09: %ASA-1-1-6021: Deny icmp reverse path check from 10.6.6.6 to IP_SRV_CACTI on interface inside
    Following attached the conf of my asa
My question is Why I can´t ping or even use snmp ???
   If anyone could me help with a tip or a document about it ...
   My best regards
   Adriano

CISCOASA/CONTEXT# packet-tracer input inside icmp 10.132.0.25 8 0 10.6.72.2
Phase: 1
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit Rule
Additional Information:
MAC Access list
Phase: 2
Type: FLOW-LOOKUP
Subtype:
Result: ALLOW
Config:
Additional Information:
Found no matching flow, creating a new flow
Phase: 3
Type: ROUTE-LOOKUP
Subtype: input
Result: ALLOW
Config:
Additional Information:
in   10.6.72.2       255.255.255.255 identity
Phase: 4
Type: ROUTE-LOOKUP
Subtype: input
Result: ALLOW
Config:
Additional Information:
in   IP_SRV_HSLCACTIP01 255.255.255.255 inside
Phase: 5
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit Rule
Additional Information:
Phase: 6
Type: IP-OPTIONS
Subtype:
Result: ALLOW
Config:
Additional Information:
Phase: 7
Type: INSPECT
Subtype: np-inspect
Result: ALLOW
Config:
Additional Information:
Phase: 8
Type: INSPECT
Subtype: np-inspect
Result: ALLOW
Config:
Additional Information:
Phase: 9
Type: FLOW-CREATION
Subtype:
Result: ALLOW
Config:
Additional Information:
New flow created with id 453866627, packet dispatched to next module
Phase: 10
Type: ROUTE-LOOKUP
Subtype: output and adjacency
Result: ALLOW
Config:
Additional Information:
found next-hop 0.0.0.0 using egress ifc identity
adjacency Active
next-hop mac address 0000.0000.0000 hits 22196
Result:
input-interface: inside
input-status: up
input-line-status: up
output-interface: inside
output-status: up
output-line-status: up
Action: allow
Route information:
route inside 10.132.0.0 255.255.252.0 10.6.72.1 1
route inside IP_SRV_HSLCACTIP01 255.255.255.255 10.6.72.1 1
CISCOASA/CONTEXT# sh route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       * - candidate default, U - per-user static route, o - ODR
       P - periodic downloaded static route
Gateway of last resort is 200.206.50.233 to network 0.0.0.0
C    200.206.50.232 255.255.255.248 is directly connected, outside
S    10.132.0.0 255.255.252.0 [1/0] via 10.6.72.1, inside
S    IP_SRV_HSLCACTIP01 255.255.255.255 [1/0] via 10.6.72.1, inside
S*   0.0.0.0 0.0.0.0 [1/0] via 200.206.50.233, outside
Regards,

Mapping of Web App context root and the physical directory of the web app

I'm running Weblogic 7.0 on Windows2000.The physical directory of my web application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directory I have
my JSPS, static HTML and WEB-INF. I define the context path of this web app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be created manually
also), the following entry gets inserted in the server's config.xml ,-
<Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the container knows
that for any request for the web app with context path as 'testapp', it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. In the above
process, nowhere such mapping is specified. I expected something like Tomcat's
server.xml, where in docbase we clearly specify this mapping between the context
path and the physical directory. Please help.

Let me give some more details and hopefully this will make things clearer.
Say you deploy /foo/bar/myweb.war and in myweb.war you configure a
context-root of /rob
During deployment, the server creates an ApplicationMBean with a path of
/foo/bar/. It then creates a WebAppComponent with a uri of myweb.war.
Next, deployment calls back on the web container and tells it to deploy
the WebAppComponent. The web container reads the myweb.war, parses
descriptors etc. The web container then updates its data structures to
register that myweb.war has a context path of /rob. (It has to figure
out all the other servlet mappings as well.)
When a request for /rob/foo comes in, the web container consults its
data structures to determine which webapp and servlet receives the
request. This is not a linear search of all webapps and servlets.
There's much better ways to do pattern matching.
Hope this clears things up. Let me know if you still have questions.
-- Rob
Arindam Chandra wrote:
Thanks for the answer. Still one thing is not clear. Whatever context path I declare
for my web app as the value of <context-root> element in the weblogic.xml (in
my example it's "/testapp"), it is no where mapped with the "URI" attribute (or
any other attribute, sub-element whatsoever in the <Application> element).
Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
So when a request of the form http://myweblogic.com:7001/testapp/... arrives at
the server, how does the server knows that it has to serve this request with files
from D:\WL8\weblogic81\TestDeploy\build\TestWebApp ? It should not be like the
web container iterates thru all the web application entries in config.xml and
tries to match with one context-root declaration. I repeat, I expected some mapping
similar to Tomcat's server.xml, where in the <docbase> element u clearly specify
the mapping between the context path and the physical directory
Rob Woollen <[email protected]> wrote:
Arindam Chandra wrote:
I'm running Weblogic 7.0 on Windows2000.The physical directory of myweb application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directoryI have
my JSPS, static HTML and WEB-INF. I define the context path of thisweb app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be createdmanually
also), the following entry gets inserted in the server's config.xml,-
<>So the server will look for your web application at the Application Path
(D:\WL8\weblogic81\TestDeploy\build|) + the web uri (TestWebApp). So
it
maps the context-root you've specified /testapp to that path.
It's a little clearer in the case where you had a full-fledged EAR.
Then you'r application path would map to the "root" of the EAR, and the
uris would point to the various modules (eg webapps.)
-- Rob
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the containerknows
that for any request for the web app with context path as 'testapp',it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. Inthe above
process, nowhere such mapping is specified. I expected something likeTomcat's
server.xml, where in docbase we clearly specify this mapping betweenthe context
path and the physical directory. Please help.

FYI: Extension Builder project w/ LCDS: channel-definition endpoint having context.root

This is an FYI of an issue and its workaround.
If developing a CS SDK Extension in Flash Builder / Extension Builder and the project is configured to use LCDS (LiveCycle DataServices), then if your services-config.xml contains Channel definitions having the variable {context.root} in the endpoint URL, then the following error will occur. This will happen even if you are not using that Channel in your Destination channel list.
The services-config.xml laid down when using LCDS integrated into ColdFusion has by default some channel definitions using context.root in the endpoint URLs.   This is how I encountered the issue. On the other hand, the free developer edition of LCDS on Tomcat puts down a services-config.xml that does not have any reference to {context.root} in channel definitions, so the problem will not be encountered there.
Since I was not using a context root (was using the default of just "/"), I commented out the offending channels in services-config.xml to resolve the issue. One could also leave the (unused) channel definitions and then remove the {context.root} part from the endpoint.
ERROR
The services configuration includes a channel-definition 'java-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
CHANNEL DEFINITION

        <channel-definition id="java-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint uri="http://{server.name}:{server.port}{context.root}/flex2gateway/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>

Make sure your context root is defined in the project properties. This is at "project/properties/Flex Server" from the menubar or package explorer context menu. Alternately, you can hardcode your context root in the services-config.xml file/channel definition.

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.

Remote Access VPN Support in Multiple Context Mode (9.1(2))?

Hi Guys,
I am currently running two Cisco ASA5520 (ASA Version: 9.1(2)) firewalls in Active/Standby failover and was contemplating the option of migrating my remote access VPN to these firewalls. However seeing that the new IOS now support mixed multiple context mode and dynamic routing. Is it safe to ask whether or not Remote Access VPN is now support in this IOS upgrade?
Multiple Context Mode New Features:
Site-to-Site VPN in multiple context mode | Site-to-site VPN tunnels are now supported in multiple context mode.
New resource type for site-to-site VPN tunnels | New resource types, vpn other and vpn burst other, were created to set the maximum number of site-to-site VPN tunnels in each context.
Dynamic routing in Security Contexts | EIGRP and OSPFv2 dynamic routing protocols are now supported in multiple context mode. OSPFv3, RIP, and multicast routing are not supported.
New resource type for routing table entries | A new resource class, routes, was created to set the maximum number of routing table entries in each context. We modified the following commands: limit-resource, show resource types, show resource usage, show resource allocation. We modified the following screen: Configuration > Context Management > Resource Class > Add Resource Class.
Mixed firewall mode support in multiple context mode | You can set the firewall mode independently for each security context in multiple context mode, so some can run in transparent mode while others run in routed mode. We modified the following command: firewall transparent. You cannot set the firewall mode in ASDM; you must use the command-line interface. Also available in Version 8.5(1).
Regards,
Leon

Hey Leon,
According to the ASA 9.1 Configuration Guide, Remote Access VPN is not yet supported with version 9.1(2). Only Site-to-Site VPN support in multiple context was introduced with release ASA 9.0(x). This was mentioned in the 9.0(x) release notes.
Regards,
Dennis

How to map a url that does not match with the context root ?

does weblogic support url that does not match the context root ?
ex. the context root is AAA. the welcome page can be
retrieved using http://localhost:7001/AAA
Can it be configured to use http://localhost:7001/BBB to bring up the index.html in context root AAA ? if so, how ?

I agree with Imp68.
It still amazes me that in 2014 so many web sites are still not standards-compliant and instead insist on sniffing for the user-agent. And, in the majority of cases, I've found that the websites work fine with any modern browser.
phardell,
To be clear, Safari is not the problem, the website is! The developer of this website is still living in the 1990s and needs to move forward with the times. Imp68's suggestion will cause Safari to "pretend" to be whatever browser you wish. Try choosing "Safari 7" if that worked for you in the past and the website will likely go back to working. If that does not work then try choosing "Internet Explorer 10" from the menu and see if that works.
No matter what the result, you should look at the bottom of the page for a link to report problems with the website. Submit a comment that tells them that they need to "modernize your website to support all modern web browsers".
Good luck.

Problem using multiple contexts in same thread

Hello,
I am having problem using multiple contexts in the same thread. Here is the scenario:
front-end is calling a ejb1 with a user1 and password. Ejb1 is then calling ejb2
using user2 and password. I am getting security exception when calling ejb2 with
the message user1 is not authorized. Looking at the documentation, context 2 should
be pushed on stack on top of context 1 and context 2 should then be used until
context.close() is called. It looks like this is not the case in this scenario?
Regards,
Jeba Bhaskaran

I have the GTX670. So pretty much the same.
When I go to Edit>Preferences>Playback I see:
When I select the monitor I am not currently using for Premiere Pro, the Program Monitor shows up full size at 1920X1080 in that monitor.
While that may not help you, at least you know a similar card can do the job and you know that it should work.. What happens if you drop down to two monitors? Will it work then?
Also, have you performed the hack that allows Premiere Pro to use the card since that card is not in the file? I have no idea if that is relevant at all, by the way. It is just an attempt at getting our systems to work the same way.

Context root

How to fetch context root of web application from FacesContex?

Hi user,
        FacesContext ctx = FacesContext.getCurrentInstance();
        HttpServletRequest request = (HttpServletRequest)ctx.getExternalContext().getRequest();
        request.getContextPath();Regards,
Koen Verhulst

How can I get the web application's context root?

I have a web application, which is defined in Tomcat's server.xml:
<Context path="/cbes" docBase="e:\work\GM\code\CBESCurrency" debug="0"
reloadable="true" crossContext="false"/>
And I hava a servlet in this web application.
How can I get the context root of the web application?
in this example: reture should be "cbes" or "/cbes"
how?
thanks alot.

getContextPath() in javax.servlet.http.HttpServletRequest

Multiple context root

Similar Messages

Maybe you are looking for