Error 404 on Tomcat 5.x w/ simple helloworld

since my first Tomcat installation (about 2 weeks ago) i can't execute a servlet.
I've red in many topics ... my question is:
Under webapps i've create:
examples
|--WEB-INF
|--classes
and put my hello.class in it.
Also create web.xml in WEB-INF folder as:
<webapp>
<display-name>hello</display-name>
<description>hello</description>
<servlet>
<servlet-name>hello</servlet-name>
<servlet-class>hello</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>hello</servlet-name>
<url-pattern>/examples</url-pattern>
</servlet-mapping>
</webapp>
I have red somewhere to modify server.xml & insert the context path
When i opened server.xml i looked a lot of section <service ... listener ... engine ...
where have i put the context path tag?
and how is the code?
Is that enough to run my servlet?
P.S.: Tomcat 5.x doesn't configure any webapps/examples folder by default!
Thks in first

since my first Tomcat installation (about 2 weeks ago)
i can't execute a servlet.
I've red in many topics ... my question is:
Under webapps i've create:
examples
|--WEB-INF
|--classes
Very good - this is correct. I'd recommend that you rename that directory under webapps to something else, anything other than examples. Call it MyFirstServlet.
and put my hello.class in it.You should put your hello.class in a package of some kind. Tomcat doesn't play nicely with servlets and beans that aren't in packages. You'll have to add "package" to your source and recompile, of course.
Also create web.xml in WEB-INF folder as:No, this is incorrect. Your web.xml does go in WEB-INF, but it should look like this:
<webapp>
    <display-name>hello</display-name>
    <description>hello</description>
    <servlet>
        <servlet-name>hello</servlet-name>
        <servlet-class>yourPackage.hello</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>hello</servlet-name>
        <url-pattern>/hello</url-pattern>
    </servlet-mapping>
</webapp>
I have red somewhere to modify server.xml & insert the
context path
You don't need to modify server.xml at all.
Now your browser URL will look like this:
http://localhost:8080/MyFirstServlet/helloSee if this works.
I'd also recommend that you follow the Sun Java coding conventions and start class names with a capital letter.

