This document is the home page of your Servlets.Net website. It is called index.jsp and is located at /home/amnon/www/amnon/index.jsp. Your web server will automatically display this document if only your domain name or host name is requested and no file path is specified in the URL. If index.jsp does not exist, the web server will look for one of the following default document names and attempt to display them: index.html, index.htm, index.jsp, index.xtp, index.shtml, and index.shtm.

When you are ready to deploy your own site, simply create your own index.html file (or one of the other default documents). Either replace this file with your new index.html file or remove this file and upload your new default document. The content you put into your new default document should be the home page of your website. If you need to see this original document again, there is a copy of it called homepage.jsp in your web document root directory.


Account Basics

Account Name amnon
Web Root Location /home/amnon/www/amnon/
Web Logs Location /home/amnon/logs/amnon/

Your Account Name should be included in all correspondence with Servlets.Net. It is also the name of your default POP3 mailbox. All email for your domain name will get stored in this POP3 mailbox until you request differently. Lastly, it is also the username you should use to connect to your account via FTP, telnet, or SSH.

The website you are viewing is located in the directory defined as the Web Root Location. This means that your default homepage document should be placed into this directory. The log files for your site are stored in the Web Logs Location directory.

Email Configuration
Default POP3 Mailbox Username amnon

When your Servlets.Net account is first configured, all email sent to any address at your hosted domain name will be saved in this mailbox on our servers. You can download this email by connecting to your Servlets.Net mail server with the Default POP3 Maibox Username defined above.

We can assist you in configuring additional email boxes, email aliases, email forwarders, or other mail services. Simply send detailed descriptions of how you want your email to work to support@servlets.net. We'll get everything configured and going for you!

Servlets.Net will soon have a web-based account management system that will let you configure your email and other services via a web browser. Stay tuned for more information regarding this service!

Servlet Engine
Servlet Engine Location /home/amnon/resin/amnon/

Included with all professional packages is a private instance of the Resin servlet engine by Caucho Technology. This servlet engine is based on the same technology that Tomcat and other leading servlet engines use. It fully supports the Servlet 2.3 and JSP 1.2 APIs. Servlets.Net has found that Resin is faster and easier to use than most of the other servlet engines available. We are confident you will enjoy using Resin for your web site.

To get started developing Servlet 2.3 and JSP 1.2 solutions, we recommend that you review the documentation that comes with your private Resin installation. Take a look at index.xtp for Resin's documentation. Simply click here to explore the private installation of Resin within your Servlets.Net account. Please note that it might take a moment for the documentation pages to be displayed the first time you access each page. This is because they are being compiled for the first time.

One of the best things about Resin is that it will automatically compile almost everything for you. This includes your servlets, JSP and XTP documents, supporting classes and JavaBeans, and much more! Simply put your source file onto the server in the appropriate directory and Resin will compile it for you. Below is a list of directories that you should know about.

You will find Resin installed in:
/home/amnon/resin/amnon/

You can stop and start the Resin servlet engine with these commands. In general, you won't need to do this. But there will be times when it makes sense to restart the servlet engine:
/home/amnon/resin/amnon/start
/home/amnon/resin/amnon/stop

Any web documents, such as HTML, JSP, or XTP files will get automatically compiled if they need to be compiled. They should be put into your web document root:
/home/amnon/www/amnon/

If your web application, JSP, or XTP files require supporting classes, they can be placed in several places. If you have JAR files that you would like all of your web applications to use, put them into the global Resin lib directory:
/home/amnon/resin/amnon/lib/

If you have JAR files that should only be used for your main web application, put them into your WEB-INF/lib directory:
/home/amnon/www/amnon/WEB-INF/lib/

If you have classes that are not contained in a JAR file and want to make them available for your main web application, put them into your WEB-INF/classes directory. This includes any servlets that you want to make available. You can put *.class files into this directory if you would like, but Resin will also automatically compile everything for you if you just put your source files into the correct place on the server. For instance, you can drop the *.java classes that you have into this location and Resin will automatically generate *.class files:
/home/amnon/www/amnon/WEB-INF/classes/

Although you do not have direct access to edit your resin.conf file, we are more than willing to make most necessary changes you need to the file for you. Unfortunately, there are some settings in that file that could cause conflicts with other customer installations if they were modified incorrectly. We have to lock some things down so that customers can't accidentally or intentionally clobber other customer's services. The resin.conf file is located at:
/home/amnon/resin/amnon/conf/resin.conf

Luckily, almost everything you would need to edit in resin.conf can be controlled by editing web.xml instead. Most of the settings that are normally in resin.conf can also be used in the web.xml file located at:
/home/amnon/www/amnon/WEB-INF/web.xml

In addition, you can edit your global database connection broker settings by modifying your database.conf, mysql_*.conf, or pgsql_*.conf files. These files are already configured for your account setup, but you might want to make changes to it at some point. See the samples below for more information on how to use databases within your servlets and JSP documents. The database configuration files are located at:
/home/amnon/resin/amnon/conf/

Databases
Database Name amnon_amnon
Database Pool Name
jdbc/amnon
Database Connection URL jdbc:mysql://localhost:3306/amnon_amnon
JDBC Driver org.gjt.mm.mysql.Driver
Database Pool Configuration File /home/amnon/resin/amnon/conf/mysql_amnon_amnon.conf

See the sample JSP documents and click on the Database Pool Name for a demonstration of using Resin's built-in database connection pooling system to connect, query, and manage data in this database.

Programming Samples
Programming Samples

We've included some sample JSP documents that demonstrate using Resin's built-in database connection pooling system to connect, query, and manage data in your database. Exploring these sample documents and their source code should prove to be a solid base for you to start programming your own application.. Note that any database samples will not work correctly if you do not have a package that includes a database.

There are also many other examples and tutorials included within the Resin documentation.

Technical Support

Technical Support Email Address

If you need any assistance or have any questions, please contact support@servlets.net. Make sure to specify your Servlets.Net Account Name in the email, preferably in the subject line of the email.

Emergency Support
Emergency Support Email Address

Servlets.Net Corporation has support engineers available 24/7 in case of emergencies. If you experience an emergency situation that is preventing your services from working properly, you can send email to support911@servlets.net. Please note that we consider network outages and service outages as emergencies. You should only use our emergency support in cases of a true system or network emergency such as a network failure, web server problem, database problem, or other service problems.

Emergency support should NOT be used if you are having difficulty with your own servlet engine or web application. Abuse of our emergency contact system will result in additional charges for after-hours emergency support.