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

Similar Messages

Changing the default deployment server.

Hi.
Is it possible to change the default deployment server in studio Creator? I�m developing some portlets, and on my computer it takes 3 minutes to deploy a new portlet to my local host, but only a few second to deploy it to a remote server.

Hi,
I guess, right now only way is to deploy to remote server( sun appserver and sun webserver) or export the WAR and deploy to any other web/app server
MJ

How do I change the order of context menu items in Private Windows?

In the context menu that appears when I right-click on a link, I prefer to have "Open Link in New Window" at the top of the menu instead of "Open Link in New Tab". I have added code to userChrome.css to make that switch:
#context-openlink {
-moz-box-ordinal-group: 1 !important;
#contentAreaContextMenu > * {
-moz-box-ordinal-group: 2;
Firefox version 20 added Private Browsing Windows. The above code still works for the non-Private windows, but doesn't affect the Private Windows, so in those I still have "Open Link in New Tab" at the top of the context menu, and "Open Link in New Private Window" as the second item. Is there a way to change the order of these menu items in Private Windows?

Clarification: In the code snippets above, the "1."s are supposed to be pound-signs; they got auto-reformatted incorrectly.

How to change the value of root-context in application.xml

Hi all,
I want to deploy an 1.4 application to SAP NetWeaver CE server. Since the name of my web-project is pretty long, I prefer to change the context-root atribute in the deployment-descriptor. Is that right that the context-root entry only can be the name of the web-project?
Everytime when I enter a value in the context-root tag, after saving the project, the value of context-root is automatically changed to the web-project name!
I would be very thankful for any suggestion!
Ali

Substitution strings are meant to be static, like global constants.
If you need some variable stuff, use application level items and set them using Application level computations/processes

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.

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.

Dot11Radio0 stuck in reset status after changing the station role

Hi Everyone.
I've got a AIR-AP1231G-A-K9 router. IOS has been upgraded to the latest version c1200-k9w7-mx.123-8.JED. Everything worked fine before I change the station role from root to repeater or workgroup bridge. Following is my configuration:
ap#sh run
Building configuration...
Current configuration : 1224 bytes
version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname ap
enable secret 5 $1$KHHu$bN/odUmHdmb.0cwa57GYs1
ip subnet-zero
no aaa new-model
dot11 syslog
dot11 ssid Lanyard
authentication open
username Cisco password 7 123A0C041104
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
ssid Lanyard
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
station-role root
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface BVI1
ip address 11.11.11.1 255.255.255.0
no ip route-cache
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip radius source-interface BVI1
bridge 1 route ip
line con 0
line vty 0 4
login local
line vty 5 15
login
end
ap#sh ip int bri
Interface IP-Address OK? Method Status Protocol
BVI1 11.11.11.1 YES NVRAM up up
Dot11Radio0 unassigned YES NVRAM up up
FastEthernet0 unassigned YES NVRAM up down
ap#
Then I changed the station role
ap#conf t
ap(config)#int dot 0
ap(config-if)#station-role repeater
ap(config-if)#end
ap#sh ip int brie
Interface IP-Address OK? Method Status Protocol
BVI1 11.11.11.1 YES NVRAM down down
Dot11Radio0 unassigned YES NVRAM reset down
FastEthernet0 unassigned YES NVRAM up down
ap#
Interface Dot11Radio0 stuck in reset. No matter I reload or powercycle the AP, I still get the same reset status on Dot11Radio0.
Please help! Any input will be appreciated.

In order to get either the repeater or the workgroup bridge functionality working, you would likely need to have a Cisco AP as root. This is because the repeater and workgroup-bridge functionalities require Cisco Aironet Information Element (IE), which requires a Cisco root AP. There is no standard for interoperability for these functionalities (not part of any 802.11 standards). You can always try to connect them, making sure that they are using the same authentication/encryption configuration. However, it is unlikely to work.

[SOLVED] changing the owner of /usr

after installing the arch successfully. i noticed that virtualbox does not work and gives a message about permission. i noticed that the ownership of /usr is not root. because i had this problem before on arch, i changed the ownership by "chown root:root /usr -R" .
Now i can not do su , mount a win drive ...... and get error for permission. How can i undo that command?????
Last edited by hadian (2013-10-06 12:59:44)

