ITA NETWORK SOLUTIONS
Tomcat Web Hosting & Domains
Shared Tomcat hosting solutions.
Best price for Java hosting with PHP support.
Shared Tomcat hosting solutions.
Best price for Java hosting with PHP support.
Listed below, you can find our awsome web hosting packages provided with care and passion!
If you are looking for premium quality web hosting package for your website, you are at the right place!
We offer outstanding user friendly web hosting packages for all!
Low cost shared web hosting
Secured servers and free SSL for your web site
You can transfer your domain for free with our hosting plans
You do not have to worry about the traffic you will be using
Our support staff is available 24/7/365 to assist you
Plesk - the best control panel + APS auto installer with more than 400 scripts and more than 1000 PHP classes
Features common to all web hosting packages.
A web hosting service is a type of Internet hosting service that allows individuals and organizations to make their website accessible via the World Wide Web.
We offer shared Plesk web hosting services. Plesk is the best control panel for web hosting automation with many features. You don't need to be website administrator to manage your site.
Shared web hosting service is a web hosting service where many websites reside on one web server connected to the Internet. This is generally the most economical option for hosting, as the overall cost of server maintenance is amortized over many customers.
Reseller hosting services for web studios and web hosting resellers.
Reseller hosting accounts where you can order space and get unlimited customers and Plesk accounts. You can setup your own web hosting plans for your customers. This reseller hosting solutions is the best choice for web studios and web developers that manage the customer's websites and pay the renew fees with profit.
Java hosting service on shared servers in order to provide the most economical Java hosting solution for our customers. We offer latest Java hosting environment together with the best hosting control panel Plesk. The Java extension for Plesk is developed by own team of Java experts and offers the best Java hosting experience that you can get!
Tomcat hosting service on shared servers. You can easily deploy and reload your applications. The shared Tomcat hosting solution that we provide is the best option for low cost Java & JSP applications. The Plesk control panel offers many more features. The Tomcat hosting extension is integrated in Plesk and you have full control over your applications and Tomcat logs. Spring & Hibernate are supported in our Tomcat hosting environment.
Tomcat Hosting on Linux Servers.
Apache Tomcat, often referred to as Tomcat Server, is an open-source Java Servlet Container developed by the Apache Software Foundation (ASF). Tomcat implements several Java EE specifications including Java Servlet, JavaServer Pages (JSP), Java EL, and WebSocket, and provides a "pure Java" HTTP web server environment in which Java code can run.
Tomcat is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation, released under the Apache License 2.0 license, and is open-source software.
Tomcat web apps should you placed directly in the DocumentRoot
. For a subscription's main domain DocumentRoot
is pointed to /httpdocs
by default.
Here's an example.
Let's say that you have a docs.mydomain.com
subdomain pointed to /docs
directory with the following structure:
With this layout the following contexts can be deployed:
Each tomcat context represents a separate web app with its own classes, libraries, JSP files, etc. E.g:
A domain or subdomain can have Tomcat web apps deployed if it:
Additionally, the domain or subdomain DocumentRoot
must be pointed to a directory which is directly under the subscription home directory. E.g.
To request a deployment go to the "Websites & Domains" section, find the domain/subdomain that should serve the web app and click its Tomcat button.
You will find a "Deployment request form" on the opened page.
This form contains:
META-INF/context.xml
The list of deployable contexts is generated by scanning the DocumentRoot
. An entry in the list is created for:
DocumentRoot
andWEB-INF
andMETA-INF/context.xml
will be ignored even if it exists unless you check the checkbox. Please do so if you have custom Resource/Realm/etc definitions there. It will be reviewed and you will be able to see how it has been applied in the "Support reply" .
We run Tomcat application server on Oracle JVM. Tomcat is run behind Apache HTTPd front-end so we could support additional environments - e.g. PHP.
We offer shared Tomcat hosting only. That is - one Tomcat running in one Java JVM hosts multiple web applications.
In order to provide isolation between applications of different customers Tomcat is started with its security manager enabled.
Tomcat calls the root directory of a domain or subdomain "application base" (appBase
config option). Apache HTTPd calls it "document root" (DocumentRoot
config option). In our environment Tomcat and Apache HTTPd virtual hosts are pointed to the same directory so DocumentRoot
and appBase
are the same thing.
Here's an example for MySQL which you can place in e.g. test.jsp
:
<%@page language="java" import="java.sql.*" contentType="text/plain; charset=UTF-8" pageEncoding="UTF-8"%>
<%
Class.forName( "com.mysql.jdbc.Driver" );
java.sql.Connection con = DriverManager.getConnection(
"jdbc:mysql://localhost/DBNAME",
"USERNAME",
"PASSWORD"
);
out.println( con.toString() );
%>
The MySQL driver is pre-installed in $TOMCAT_HOME/lib
so you don't need to put it in your web app's WEB-INF/lib
.
PostgreSQL drivers are not pre-installed. Neither are SQLite and HSQLDB drivers.
It is important to test your Tomcat web apps locally before requesting their deployment. The tests have to be done with Tomcat's security manager enabled. To enable the security manager locally open a terminal window and run:
# Linux/Unix/Mac:
cd $TOMCAT_HOME
./bin/catalina.sh run -security
# Windows:
cd %TOMCAT_HOME%
bin\catalina.bat run -security
We offer production environment for hosting your Tomcat web apps. This environment is not suitable for development or testing.
To Start/Stop/Reload web apps go to the "Websites & Domains" section, find the domain/subdomain containing the web app and click its Tomcat button. You will see the list in the "Deployed web applications" section. Started web apps can be stopped and stopped ones can be started. To reload a web app stop it first and then start it.
Our hosting servers are configured for production use. The automatic reloads which are usually enabled in the default Tomcat configuration are disabled. No automatic checks for JSP, class, JAR, web.xml, etc modifications are performed.
You need to manually reload your web apps after doing modifications.
Tomcat's security policy is defined in the file $TOMCAT_HOME/conf/catalina.policy
.
Our policy grants all the permissions in the default catalina.policy
distributed with Tomcat. It also grants several additional permissions commonly required by web apps. Some of them are:
If you find that a permission is required by your web app but it is not granted by our policy you could request it via the HelpDesk. Our administrators will review your request and grant the permission if it is appropriate.
Please note that requests for permissions that might affect the application isolation or the security of the other users' web apps will be denied.
Tomcat logs can be found in the /logs-tomcat
directory which is placed in the subscription's home. The logs are rotated when they reach 1 MB and 10 old log files are preserved.
The STDOUT
and STDERR
streams of each application are redirected to these logs so e.g. System.out.println(..)
and System.err.println(..)
go there.
We do not recommend using connection pooling in our environment since the connection establishment to the DB is lightweight process. Just close the DB connections when you're finished with them and reopen them when needed.
A request scope is an excellent lifespan for a DB connection.
Be especially careful when reusing pooled connections since the RDBMS might be configured to timeout inactive connections and you might encounter:
java.sql.SQLException: No operations allowed after connection closed
mail.jar
and activation.jar
are pre-installed in $TOMCAT_HOME/lib
.
Don't put them in your web app's WEB-INF/lib as this might cause problems.
You can place this code in a file called e.g. `mail.jsp` to send mail:
java.util.Properties props = new java.util.Properties(); String auth_user = "[email protected]"; String auth_password = "PASSWORD"; String from = "[email protected]"; String to = "[email protected]"; props.put("mail.smtp.host", "localhost"); props.put("mail.smtp.port", "25"); props.put("mail.smtp.auth", "true"); props.put("mail.smtp.ssl.enable", "false"); // props.put("mail.smtp.starttls.enable", "true"); String subject = "Testing java mail with settings: " + props.toString(); String body = "This is the message body."; javax.mail.Session sess = javax.mail.Session.getInstance( props, new javax.mail.Authenticator() { protected PasswordAuthentication getPasswordAuthentication() { return new PasswordAuthentication( auth_user, auth_password ); } } ); try { MimeMessage message = new MimeMessage( sess ); message.setFrom( new InternetAddress( from ) ); message.addRecipient( Message.RecipientType.TO, new InternetAddress( to ) ); message.setSubject( subject ); message.setText( body ); Transport.send( message ); out.println( "The message has been sent. Subject: " + subject ); } catch( Exception ex ) { ex.printStackTrace( new java.io.PrintWriter(out) ); out.println( ex.getMessage() ); }
Note that sending mail via SSL/TLS might require setting the mail.smtp.host
to the hostname of the server that your hosting account is on(e.g. fenix.livehostserver.com
) instead of localhost
.
This is needed in order the SSL certificate to be verified successfully.
WAR
files must be extracted in order to be deployed. E.g. the contents of test.war
should be placed in a directory named test
.
WAR
stands for Web application Archive .
In order your mappings to work as expected two things must be done:
WEB-INF/web.xml
The second step is done via .htaccess
files. Here's an example. Let's say you have the following context:
http://docs.mydomain.com/app1/
and this web app has:
/docs/app1/WEB-INF/web.xml
which contains:
<servlet-mapping>
<servlet-name>MyServlet</servlet-name>
<url-pattern>/myservlet/action1</url-pattern>
</servlet-mapping>
You have to create the file:
/docs/.htaccess
which contains:
RewriteEngine On
RewriteRule ^app1/myservlet/action1$ ajp://127.0.0.1:8009/app1/myservlet/action1 [NE,P,L]
You can also map all requests for the app1
web app to Tomcat like this:
RewriteEngine On
RewriteRule ^app1/(.*)$ ajp://127.0.0.1:8009/app1/$1 [NE,P,L]
Or you can even forward all requests for this subdomain to the Tomcat backend:
RewriteEngine On
RewriteRule ^(.*)$ ajp://127.0.0.1:8009/$1 [NE,P,L]
The Tomcat security policy grants web apps read/write/delete permissions for all the files and dirs under the subscription home.
The file system permissions must also allow the system user "tomcat" to do the respective operation.
E.g. to create a directory which is writable by "tomcat" you can login via FTP and do:
mkdir docs/app1/store1
chmod a+rwx docs/app1/store1
You can also create dirs and manage permissions via Plesk File Manager .
If you encounter:
java.security.AccessControlException: access denied (java.io.FilePermission /SOME/PATH)
the usual causes are:
You should be extra carefull when using relative paths. They can be relative to something different than what you expect. In order to check a relative path you can place a code like this in e.g. test.jsp
:
<%@page contentType="text/plain; charset=UTF-8" pageEncoding="UTF-8"%>
<%
java.io.File f = new java.io.File(".");
out.println( "path: " + f.getAbsolutePath() );
%>
The directories which you see when you login via FTP or in the Plesk File manager are relative to the subscription home dir. Here's an example of an absolute path:
/var/www/vhosts/mydomain.com/docs/WEB-INF/uploads/file1.txt
"Tomcat management" page shows the actual DocumentRoot
for the domain/subdomain.
PyroCMS is an easy to use, powerful, and modular CMS and development platform built with Laravel 5.
PyroCMS HostingJoomla is an award-winning content management system (CMS), which enables you to build Web sites and powerful online applications. Many aspects, including its ease-of-use and extensibility, have made Joomla the most popular Web site software available. Best of all, Joomla is an open source solution that is freely available to everyone.
Joomla HostingLeafpub is an open source blogging platform with inline editing, handlebar templates, and a beautiful user interface.
Leafpub HostingLiveSite is a cost effective solution for smaller organizations that need enterprise features without the cost and complexity of enterprise solutions.
LiveSite HostingPHP-Fusion is a light-weight open-source content management system (CMS) written in PHP 5. It utilises a MySQL database to store your site content and includes a simple, comprehensive administration system. PHP-Fusion includes the most common features you would expect to see in many other CMS packages.
PHP-Fusion HostingSmartClient is set of mobile and cross-browser HTML5 UI components combined with a Java-based Ajax framework, created by Isomorphic Software to build business web applications.
SmartClient HostingdotCMS is an open source content management system (CMS) written in Java for managing content and content driven sites and applications.
dotCMS HostingOpenWGA is Web Content Management computer software running on the Java Enterprise Edition Platform.
OpenWGA HostingLogicalDOC is a free document management system that is designed to handle and share documents within an organization.
LogicalDOC HostingeXo Platform is an open source, standard-based, Enterprise Social Collaboration Platform written in Java.
eXo Platform HostingAmetys is a free and open source content management system (CMS) written in Java.
Ametys CMS HostingHippo CMS is an open-source, dual licensed, Content Management System.
Hippo CMS HostingJava Hosting packages on Linux servers.
Java HostingGoogle Web Toolkit, or GWT Web Toolkit, is an open source set of tools that allows web developers to create and maintain complex JavaScript front-end applications in Java.
Google Web Toolkit HostingLiferay makes software that helps companies create digital experiences on web, mobile and connected devices.
Liferay Hosting