General.

Servers.

Email.

MySQL.

CGI & PHP.

JSP & Servlets.



Technical Support Page.

Please read these pages if you are having difficulties or aren't sure what to do.

If you don't find the information that you need please email: support@jabhosting.co.uk


General Information.

Default page filename.
Your default, home, or index page needs to be called index.html or index.php if you have PHP enabled space.

File Transfering.
To upload your web-site you need to use FTP (File Transfer Protocol). There are many different ftp client programs around. We recommend CuteFTP for Windows® or gFTP for Linux users.

File/Directory Structure.
For accounts setup before January 2004:
The directory you see when you login with an FTP client is as follows:
File Structure Diagram
All your files should be in the root of the file system. You can create extra directories as required for your graphics etc. But your index page must be here.

admin contains nightly vistor stats updates. These can be found in the webalizer directory and can be accessed through your site with http://www.YOURDOMAIN/admin/webalizer/index.html
It is password protected and you must use your main account username and password to access the stats.

logs. This directory contains your raw access logs. These can be downloaded and read with log analyser software if required. Please note these files can get very big!

This directory is blocked from being served by the server. It can only be accessed by FTP.

cgi-bin You will only have this directory if your package includes scripting. You run your Perl scripts from this directory. See CGI & PHP for more info.

For accounts setup after January 2004:
The directory you see when you login with an FTP client is as follows:
File Structure Diagram
All your html, php and image files should be in the public_html directory of the file system. You can create extra directories as required for your graphics etc. But your index page must be here.

Files that you don't want to be publically available can go into the root of your space if required. If you are using PHP, it is able to access files stored in the root area.

admin will usually contain nothing but may have some system files for your site. It can not be accessed via http.

logs, this directory contains your raw access logs. These can be downloaded and read with log analyser software if required. Please note these files can get very big! This directory is blocked from being served by the server. It can only be accessed by FTP.

cgi-bin You will only have this directory if your package includes scripting. You run your Perl scripts from this directory. See CGI & PHP for more info.

tmp this is used mainly by PHP as a temporary store, if you are using the PHP file upload functions.

webalizer is where your web-site statistics are stored it can be accessed by http://www.YOURDOMAIN/webalizer/index.html
It is password protected and you must use your main account username and password to access the stats.

Back to top


Which Server to use.

When your domain is registered and activated we provide some virtual servers for you to use:

www : www.YOUR-DOMAIN.com
ftp : ftp.YOUR-DOMAIN.com
pop3 : mail.YOUR-DOMAIN.com
smtp **: Please use your dial-up ISP's smtp server

** Please note the due to the ever increasing amount of bulk unsolicted email (SPAM) being sent and scans looking for open mail relays, we request that you use the mail server of the ISP that you use to connect to the Internet.

If you are unable to do this then please contact us and we can discuss some alternative options.


Back to top


Email Information and Settings.

Your emails addresses are set-up normally when your account is set-up. If you need to change these or have them forwarded to other addresses please email support with the changes. This will be done at the next convenient opportunity.

The default set-up is to have all your email addresses delivered to one mailbox. This can then be picked up directly from our servers with any pop3 compliant email application. If you have more than one mailbox with your account you will have been assigned a username and password for each mailbox.

We use the Spamhaus Project (http://www.spamhaus.org/) to check all email that is delivered to our system. This is not so much a filter but a black list that is checked when the system sending the email connects to our system. If the sending system appears in the black list then the mail will be rejected.

To help protect you against viruses, we use ClamAV (http://www.clamav.net/) to scan all emails before they are sent to your mailboxes. The virus definations get updated twice a day to make sure we catch all the latest threats.

**NOTE: Due the recent sobigF and similar viruses we have blocked email with certain attachments: .exe, .pif, .scr, .com. To try and reduce the traffic problem that these viruses cause we are not returning them but silently dropping them.

Back to top


MySQL Information and Settings.

If have included mySQL in your hosting package then you will have been set-up with a database for your own use. Nobody else can have access to this database. Only your username and password has access.

The database username is usually your account username the password will also match that of the mainaccount. The name of the database will also be the same as your username.

Access to the database is restricted to the local server. Remote access from another server is not permitted.

We recommend that you create some scripts of your own to create tables and administer the database. We can supply some templates if required.

Back to top


CGI & PHP.

If you have included scripting in your hosting package you will be able to use PHP, Perl and server side includes (SSI).

Perl Scripts
Your scripts should be placed in the cgi-bin directory. File permissions are important. For the server to run your script you need to set the executable bit for the everyone group. e.g chmod 0705. Your ftp client should be able to do this when you upload the file however some ftp clients lack this functionality.

The first line in your perl script should read #!/usr/bin/perl this is very important.

The file extension should be either .pl or .cgi

Another common problem encountered is when your script sends data before it has sent headers. Your can either use the CGI.pm module or output your own e.g.
#!/usr/bin/perl
use CGI;
print header;
# now you can send data
or
#!/usr/bin/perl
print "Content-type: text/html\n\n";
#now you can output data
either will work.

PHP
PHP scripts can be placed anywhere in your directory tree.

Make sure that they have a .php file extension.

There is a huge amount of information on the php.net website. Your first port of call concerning php should be www.php.net

Back to top


JSP & Servlet Information.
File Structure Diagram

If you have included JSP/Servlet technology in your hosting package you will have a slightly different public_html directory. An extra directory will be present from which you can run your JSP and servlets from.

The webapp directory is your Tomcat context. You should place all your html, jsp and image files in here. In there is another directory called WEB-INF, where you have classes, which is where you put your class files in a structured package directory tree, and lib, which is for your jar (.jar) files.

Also in the WEB-INF folder is the web.xml file. This is where you can add extra configuration for you context such as servlet mappings, init parameters and other configuration options.

 

** Note: you must create mappings for your servlets in the web.xml file otherwise they will not run.

An example of web.xml
<?xml version="1.0" encoding="UTF-8"?>
<!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>
		<servlet>
			<servlet-name>test</servlet-name>
			<servlet-class>uk.co.jabhosting.TestServlet</servlet-class>
    			<initparam>
				<param-name>config</param-name>
				<param-value>/WEB-INF/testconfig.xml</param-value>
			</initparam>
    			<load-on-startup>2</load-on-startup>
  		</servlet>
  		<servlet-mapping>
    			<servlet-name>test</servlet-name>
    			<url-pattern>/servlet/TestServlet</url-pattern>
  		</servlet-mapping>
  		<session-config>
    			<session-timeout>
            		30
        		</session-timeout>
  		</session-config>
		<welcome-file-list>
    			<welcome-file>
            		index.jsp
        		</welcome-file>
    			<welcome-file>
            		index.html
        		</welcome-file>
    			<welcome-file>
            		index.htm
        		</welcome-file>
  		</welcome-file-list>
  		<error-page>
    			<exception-type>java.lang.Exception</exception-type>
    			<location>/exception.jsp</location>
  		</error-page>
	</web-app>
		

To access the jsp and servlet enabled space via http, you would use http://www.YOURDOMAIN/webapp/index.jsp

Based on the above web.xml as an example, you would access the TestServlet servlet by using http://www.YOURDOMAIN/webapp/servlet/TestServlet

When you have uploaded your java based site to the server it is sometimes necessary for us to restart your context, although your context will look for changes and reload itself. If that is required please email support@jabhosting.co.uk to let us know and we will restart it at the next convenient opportunity.

For more information on using your java enabled space we recommend having a look at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html this explains how your context can be used.

Back to top