Similar Messages

  • Getting error 404 when iam running a simple login servlet in tomcat

    hi
    this is my Login.java
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    public class Login extends HttpServlet
         public void doPost(HttpServletRequest rq, HttpServletResponse rs)
              String username =rq.getParameter("username");
              String password =rq.getParameter("password");
    try{
              rs.setContentType("text/html");
              PrintWriter out=rs.getWriter();
              out.println("<html><body>");
              out.println("thank u, " + username + "you r logged sucessfully");
              out.println("</body></html>");
              out.close();
              }catch(Exception e){
                   e.printStackTrace();
    i have saved in the form ofC:\Program Files\apache-tomcat-4.1\webapps\sravan\WEB-INF\classes\Login.class
    where sravan is my folder
    step 2: Login.html
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <html>
    <head>
    <title>login page</title></head>
    <body>
    <h1> WELCOME TO THE SERVLET HOME PAGE</h1>
    ENTER UR USERNAME AND PASSWORD
    <form action="/sravan/Login" method="Post">
         username<input type="text" name="username" >
         password<input type="password" name="password" >
         <input type="submit" value="submit"></form>
         </body>
    </html>
    i have saved in the form C:\Program Files\apache-tomcat-4.1\webapps\sravan\Login.html
    step3:
    my web.xml
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    <display-name>beginning j2ee</display-name>
    <servlet>
    <servlet-name>Login</servlet-name>
    <servlet-class>Login</servlet-class>
    </servlet>
    <servlet-mapping>
    <servlet-name>Login</servlet-name>
    <url-pattern>Login</url-pattern>
    </servlet-mapping>
    </web-app>
    i have saved in C:\Program Files\apache-tomcat-4.1\webapps\sravan\WEB-INF\web.xml
    step4:
    here is my server.xml
    <Context path="/sravan" docBase="sravan" debug="0" reloadable="true" privileged="true"/>
    saved in C:\Program Files\apache-tomcat-4.1\webapps\sravan\WEB-INF\server.xml
    everything is fine....program is compiled ...but when iam running the servlet in tomcat iam getting error 404 Login.html not found....
    so plz kindly help me this my first servlet .....

    There seems not to be any '.html' in your url-pattern
    <url-pattern>Login</url-pattern>- so i presume you should use
    http://yourhost/Logininstead.

  • Error 404 missing page with BO EDGE 3.1 SP3 - Tomcat via wdeploy

    Hi,
    We have a problem with the deployment of the webapps on Tomcat 5.5 (5.5.31) of our BO Edge 3.1 SP3 installation.
    All seems to be working fine untill we try to open a WebI document or try to create a new document (any).  Whenever we try to perform one of those actions we always receive an http error 404: Requested resource() is not available...
    I already browsed through other threads and it says that some of the war files could be corrupted. So we undeployed and redeployed, but no progress towards the error...
    Another solution is to see in the java/webapps in the installation directory and compare to the files deployed in the Tomcat directory but I detected no changes.
    We have this issue on 2 of our web servers on which we deployed the war files: our internal webserver, and on our webserver in the DMZ.
    The strange is that when I try to connect with yet another web server that isn't yet updated (from our current production environment) all features are working fine... However  SAP/BusinessObjects states that you should always perform an update of your war files as well (I noticed some differences in size between the different version, so I guess that it is really needed to redeploy...)
    Is anyone else experiencing the same problem?
    How can this be solved?   We really want to go to the latest SP and deploy it in the DMZ zone.
    Any advise is appreciated.
    Jorn

    Antatack,
    this the exact procedure we have followed.  We did redeploy all war files because we updated to SP 3.
    However:
    now we get an error message when we try to open a WebI document
    now we get an error message when we try to create a new document (Webi, Deski, ...)
    when we test it from our webserver running the war files from XI 3.1 all works well.
    We cannot find a difference in the war files on the Edge server and the ones deployed on the Webserver(s)
    Can someone please help us out?

  • Simple OC4J Problem. Can't open localhost error: 404 Not Found

    Hi, I am a new to Oracle Application developmen. I just installed Application server 10g R1 [ as where i am doing an internship they are using this version]. I have installed OC4J as guided in installation guide. But when it comes to testing the oc4j server, as they ask to test it by this url: http://localhost:8888/ .. On chrome it gives an error: 404 Not Found Resource / not found on this server and on internet explorer it gives: The page cannot be displayed.
    Your response will be highly appreciated. Thankyou

    Instead of redirect add the default suffix in web.xml.
    <context-param>
    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
    <param-value>.jsf</param-value>
    </context-param>

  • While running servlets getting errors 404 or 505 resource not found

    Hi all,
    I'm novice to J2EE.
    I've encountered a problem while accessing the deployed module in weblogic 8.1 server.
    I'm sure that the webapplication module is deployed as i saw my module in administration console & also the status said that it is deployed.
    when i access my web application by specifying the proper server and port no and context root it is showing
    either 505 - resource not found error(http://localhost:7001/Suresh-2/Suresh) or 404 - not found error.( http://localhost:7001/Suresh-2/Suresh)
    Now let me elaborate what i've done till now.
    My webapplication folder structure is : C:\bea\user_projects\domains\mydomain\applications\Suresh\WEB-INF\classes\Sai\ServExamp.class
    My servlet is ServExamp.java
    I created a folder called "Suresh".  In that folder created another folder called "WEB-INF".  In WEB-INF created a folder called "Classes".
    Since my servlet is in package "Sai", the .class file reside in \Suresh\WEB-INF\Classes\Sai\ServExamp.class
    The source code is :
    package Sai;
    import javax.servlet.;*
    import javax.servlet.http.;*
    import java.io.;*
    public class ServExamp extends HttpServlet
    public void doPost(HttpServletRequest req,HttpServletResponse res)throws IOException
    PrintWriter out=res.getWriter();
    java.util.Date today=new java.util.Date();
    out.println("<html>"+"<body>"+
    *"<h1 align=center>HF\'s Chapter1 Servlet </h1>"*
    +"<br>"+today+"</body>"+"</html>");
    Now i'm almost done creating a web application.  Next, I constructed a simple web.xml descriptor that gives a web friendly name for my servlet, and points to the servlet. I constructed  web.xml descriptor file in the WEB-INF folder (C:\bea\user_projects\domains\mydomain\applications\Suresh\WEB-INF\).
    The web.xml file source is :
    *<!DOCTYPE web-app*
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    *"http://java.sun.com/dtd/web-app_2_3.dtd">*
    *<web-app>*
    *<display-name>Hello World Web Application</display-name>*
    *<description>Test Servlet</description>*
    *<servlet>*
    *<servlet-name>ServExamp</servlet-name>*
    *<servlet-class>Sai.ServExamp</servlet-class>*
    *</servlet>*
    *<servlet-mapping>*
    *<servlet-name>ServExamp</servlet-name>*
    *<url-pattern>/Suresh</url-pattern>*
    *</servlet-mapping>*
    *</web-app>*
    Now I have told Weblogic that the URI /Suresh corresponds to my servlet "Sai.ServExamp".
    My Web Application is ready to be deployed at this point. I logged onto Weblogic's admin console,
    *1) clicked on deployments, then navigated to "Web Application Modules" .*
    *2) Clicked "Deploy new Web Application Module"*
    *3) Navigated to the location of your web application folder (Suresh). There was a radio button next to it indicating that I can select that folder as a valid web application.*
    *4) I Clicked that radio button and clicked "Target Module".*
    *5) It informed that my web application "Suresh" will be deployed to myServer.It asked a name for my web application deployment. By default it was "Suresh"*
    I clicked Deploy.
    *6) After deployment, my web application "Suresh" appeared in the "Web Application Modules" tree on the left.*
    I Clicked on "Suresh"( my web application) then clicked the testing tab, then clicked the link shown there(http://localhost:7001/Suresh-2).
    It was not showing  my servlet (showed a 403 error)
    Error - 403
    This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
    I think so it came b'coz I don't have an index.html or index.jsp page.
    *7)Instead,I added my servlet on to the URL it provided.*
    http://localhost:7001/Suresh-2/Suresh
    It is showing these error code: Http: 505 resource not allowed
    The page cannot be displayed
    The page you are looking for cannot be displayed because the address is incorrect.
    Please try the following:
    If you typed the page address in the Address bar, check that it is entered correctly.
    Open the localhost:7001 home page and then look for links to the information you want.
    Click  Search to look for information on the Internet.
    when i just type : http://localhost:7001/   -> Error 404 not found error
    it's showing
    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 want to run my web application & any help would be appreciated.
    Thanks in advance.
    with regards,
    S.SayeeNarayanan.
    Note: I even deployed my war file, which i got by execution of (jar cv0f webapp.war . ) command from the root directory of my web application i.e. Suresh
    Then executed my webapplication it is showing
    error-505 resource not allowed.
    --------------------------------------------------------------------------------------------

    nammathamizhan wrote:
    Hi all,
    I'm novice to J2EE.
    You're also a novice to this forum.
    First, turn off the bold font.
    Second, post your question once and only once to a single forum. You only waited an hour before reposting your question. That's not the way this works. Asking your question multiple times will not increase the likelihood that you''ll get an answer. As a matter of fact, you're guaranteed nothing at all. Give it your best effort and hope for success. This isn't a paid consultancy - we're volunteers.
    I've encountered a problem while accessing the deployed module in weblogic 8.1 server.
    I'm sure that the webapplication module is deployed as i saw my module in administration console & also the status said that it is deployed.
    when i access my web application by specifying the proper server and port no and context root it is showing
    either 505 - resource not found error(http://localhost:7001/Suresh-2/Suresh) or 404 - not found error.( http://localhost:7001/Suresh-2/Suresh)
    If you're correct, and it's deployed, that would suggest that the URL you gave is incorrect.
    >
    Now let me elaborate what i've done till now.Good info - almost too much.
    %

  • Error 404, JSP file not found

    Hello all
    I am using tomcat on solaris. I have copied my war file under the webapps folder. When I start the tomcat services, it shows the messages for adding the context path for that war file, it also creates a folder for it under webapps but fails to show me any of the jsp pages. I can view all the html and gif files, but none of the jsps (gives the error - 404). If I rename my war file, and then start tomcat services, it works well. I don't want to rename my war file. Pls help!!
    For further details - I have checked my server.xml file, and it is correct. There was an old version of the same folder under webapps, which I got rid off, but seems that somewhere it is still caching it.
    In my server.xml file, if I do
    <Context path="/first"
    docBase="webapps/first"
    crossContext="false"
    debug="0"
    reloadable="true" >
    </Context>
    IT FAILS !! but if I just change the <Context path="/first1" , it works and does not give any error for jsp page. There isn't any contect path named "first" in my server.xml file.
    Thanks in advance.
    Regards
    Anusha

    Actually, I don't know how to create a subdirectory under webapps directory. When I tried to add a subdirectory calle myapp (.../webapps/myapp), I got "The requested URL /application/ was not found on this server" error message. Do I need to modify server.xml or web.xml in conf directory?
    Thanks in advance!
    tacomaZ

  • Error 404 Not Found

    Hi,
    When i am opening an URL(http://hema-vaio:9704/analytics) in IE i'm getting Error 404 not Found some times and some times i'm getting analytics page.how to resolve this issue.

    Hi,
    Some times it may happen due to obiee 11g installation (simple/software only/enterprise ) due to JVM processor speed only. its still starting the Admin server/bi server still in progress please give some time.
    Note: Use JRockit 1.6.0_26 and above version 64bit along with OBIEE11g software only so this will not through like that kind of error. if u goes with simple option with jdk it may slowly starting bi server/admin server thats cause.
    if its not working kindly check the status of u r opmn server via command prompt
    D:\Oracle\Middleware\instances\instance1\bin\opmctl status
    D:\Oracle\Middleware\instances\instance1\bin\opmctl startall
    D:\Oracle\Middleware\instances\instance1\bin\opmctl stopall
    if any one services down make sure try to login to enterprise manager console and check what all services are down.restart it
    for some more ref:
    https://kr.forums.oracle.com/forums/thread.jspa?threadID=1126761
    Thanks
    Deva
    Edited by: Devarasu on Mar 13, 2012 4:01 PM

  • Error 404: the request resource is not available

    Hello,
    I'm a newbie am using the Sun One (Forte 4.0 Community Edition) to develop a JSP/Servlet application.
    I'm using the built-in version of Tomcat, that comes with forte. Tomcat has been installed in tyhe following directory:
    C:\forte\forte4j\tomcat401
    My application has the following path:
    C:\forte\RDoku\tomcat401_base\webapps\designer
    After reading the documentation that comes with this version of Forte, it seems that Tomcat can be configured to work this
    way. Is that correct?
    Anyway, when I start tomcat(within forte), the login page, login.jsp is loaded successfully. The action of the login
    form is servlet/com.doku.login. My web.xml file looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    <!-- Define servlets that are included in the example application -->
    <servlet>
    <servlet-name>login</servlet-name>
         <servlet-class>com.doku.login</servlet-class>
    </servlet>
    </web-app>
    My problem is that when I submit the form, I get the following error:
    Error 404, /servlet/com.doku.login, the request resource (/servlet/com.doku.login) is not available.
    I would really appreciate it if anyone could help me in solving this mystery.
    Regards,
    Rudi

    Hey Rudi
    Everything seems to be in place ..except your package structure..
    your webapp has the context of designer.
    Therfore your directory structure for tomcat should look somewhat like this
    webapps
    --designer
    web-inf < web.xml(i think)
    classes  <Place your class files here(if loose)
    lib < jar files
    1.) Somehow tomcat is creating another context in servlet (unless you have created one yourself).I would urge u to check the invocation for your webapp (By saying that i am pointing at the error /servlet/com.doku.login...instead of /designer/com.doku.login).
    change the action of the form to
    /designer/...instead of /servlet/
    2.)Further..on examining your depoyment descriptor..i found missing entries for the <servlet-mapping> element.Tomcat uses your deployment descriptor to map the incoming requests to your classes.The element must be specified in order to allow a smooth mapping from the request to the corresponding servlet class.
    Let me explain by using an example
    a.)my form action="/designer/Hello" method="get"
    b.)The directory structure for my webapp(designer ) is as above
    c.)web.xml
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    <!-- Define servlets that are included in the example application -->
    <servlet>
    <servlet-name>Hello</servlet-name>
    <servlet-class>package.HelloWorld</servlet-class>
    </servlet>
    <servlet-mapping>
    <servlet-name>Hello</servlet-name>
    <url-pattern>/Hello</url-pattern>
    </servlet-mapping>
    </web-app>
    so for all incoming requests in the form /servlet/Hello will be mapped to your class defined in the package package.HelloWorld
    Let me know if u have more questions.

  • Server error 404

    Hi experts,
    I am new to the bsp concept I creted simple application to display some text on the browser I was done with creation bsp application ,page and everything but when I want to executre it is showing the error in the browser as http server error 404.
    regards,
    Srinivas.D

    Hi Srinivas,
    You will have to activate the services in transaction SICF....
    Go to SICF, click on execute...
    Then it will give you a tree structure....
    drill down to /sap/bc/bsp/sap/your_application_name
    right click on your_application_name and click on activate....
    Hope this helps.
    <b><i>Do reward each useful answer..!</i></b>
    Thanks,
    Tatvagna.

  • Java Servlet page not opening error 404

    Hi!
    I am working with servlets. I compiled the java file and the class file is been moved to
    c:\javawebserver2.0\servlets, and the html files moved to public_html. Html files r opening
    the classpath is mapped to jsdk.jar i.e
    set CLASSPATH=c:\javawebserver2.0\lib\jsdk.jar
    Built-in samples r working without any problem
    when i try to run the servlet
    Page Not Found error 404 occuring
    Please do the favour for me
    thanks

    404 Not Found means you didn't deploy the app properly.
    I think deploying an app like this is a terrible idea. If you have more than one app deployed on a production web server/servlet engine, you wouldn't want to put them all in the same place. "public_html" and the generic "servlets" directory shouldn't be used as dumping grounds for all your apps.
    Learn how to deploy using a WAR file. It'll keep all your apps separate and their constitutive parts together.
    Why Java Web Server? I don't think anyone uses it seriously anymore. Tomcat is the reference implementation of the servlet/JSP specs. I'd download that and use it instead of JWS. JMO, of course.

  • JSP error 404

    Well, i've installed configured and now running Apache2 & Tomcat5 with jk2 connector in a Linux server.
    I create a file index.jsp and put it in <catalina_home>/webapps/examples
    Why tomcat return Error 404 when i use http://192.168.0.1/examples?
    I think that the configuration of connector is ok because the error page is from tomcat and not from Apache.
    i suppose somewhere in Tomcat configuration is wrong, bu t i don't know where.

    YEAH, i've resolve my first problem with Tomcat.
    For anyone who read this topic ....
    For every application (in this case examples), Tomcat wants this folder structure:
    webapps
           |------<my_application>
                                 |------<WEB-INF>
                                                      |------<classes>of course for this examples all the folder are empty except <my_application> where there is index.jsp file
    Ok?
    Thanks to who have replies to me and to everyone spend time to answer topics in this forum

  • Error 404 then the registration of the licence Management

    I have a problem then the registration of the SQL Server Migration Assistant for MySQL licence.
    After the installation, the application ask me to registrer.  On the Sign In Web page, I enter my Win Live Id & password, I clik "Sign In", and  arrive to this page :
    http://www.microsoft.com/404.htm 
    an simple error 404 page.
    I realy need to work with this assistant.
    Do you know a solution, please?
    Thank you.

    Hello,
    Please consider the following resource. Read the “Licensing SSMA” section.
    http://blogs.msdn.com/b/ssma/archive/2011/02/07/mysql-to-sql-server-migration-how-to-use-ssma.aspx
    I had a similar issue when I was trying to download the registration key from the corporate network because of network security enabled.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • "Error 404: file not found"displayed when trying to run a process on server

    Iam trying to run a "weblogic integration-process application" on server to test the application. Iam using weblogic workshop 9.2.
    It is giving me the below error:
    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
    File iam trying to run is RequestQuote.java
    The file is in Tutorial_process_application_web/src/requestquote/
    In the browser it is opening the below link:
    http://localhost:7051/Tutorial_Process_Application_Web/requestquote/RequestQuote.java
    I tried adding "src" in between but still same error is coming. I tried running just http://localhost:7051/, it is opening the weblogic integration window.
    I have pasted the web.xml and all other configuration files below. Please let me know what changes i have to make to get the testing window.
    Thanks,
    Vishu.
    web.xml
    <?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>
    Tutorial_Process_Application_Web</display-name>
    <listener>
    <listener-class>com.bea.wli.management.WliWebAppListener</listener-class>
    </listener>
    <welcome-file-list>
    <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>
    </web-app>
    weblogic.xml
    <?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:context-root>Tutorial_Process_Application_Web</wls:context-root>
    <wls:library-ref>
    <wls:library-name>struts-1.2</wls:library-name>
    <wls:specification-version>1.2</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>jstl</wls:library-name>
    <wls:specification-version>1.1</wls:specification-version>
    <wls:implementation-version>1.1.2</wls:implementation-version>
    </wls:library-ref>
    <wls:url-match-map>weblogic.servlet.utils.SimpleApacheURLMatchMap</wls:url-match-map>
    </wls:weblogic-web-app>
    application.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <application id="Application_ID" version="1.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/application_1_4.xsd">
    <display-name>
    Tutorial_Process_Application_Ear</display-name>
    <module id="WebModule_1180909671484">
    <web>
    <web-uri>Tutorial_Process_Application_Web.war</web-uri>
    <context-root>Tutorial_Process_Application_Web</context-root>
    </web>
    </module>
    <module>
    <ejb>Tutorial_Process_Application_Web_WLI_ProjectBeans</ejb>
    </module>
    <module>
    <ejb>Tutorial_Process_Application_Web_WLI_ComponentBeans</ejb>
    </module>
    </application>
    weblogic-application.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-application 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/j2ee_1_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
    <wls:ejb>
    <wls:start-mdbs-with-application>false</wls:start-mdbs-with-application>
    </wls:ejb>
    <wls:application-param>
    <wls:param-name>webapp.encoding.default</wls:param-name>
    <wls:param-value>UTF-8</wls:param-value>
    </wls:application-param>
    <wls:classloader-structure>
    <wls:classloader-structure>
    <wls:module-ref>
    <wls:module-uri>Tutorial_Process_Application_Web.war</wls:module-uri>
    </wls:module-ref>
    <wls:classloader-structure>
    <wls:module-ref>
    <wls:module-uri>Tutorial_Process_Application_Web_WLI_ProjectBeans</wls:module-uri>
    </wls:module-ref>
    </wls:classloader-structure>
    <wls:classloader-structure>
    <wls:module-ref>
    <wls:module-uri>Tutorial_Process_Application_Web_WLI_ComponentBeans</wls:module-uri>
    </wls:module-ref>
    </wls:classloader-structure>
    </wls:classloader-structure>
    </wls:classloader-structure>
    <wls:listener>
    <wls:listener-class>com.bea.wli.management.WLIAppListener</wls:listener-class>
    </wls:listener>
    <wls:library-ref>
    <wls:library-name>beehive-controls-1.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wls-commonslogging-bridge</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>weblogic-controls-1.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    </wls:weblogic-application>
    Edited by gvishu at 06/04/2007 9:39 AM

    sorry i didnt mention the weblogic workshop version, it is weblogic workshop 9.2.
    Thanks,
    vishu

  • Error 404 -- Not Found, when a Servlet is invoked from browser

    Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
              even the simplest servlet.
              I painstakenly went through all the steps that are listed in the WebLogic
              Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
              have missed a step somewhere.
              I have modified the weblogic.properties file as per all the instrustions,
              but the server simply won't recognize any servlets, not even the SqlServlet
              that came with the server as an example.
              It would require more than 1 exchange of posts to resolve it for me, and I
              am wondering if one of you is willing to work with me on this until I have
              managed to configure the server to make a servlet work on it.
              The server does function as a Web server as I can run the index.html
              document by entering the URL: http://localhost:7001/index.html
              I am pasting the contents of weblogic.properties file below to get the
              person who is willing to help me started.
              The machine I have is a Pentium III with Windows 2000 Professional on it.
              It's a home machine and the WebLogic server is the freely downloadable
              version. I am using it to prepare for a potential contract work.
              I have managed to modify setEnv.cmd file and have managed to compile the
              SqlServlet.java, which is an example servlet. Neither this particular
              servlet nor a HelloWorld type of very basic servlet I have written are
              recognized by the server.
              As you can see from my weblogic.properties file (pasted at the end of this
              post), the SqlServlet has been registered. I have also uncommented the lines
              to allow for the following type of URL:
              http://localhost:7001/servlet/myServlet
              Thanks!
              Anjum Jaleel
              CONTENTS OF MY weblogic.properties file
              # THE WEBLOGIC PROPERTIES FILE
              # This file, which conforms to the java.util.Properties file
              # definition, configures your WebLogic products. You cannot run
              # WebLogic Server without setting required configuration properties in this
              # file. Required properties are marked and appear first in the file.
              # Details on each entry and important information about configuration
              # and security are documented on our website. Please go to:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # for full instructions on how to edit this file.
              # You do not need to include properties in this file unless you want to
              # change the default, embedded property. Some properties on the
              # AdminProps page are not listed here because the default property
              # is being used. You can change the default by adding the property and
              # its value to this file.
              # You cannot set weblogic.system.home in this file, since the WebLogic
              Server
              # must know where home is in order to retrieve this file. You can
              # change WebLogic home on the command line when you start the
              # WebLogic Server.
              # CLUSTER USERS: Note that the (shared) per-cluster properties file should
              # contain most all of the properties in this file. The only properties
              # that potentially belong in a per-server properties file for a server
              # running in a cluster are the registration (startup class) of pinned
              # RMI objects, and a few tuning properties that may be different for
              # servers in the cluster, depending upon hardware and memory. If you use
              # a per-server properties file, please REMOVE all properties except those
              # that are specifically required in the per-server properties file. You
              # can find specific notes on clusters by searching through this file for
              # "CLUSTER USERS".
              # The way this file is organized:
              # Core properties (includes REQUIRED and RECOMMENDED)
              # Core system properties
              # Core security-related properties
              # Core security-related properties for SSL
              # Core HTTPD administrative properties
              # Optional properties
              # Administrator properties
              # System properties
              # System startup files
              # System shutdown files
              # Security-related properties for Workspaces
              # Jolt for WebLogic properties
              # WebLogic Enterprise Connectivity properties
              # WebLogic File properties
              # WebLogic JMS demo properties
              # WebLogic RMI demo properties
              # WebLogic EJB demo properties
              # WebLogic XML demo properties
              # WebLogic ZAC demo properties
              # HTTPD administrative properties
              # WebLogic JDBC driver properties
              # WebLogic JDBC connection pool management
              # WebLogic demo connection pool
              # WebLogic HTTP Servlet properties
              # Proxy servlet registration
              # Classpath servlet registration
              # File servlet registration
              # ServerSideInclude servlet registration
              # PageCompileServlet (used by JHTML)
              # JSPServlet (used by JSP)
              # ServletServlet registration
              # Servlet reload properties
              # Servlet ACLs
              # WebLogic JSP properties
              # WebLogic JHTML properties
              # WebLogic RMI over IIOP properties
              # User-written and demo servlet registrations
              # CORE PROPERTIES
              # You should set these before you start the WebLogic Server the first time.
              # If you need more instructions on individual properties in this
              # section, check the same section in the Optional Properties, where
              # we've left the long explanations. Or, better yet, go to our
              # website and read all about properties, at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # CORE SYSTEM PROPERTIES
              # TCP/IP port number at which the WebLogic Server listens for connections
              weblogic.system.listenPort=7001
              # CORE SECURITY-RELATED PROPERTIES
              # Read important information about security at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # REQUIRED: The system password MUST be set in order to start the
              # WebLogic Server. This password is case-sensitive, at least 8 characters.
              # The username for the privileged user is ALWAYS "system".
              # This username and password also includes httpd access (see
              # HTTPD properties below).
              weblogic.password.system=lovkako1
              # RECOMMEND Set to 'everyone' if HTTPD is enabled
              weblogic.allow.execute.weblogic.servlet=everyone
              # Set individual ACLs to restrict access to HTTP-related resources,
              # such as the Administration servlets.
              # To make your own servlets generally available, follow this
              # pattern (provide a weblogic.allow.execute) for your packages and
              # set ACLs as appropriate.
              # CORE SECURITY-RELATED PROPERTIES FOR SSL
              # Read important information about SSL at:
              # http://www.weblogic.com/docs51/classdocs/API_secure.html
              # Enable SSL
              # (default if property not defined is false)
              weblogic.security.ssl.enable=true
              # SSL listen port
              weblogic.system.SSLListenPort=7002
              # Servlets for SSL
              # Authentication servlet for creating tokens for applets
              weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
              ervlet
              # Limits number of unclaimed stored tokens
              weblogic.security.certificateCacheSize=3
              # Capture CA root of client servlet
              weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
              # Certificates for SSL
              # Name of acceptable CA roots
              # For client authentication change value to a valid .pem file
              #weblogic.security.clientRootCA=SecureServerCA.pem
              # Server certificates for SSL
              weblogic.security.certificate.server=democert.pem
              weblogic.security.key.server=demokey.pem
              weblogic.security.certificate.authority=ca.pem
              # registration for certificate generator servlet
              weblogic.httpd.register.Certificate=utils.certificate
              weblogic.allow.execute.weblogic.servlet.Certificate=system
              # CORE HTTPD ADMINISTRATIVE PROPERTIES
              # True permits the HTTPD to run (default)
              # Uncomment this property to disable HTTPD
              weblogic.httpd.enable=true
              # If authentication is required, add username/password for each user
              # who will be included in an ACL, as in this commented-out example:
              #weblogic.password.peter=#8gjsL4*
              # OPTIONAL PROPERTIES
              # These properties affect the behavior of the WebLogic Server.
              # You only need to set these properties if you want
              # to change the default setting, which is the property shown.
              # ADMINISTRATOR PROPERTIES
              # Administrator properties are optional information properties,
              # particularly useful for clusters.
              #weblogic.administrator.location=3355 California Drive, West Hampshire, CA
              94104
              #weblogic.administrator.name=Joe Administrator
              #weblogic.administrator.phone=1 415 555 1234
              # SYSTEM PROPERTIES
              # System properties in this section are set to system defaults
              # Performance pack. The shared library must be accessible from your
              # PATH (NT) or from your shared library path (UNIX; the name of the
              # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
              weblogic.system.nativeIO.enable=true
              # Outputs logging information to the console as well as to the log file
              weblogic.system.enableConsole=true
              # Sets the directory or URL for the WebLogic Admin help pages
              # The help pages are shipped in the "docs/adminhelp" directory, in the
              # default document root in public_html
              weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
              p/
              # If you prefer to access the most recent help pages, you can do so online
              # by commenting out the previous property and uncommenting this one:
              #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
              # Properties for tuning the server's performance
              # Number of WebLogic Server execute threads.
              weblogic.system.executeThreadCount=15
              # Other optional system properties
              # Limits size of weblogic.log (in K) and versions old log
              weblogic.system.maxLogFileSize=1024
              # Adjust minimum length of password
              weblogic.system.minPasswordLen=8
              # UNIX only: If running on port 80 on UNIX, enable the setUID program
              #weblogic.system.enableSetUID=false
              # UNIX only: Unprivileged user to setUID to after starting up
              # WebLogic Server on port 80
              #weblogic.system.nonPrivUser=nobody
              # CLUSTER-SPECIFIC PROPERTIES
              # Cluster-specific properties in this section are set to system defaults.
              # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
              # in the per-cluster properties file ONLY.
              # Time-to-live (number of hops) for the cluster's multicast messages
              # (default 1, range 1-255).
              #weblogic.cluster.multicastTTL=1
              # Sets the load-balancing algorithm to be used between
              # replicated services if none is specified. If not specified,
              # round-robin is used.
              #weblogic.cluster.defaultLoadAlgorithm=round-robin
              # SERVER-SPECIFIC CLUSTER PROPERTIES
              # Cluster-related properties in this section are set to system defaults.
              # CLUSTER USERS: Note that these server-specific cluster-related properties
              # should be set in the per-server properties file ONLY.
              # Sets the weight of the individual server for the weight-based
              load-balancing.
              # Range is 0 - 100.
              # Larger numbers increase the amount of traffic routed to this server.
              #weblogic.system.weight=100
              # SYSTEM STARTUP FILES - Examples
              # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
              # objects should be registered in the per-server properties file.
              # All other startup classes should be registered in the per-cluster
              # properties file.
              # For more info on writing and using startup file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs51/classdocs/API_t3.html
              # Register a startup class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.startupClass.[virtual_name]=[full_pathname]
              # Add arguments for the startup class
              #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/StartupQuery.java
              #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
              #weblogic.system.startupArgs.doquery=\
              # query=select * from emp,\
              # db=jdbc:weblogic:pool:demoPool
              # SYSTEM SHUTDOWN FILES - Examples
              # For more info on writing and using shutdown file, see the
              # Developers Guide "Writing a WebLogic Client application," at
              # http://www.weblogic.com/docs51/classdocs/API_t3.html
              # Register a shutdown class by giving it a virtual name and
              # supplying its full pathname.
              #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
              # Add arguments for the shutdown class
              #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
              # This example shows the entry for examples/t3client/ShutdownTest.java
              #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
              #weblogic.system.shutdownArgs.ShutdownTest=\
              # outfile=c:/temp/shutdown.log
              # SECURITY-RELATED PROPERTIES FOR WORKSPACES
              # For backward compatibility, the following entries disable Access
              # Control on Workspaces
              weblogic.allow.read.weblogic.workspace=everyone
              weblogic.allow.write.weblogic.workspace=everyone
              # JOLT FOR WEBLOGIC PROPERTIES
              # These properties configure a BEA Jolt connection pool for use with
              # the simpapp and bankapp examples, and register a servlet for use with
              # with the simpapp example. The default server address provided here
              # points to a public TUXEDO server that is hosted by BEA for use with
              # this example.
              # Servlet registration for simpapp example:
              #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
              t
              # Pool creation and cleanup
              # note this example is set up to work with the public
              # demo TUXEDO server available from BEA's website:
              #weblogic.system.startupClass.demojoltpoolStart=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
              #weblogic.system.startupArgs.demojoltpoolStart=\
              # poolname=demojoltpool,\
              # appaddrlist=//beademo1.beasys.com:8000,\
              # failoverlist=//beademo1.beasys.com:8000,\
              # minpoolsize=1,\
              # maxpoolsize=3
              #weblogic.system.shutdownClass.demojoltpoolStop=\
              # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
              #weblogic.system.shutdownArgs.demojoltpoolStop=\
              # poolname=demojoltpool
              # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
              # The registrations enable a BEA IIOP connection pool and
              # register servlets for use with the simpapp and university examples.
              # Configure for your environment and uncomment to use.
              # Uncommenting these properties requires WebLogic Enterprise Connectivity
              # and an operating WebLogic Enterprise Server.
              # Servlet registration for simpapp servlet example
              #weblogic.httpd.register.SimpappServlet=\
              # examples.wlec.servlets.simpapp.SimpappServlet
              #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
              # Servlet registration for simpapp EJB example
              # (You'll need to add the wlec_ejb_simpapp.jar to the
              # weblogic.ejb.deploy property in this file.)
              #weblogic.httpd.register.ejbSimpappServlet=\
              # examples.wlec.ejb.simpapp.ejbSimpappServlet
              #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
              # Pool creation and cleanup for the simpapp example
              #weblogic.CORBA.connectionPool.simplepool=\
              # appaddrlist=//wlehost:2468,\
              # failoverlist=//wlehost:2468,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # domainname=simpapp
              # Servlet registration for university Servlet example:
              #weblogic.httpd.register.UniversityServlet=\
              # examples.wlec.servlets.university.UniversityServlet
              #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
              # Pool creation and cleanup for the University example:
              #weblogic.CORBA.connectionPool.Univpool=\
              # appaddrlist=//wlehost:2498,\
              # failoverlist=//wlehost:2498,\
              # minpoolsize=2,\
              # maxpoolsize=3,\
              # username=wleuser,\
              # userrole=developer,\
              # apppassword=wlepassword,\
              # domainname=university
              # WEBLOGIC FILE PROPERTIES
              # Maps a volume name to a path, for client file read/write
              #weblogic.io.fileSystem.[volumeName]=[fullPathName]
              # WEBLOGIC JMS DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL JMS deployment should be done in the
              # per-cluster properties file ONLY.
              # You set up a JDBC connection pool if you want persistent messages
              # (including durable subscriptions). To use JMS and EJBs in the same
              # transaction, both must use the same JDBC connection pool. Uncomment
              # the following property to use the default JDBC connection pool
              # 'demo', which is defined in the Demo connection pool section of this file.
              #weblogic.jms.connectionPool=demoPool
              # The JMS Webshare example demonstrates how the ClientID for a
              # durable subscriber is configured in the connection factory:
              #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
              #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
              #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
              #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
              # The JMS trader example shows how to use JMS with an EJB. In addition
              # to uncommenting the following properties, you must also set up and
              # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
              # ejb_basic_statelessSession.jar to try out this JMS example:
              #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
              #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
              #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
              #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
              # Registers the underlying servlet
              #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
              # These properties are used with the ServerReceive JMS example,
              # which demonstrates how to establish a JMS message consumer
              # in a startup class:
              #weblogic.system.startupClass.serverReceive=\
              # examples.jms.startup.ServerReceive
              #weblogic.system.startupArgs.serverReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              # These properties are used with the PoolReceive JMS example,
              # which demonstrates how to establish a pool of JMS message consumers
              # in a startup class:
              #weblogic.system.startupClass.poolReceive=\
              # examples.jms.startup.PoolReceive
              #weblogic.system.startupArgs.poolReceive=\
              # connectionFactory=javax.jms.TopicConnectionFactory,\
              # topic=javax.jms.exampleTopic
              #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
              # WEBLOGIC RMI DEMO PROPERTIES
              # CLUSTER USERS: Note that pinned RMI objects should be registered
              # in the per-server properties file ONLY. All other RMI startup
              # classes should be registered in the per-cluster properties file.
              # Remote classes registered at startup after the pattern:
              #weblogic.system.startupClass.[virtualName]=[fullPackageName]
              # These examples can be compiled to see RMI in action. Uncomment to use:
              #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
              #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
              #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
              # WEBLOGIC EJB DEMO PROPERTIES
              # CLUSTER USERS: Note that ALL EJB deployment should be done in the
              # per-cluster properties file ONLY.
              # See WebLogic Demo Connection Pool below for a connection pool
              # to use with these examples.
              # Deploys EJBeans. Uncomment the appropriate lines below and
              # modify DBMS-related info and paths to match your particular installation:
              #weblogic.ejb.deploy=\
              # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
              # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
              # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
              # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
              # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
              # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
              # g:/weblogic/myserver/ejb_subclass.jar, \
              # g:/weblogic/myserver/jolt_ejb_bankapp.jar
              # Servlet used by the EJB basic beanManaged example
              # Uncomment to use:
              #weblogic.httpd.register.beanManaged=\
              # examples.ejb.basic.beanManaged.Servlet
              # Add a list of users (set the password with
              weblogic.password.[username]=XXX)
              # to set an ACL for this servlet:
              #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
              #weblogic.password.user1=user1Password
              #weblogic.password.user2=user2Password
              # WEBLOGIC XML DEMO PROPERTIES
              # These properties are required to run the XML examples.
              # Uncomment to use.
              # CLUSTER USERS: Note that ALL servlets should be set up
              # in the per-cluster properties file ONLY.
              #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
              # BizTalk example properties
              #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
              #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
              #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
              dapter
              #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
              # WEBLOGIC ZAC DEMO PROPERTIES
              # These registrations enable the ZAC Publish Wizard.
              weblogic.zac.enable=true
              # Set the publish root for a WebLogic Server. Edit and
              # uncomment to use.
              #weblogic.zac.publishRoot=g:/weblogic/zac
              # Set an ACL for each package you publish. The [name] is
              # the "Package name" you assign in the ZAC Publish Wizard.
              # Publish a package, edit this property, and uncomment to use.
              #weblogic.allow.read.weblogic.zac.[name]=[user list]
              #weblogic.allow.write.weblogic.zac.[name]=system
              # HTTPD ADMINISTRATIVE PROPERTIES
              # Enables logging of HTTPD info in common log format and
              # sets the log file name (default is "access.log" in "myserver")
              weblogic.httpd.enableLogFile=true
              weblogic.httpd.logFileName=access.log
              # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
              weblogic.httpd.enableEvents=false
              # Enables HTTP sessions
              weblogic.httpd.session.enable=true
              # Sets an optional cookie name. The default name is "WebLogicSession".
              # Prior to version 4.0, the default was "TengahSession". To make
              # this backward compatible with cookies generated from previous
              # installations, you should set this property to "TengahSession".
              # Uncomment this line and set this to any string of your choice,
              # or comment out this property to use the default.
              #weblogic.httpd.session.cookie.name=WebLogicSession
              # MIME types
              weblogic.httpd.mimeType.text/html=html,htm
              weblogic.httpd.mimeType.image/gif=gif
              weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
              weblogic.httpd.mimeType.application/pdf=pdf
              weblogic.httpd.mimeType.application/zip=zip
              weblogic.httpd.mimeType.application/x-java-vm=class
              weblogic.httpd.mimeType.application/x-java-archive=jar
              weblogic.httpd.mimeType.application/x-java-serialized-object=ser
              weblogic.httpd.mimeType.application/octet-stream=exe
              weblogic.httpd.mimeType.text/vnd.wap.wml=wml
              weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
              weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
              weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
              weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
              # In seconds, the keep-alive for HTTP and HTTPS requests
              weblogic.httpd.http.keepAliveSecs=60
              weblogic.httpd.https.keepAliveSecs=120
              # WEBLOGIC JDBC DRIVER PROPERTIES
              # Enables JDBC driver logging and sets the file name for the log
              # The weblogic.jdbc.logFile is placed in the per-server
              # directory (default is "myserver")
              weblogic.jdbc.enableLogFile=false
              weblogic.jdbc.logFileName=jdbc.log
              # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
              # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
              # in the per-cluster properties file ONLY.
              # For creating JDBC connection pools. This example shows a connection
              # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
              # to use 4 JDBC connections (with a potential for up to 10 connections,
              # incremented by two at a time, with a delay of 1 second between each
              # attempt to connect to the database), to an Oracle database server called
              # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
              # connections are dropped from the pool until only 4 connections remain
              open.
              # Every 10 minutes, any unused connections in the pool are tested and
              # refreshed if they are not viable.
              #weblogic.jdbc.connectionPool.oraclePool=\
              # url=jdbc:weblogic:oracle,\
              # driver=weblogic.jdbc.oci.Driver,\
              # loginDelaySecs=1,\
              # initialCapacity=4,\
              # maxCapacity=10,\
              # capacityIncrement=2,\
              # allowShrinking=true,\
              # shrinkPeriodMins=15,\
              # refreshMinutes=10,\
              # testTable=dual,\
              # props=user=SCOTT;password=tiger;server=DEMO
              # Get more details on each argument for this property in the
              # Administrators Guide on setting properties at:
              # http://www.weblogic.com/docs51/admindocs/properties.html
              # Set up ACLs for this connection pool with the following:
              #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
              # guest,joe,jill
              #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
              # joe,jill
              #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

    Problem Resolved!
              I found out that I had 'http' instead of 'httpd' in the statement where I
              registered my servlet, SqlServlet.
              Now, I am having difficulty with hot deployment. The server is returning
              error 404.
              

  • 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.

Maybe you are looking for