Wls 6.1 ; DefaultWebApp not working?

If I run the default server, and in a browser URL type:
'http://localhost:7001/DefaultWebApp', shouldn't I see
the index.html page?

You could maybe try something like this:
<WebServer DefaultWebApp="public_html" Name="myserver"/>
<Application Deployed="true" Name="public_html"
Path=".\config\mydomain\applications">
<WebAppComponent Name="public_html"
Targets="myserver" URI="public_html" WebServers="myserver"/>
</Application>
<Application Deployed="true" Name="public"
Path=".\config\mydomain\applications">
<WebAppComponent Name="public_html"
Targets="myserver" URI="public_html" WebServers="myserver"/>
</Application>
The WebAppComponent Name defines the context used, so if you define it as
two Applications pointing to the same path and URI you can use one as the
default and one on the original context.
Gareth
"Gareth Chapman" <[email protected]> wrote in message
news:[email protected]..
If a webapp is set as the default web app, then the original context isnot
available for it any more:
e.g
a web app called MyApp would normally be accessed:
http://localhost:7001/MyApp
if this is set as the default then it is accessed: http://localhost:7001
and
the previous context is no longer available.
Gareth
"Eli Corrales" <[email protected]> wrote in message
news:3c0fd469$[email protected]..
If I run the default server, and in a browser URL type:
'http://localhost:7001/DefaultWebApp', shouldn't I see
the index.html page?