chown root:root /usr -R
I don't know what you have going on.
/usr should have been
ls -ld /usr
drwxr-xr-x 9 root root 4096 Aug 2 11:22 /usr
And su should be
ls -l /usr/bin/su
-rwsr-xr-x 1 root root 27496 Jul 31 08:15 /usr/bin/su
Did you remove suid on mount and su?
ls -l /usr/bin | grep rws
-rwsr-sr-x 1 daemon daemon 46064 May 12 09:31 at
-rwsr-xr-x 1 root root 55736 May 30 08:17 chage
-rwsr-xr-x 1 root root 23520 Jul 31 08:15 chfn
-rwsr-xr-x 1 root root 19360 Jul 31 08:15 chsh
-rwsr-xr-x 1 root root 44296 Jun 23 04:17 crontab
-rwsr-xr-x 1 root root 24000 May 30 08:17 expiry
-rwsr-xr-x 1 root root 31384 Jul 31 11:25 fusermount
-rwsr-xr-x 1 root root 69200 May 30 08:17 gpasswd
-rwsr-xr-x 1 root root 52104 Jun 10 01:46 ksu
-rwsr-xr-x 1 root root 40104 Jul 31 08:15 mount
-rwsr-sr-x 1 root root 39704 Jul 4 03:19 mount.cifs
-rwsr-xr-x 1 root root 10608 Jul 31 08:15 newgrp
-rwsr-xr-x 1 root root 47816 May 30 08:17 passwd
-rwsr-xr-x 1 root root 23304 Jun 14 09:57 pkexec
-rwsrwxr-x 1 root root 56464 May 29 23:31 rcp
-rwsrwxr-x 1 root root 52552 May 29 23:31 rlogin
-rwsrwxr-x 1 root root 52296 May 29 23:31 rsh
-rwsr-xr-x 1 root root 33272 May 30 08:17 sg
-rwsr-xr-x 1 root root 27496 Jul 31 08:15 su
-rwsr-xr-x 1 root root 129384 Jun 14 03:58 sudo
-rwsr-xr-x 1 root root 27544 Jul 31 08:15 umount
-rwsr-sr-x 1 root root 31344 May 19 10:04 unix_chkpwd
-rwsr-xr-x 1 root root 2133544 Sep 13 06:29 Xorg
EDIT:
Also everything in /usr isn't suppose to be owned by root
find /usr ! -user root
/usr/share/polkit-1/rules.d
/usr/bin/at
Last edited by teckk (2013-09-26 18:09:33)

Change the name of a field in the forms

Hello, experts:
As I can change the name of a field in the forms?
When you change the name of a field on the form, the field name in the database also changes?
Joan

Hello Joan:
If you mean the label of the form you can do with CTR + Double Click.
Remember not to change the integrity of the database. Is only allowed to user fields
make changes at the level of views, stored procedures, among others, which do not compromise the integrity of
data.
Remember, even if they change the label, has changed the field name in the database, only the presentation
the form.
Edwin Mauricio Nieto Leó

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

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.

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

Deploying application with several web modules having the same context root

Hi,
I would like to be able to deploy an application in Weblogic 12c having one ejb module and several web modules with the same context root. Even though the web modules have the same context root, each of them is deployed to a different virtual host.
Weblogic allows deploying the modules this way as long as their targets are different (i.e. each having a distinct virtual host). However this works only when I don't select a target for the .ear:
Component Type Current Targets
application.ear Enterprise Application (None specified)
application.jar EJB AdminServer
web1.war WEBAPP virtualHost1
web2.war WEBAPP virtualHost2
However if I select as target for the .ear to be AdminServer, the deployment doesn't work anymore, complaining that the context roots are in conflict.
If I remove web2.war from the .ear and deploy the .ear and .jar to AdminServer and web1.war to virtualHost1, the deployment works but the strange thing is that the web application can be accessed also through the AdminServer's main network channel, even though I would expect that it should be accessible only through virtualHost1 network channel. I believe this is the reason why there are context root conflicts when specifying a target for the .ear, because both wars are made accessible to the main network channel.
The reason why I want to keep the wars inside the same .ear is because I want to make them access the application's local EJBs (since as far as I know it's not possible to access a local EJB outside the application even if they belong to the same VM).
Is there a way to deploy the web modules only to the virtual hosts without being targeted to the main network channel?
Regards,
Alexandru

Murphy's Law: If anything can go wrong it will
A corollary to Murphy's law: When everything fails, read the manual.
Web application funda: Every web application must have its own context root. So, if wkfsocos is one
web application then, wkfsocos1 is another web application -
and hence must have its own context root.
Hello Aman,
If you are in E-Commerce version 4.0, then read this
[ISA_Buildtool document |https://service.sap.com/~sapdownload/011000358700001920472003E/ISA_BuildTool_10.pdf]
to create a copy of the application in its own context root.
From your URL pattern I guess you are in E-Commerce version 4.0.
If you are in E-Commerce 5.0 or above, then the
[Extension Guide |http://service.sap.com/~sapdownload/011000358700006120622006E/]gives steps to create a copy with its own context root for use in modification.
(See the chapter on - Creating a project specific Web Application with own context root )
Both these links require access to SAP Service Marketplace. You can also find the
documents through /instguides shortcut in Service Marketplace.
Easwar Ram
http://www.parxlns.com

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

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.

Change the integrated deployment context root

Similar Messages

Maybe you are looking for