Associating Default Web Application with Virtual Host

Hi
We are trying to run several virtual hosts on the same managed server. However, each of those virtual hosts (e.g. bob.mydomain.com, john.mydomain.com) will need to have a different default web application (the rest of the deployed web applications will be the same between hosts). We tried to create default web applications with <context-root> in weblogic.xml set to / (also tried "") - however when attempting to deploy 2nd default web app an error message comes up:
Context path '/""' is already in use
So, it appears that we can't associate a default web application with a virtual host. Any ideas on how to solve it?
Our Environment:
Weblogic version: 10.3 TP, Windows
Many thanks
Jason

Is your webapp targetted to the correct virtual-host during deployment?It could be possible that your webapp is targetted to the default web-server instead of the virtual-host causing this error. Can you validate this from your config file?
You can also configure default webapps for virtual hosts by setting the default-web-app-context-root element of virtual-host element in your config file

Similar Messages

  • Configuring default web apps for virtual hosts

    Hi,
    This posting is meant save time for anyone trying to specify a default web app
    for each of their virtual hosts (as opposed to specifying a default web app for
    each of their wl servers). This applies to weblogic 6.1, on NT. (I haven't tried
    this on other platforms).
    If you are trying to use the admin console to do this, give up. It's not possible.
    The "Virtual Host/Configuration" window lets you specify everything about that
    vhost configuration EXCEPT a default web app. (The "Default Web Application" drop
    down menu will always have only one option to choose from: "none").
    Instead, shutdown your server, and edit your domain's config.xml file manually.
    Attached is an example config file that specifies that the web app "kz" should
    be the default web app for the vhost "wl.kz.com", and that the web app "kahuna"
    should be the default web app for the vhost "www.kahuna.com".
    Hope this helps,
    Brian O'Donnell
    Lead Developer, Learning Network
    [config.xml]

    Hi,
    Is it possible to configure default web appls for virtual hosts
    with Weblogic 6.0 on NT platform? I tried to configure the configure.xml as Brian
    did, it doesnot work. I am just wondering if there's any other possible way to
    do this.
    Thanks.
    Mei
    "Brian O'Donnell" <[email protected]> wrote:
    >
    >
    >
    Hi,
    This posting is meant save time for anyone trying to specify a default
    web app
    for each of their virtual hosts (as opposed to specifying a default web
    app for
    each of their wl servers). This applies to weblogic 6.1, on NT. (I haven't
    tried
    this on other platforms).
    If you are trying to use the admin console to do this, give up. It's
    not possible.
    The "Virtual Host/Configuration" window lets you specify everything about
    that
    vhost configuration EXCEPT a default web app. (The "Default Web Application"
    drop
    down menu will always have only one option to choose from: "none").
    Instead, shutdown your server, and edit your domain's config.xml file
    manually.
    Attached is an example config file that specifies that the web app "kz"
    should
    be the default web app for the vhost "wl.kz.com", and that the web app
    "kahuna"
    should be the default web app for the vhost "www.kahuna.com".
    Hope this helps,
    Brian O'Donnell
    Lead Developer, Learning Network

  • Is weblogic 8.1.1 capapble of having a default web app on virtual hosts?

    I have a number of virtual host being served on the same weblogic 8.1.1
    server. For example, say www.abc.com , www.def.com and www.ghi.com and they
    each have their own directory underneath the applications directory ABC,
    DEF, GHI. When the user types out http://www.abc.com or def.com or even
    www.ghi.com, I would like weblogic to automatically goto the appropriate web
    app I want to associated with each virtual host.
    Is this possible? So far, I've seen it can't.
    I put in the <context-root>/</context-root> in the weblogic.xml file, but
    the server only lets you have one context root. So the first web app to
    load gets the context root, so www.def.com can get the DEF application, but
    the rest of them have to have some context, in other words www.abc.com/ABC
    or even www.abc/GHI will work, but I don't want that! This was easily
    configurable in 7.0SP1+2. Where and how do I do this in 8.1.1?
    If you've tried this and got it to work, please post any files you might
    have that are useful? I'm not sure where to goto next. Thanks.

    I think I found out what my problem is. There appears to be no restrictions
    in the server for the virtual host name being the same name as the
    application name. When there is, WLS seems to lose control of where to goto
    in the config.xml file. I just prefixed my virtual host names with 'vh' and
    all is good!
    "Flip" <!no_spam![email protected]> wrote in message
    news:[email protected]..
    I have a number of virtual host being served on the same weblogic 8.1.1
    server. For example, say www.abc.com , www.def.com and www.ghi.com andthey
    each have their own directory underneath the applications directory ABC,
    DEF, GHI. When the user types out http://www.abc.com or def.com or even
    www.ghi.com, I would like weblogic to automatically goto the appropriateweb
    app I want to associated with each virtual host.
    Is this possible? So far, I've seen it can't.
    I put in the <context-root>/</context-root> in the weblogic.xml file, but
    the server only lets you have one context root. So the first web app to
    load gets the context root, so www.def.com can get the DEF application,but
    the rest of them have to have some context, in other words www.abc.com/ABC
    or even www.abc/GHI will work, but I don't want that! This was easily
    configurable in 7.0SP1+2. Where and how do I do this in 8.1.1?
    If you've tried this and got it to work, please post any files you might
    have that are useful? I'm not sure where to goto next. Thanks.

  • Unable to force logout of Default Web Application

    Thi is a repost : still having the problem ... any ideas ?
    Original Post ........................................
    ........................................................ I am having a problemlogging out....I can not log out. Using WLS 6.0sp1 using form based authentication
    with a custom RDMBS Realm. I believe this functionality was working but now that
    the application has been set up as the default web application logout no longer
    works ?
    In our application we have a logout link that points to a jsp page that does the
    following:
    <% if (session != null) session.invalidate(); session = null; %>
    Note, this is the last jsp to be executed on the page. I looked at the compiled
    servlet and it doesn not appear that anything is being done that would reinitialize
    the session ...
    Here is the try-catch of the compiled jsp servlet .. try { // error page try block
    out.print("...");
    if (session != null) session.invalidate();
    session = null;
    out.print("...."); .... }
    catch (Exception __ee) {
    while (out != null && out != originalOut) out = pageContext.popBody(); pageContext.handlePageException(_ee);
    After this page is returned, the user can still access protected content, any
    ideas ????
    Is there a method in Weblogic security package to deauthenticate a user to force
    re authentication ?
    I just double checked it and lo and behold the session is actually being invalidated
    because the users session data is gone, however they are still able to access
    protected resources. Does this mean that weblogic is not using session to maintain
    authenicated flag ? Or does this mean that the call to pageContext.popBody() is
    creating a new session ? Or does this mean that weblogic has a bug ? Or does this
    mean that I don't know what I'm doing ?
    Bea, please provide a complete response, I have seen this type of post many times
    on this board, can we solve this problem once and for all.
    Thank you kindly,
    Mark Lesk

    I checked this angle. They are able to see protected content.
    However, bea has finally acknowledged the problem. It exists when you are using
    multiple web applications with single sign-on.
    The problem has supposedly been fixed in a rolling patch available for SP2 of
    WebLogic 6.0. Three new methods have been added that provide the ability to log
    users out.
    Hip Hip Hooray !!!!
    See this link : http://commerce.bea.com/downloads/wls_patches.jsp
    The new logout methods are described in the associated readme.
    Thanks
    - Mark
    "mblumrich" <[email protected]> wrote:
    potentially a silly question.... but are you sure the users are not simply
    looking at pages that are in the web browser's cache? Are they able to
    look
    at privileged content that they haven't seen before?
    cheers,
    Markus
    "Mark Lesk" <[email protected]> wrote in message
    news:[email protected]
    Thi is a repost : still having the problem ... any ideas ?
    Original Post ........................................
    ........................................................ I am having
    a
    problem
    logging out....I can not log out. Using WLS 6.0sp1 using form basedauthentication
    with a custom RDMBS Realm. I believe this functionality was workingbut
    now that
    the application has been set up as the default web application logoutno
    longer
    works ?
    In our application we have a logout link that points to a jsp pagethat
    does the
    following:
    <% if (session != null) session.invalidate(); session = null; %>
    Note, this is the last jsp to be executed on the page. I looked atthe
    compiled
    servlet and it doesn not appear that anything is being done that wouldreinitialize
    the session ...
    Here is the try-catch of the compiled jsp servlet .. try { // errorpage
    try block
    out.print("...");
    if (session != null) session.invalidate();
    session = null;
    out.print("...."); .... }
    catch (Exception __ee)
    while (out != null && out != _originalOut) out = pageContext.popBody();pageContext.handlePageException(__ee);
    After this page is returned, the user can still access protected content,any
    ideas ????
    Is there a method in Weblogic security package to deauthenticate auser to
    force
    re authentication ?
    I just double checked it and lo and behold the session is actuallybeing
    invalidated
    because the users session data is gone, however they are still ableto
    access
    protected resources. Does this mean that weblogic is not using sessionto
    maintain
    authenicated flag ? Or does this mean that the call topageContext.popBody() is
    creating a new session ? Or does this mean that weblogic has a bug? Or
    does this
    mean that I don't know what I'm doing ?
    Bea, please provide a complete response, I have seen this type of postmany times
    on this board, can we solve this problem once and for all.
    Thank you kindly,
    Mark Lesk

  • Deploying applications to virtual hosts and root contexts on OC4J

    Hi
    Does anyone out there know how to use hostnames other than the default to talk to an OC4J application (live virtual hosts in Apache). I have a server called web.mydomain.com but for a particular website I want to access it as shop.otherdomain.com - the same machine just 2 different DNS entries. I want OC4J to accept requests for both these machines and display a different site depending on which is accessed. This functionality is provided in Tomcat by the &lt;host&gt; construct - but how do you do it in OC4J?
    A secondary question related to this is how to deploy an application to the root context of one of these virtual hosts? The Enterprise Manager interface won't let you map anything to the '/' URL.
    I have read a lot of documentation and found little of relevance (fairly typical). I hope this is just a simple option I have overlooked.
    Thanks,
    Anthony.

    Sorry... Forgot to mention:
    I have read the post about using URL rewriting but this seems like a bit of a fudge. I was wondering if there was a way to do this from the OC4J setup. Preferably through the Enterprise Manager?
    Anthony.

  • Problem with tutorial; "Build a Web Application with JDeveloper 11g Using "

    I've got a rather new installation of Vista Business x64 on my developer rig, and last week I installed the new JDeveloper 11g version. The installation was all-inclusive, no customization on my end.
    In addition I've got a test installation of an Oracle DB 11gR1 on an available server here.
    To familiarize myself with the new JDeveloper I decided to spend some time with the JDeveloper 11g tutorials found here: http://www.oracle.com/technology/obe/obe11jdev/11/index.html.
    I've started twice on the second tutorial, "Build a Web Application with JDeveloper 11g Using EJB, JPA, and JavaServer Faces", and find myself repeatedly stuck at step 19 in section "Creating the Data Model and Testing it".
    It seems impossible to deploy the application to the default application server. The server starts fine on its own, I can access it via the admin console on port 7001 and it looks good. However, when I try to run the HRFacadeBean funny things are happening, symptomized by the following error messages seen in the IDE log-area:
    The "Messages" pane displays:
    "Compiling...
    Context: MakeProjectAndDependenciesCommand application=HR_EJB_JPA_App.jws project=EJBModel.jpr
    C:\Oracle\Middleware\jdk160_05\jre\bin\java.exe -jar C:\Oracle\Middleware\jdeveloper\jdev\lib\ojc.jar -g -warn -nowarn:320 -nowarn:372 -nowarn:412 -nowarn:413 -nowarn:415 -nowarn:486 -nowarn:487 -nowarn:489 -nowarn:556 -nowarn:558 -nowarn:560 -nowarn:561 -nowarn:705 -Xlint:-fallthrough -Xlint:-serial -Xlint:-unchecked -source 1.6 -target 1.6 -noquiet -encoding Cp1252 -d C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\classes -namereferences -make C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\classes\EJBModel.cdi -classpath C:\Oracle\Middleware\jdk160_05\jre\lib\resources.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\rt.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\jsse.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\jce.jar;C:\Oracle\Middleware\jdk160_05\jre\lib\charsets.jar;C:\JDeveloper\mywork\HR_EJB_JPA_App\.adf;C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\classes;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\toplink.jar;C:\Oracle\Middleware\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\Oracle\Middleware\modules\javax.persistence_1.0.0.0_1-0.jar;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\eclipselink.jar;C:\Oracle\Middleware\jdeveloper\modules\oracle.xdk_11.1.1\xmlparserv2.jar;C:\Oracle\Middleware\jdeveloper\modules\oracle.xdk_11.1.1\xml.jar;C:\Oracle\Middleware\modules\javax.jsf_1.2.0.0.jar;C:\Oracle\Middleware\modules\javax.ejb_3.0.1.jar;C:\Oracle\Middleware\modules\javax.enterprise.deploy_1.2.jar;C:\Oracle\Middleware\modules\javax.interceptor_1.0.jar;C:\Oracle\Middleware\modules\javax.jms_1.1.1.jar;C:\Oracle\Middleware\modules\javax.jsp_1.1.0.0_2-1.jar;C:\Oracle\Middleware\modules\javax.jws_2.0.jar;C:\Oracle\Middleware\modules\javax.activation_1.1.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.mail_1.1.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.soap_1.3.1.0.jar;C:\Oracle\Middleware\modules\javax.xml.rpc_1.2.1.jar;C:\Oracle\Middleware\modules\javax.xml.ws_2.1.1.jar;C:\Oracle\Middleware\modules\javax.management.j2ee_1.0.jar;C:\Oracle\Middleware\modules\javax.resource_1.5.1.jar;C:\Oracle\Middleware\modules\javax.servlet_1.0.0.0_2-5.jar;C:\Oracle\Middleware\modules\javax.transaction_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\Middleware\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar;C:\Oracle\Middleware\wlserver_10.3\common\lib -sourcepath C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src;C:\Oracle\Middleware\jdk160_05\src.zip;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\toplink-src.zip;C:\Oracle\Middleware\jdeveloper\modules\oracle.toplink_11.1.1\eclipselink-src.zip C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\Dept.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\Emp.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacadeLocal.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacadeClient.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacade.java C:\JDeveloper\mywork\HR_EJB_JPA_App\EJBModel\src\oracle\HRFacadeBean.java
    [11:45:27 PM] Successful compilation: 0 errors, 0 warnings.
    [Application HR_EJB_JPA_App is bound to Server Instance DefaultServer]
    [Starting Server Instance DefaultServer]
    #### Server Instance DefaultServer could not be started: Server Instance was terminated.
    The "Running: DefaultServer" displays:
    "C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd
    [waiting for the server to complete its initialization...]
    [Server Instance DefaultServer is shutting down.  All applications currently running will be terminated and undeployed.]
    Process exited.
    C:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Connecting to t3://localhost:7101 with userid weblogic ...
    This Exception occurred at Wed Oct 29 23:47:40 CET 2008.
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:512)
         at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
         at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:305)
         at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
         at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
         at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:125)
         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 org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
         at org.python.core.PyMethod.__call__(PyMethod.java:96)
         at org.python.core.PyObject.__call__(PyObject.java:248)
         at org.python.core.PyObject.invoke(PyObject.java:2016)
         at org.python.pycode._pyx4.connect$1(<iostream>:16)
         at org.python.pycode._pyx4.call_function(<iostream>)
         at org.python.core.PyTableCode.call(PyTableCode.java:208)
         at org.python.core.PyTableCode.call(PyTableCode.java:404)
         at org.python.core.PyFunction.__call__(PyFunction.java:184)
         at org.python.pycode._pyx16.f$0(C:\Oracle\Middleware\user_projects\domains\base_domain\shutdown.py:1)
         at org.python.pycode._pyx16.call_function(C:\Oracle\Middleware\user_projects\domains\base_domain\shutdown.py)
         at org.python.core.PyTableCode.call(PyTableCode.java:208)
         at org.python.core.PyCode.call(PyCode.java:14)
         at org.python.core.Py.runCode(Py.java:1135)
         at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
         at weblogic.management.scripting.WLST.main(WLST.java:129)
         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 weblogic.WLST.main(WLST.java:29)
    Caused by: java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
         at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
         ... 38 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
         at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
         at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:303)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:193)
         ... 43 more
    Problem invoking WLST - Traceback (innermost last):
    File "C:\Oracle\Middleware\user_projects\domains\base_domain\shutdown.py", line 1, in ?
    File "<iostream>", line 22, in connect
    WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7101 Use dumpStack() to view the full stacktrace
    Done
    I'm not that familiar with these things but it seems to me that there is an issue with port numbers here. The application seems to expect a app.server service at port 7101, but does'nt find one.
    Any suggestions on how to fix this problem would be appreciated?
    LA$$E

    Jupp,
    It fails in a similar way.
    What I did was; create a simle 'Hello World' html file, saving it with the jsp extension. In Jdev11g i made a new application and an emtpy project, then loaded the jsp file and made it the default run-target. This compiles nicely.
    When running the project it first attempts to start the WebLogicServer (WLS). After a few minutes it is started as seen in the "Running: DefaultServer" pane:
    C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd
    [waiting for the server to complete its initialization...]
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=;C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.5/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\jdeveloper\modules\features\adf.share_11.1.1.jar;;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;;
    PATH=C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.5\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\oracle_client\product\11.1.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    java version "1.6.0_05"
    Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
    Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -DproxySet=false -Djbo.34010=false -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Doracle.home=C:\Oracle\Middleware\jdeveloper -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\oracle\jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_TW.jar>
    <30.okt.2008 kl 19.20 CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
    <30.okt.2008 kl 19.20 CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Mon Aug 18 22:39:18 EDT 2008 1142987 >
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <30.okt.2008 kl 19.20 CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <30.okt.2008 kl 19.20 CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
    <30.okt.2008 kl 19.20 CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <30.okt.2008 kl 19.20 CET> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddi.war'.>
    <30.okt.2008 kl 19.20 CET> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddiexplorer.war'.>
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <30.okt.2008 kl 19.20 CET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <30.okt.2008 kl 19.20 CET> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <30.okt.2008 kl 19.20 CET> <Warning> <Server> <BEA-002611> <Hostname "Kromp.lan", maps to multiple IP addresses: 10.0.0.8, 127.0.0.1>
    <30.okt.2008 kl 19.20 CET> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.0.0.8:7001 for protocols iiop, t3, ldap, snmp, http.>
    <30.okt.2008 kl 19.20 CET> <Warning> <Server> <BEA-002611> <Hostname "127.0.0.1", maps to multiple IP addresses: 10.0.0.8, 127.0.0.1>
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Development Mode>
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <30.okt.2008 kl 19.20 CET> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    DefaultServer startup time: 121552 ms.
    DefaultServer started.
    In the "Messages" pane, however, things are not looking so good:
    Context: MakeProjectAndDependenciesCommand application=TestAppJsp.jws project=TestProjJsp.jpr
    [7:20:49 PM] Successful compilation: 0 errors, 0 warnings.
    [Application TestAppJsp is bound to Server Instance DefaultServer]
    [Starting Server Instance DefaultServer]
    #### Server Instance DefaultServer could not be started: Server Instance was terminated.
    But, of course, the server is actually running as I can access it via its Admin Console.
    So, I try to run the project again, and this time the following is shown in the "Messages" pane:
    Compiling...
    Context: MakeProjectAndDependenciesCommand application=TestAppJsp.jws project=TestProjJsp.jpr
    [7:26:39 PM] Successful compilation: 0 errors, 0 warnings.
    [Application TestAppJsp is bound to Server Instance DefaultServer]
    [Starting Server Instance DefaultServer]
    #### Server Instance DefaultServer could not be started: Server Instance was terminated.
    The "Running: DefaultServer" now comes up with:
    C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd
    [waiting for the server to complete its initialization...]
    [Server Instance DefaultServer is shutting down.  All applications currently running will be terminated and undeployed.]
    Process exited.
    The WLS is still running though as I can still access its adm console.
    To me it seems that it is attempting to start a separate instance of the WLS for each run attempt, but then I could be wrong.....:(
    Later I'll try to change the default WLS port from 7001 to 7101 as suggested in another port here.
    I must admit that I'm a bit surprised that the JDev11g doesn't work fine at this very simple level when performing a default install.

  • Precompilation of JSPs for default web application

    Hello,
    Once in a while I need to redeploy my "Default" web application. I would like to have its all JSPs precompiled, so that it was immediatly available after redeployment.
    However, if I try to redeploy my web application (.war file) under, let's say, "DefaultWebApp" root context, using the administration console, with the "Precompile JSPs" option enabled, it does compile all JSPs, but ONLY those deployed under the "DefaultWebApp" root context.
    However, If I access a url like "http://somehost/SomeResource.jsp" (a file that belongs to that default web application"), I can see (due to a pause) that my JSPs have not been compiled under the root context.
    Is there any way to precompile JSPs for my default web applications?
    Sincerely,
    Sergei Batiuk.

    Hello,
    Once in a while I need to redeploy my "Default" web application. I would like to have its all JSPs precompiled, so that it was immediatly available after redeployment.
    However, if I try to redeploy my web application (.war file) under, let's say, "DefaultWebApp" root context, using the administration console, with the "Precompile JSPs" option enabled, it does compile all JSPs, but ONLY those deployed under the "DefaultWebApp" root context.
    However, If I access a url like "http://somehost/SomeResource.jsp" (a file that belongs to that default web application"), I can see (due to a pause) that my JSPs have not been compiled under the root context.
    Is there any way to precompile JSPs for my default web applications?
    Sincerely,
    Sergei Batiuk.

  • Default Web Application - new bug in SP1?

    Just rebuilding everything from scratch to test out SP1. Have noticed
    that the admin console now always seems to report only "(none)" in the
    Default Web Application drop-down, even if other web apps are deployed
    to the server. Editing the config.xml directly detours the problem, in
    that the default app can be set and used, but the admin console still
    says "(none)".
    Lots of other good things fixed in SP1 though!
    Chris

    What you can do if you may shutdown the server is to replace the
    console.war from WLS6.0SP1 with that from WLS6.0, do the mods and put
    the new back in place. If you may stop the server, this is I think the
    easiest sollution.
    Regards,
    Merg
    "Rich " <[email protected]> wrote in message
    news:3ad33260$[email protected]..
    >
    Is there a fix for this issue, or a work around? I am having adifficult time
    getting the web application to show up...and be accessible in abrowser.
    >
    Thanks.
    Chris Palmer <[email protected]> wrote:
    Just rebuilding everything from scratch to test out SP1. Have noticed
    that the admin console now always seems to report only "(none)" in
    the
    Default Web Application drop-down, even if other web apps aredeployed
    to the server. Editing the config.xml directly detours the problem,in
    that the default app can be set and used, but the admin console still
    says "(none)".
    Lots of other good things fixed in SP1 though!
    Chris

  • Default Web Application is not visible in Weblogic Console

    We are using Weblogic 5.1.0 SP7
              We moved our Application from the Implicitly Defined Default Web
              Application which is configurated by the
              weblogic properties to a Web Application. Because we don't want to
              change any URL in our Application, we
              decided to deploy it as Explicitly Defined Default Web Application.
              By this we recordniced that the weblogic.httpd.defaultWebApp property
              worked not that way descibed in the
              Weblogic Documentation. You have to write the path to the WebApp not the
              name!
              So we have the following Entry in the weblogic.properties:
              weblogic.httpd.defaultWebApp=i:/if_home2/web
              This works fine. The Server starts and serves the WebApp the way we
              expected. But wenn we start the Weblogic
              Console the WebApp ist not visible in the "myserver/HTTP/Servlet web
              applications" folder. This one is empty
              now! Previously the "General" Entry for the Implicitly Defined Default
              Web Application was shown here, which
              showed our Servlets and JSP's and their hit count and parameters.
              So there is no chance to monitor the Servlets and JSP's of the default
              Web Application.
              I tried to deploy our WebApp a secound time with
              weblogic.httpd.webApp.OurApp=i:/if_home2/web
              but this create a second independent WebApp. OurApp is shown in the
              Weblogic Console but it does not monitor
              the hits to the default WebApp. So this is not a solution!
              Any idea to make the default Web Application visible in the Weblogic
              Console?
              

    in my development environment i checked in site collection feature, it isn't available in site collection feature but still i am getting those web parts in web part gallery while adding it on page.
    Also, in Production environment, feature is available in /templates/features folder after deployment, but not available in web part gallery while adding it on page.
    I tried with uploading .webpart file which is available in /templates/features production environment as i mentioned, is running for one web part. Not for second web part and giving me security error.
    As, uploading .webpart file is not feasible solution, please tell me how could i do that with .wsp file?
    please tell me what could be another workaround. 
     

  • Unable to logout of Default Web Application

    Thi is a repost : still having the problem ... any ideas ?
    Original Post ........................................
    ........................................................I am having a problem logging out....I can not log out. Using WLS 6.0sp1 using
    form based authentication with a custom RDMBS Realm. I believe this functionality
    was working but now that the application has been set up as the default web application
    logout no longer works ?
    In our application we have a logout link that points to a jsp page that does the
    following:
    <% if (session != null) session.invalidate(); session = null; %>
    Note, this is the last jsp to be executed on the page. I looked at the compiled
    servlet and it doesn not appear that anything is being done that would reinitialize
    the session ...
    Here is the try-catch of the compiled jsp servlet .. try { // error page try block
    out.print("...");
    if (session != null) session.invalidate();
    session = null;
    out.print("...."); .... }
    catch (Exception __ee) {
    while (out != null && out != originalOut) out = pageContext.popBody(); pageContext.handlePageException(_ee);
    After this page is returned, the user can still access protected content, any
    ideas ????
    Is there a method in Weblogic security package to deauthenticate a user to force
    re authentication ?
    I just double checked it and lo and behold the session is actually being invalidated
    because the users session data is gone, however they are still able to access
    protected resources. Does this mean that weblogic is not using session to maintain
    authenicated flag ? Or does this mean that the call to pageContext.popBody() is
    creating a new session ? Or does this mean that weblogic has a bug ? Or does this
    mean that I don't know what I'm doing ?
    Bea, please provide a complete response, I have seen this type of post many times
    on this board, can we solve this problem once and for all.
    Thank you kindly,
    Mark Lesk

    Thi is a repost : still having the problem ... any ideas ?
    Original Post ........................................
    ........................................................I am having a problem logging out....I can not log out. Using WLS 6.0sp1 using
    form based authentication with a custom RDMBS Realm. I believe this functionality
    was working but now that the application has been set up as the default web application
    logout no longer works ?
    In our application we have a logout link that points to a jsp page that does the
    following:
    <% if (session != null) session.invalidate(); session = null; %>
    Note, this is the last jsp to be executed on the page. I looked at the compiled
    servlet and it doesn not appear that anything is being done that would reinitialize
    the session ...
    Here is the try-catch of the compiled jsp servlet .. try { // error page try block
    out.print("...");
    if (session != null) session.invalidate();
    session = null;
    out.print("...."); .... }
    catch (Exception __ee) {
    while (out != null && out != originalOut) out = pageContext.popBody(); pageContext.handlePageException(_ee);
    After this page is returned, the user can still access protected content, any
    ideas ????
    Is there a method in Weblogic security package to deauthenticate a user to force
    re authentication ?
    I just double checked it and lo and behold the session is actually being invalidated
    because the users session data is gone, however they are still able to access
    protected resources. Does this mean that weblogic is not using session to maintain
    authenicated flag ? Or does this mean that the call to pageContext.popBody() is
    creating a new session ? Or does this mean that weblogic has a bug ? Or does this
    mean that I don't know what I'm doing ?
    Bea, please provide a complete response, I have seen this type of post many times
    on this board, can we solve this problem once and for all.
    Thank you kindly,
    Mark Lesk

  • Default Web Application ist not visible in WebLogic Console

    We are using Weblogic 5.1.0 SP7
              We moved our Application from the Implicitly Defined Default Web
              Application which is configurated by the weblogic properties to a Web
              Application. Because we don't want to change any URL in our Application,
              we decided to deploy it as Explicitly Defined Default Web Application.
              By this we recordniced that the weblogic.httpd.defaultWebApp property
              worked not that way descibed in the Weblogic Documentation. You have to
              write the path to the WebApp not the name!
              So we have the following Entry in the weblogic.properties:
              weblogic.httpd.defaultWebApp=i:/if_home2/web
              This works fine. The Server starts and serves the WebApp the way we
              expected. But wenn we start the Weblogic Console the WebApp ist not
              visible in the "myserver/HTTP/Servlet web applications" folder. This one
              is empty now! Previously the "General" Entry for the Implicitly Defined
              Default Web Application was shown here, which showed our Servlets and
              JSP's and their hit count and parameters.
              So there is no chance to monitor the Servlets and JSP's of the default
              Web Application.
              I tried to deploy our WebApp a secound time with
              weblogic.httpd.webApp.OurApp=i:/if_home2/web
              but this create a second independent WebApp. OurApp is shown in the
              Weblogic Console but it does not monitor the hits to the default WebApp.
              So this is not a solution!
              Any idea to make the default Web Application visible in the Weblogic
              Console?
              

    Hello Nadar,
    Tell me how are you starting server in the cluster, through nodemanager or commnadline.
    Kuldeep

  • Console.war as default web application...

    Hi,
    I tried to add the console.war as my default web application for my Admin
    server, but when restarting the server it complained with the following
    error:
    The WebLogic Server did not start up properly.
    "Exception raised: weblogic.management.configuration.ConfigurationException:
    undefined mbean reference:
    mydomain:Name=console,Server=myserver,Type=WebAppComponent"
    And the server does not start at all - I had to manually update the
    config.xml to remove the console.war as a default web application...
    Does anybody knows if this is a bug? Does it happens only with the
    console.war? or there are any other scenarios that it can happen as well?
    Thanks,
    Marcelo.

    It's 6.1 - I want to set up it as default on my Admin server instance, which
    is running as a Admin server only... Not critical, but...
    Thanks,
    Marcelo
    "Kumar Allamraju" <[email protected]> wrote in message
    news:[email protected]..
    Is this problem with 6.0 or 6.1?
    BTW, why do you want configure console.war as default webapp?
    Marcelo Caldas wrote:
    Hi,
    I tried to add the console.war as my default web application for my
    Admin
    server, but when restarting the server it complained with the following
    error:
    The WebLogic Server did not start up properly.
    "Exception raised:weblogic.management.configuration.ConfigurationException:
    undefined mbean reference:
    mydomain:Name=console,Server=myserver,Type=WebAppComponent"
    And the server does not start at all - I had to manually update the
    config.xml to remove the console.war as a default web application...
    Does anybody knows if this is a bug? Does it happens only with the
    console.war? or there are any other scenarios that it can happen aswell?
    >>
    Thanks,
    Marcelo.

  • Deploy web application with exploded directory format

    I am quite new with Oracle9iAS Containers for J2EE. Currently, my project is not using EJB, only JSP and Servlets. I want to deploy the war file with exploded directory format. I don't want to use the default web application directory j2ee/home/default-web-app. The "Using Oracle9iAS Containers for J2EE" get start documentation only explained how to deploy J2ee application. What about the web application without EJB jar file? Anybody knows how to do that. Please let me know.
    Thanks in advance.

    Though you don't have ejbs, you can still use the ear file format. This would be most convenient way of deploying.
    Use of a tool like Ant is recommended if you are not using JDeveloper.
    Also, you can findinfo on deploying using a exploded directory
    http://otn.oracle.com/docs/tech/java/oc4j/htdocs/getstart.htm#1027810
    But recommed having ear file as it is convenient. If you want to see an example of use of Ant and deploying using ear file
    check out one of the recently posted how-tos E.g. http://otn.oracle.com/tech/java/oc4j/htdocs/how-to-servlet-events.html

  • Configuring Default Web Application w/ WLS6.0 SP2

              I have 2 Machines with no shared file system.
              I have identical directory structures on both:
              /usr/local/weblogic/config/qadomain/applications/DefaultWebApp
              I have 2 Servers within the cluster:
              ServerA and ServerB within ClusterA
              I have 1 DefaultWebApp that I have Chosen ClusterA
              When starting ServerA I receive and error:
              <Error deploying application DefaultWebApp: ServerB not deployed on ServerA>
              Can someone tell me the what's missing in this configuration?
              

    You should add it to config.xml by yourself, should be something like:
    <Server AdministrationPort="0"
    ListenPort="8001" Name="testServer">
    <Log FileName="config/mydomain/logs/weblogic-testServer.log"
    Name="testServer"/>
    <WebServer DefaultWebApp="WebApp_testServer"
    LogFileName="config/mydomain/logs/access-testServer.log"
    Name="testServer"/>
    <KernelDebug Name="testServer"/>
    <SSL Name="testServer"/>
    <ServerDebug Name="testServer"/>
    </Server>
    Good luck.
    "Ton Bode" <[email protected]> wrote in message
    news:[email protected]..
    Sorry, wrong group, and it seems to be a bug in the WLS 6.0 sp1 and sp2
    versions
    "Ton Bode" <[email protected]> wrote in message
    news:3b5ec3e3$[email protected]..
    I am running WLS6.0 sp2 on Win2K.
    When I try to select a Default Web Application (selecting myserver,
    Configuration, HTTP, Default Web Application) there is no Application
    that
    I
    can select. I suppose at least the DefaultWebApp_myserver should be
    available. This WebApp is deployed and targeted to myserver. But also
    Console and Certificate should be available. What do I need to do inorder
    to select a Web Application as default?
    Ton Bode

  • Configuring webclient  with Virtual Host

    i configure portal with a virtual host.
    Portal it is ok. i can navigate and login with the virtual host server. But the collaboration portlets (Message portlet, calendar portlet) link to the original server.
    what can i do to work also with virtual host?
    my original server is the internal host name.
    the virtual host is the public server name.
    thanks in advance
    Regards
    giorgio

    no problem from flex side.. need to escape crossdomain.xml
    file in htacess for codeigniter i.e RewriteCond $1
    !^(index\.php|images|application|uploads|robots\.txt|crossdomain\.xml)
    in htaccess file.

Maybe you are looking for


HashFlare