Similar Messages

  • Wls 11g jaas module not working

    Hi,
    I am successfully using a standard JAAS module to authorize and authenticate users on an HPUX – WebLogic 9.2 environment. However when we port this exact JAAS module to a LINUX – WebLogic 11g environment, the JAAS module times-out after 25 minutes at WebLogic managed server startup and eventually fails.
    We want to know if anything has changed from a JAAS perspective when comparing WebLogic 9.2 versus 11g? We have been unable to get JAAS authentication working. We tried re-creating the jar file but have now run out of options. They have over 16 different Linux servers that all have the same problem. All time out once the JAAS module has been implemented.
    We are primarily interested in knowing if there have been any significant changes to the JAAS functionality between WLS 9.2 and 11g versions. They have tried recompiling/recreating the JAAS file on our Linux servers but the same result occurs. It simply stalls and then doesn't work after appearing to be hung for 25 minutes at start-up time.
    It is a custom JAAS module that we have implemented. However the very same JAAS module that works for WLS 9.2 does not work for WLS 11g.
    Any suggestions on how we can get this working would be very helpful.
    Thanks in advance.
    Edited by: user10600611 on Jul 8, 2010 5:53 PM

    Yes, the packaging has changed somwhat, when you compiled for 11g didn't u get compilcation exceptions?
    If you didnt, then you might not be using those packages.
    Can u paste the stak trace/ thread dump at the time it was hung?

  • WLCS 3.1 + WLS SP 9 --*** PORTALS Not WORKING!!!!

    After applying WLS SP 9.0 our portals not working.
    Can anybody throw some light, PLEASE !!! **URGENT**
    We are getting the following Error:
    Sun May 06 21:24:44 GMT+03:00 2001:<E> <ServletContext-General> Servlet failed
    with Exception weblogic.servlet.jsp.JspException: (line -1): Error in tag library
    at: 'wl': The Tag class 'weblogi x.jsp.tags.CacheTag' has no setter method corresponding
    to TLD declared attribute 'async', (JSP 1. spec, 5.4.1) at java.lang.Throwable.fillInStackTrace(Native
    Method) at java.lang.Throwable.fillInStackTrace(Compiled Code) at java.lang.Throwable.<init>(Compiled
    Code) at java.lang.Exception.<init>(Compiled Code) at java.lang.RuntimeException.<init>(Compiled
    Code) at weblogic.servlet.jsp.JspException.<init>(Compiled Code) at weblogic.servlet.jsp.JspException.<init>(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.jspException(Compiled Code) at weblogic.servlet.jsp.StandardTagLib.processTag(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.processTagElements(Compiled Code)
    at weblogic.servlet.jsp.StandardTagLib.<init>(Compiled Code) at weblogic.servlet.jsp.JspLexer.loadTagLib(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(Compiled Code) at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(Compiled Code) at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code) at weblogic.servlet.jsp.JspLexer.parse(Compiled
    Code) at weblogic.servlet.jsp.JspParser.doit(Compiled Code) at weblogic.servlet.jsp.JspParser.parse(Compiled
    Code) at weblogic.servlet.jsp.Jsp2Java.outputs(Compiled Code) at weblogic.utils.compiler.CodeGenerator.generate(Compiled
    Code) at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code) at weblogic.servlet.jsp.JspStub.prepareServlet(Compiled
    Code) at weblogic.servlet.jsp.JspStub.checkForReload(Compiled Code) at weblogic.servlet.internal.ServletStubImpl.getServlet(Compiled
    Code) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(Compiled Code) at com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(Compiled
    Code) at com.beasys.commerce.foundation.flow.FlowManager.service(Compiled Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
    Code) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code) at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code) at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code) at weblogic.socket.MuxableSocketHTTP.execute(Compiled
    Code) at weblogic.kernel.ExecuteThread.run(Compiled Code)

    I have gotten it to work by replacing the sp9 weblogic-tags-510.jar with
    the sp8 weblogic-tags-510.jar. We haven't experienced any problems with
    our app after using this workaround. However, we haven't completely
    tested it either.
    psimon wrote:
    You should use sp6 or sp8 instead of sp9
    Pascal
    Nadeem a écrit :
    After applying WLS SP 9.0 our portals not working.
    Can anybody throw some light, PLEASE !!! **URGENT**
    We are getting the following Error:
    Sun May 06 21:24:44 GMT+03:00 2001:<E> <ServletContext-General>
    Servlet failed
    with Exception weblogic.servlet.jsp.JspException: (line -1): Error
    in tag library
    at: 'wl': The Tag class 'weblogi x.jsp.tags.CacheTag' has no setter
    method corresponding
    to TLD declared attribute 'async', (JSP 1. spec, 5.4.1) at
    java.lang.Throwable.fillInStackTrace(Native
    Method) at java.lang.Throwable.fillInStackTrace(Compiled Code) at
    java.lang.Throwable.<init>(Compiled
    Code) at java.lang.Exception.<init>(Compiled Code) at
    java.lang.RuntimeException.<init>(Compiled
    Code) at weblogic.servlet.jsp.JspException.<init>(Compiled Code) at
    weblogic.servlet.jsp.JspException.<init>(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.jspException(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.processTag(Compiled
    Code) at
    weblogic.servlet.jsp.StandardTagLib.processTagElements(Compiled
    Code)
    at weblogic.servlet.jsp.StandardTagLib.<init>(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.loadTagLib(Compiled
    Code) at
    weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(Compiled Code)
    at
    weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.mDIRECTIVE(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.parse(Compiled
    Code) at weblogic.servlet.jsp.JspParser.doit(Compiled Code) at
    weblogic.servlet.jsp.JspParser.parse(Compiled
    Code) at weblogic.servlet.jsp.Jsp2Java.outputs(Compiled Code) at
    weblogic.utils.compiler.CodeGenerator.generate(Compiled
    Code) at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code) at
    weblogic.servlet.jsp.JspStub.prepareServlet(Compiled
    Code) at weblogic.servlet.jsp.JspStub.checkForReload(Compiled Code)
    at weblogic.servlet.internal.ServletStubImpl.getServlet(Compiled
    Code) at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
    Code)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(Compiled
    Code) at
    com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(Compiled
    Code) at
    com.beasys.commerce.foundation.flow.FlowManager.service(Compiled
    Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code) at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
    Code) at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
    Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
    Code) at
    weblogic
    servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code) at
    weblogic.socket.MuxableSocketHTTP.execute(Compiled
    Code) at weblogic.kernel.ExecuteThread.run(Compiled Code)

  • Apache plugin support for WLS  6.1 is not working for me.

    Following are the additional configurations I used in httpd.conf after doing LoadModule
    & AddModule
    Alias /weblogic "/opt/BEA/wlserver6.1/config/petstore/applications"
    <Location /weblogic>
    SetHandler weblogic-handler
    </Location>
    <IfModule mod_weblogic.c>
    WebLogicHost localhost
    WebLogicPort 7003
    </IfModule>
    I get Permission denied & not even 403/forbidden for Petstore example jsps. I
    am trying
    to proxy it by URL basis not on mime type. I tried doing same thing for one of
    my own domains
    & server. The results were same. Now, If I try to comment out the Alias line from
    my httpd.conf
    file, it gives me 404 error. Can anyone help me out in this regard? I doubt my
    configurations
    in my weblogic's config.xml file.
    Thanks,
    Naveen

    Hi.
    I'm not clear on what you are trying to accomplish with the alias pointing to the absolute
    path of your WLS applications directory. This is not how the plugin works. As you have it
    set up now the plugin looks for URLs with /weblogic in them and proxies those requests to a
    running instance of WLS.
    For example, the plugin will accept the following URL and forward it to WLS:
    http://host:port/weblogic/index.html
    WLS will respond IF you have a webapp named weblogic. From your example it looks like you
    are trying to proxy to the petstore example. The URL to access the petstore example that
    ships with wls is something like: http://localhost:7003/estore/control/main so if you want
    to proxy by path you may want to proxy when the path contains /estore instead of /weblogic.
    Hope this helps.
    Michael
    Naveen wrote:
    Following are the additional configurations I used in httpd.conf after doing LoadModule
    & AddModule
    Alias /weblogic "/opt/BEA/wlserver6.1/config/petstore/applications"
    <Location /weblogic>
    SetHandler weblogic-handler
    </Location>
    <IfModule mod_weblogic.c>
    WebLogicHost localhost
    WebLogicPort 7003
    </IfModule>
    I get Permission denied & not even 403/forbidden for Petstore example jsps. I
    am trying
    to proxy it by URL basis not on mime type. I tried doing same thing for one of
    my own domains
    & server. The results were same. Now, If I try to comment out the Alias line from
    my httpd.conf
    file, it gives me 404 error. Can anyone help me out in this regard? I doubt my
    configurations
    in my weblogic's config.xml file.
    Thanks,
    Naveen--
    Michael Young
    Developer Relations Engineer
    BEA Support
    [att1.html]

  • JDK 7 + Red Hat 6 64-bit = WLS 10.3.6 and WLS 12.1 installer not working

    Hi,
    I have installed Weblogic 10.3.6 and 12.1 on two different Red Hat 6 64-bit servers. I started out using JDK 7 (1.7.0_05) but when I reached the screen where you select which products to install I could not select or deselect anything with the mouse. On others I could not use the keyboard for input. As soon as I switched to JDK 6 everything worked fine.
    As a workaround I installed and configured everything with JDK 6 and switched to JDK 7. This works fine and the developers are happy.
    But I have discovered that the I have the same problem when I use config.sh, so it is general problem with the GUI and JDK 7.
    I opened a Service Request on MOS in June but I don't think the support guy has much of a clue. He has been testing with Windows. His last suggestion was running the installer with -d64, but according to the manual this should only be used when using a 32/64-bit hybrid JDK, which is not the case.
    Anybody has any ideas?
    Regards Peter

    Hi Peter,
    I check the SR well I think it not so see to reproduce in other environment.
    But we can instead to engineer to reproduce on their environment.
    But as of I would suggest to use command line or silent mode to install wls.
    Going through GUI will have many complex issue on OS to OS base so best practice is to have such installation using command line or silent modes.
    Note: If engineer is unable to reproduce such issue in their environment then Oracle will not consider that is BUG then there would be issue in your environment only.
    Regards,
    Kal

  • Servlet reloading not working with WLS 5.1 sp8

              I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
              problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
              work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
              the servler reloading works fine.
              Does anybody experience similar problem or have I forgot to do something?
              WLS properties/env vars setting:
              - weblogic.httpd.servlet.reloadCheckSecs=0
              - WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
              - JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
              Thanks in advance for any help.
              

              I've experienced the same problem with both sp6 and sp8. In both cases I performed several test, including
              - varied the value of weblogic.httpd.servlet.reloadCheckSecs
              - changes to the package depth the servlet belonged to
              - changes to the string length of the package names the servlet belonged to
              At best, the servlet would reload sometimes. I've moved back to sp5 and the problem has subsided.
              Note: I did not try registering the servlet to see how that would effect the dynamic reloading.
              Hope this helps
              - Dave
              "Michel Dinh" <[email protected]> wrote:
              >
              >I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
              >problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
              >work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
              >the servler reloading works fine.
              >
              >
              >Does anybody experience similar problem or have I forgot to do something?
              >
              >WLS properties/env vars setting:
              >
              >- weblogic.httpd.servlet.reloadCheckSecs=0
              >- WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
              >- JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
              >
              >Thanks in advance for any help.
              

  • Literalxml encoding style not working in WLS 7.0 SP1

    I am posting the following handcrafted message via an HTTPS client POST on to the
    Web Service URL :
    <env:Envelope
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <env:Header></env:Header>
    <env:Body>
    <sendMessage env:encodingStyle="http://xml.apache.org/xml-soap/literalxml">
    <string><TAG1><TAG>val</TAG>abcfdf</TAG1></string>
    </sendMessage>
    </env:Body>
    </env:Envelope>
    I obviously do not want to escape the XML contents of string param in the method
    sendMessage. I thought literalxml ecnodingstyle would do the trick.
    Is there any jar etc that needs to be loaded into WLS 7 to make this work?
    Note that its an HTTPS post of the raw message, and I do not want to use client
    apis that will do things under the hood.
    Thanks a lot.

    Hi Suteertha,
    There are SwA examples at the following link:
    http://dev2dev.bea.com/direct/webservice/index.html
    Regards,
    Mike Wooten
    "Suteertha Guha" <[email protected]> wrote:
    >
    I got the document type running.
    Input is :
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <env:Header>
    </env:Header>
    <env:Body>
    <ns100:sendMessage xmlns:ns100="http://striker.mk.telcordia.com:9001/"><test><ABC>abcval</ABC><
    def>defff</def></test></ns100:sendMessage>
    </env:Body>
    </env:Envelope>
    Corr Output is :
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/200
    1/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xml
    soap.org/soap/encoding/"><env:Header></env:Header><env:Body env:encodingStyle="http://schemas.xmlsoa
    p.org/soap/encoding/"><ns100:sendMessageResponse xmlns:ns100="http://striker.mk.telcordia.com:9001/"
    xsi:type="xsd:string">abcval</ns100:sendMessageResponse></env:Body></env:Envelope>
    My CDATA enclosed input is :
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <env:Header>
    </env:Header>
    <env:Body>
    <ns100:sendMessage xmlns:ns100="http://striker.mk.telcordia.com:9001/"><![CDATA[<test><ABC>abcval</ABC><def>defff</def></test>]]></ns100:sendMessage>
    </env:Body>
    </env:Envelope>
    Corr output is :
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/200
    1/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xml
    soap.org/soap/encoding/"><env:Header></env:Header><env:Body env:encodingStyle="http://schemas.xmlsoa
    p.org/soap/encoding/"><ns100:sendMessageResponse xmlns:ns100="http://striker.mk.telcordia.com:9001/"
    xsi:type="xsd:string"><test><ABC>abcval</ABC><def>defff</def></tes
    t></ns100:sendMessageResponse></env:Body></env:Envelope>
    Looks like CDATA enclosure is a must to pick up XML, document style or
    rpc style.
    Also, on the way out, chars are getting escaped.
    I failed while trying attachments, can you provide me an example that
    takes in
    and returns an attachment in WLS 7.0?

  • GoLink not working from standalone wls

    version 11.1.2.3
    I have a goLink field on the UI that points to a file in public network drive. When I run the UI from within the Integrated weblogic server it opens the file just fine.
    But when I deploy the app to a standalone wls in the same box, goLink does not work. When I click on the link nothing happens.
    On the 'Destination' field in goLink, the public path is defined as : \\somepath\dir1\dir2\Scripts\sometxt.txt
    Any idea the standalone wls can open this file? Do I need to so some setup in the server?
    Thanks.

    The server can't reach out of his sandbox. This would be a security risk. One way is to use a servlet which can open the file and send it to the client. In this car you can use a normal url like /fileservlet?filr=yourfilename and the seller knows which file to send to the client.
    The general modus operandi is the same as when you pipe an image to a client like outlined here: https://tompeez.wordpress.com/2011/12/16/jdev11-1-2-1-0-handling-imagesfiles-in-adf-part-3/
    Or you put all the files under the web root of the application.
    Timo

  • DADs on WLS 11g (version 10.3.6.0) do not work (Error 404--Not Found)

    Actually we use Application Server 10g (version 10.1.2.3.0) for different Forms 10g Applications (roundabout 1000 Forms) and want to change to Forms 11g and Weblogic Server 11g (version 10.3.6.0). A Test-Application on the Weblogic Server works fine, but DAD’s do not work at all.
    In Enterprise Manager 10g i can configure DADs within the GUI of the Enterprise Manager, where i can see, if a connection could be established or not.
    In Enterprise Manager 11g Fusion Middleware Control this doesn't seem to exist anymore, so i tried to configure the DADs manually, but something has to be wrong or missing, because there is no connection to the database and the following error appears:
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    I added several DAD’s to /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/mod_plsql/dads.conf like this:
    <Location /pls/jd-download-dev>
    SetHandler pls_handler
    Order allow,deny
    Allow from All
    AllowOverride None
    PlsqlDatabaseUsername w_web_user_download
    PlsqlDatabasePassword @BWKChfgPacV6yQL40lIKZqXUUA9wC4cmAw==
    PlsqlDatabaseConnectString jddev TNSFormat
    PlsqlNLSLanguage German_Germany.WE8ISO8859P1
    PlsqlAuthenticationMode Basic
    PlsqlDefaultPage w_anwendung.p_web_show_document
    PlsqlAlwaysDescribeProcedure Off
    PlsqlErrorStyle DebugStyle
    </Location>
    The passwords were obfuscated with dadTool.pl and the http-Server restarted with /opt/oracle/product/Middleware/asinst_1/bin/opmnctl restartproc process-type=OHS
    The files /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/mod_plsql.cache.conf and /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/moduleconf.plsql.conf were left unchanged.
    Our Test-Application generates the following link
    'http://172.106.2.7:9001/pls/jddevdev/B_ARCHIVE.P_ARCHIVE_VIEW?docfid=200'
    that seems to be ok, because when i replace IP and port with our old IAS it works fine, but the WebLogic Server generates the above mentioned error.
    To get some more information i searched an error_log in /opt/oracle/product/Middleware/asinst_1/diagnostics/logs/OHS/ohs1 but there isn’t any.
    I used the following Documentation for configuring the DADs which is for HTTP Server 11g Release 1 (version 11.1.1), because I could not find one for version 10.3.6.0:
    http://docs.oracle.com/cd/E23943_01/web.1111/e10144/under_mods.htm#i1055269
    So probably there are differences between configuring version 10.3.6.0 and version 11.1.1 and so something is wrong configured or missing...
    Thank you in advance for your help
    Udo

    Hi Raj,
    it is a Sparc Solaris 10
    and yes that's my enviorment.
    After some more tests it's seems it's not a real bug but no realy nice working solution.
    Eclipse uses for all instances the same secure storage, where OEPE also saves the password.
    And if I look right the pasword was saved without the user context, so if you use an other user he takes the same password from the old user.
    and I doesn't know how do OEPE check the connection in reality or only reply the last failed login message.
    After deleting the complete secure storage and test it again with the juno version it works well.

  • WLS 6.1 SP1 URL Rewriting Still Not Working?

              Anyone having success with URL Rewriting? The SessionServlet example is STILL
              not working for me when cookies are disabled. New sessions are created every
              access and the counter never increments past 1.
              Any info would be appreciated.
              Regards, Jeff
              

              The SessionServlet example works fine for me. By default URL re-writing is enabled
              and it will come into picture if the browser doesn't accept cookies.
              Try the examplesWebApp which is in 'examples' domain. It has SessionServlet as
              part of it.
              Sathish Santhanam
              Developer Relations Engineer
              BEA Support
              

  • Jrockit multicast bug on RHEL4, WLS cluster does not works!

    OS and Kernel Version: Linux achilles1 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 16:59:36 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
    We use Bea Weblogic 8.1SP5 with Jrockit JVM 1.4.2 on RHEL3. We upgraded to operating system to RHEL4, and found that the interface binding for multicast communication does not bind to the correct interface, it is always using the default interface. We tried it from a sample program, and found that the error is in the JVM.
    This is a critical error for us, because our application server cluster use multicast for cluster communication.
    No error msg. It seems like this BUG:
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4082533 but it is solved.
    List steps to reproduce the problem:
    socket = new MulticastSocket(i);
    if(s2 != null)
    try
    InetAddress inetaddress = InetAddress.getByName(s2);
    System.out.println("Using interface at " + inetaddress.getHostAddress());
    socket.setInterface(inetaddress);
    System.out.println(socket.getInterface());
    catch(SocketException socketexception)
    throw socketexception;
    }

    Helo,
    You can reproduce it by this way (we have 6 RHEL4 servers, problem is the same). We tried with programs written in C (mcast,Tibco), multicast perfectly works on all interfaces on all servers. But in Java:
    Server:
    [wlxapp@webex3]$ uname -a
    Linux webex3 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 17:05:24 EDT 2006 i686 i686 i386 GNU/Linux
    Problem - with Bea mukticast tester (or any Java class), using the nondefault webex3-priv interface(eth1):
    [wlxapp@webex3]$ java -cp wl9.jar utils.MulticastTest -N webex3_priv -I webex3_priv -A 224.1.1.11 Starting test. Hit any key to abort Using interface at 192.168.1.1 Using multicast address 224.1.1.11:7001 Will send messages under the name webex3_priv every 2 seconds Will print warning every 600 seconds if no messages are received
    I (webex3_priv) sent message num 1
    I (webex3_priv) sent message num 2
    I (webex3_priv) sent message num 3
    Did not receive any message.
    But if we use the default webex3 interface (eth0)
    [wlxapp@webex3]$ java -cp wl9.jar utils.MulticastTest -N webex3 -I webex3 -A 224.1.1.11 Starting test. Hit any key to abort Using interface at 10.4.20.4 Using multicast address 224.1.1.11:7001 Will send messages under the name webex3 every 2 seconds Will print warning every 600 seconds if no messages are received
    I (webex3) sent message num 1
    I (webex3) sent message num 2 Received message 2 from webex3
    I (webex3) sent message num 3 Received message 3 from webex3
    Works perfectly.
    TCPDUMP:Messages are out from server(other srv also see it), so we have problems probably with receiving them:
    [root@webex3]# tcpdump -i eth1
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
    11:42:56.647362 IP webex3_priv.idmz.t-mobile.intra.afs3-callback > 224.1.1.111.afs3-callback: rx type 95 (1472)
    11:42:56.648168 IP webex3_priv.idmz.t-mobile.intra > 224.1.1.111: udp
    11:42:56.648245 IP webex3_priv.idmz.t-mobile.intra > 224.1.1.111: udp
    We examined the lsof output, the tester bind to all interfaces, so it should receive the messages:
    [wlxapp@webex3]$ /usr/sbin/lsof -p 11127
    gij 11127 wlxapp 8u IPv4 150320 UDP *:afs3-callback
    We tried the test with Java 1.4.2 and 1.5 (Jrockit and Sun), the results are the same.
    You can easily reproduce the problem with an RHEL4 server with 2 network interface.
    Our real problem that if multicast have problems, our Weblogic clusters does not works.

  • Application not working with JSF 1.2

    I am new to JSF. I am trying to create a sample application with JSF 1.2. I am using weblogic 10.0. I have followed the instructions give in the whitepaper to configure JSF 1.2.
    http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
    Deployment descriptor contains following content.
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>AlfaInsPortalWebApp</display-name>
    <context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>server</param-value>
    <!--<description>
                   State saving method: "client" or "server" (= default)
                   See JSF Specification 2.5.2
              </description>-->
    </context-param>
    <listener>
    <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
    </listener>
    <servlet>
    <servlet-name>faces</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    </servlet>
    <servlet-mapping>
    <servlet-name>faces</servlet-name>
    <url-pattern>*.jsf</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>faces</servlet-name>
    <url-pattern>*.faces</url-pattern>
    </servlet-mapping>
    <welcome-file-list>
    <welcome-file>index.jsf</welcome-file>
    <welcome-file>index.faces</welcome-file>
    <welcome-file>index.html</welcome-file>
    <welcome-file>index.htm</welcome-file>
    <welcome-file>index.jsp</welcome-file>
    <welcome-file>default.html</welcome-file>
    <welcome-file>default.htm</welcome-file>
    <welcome-file>default.jsp</welcome-file>
    </welcome-file-list>
         <session-config>
         <session-timeout>30</session-timeout>
         </session-config>
    </web-app>
    Weblogic.xml contains reference to following libraries
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
         <wls:container-descriptor>
              <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
         </wls:container-descriptor>
    <wls:context-root>AlfaInsPortalWebApp</wls:context-root>
    <wls:library-ref>
    <wls:library-name>jstl</wls:library-name>
    <wls:specification-version>1.2</wls:specification-version>
    <wls:exact-match>true</wls:exact-match>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-tools-visitor-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-tools-framework-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-commonui-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-framework-full-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-clipper-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-lookandfeel-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-rest-full-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-framework-rest-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-rest-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-light-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-wsrp-producer-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-framework-common-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-framework-struts-1.2-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>struts-1.2</wls:library-name>
    <wls:specification-version>1.2</wls:specification-version>
    <wls:exact-match>true</wls:exact-match>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wlp-services-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>content-management-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>beehive-netui-1.0.1-10.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:exact-match>true</wls:exact-match>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>beehive-netui-resources-1.0.1-10.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:exact-match>true</wls:exact-match>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>p13n-web-lib</wls:library-name>
    <wls:specification-version>10.2.0</wls:specification-version>
    <wls:implementation-version>10.2.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>jsf</wls:library-name>
    <wls:specification-version>1.2</wls:specification-version>
    <wls:implementation-version>1.2.3.1</wls:implementation-version>
    </wls:library-ref>
    </wls:weblogic-web-app>
    When i start the application server following logs were obtained
    Apr 9, 2010 7:09:32 AM com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
    Apr 9, 2010 7:09:33 AM com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
    Apr 9, 2010 7:09:33 AM com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
    Apr 9, 2010 7:09:33 AM com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
    When i invoke the application I get the following error.
    java.lang.NoSuchMethodError: initView
         at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:92)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Please help me in configuring JSF 1.2.

    If you are new to JSF, then I'd try and simplify the environment in which you are working as the first step to achieving a successful outcome.
    JSF 1.2 is a certified and well tested component of WLS, so we know it works. I'm not sure of the effect of all those additional modules you are adding in there -- it appears as if you have gotten a Faces implementation instantiated, but there could be some form of version difference/conflict since it can't find a method its looking for.
    Using Oracle Enterprise Pack for Eclipse (http://www.oracle.com/technology/software/products/oepe/oepe_11115.html) you can build yourself out a pretty simple JSF application to get started from and deploy it to a WLS server. This would remove all the additional libraries you currently have, provide you with a bundled applicaton to deploy and give you a pretty good environment from which you can learn and experiment with JSF.
    -steve-

  • Application is not working in Different environments

    Hi Experts,
    I am working in jdev 11.1.1.3.0 with ADF BC
    I have deployed my application in 1 environment it's working fine, the same application i depoyed in another environment it's not working.
    in the log i am getting as
    <Started WebLogic Managed Server "CardEmbosser_ms2" for domain "WLINTQA1" running in Production Mode>
    <Sep 15, 2010 10:31:27 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Sep 15, 2010 10:31:27 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Sep 15, 2010 10:36:12 AM EDT> <Notice> <StdErr> <BEA-000000> <Sep 15, 2010 10:36:12 AM oracle.mds.internal.lcm.logging.MDSLCMLogger info
    INFO: Application ID : CardEmbossNewUI#V2.0>
    <Sep 15, 2010 10:36:13 AM EDT> <Notice> <StdErr> <BEA-000000> <Sep 15, 2010 10:36:13 AM oracle.mds.internal.lcm.logging.MDSLCMLogger info
    INFO: "Metadata Services: Metadata archive (MAR) not found.">
    <Sep 15, 2010 10:36:33 AM EDT> <Notice> <StdErr> <BEA-000000> <Sep 15, 2010 10:36:33 AM com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Mojarra (1.2_09-20081212-SNAPSHOT) for context '/CardEmbossNewUI'>
    <Sep 15, 2010 10:37:01 AM EDT> <Notice> <StdErr> <BEA-000000> <Sep 15, 2010 10:37:01 AM oracle.adf.mbean.share.connection.ConnectionsRuntimeMXBeanImpl getNonCachedConnectionsContext
    INFO: Registering Connection Runtime MBean>
    <Sep 15, 2010 10:37:04 AM EDT> <Notice> <StdErr> <BEA-000000> <Sep 15, 2010 10:37:04 AM oracle.adf.share.jndi.ReferenceStoreHelper getReferencesMapEx
    WARNING: Incomplete connection reference object for connection:Apps>
    <Sep 15, 2010 10:38:01 AM EDT> <Notice> <StdErr> <BEA-000000> <Sep 15, 2010 10:38:01 AM oracle.jbo.uicli.mom.CpxUtils$Visitor logMainApplicationCpx
    INFO: zip:/opt/oracle/domains/WLINTQA1/servers/CardEmbosser_ms2/tmp/_WL_user/CardEmbossNewUI_V2.0/jk9b9a/war/WEB-INF/lib/_wl_cls_gen.jar!/view/DataBindings.cpx>
    Can any one suggest me what is wrong here.

    Error which i am getting while going from one page to another page is:
    <Sep 16, 2010 8:58:36 AM EDT> <Notice> <StdErr>
    <BEA-000000> <Sep 16, 2010 8:58:36 AM oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator handleError
    SEVERE: Server Exception during PPR, #15
    javax.servlet.ServletException: java.lang.NoClassDefFoundError: javax/faces/webapp/UIComponentTag$UIComponentTagAdapter
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:341)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
    at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
    at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
    at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
    at weblogic.work.ExecuteThread.executeExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.NoClassDefFoundError: javax/faces/webapp/UIComponentTag$UIComponentTagAdapter
    at oracle.adfinternal.view.faces.model.FacesExpressionEvaluator._evaluate(FacesExpressionEvaluator.java:58)
    at oracle.adfinternal.view.faces.model.FacesExpressionEvaluator.evaluate(FacesExpressionEvaluator.java:36)
    at oracle.adfinternal.view.faces.model.FacesExpressionEvaluator._evaluate(FacesExpressionEvaluator.java:79)
    at oracle.adfinternal.view.faces.model.FacesExpressionEvaluator.evaluate(FacesExpressionEvaluator.java:36)
    at oracle.adf.model.binding.DCUtil.elEvaluate(DCUtil.java:796)
    at oracle.adf.model.binding.DCBindingContainer.evaluateParameterWithElCheck(DCBindingContainer.java:1452)
    at oracle.adf.model.binding.DCBindingContainer.evaluateParameter(DCBindingContainer.java:1501)
    at oracle.adf.model.binding.DCParameter.internalEvaluateExpresion(DCParameter.java:202)
    at oracle.adf.model.binding.DCParameter.evaluateValue(DCParameter.java:76)
    at oracle.adf.model.binding.DCParameter.getValue(DCParameter.java:111)
    at oracle.jbo.uicli.binding.JUSearchBindingCustomizer.getCriteriaName(JUSearchBindingCustomizer.java:1956)
    at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding._getCurrentViewCriteriaName(FacesCtrlSearchBinding.java:3600)
    at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding.getQueryDescriptor(FacesCtrlSearchBinding.java:153)
    at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding.internalGet(FacesCtrlSearchBinding.java:3414)
    at oracle.adf.model.binding.DCExecutableBinding.get(DCExecutableBinding.java:115)
    at javax.el.MapELResolver.getValue(MapELResolver.java:164)
    at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
    at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
    at com.sun.el.parser.AstValue.getValue(AstValue.java:118)
    at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
    at org.apache.myfaces.trinidad.bean.FacesBeanImpl.getProperty(FacesBeanImpl.java:68)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.getProperty(UIXComponentBase.java:1197)
    at oracle.adf.view.rich.component.UIXQuery.getValue(UIXQuery.java:442)
    at oracle.adf.view.rich.component.UIXQuery._setupAndStoreContextInRequest(UIXQuery.java:267)
    at oracle.adf.view.rich.component.UIXQuery.invokeOnComponent(UIXQuery.java:157)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnNamingContainerComponent(UIXComponentBase.java:1383)
    at oracle.adf.view.rich.component.fragment.UIXRegion.invokeOnComponent(UIXRegion.java:544)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at oracle.adf.view.rich.component.fragment.UIXInclude.invokeOnComponent(UIXInclude.java:141)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnChildrenComponents(UIXComponentBase.java:1333)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.invokeOnComponent(UIXComponentBase.java:1427)
    at oracle.adf.view.rich.component.rich.RichDocument.invokeOnComponent(RichDocument.java:161)
    at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:731)
    at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:675)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._fixClientIds(LifecycleImpl.java:925)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:378)
    at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
    at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         ... 34 more
    Caused by: java.lang.ClassNotFoundException: javax.faces.webapp.UIComponentTag$UIComponentTagAdapter
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
    ... 106 more>
    Can any one help me, it's very urgent for me, what may be the issue here.

  • Weblogic Http Apache Plugin not working

    Hi,
    I have installed weblogic server 10.3 on WindowsXP Professional and Http Apache 2.2 is running on port 80. I followed the following document to configure the Apache plugin:
    http://e-docs.bea.com/wls/docs103/plugins/apache.html
    but when I go and test the plugin it always comes back with 404 page not found. As per the documentation I am testing it as
    http://localhost:80/weblogic/
    Here is my httpd.conf
    Include "C:/bea/alui/plumtreeconf/"
    # This is the main Apache HTTP server configuration file.  It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do.  They're here only as hints or reminders.  If you are unsure
    # consult the online docs. You have been warned. 
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path.  If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    # with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the
    # server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log".
    # NOTE: Where filenames are specified, you must use forward slashes
    # instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
    # If a drive letter is omitted, the drive on which httpd.exe is located
    # will be used by default.  It is recommended that you always supply
    # an explicit drive letter in absolute paths to avoid confusion.
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path.  If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk.  If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "C:/Program Files/Apache Software Foundation/Apache2.2"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    #LoadModule authn_alias_module modules/mod_authn_alias.so
    #LoadModule authn_anon_module modules/mod_authn_anon.so
    #LoadModule authn_dbd_module modules/mod_authn_dbd.so
    #LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authn_file_module modules/mod_authn_file.so
    #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    #LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_host_module modules/mod_authz_host.so
    #LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule cache_module modules/mod_cache.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule cgi_module modules/mod_cgi.so
    #LoadModule charset_lite_module modules/mod_charset_lite.so
    #LoadModule dav_module modules/mod_dav.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule dav_lock_module modules/mod_dav_lock.so
    #LoadModule dbd_module modules/mod_dbd.so
    #LoadModule deflate_module modules/mod_deflate.so
    LoadModule dir_module modules/mod_dir.so
    #LoadModule disk_cache_module modules/mod_disk_cache.so
    #LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule env_module modules/mod_env.so
    #LoadModule expires_module modules/mod_expires.so
    #LoadModule ext_filter_module modules/mod_ext_filter.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule filter_module modules/mod_filter.so
    #LoadModule headers_module modules/mod_headers.so
    #LoadModule ident_module modules/mod_ident.so
    #LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule include_module modules/mod_include.so
    #LoadModule info_module modules/mod_info.so
    LoadModule isapi_module modules/mod_isapi.so
    #LoadModule ldap_module modules/mod_ldap.so
    #LoadModule logio_module modules/mod_logio.so
    LoadModule log_config_module modules/mod_log_config.so
    #LoadModule log_forensic_module modules/mod_log_forensic.so
    #LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule proxy_module modules/mod_proxy.so
    #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    #LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule setenvif_module modules/mod_setenvif.so
    #LoadModule speling_module modules/mod_speling.so
    #LoadModule ssl_module modules/mod_ssl.so
    #LoadModule status_module modules/mod_status.so
    #LoadModule substitute_module modules/mod_substitute.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    #LoadModule userdir_module modules/mod_userdir.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule version_module modules/mod_version.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule weblogic_module modules/mod_wl_22.so
    <IfModule mod_weblogic.c>
      WebLogicHost localhost
      WebLogicPort 7001
    </IfModule>
    <Location /weblogic>
      SetHandler weblogic-handler
      PathTrim /weblogic
    </Location>
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch. 
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User daemon
    Group daemon
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition.  These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed.  This address appears on some server-generated pages, such
    # as error documents.  e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName localhost:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "C:/Program Files/Apache Software Foundation/Apache2.2/htdocs"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features. 
    ProxyRequests On
    <Directory />
        Options FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "C:/Program Files/Apache Software Foundation/Apache2.2/htdocs">
        # Possible values for the Options directive are "None", "All",
        # or any combination of:
        #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
        # Note that "MultiViews" must be named *explicitly* --- "Options All"
        # doesn't give it to you.
        # The Options directive is both complicated and important.  Please see
        # http://httpd.apache.org/docs/2.2/mod/core.html#options
        # for more information.
        Options Indexes FollowSymLinks
        # AllowOverride controls what directives may be placed in .htaccess files.
        # It can be "All", "None", or any combination of the keywords:
        #   Options FileInfo AuthConfig Limit
        AllowOverride None
        # Controls who can get stuff from this server.
        Order allow,deny
        Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
        DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
        Order allow,deny
        Deny from all
        Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here.  If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "logs/error.log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
        # The following directives define some format nicknames for use with
        # a CustomLog directive (see below).
        LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
        LogFormat "%h %l %u %t \"%r\" %>s %b" common
        <IfModule logio_module>
          # You need to enable mod_logio.c to use %I and %O
          LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
        </IfModule>
        # The location and format of the access logfile (Common Logfile Format).
        # If you do not define any access logfiles within a <VirtualHost>
        # container, they will be logged here.  Contrariwise, if you *do*
        # define per-<VirtualHost> access logfiles, transactions will be
        # logged therein and *not* in this file.
        CustomLog "logs/access.log" common
        # If you prefer a logfile with access, agent, and referer information
        # (Combined Logfile Format) you can use the following directive.
        #CustomLog "logs/access.log" combined
    </IfModule>
    <IfModule alias_module>
        # Redirect: Allows you to tell clients about documents that used to
        # exist in your server's namespace, but do not anymore. The client
        # will make a new request for the document at its new location.
        # Example:
        # Redirect permanent /foo http://localhost/bar
        # Alias: Maps web paths into filesystem paths and is used to
        # access content that does not live under the DocumentRoot.
        # Example:
        # Alias /webpath /full/filesystem/path
        # If you include a trailing / on /webpath then the server will
        # require it to be present in the URL.  You will also likely
        # need to provide a <Directory> section to allow access to
        # the filesystem path.
        # ScriptAlias: This controls which directories contain server scripts.
        # ScriptAliases are essentially the same as Aliases, except that
        # documents in the target directory are treated as applications and
        # run by the server when requested rather than as documents sent to the
        # client.  The same rules about trailing "/" apply to ScriptAlias
        # directives as to Alias.
        ScriptAlias /cgi-bin/ "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
        # ScriptSock: On threaded servers, designate the path to the UNIX
        # socket used to communicate with the CGI daemon of mod_cgid.
        #Scriptsock logs/cgisock
    </IfModule>
    # "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value.  If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
        # TypesConfig points to the file containing the list of mappings from
        # filename extension to MIME-type.
        TypesConfig conf/mime.types
        # AddType allows you to add to or override the MIME configuration
        # file specified in TypesConfig for specific file types.
        #AddType application/x-gzip .tgz
        # AddEncoding allows you to have certain browsers uncompress
        # information on the fly. Note: Not all browsers support this.
        #AddEncoding x-compress .Z
        #AddEncoding x-gzip .gz .tgz
        # If the AddEncoding directives above are commented-out, then you
        # probably should define those extensions to indicate media types:
        AddType application/x-compress .Z
        AddType application/x-gzip .gz .tgz
        # AddHandler allows you to map certain file extensions to "handlers":
        # actions unrelated to filetype. These can be either built into the server
        # or added with the Action directive (see below)
        # To use CGI scripts outside of ScriptAliased directories:
        # (You will also need to add "ExecCGI" to the "Options" directive.)
        #AddHandler cgi-script .cgi
        # For type maps (negotiated resources):
        #AddHandler type-map var
        # Filters allow you to process content before it is sent to the client.
        # To parse .shtml files for server-side includes (SSI):
        # (You will also need to add "Includes" to the "Options" directive.)
        #AddType text/html .shtml
        #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://localhost/subscription_info.html
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files.  This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    #Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    #Include conf/extra/httpd-autoindex.conf
    # Language settings
    #Include conf/extra/httpd-languages.conf
    # User home directories
    #Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    #Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    # Note: The following must must be present to support
    #       starting without SSL on platforms with no /dev/random equivalent
    #       but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>Is there anything else I need to add to this file. As I am trying to install ALUI and for this I need to add the plugin as when I go to my portal page none of the
    images shows. Any help is appreciated.
    Thanks

    Hi,
    There is patch for the webserver(Apache Plugin),thats needs to be downloaded from Metalink,dont use the default plugin that comes with the weblogic 10.3 installtion.
    Regards,
    Dinesh

  • Configuration Template Builder WL8.1 does not work

    Hello,
         After spending nearly 2 days now trying to get a Configuration Template
    built, I've concluded this simply does not work. Has anyone used the
    Config Template builder to package a semi-complex application on top of WLI?
         I'm trying to have 2 of my applications, the JMS and JDBC resources,
    and a WLI event generator packaged up for easy deployment to someone
    else's server configuration. The problem with this is that there are
    required resources for WLI, namely a database. The Pointbase database
    included for WLI does not get included in the template automatically.
    There are also some flat-out bugs:
    If you choose to include a resource adapter "application", such as
    jms-xa-adp.rar, the template builder does not bundle this in the
    template and deploy it correctly. The template builder restricts you to
    putting applications in the relative path starting at ./
    For jms-xa-adp.rar, its original location is in $WL_HOME/server/lib, and
    the template builder defaults to put it in ./lib of your template.
    However, when you create a domain with the template, jms-xa-adp.rar does
    not get placed in your ./lib directory. This causes you to then go and
    manually edit your config.xml to point back at $WL_HOME/server/lib or to
    manually copy jms-xa-adp.rar into your ./lib directory (which the
    template mechanism should do for you).
    Relative paths in the config.xml file require you to execute the config
    builder from the directory of the domain you are making a template for.
    The template builder should instead be smart enough to realize that
    relative paths in the config.xml file are relative to the directory that
    the config.xml is in, not the one you are running the template builder
    from. You'll get an error when trying to create the template cause it
    won't find the resources if you're not in that directory.
    If anyone has successfully used this to package a WLI application in a
    template, please share your experiences and how to do so. In the
    meantime, I'm claiming there is no way to nicely package up a server
    configuration for a WLI app in Weblogic, and this is a big shortcoming.
    Weblogic needs a simple transferrable way of creating server
    configurations (it tries to do this with the template, but that is
    failing). With JBoss, for example, you simply copy your server directory
    into another installation. This doesn't work with Weblogic unfortunately
    because it puts hard-coded paths in the config.xml file.
    Thanks

    Russ,
         Thank you for the detailed responses. The only one I'm currently
    struggling with still is the #5, with the scripts between the two. One
    of the major benefits of using a J2EE App Server is supposed to be the
    portability between servers. I find it disconcerting that BEA Weblogic
    restricts me to the platform I created the domain on by creating
    platform-specific startup/shutdown scripts for only the platform created
    on. It's understandable that a script converter would be difficult, but
    at least both the .sh/.cmd files should be created from the first time
    you make a domain. If the user only wants one or the other, they can
    delete the appropriate one. It's also understandable that the
    users/deployers shouldn't have to manually convert a startup/shutdown
    script to take the domain to a different box.
         JBoss clearly has BEA beat on ease of deployment here. Their model is
    the concept I'm thinking of: you have some generic startup/shutdown
    scripts that can load a platform-independent server configuration. You
    truly can copy directories as-is between JBoss installations.
         I was hoping to package up a server domain for use on any of the
    supported platforms, but since I don't have the time to manually convert
    the startup/shutdown scripts, I'm going to have to tell people it's only
    for Solaris now.
         Hopefully BEA can fix this in a future SP. There's no need for this
    platform-dependency. Also, if the Windows version can generate both
    scripts at creation time, then the Solaris should be able to do this as
    well (or at least give you the option).
    Thanks again for the replies
    russ wrote:
    Hi Steven,
    I have several comments and questions about your last two posts. I will try to
    address them in order.
    1) "The Pointbase database included for WLI does not get included in the template
    automatically."
         By default the template builder only includes the *.cmd and *.sh files in the
    template from your domain directory. If you begin building with an existing
    domain template all files that were in the template will get included. This was
    done because there is no way for the builder to automatically determine all the
    files that are required by your template/domain and we steered away from recursively
    including all files from the directory so that unused files were not needlessly
    included. We can extrapolate some files based on the application paths in the
    config.xml, but the rest is left up to the template builder to be aware of what
    is needed for their domain to run. So, if you need the Pointbase *.dbn and *.wal
    files included in your template just select these files on the ?Add Files? panel
    of the template builder and add them to the ?Domain Directory?.
    2) ?If you choose to include a resource adapter "application", such as jms-xa-adp.rar,
    the template builder does not bundle this in the template and deploy it correctly.?
         The template builder considers application files to be in two categories: Imported
    or Internal. When you are at the ?Add Applications? panel of the builder you
    will see a checklist of all the applications that are in the domain you selected.
    On the right hand side there are two text fields. The top one displays the application
    path as it is currently set in the config.xml of that domain. The bottom field
    will be different depending on what category the application falls into. As you
    click on each application in the list, you may notice that the bottom field may
    change from an editable field titled ?Imported Application Path? to a non-editable
    field titled ?Internal Application Path?. The difference between the two categories
    is that an ?Imported? application?s files will be included in the template jar.
    An ?Internal? application?s files will not be included in the template jar because
    they are considered internal to the weblogic installation. The jms-xa-adp.rar
    should fall into the internal category and should not get included in your template.
         From what you are describing it sounds like the builder attempted to import that
    application when it should not have. In an attempt to recreate the problem you
    are seeing I deployed that Connector Module through the WLS console and ended
    up with an application path of ?C:\bea\weblogic81\server\lib? where ?C:\bea\weblogic81?
    is my WL_HOME (a.k.a. USER_INSTALL_DIR). If I then attempt to build a template
    from this domain, the builder recognizes this as an internal path and does not
    include it inside my template. If the current application path you had looks
    different from the one above, that may explain why the builder was attempting
    to import it. What was the value of the ?Current Application Path? for that application
    deployment?
    3) ?Relative paths in the config.xml file require you to execute the config builder
    from the directory of the domain you are making a template for.?
         The builder is ?smart? enough to determine relative paths. You should not have
    to invoke it from the domain directory you are working with. There is a known
    bug in the WebLogic Platform 8.1.1.0 release of the template builder that will
    cause it to not find files with relative paths in your domain directory if the
    application path in the config.xml is just a ?.?. If this is the case, you should
    see a FileNotFoundException when you attempt to create the template. This will
    be fixed in SP2 and you can work around this problem by changing those paths to
    ?./? instead. If this was not the case, what was the path the wizard choked
    on?
    4) ?Looking through the config file, it seems that it's all of the WLI components
    that have absolute paths in the config file. In addition, BEA_WLS_DBMS_ADK has
    an absolute path, not sure if that is WLI or WLS. ?
         BEA_WLS_DBMS_ADK is an integration application. If you created the original
    domain using the configuration wizard most of the applications in an integration
    enabled domain will reference paths inside of you installation directory or ?internal?
    paths. For instance, I used the wizard to create a ?Basic WebLogic Integration
    Domain?. The path for that application in this domain is: ?C:\bea\weblogic81/integration/adapters/dbms/lib/BEA_WLS_DBMS_ADK.ear?
    where ?C:\bea\weblogic81? is my WL_HOME or USER_INSTALL_DIR. When I load this
    domain into the builder it shows this application as ?internal? and the ?Internal
    Application Path? is "$USER_INSTALL_DIR$/integration/adapters/dbms/lib/BEA_WLS_DBMS_ADK.ear".
    This will be set as the path value of this application in the config.xml that
    will be included in the template you build. When you later use the Configuration
    Wizard on this template it will substitute the $USER_INSTALL_DIR$ to the value
    of the installation directory of the machine you are creating it on.
         If you were to Change these to relative paths, as Mark previously suggested,
    it will only work if you copy the domain directory to the same location relative
    to your installation directory on the target machine. Also, if you copy the domain
    in this manner you will more than likely run into problems with your start/stop
    scripts and be forced to hand modify all the paths contained within. The configuration
    wizard tries to alleviate these problems and make the configuration entirely portable.
    This gives the user who creates the domain from your template the ability to
    put it anywhere they want regardless of the paths in the config.xml.
    5) ?However, there is another major problem with the Template Builder: it only
    includes the startup/shutdown script for the platform you create the template
    on. ???I built the template on Solaris with the UNIX scripts. However, I tried
    to create a new config on Windows with this template, and the scripts were not
    converted to .bat files!?
         As I stated previously, the builder will only include *.cmd and *.sh scripts
    into your template by default. If you created the domain on a unix platform using
    the configuration wizard it will not extract the *.cmd files since these aren?t
    considered to be useful on unix. If you were then to attempt building a template
    from this domain and take it onto a windows platform, it will obviously be missing
    any windows scripts. Conversely, the wizard will extract *.sh scripts on windows
    because they can still be useful if a user has an MKS or Cygwin type environment
    installed. The config wizard and template builder do not have the ability to convert
    scripts. The builder will only include existing scripts that are in your domain
    directory and automatically determine any necessary string substitutions that
    will be needed. Please note that since WebLogic is only supported on the NT/2K/XP
    versions of windows you will find that the wizards use ?.cmd? files and not ?.bat?
    files since these are more commonly associated with Win 95/98/ME.
         I will be happy to answer any more questions you may have and would also like
    to take a look at your domain configuration to try and get a better understanding
    of the problems you are encountering.
    thanx,
    russ

Maybe you are looking for