RedHat Java Servlet JSP Support, RedHat Java Servlet JSP, Java Servlet JSP

It is installed on all web servers and there are no additional charges for nominal use. This page will provide you valuable links for support.

• Jakarta.Apache.Org/Tomcat - Jakarta Tomcat is a project of the Apache Software Foundation, authors of the #1 web server on the internet.   

• Your Own Samples - From your site control panel we have an JSP wizard that will install a WAR (Web ARchive) of examples under your website.  This includes a working JSP and Servlet example of using JDBC to connect to our MySQL database.

Secure Server support is also available if you have your own site certificate.

 

Technical Support

Other than problems with getting the Wizard examples working, there is no unpaid support for Java Servlets/JSP.  They are  very powerful and complex components and beyond what we can support for our large volume of web sites.  Outside of contracted support, questions will be answered on an "as available" basis.

If you find a valuable Java Servlet/JSP resource you would like to share with others, please let us know and we will add a link and information to this page.

With each tomcat installation we install the Tomcat Web Application Manager which allows you to stop/start/reload your WARS.  You can reach this using a url like http://www.yourdomain.com/manager/html/list. This application is password protected with your control panel username and password. 

Using the Tomcat Web Application Manager, you can add additional WARS to your website. Once the WAR has been deployed, it will be available by accessing port 8080 on your website.  ie - if your new war is named mywar, you will be able to access it using the URL of http://www.yourdomain.com:8080/mywar.

The normal web server listens for requests on port 80.  Tomcat listens for requests on port 8080.  With the example WAR, we have configured the normal apache server to forward all requests for this directory to the Tomcat server listening on port 8080.  You can also access Tomcat directly on port 8080.  ie - http://www.yourdomain.com:8080.  If you want to incorporate JSP/Servlets within your website without specifying the port, we suggest that you place your files within the example directory and create your links appropriately. 

Tomcat Application Manager:

The Tomcat Application Manager allows you to control your WARs.  You can stop/start/reload your existing WARs.  If you have made a change to your web.xml file, you may have to reload the WAR for Tomcat to recognize your changes.  

You can also add a new WAR to Tomcat.  This new war will only exist for the duration of the current run of Tomcat.  Upon the next system update (daily at 4am, 8am, 12 pm, 4pm, 8pm, 12am) Tomcat may be restarted.  If you need to add a new WAR to your website, let us know at service@thebook.com.  A new WAR can be either a .war file (ie - myWar.war) or a directory (ie /pub/users/thebook-demo/www/myWar/).

To add a new WAR using the Tomcat Application Manager.  

1. Upload your file(s) to your website.  You can either upload a .jar file or use a directory containing a WEB-INF sub directory.  
   Ie - /pub/users/thebook-demo/www/myWar.jar  or /pub/users/thebook-demo/www/myWar/.... 
2. Create a configuration context file: ie - /pub/users/thebook-demo/www/myWar.xml:
   <Context path="/myWAR" docBase="/pub/users/yourname/www/" debug="0" reloadable="true" crossContext="true">
   </Context>
3. Load the Tomcat Application Manager : http://www.thebook-demo.com/manager/html/list
4. To install a new Application, you need to specify a Path:, a Config URL, and a WAR URL.  
   Path: /myWAR
       This is the directory under your website where your WAR lives.  In the case of a .jar file, this 
       directory does not really exist.
       ie - if you want your WAR to respond to http://www.thebook-demo.com:8080/xyz, Path: would be /xyz
5. Config URL: file:/pub/users/thebook-demo/www/myWar.xml
       This is the full path to the xml file from step 2.
6. WAR URL: jar:file:/pub/users/thebook-demo/www/myWar.war!/ or file:/pub/users/thebook-demo/www/myWar/
       This is the path to either the .war file for your war or to the directory of your war.
   
       If you are deploying a WAR packed within a jar file, this should be something like:
           jar:file:/pub/users/thebook-demo/www/myWar.jar!/     (Note - the !/ at the end is IMPORTANT)
   
       If you are deploying a WAR which is set up in the /myWAR directory, this should be something like:
           file:/pub/users/thebook-demo/www/myWar

WEB.XML

Below is a list of all legal tags that can occur directly within an <web-app>...</web-app> element. They are all optional, but if they appear, they must appear in the order given below. 

<icon> 
<display-name> 
<description> 
<distributable> 
<context-param> 
<filter> 
<filter-mapping> 
<listener> 
<servlet> 
<servlet-mapping> 
<session-config> 
<mime-mapping> 
<welcome-file-list> 
<error-page> 
<taglib> 
<resource-env-ref> 
<resource-ref> 
<security-constraint> 
<login-config> 
<security-role> 
<env-entry> 
<ejb-ref> 
<ejb-local-ref> 

Servlets

To compile your own servlets via telnet, you would have to use the java compiler.  

To compile the java source for HelloWorldExample.java, you would first cd to java-server/WEB-INF/classes, then give the following command:
    javac -classpath /usr/local/etc/tomcat/common/lib/servlet.jar HelloWorldExample.java

If you have additional class files you need to compile against, you would have to adjust the classpasth appropriately.

Here are a few links we have found useful.

http://www.jspin.com/home/references/coderefe/jsp

http://www.onjava.com/pub/a/onjava/excerpt/java_cookbook_ch18/index.html

http://javaboutique.internet.com/tutorials/JSP/

[Home]   [Web Hosting]   [Extras]   [FAQ List]   [Support]    [Sign Up!]   [About Us]   [Contact Us] © Copyright 1996-2007 Software Workshop Inc.™