jsp hosting Планове и цени
Предлагаме страхотни jsp hosting пакети на супер цени!
-
J-STARTER
Временна оферта - 50% отстъпка
ДДС се прилага на EU клиенти -
(
12 лв.) 6 лв. / 1 месец (без ДДС) -
(
34 лв.) 17 лв. / 3 месеца (без ДДС) -
(
66 лв.) 33 лв. / 6 месеца (без ДДС) -
(
130 лв.) 65 лв. / 1 година (без ДДС) -
(
258 лв.) 129 лв. / 2 години (без ДДС) - 10GB дисково пространство
- Java, JSP, Tomcat
- Неограничен трафик
- 1 домейн на акаунт
- 1 Tomcat приложение
- 10 под-домейна
- 10 FTP акаунта
- Месечно плащане
- Поръчай
-
J-BASIC
Временна оферта - 50% отстъпка
ДДС се прилага на EU клиенти -
(
14 лв.) 7 лв. / 1 месец (без ДДС) -
(
40 лв.) 20 лв. / 3 месеца (без ДДС) -
(
78 лв.) 39 лв. / 6 месеца (без ДДС) -
(
154 лв.) 77 лв. / 1 година (без ДДС) -
(
306 лв.) 153 лв. / 2 години (без ДДС) - 20GB дисково пространство
- Java, JSP, Tomcat
- Неограничен трафик
- 2 домейна на акаунт
- 5 Tomcat приложения
- 20 под-домейна
- 20 FTP акаунта
- Месечно плащане
- Поръчай
-
J-PRO
Временна оферта - 50% отстъпка
ДДС се прилага на EU клиенти -
(
16 лв.) 8 лв. / 1 месец (без ДДС) -
(
46 лв.) 23 лв. / 3 месеца (без ДДС) -
(
90 лв.) 45 лв. / 6 месеца (без ДДС) -
(
178 лв.) 89 лв. / 1 година (без ДДС) -
(
354 лв.) 177 лв. / 2 години (без ДДС) - 30GB дисково пространство
- Java, JSP, Tomcat
- Неограничен трафик
- 3 домейна на акаунт
- 10 Tomcat приложения
- 30 под-домейна
- 30 FTP акаунта
- Месечно плащане
- Поръчай
-
J-ENTERPRISE
Временна оферта - 50% отстъпка
ДДС се прилага на EU клиенти -
(
20 лв.) 10 лв. / 1 месец (без ДДС) -
(
58 лв.) 29 лв. / 3 месеца (без ДДС) -
(
114 лв.) 57 лв. / 6 месеца (без ДДС) -
(
226 лв.) 113 лв. / 1 година (без ДДС) -
(
450 лв.) 225 лв. / 2 години (без ДДС) - 50GB дисково пространство
- Java, JSP, Tomcat
- Неограничен трафик
- 5 домейна на акаунт
- Неограничен брой Tomcat приложения
- 50 под-домейна
- 50 FTP акаунта
- Месечно плащане
- Поръчай
jsp hosting Основни характеристики
Ако търсиш jsp hosting пакет с премиум качество за твоя сайт, значи си на правилното място!
Ние предлагаме уникални jsp hosting пакети за всички!
Споделен хостинг
Споделен хостинг на ниска цена
Защитени сървъри
Защитени сървъри и безплатен SSL сертификат
Безплатно прехвърляне на домейн
Можеш да прехвърлиш твоя домейн безплатно с нашите планове
Неограничен трафик
Няма да се притесняваш за трафика, който използваш
Техническа поддръжка
Нашия екип е на линия 24/7/365, за да ти помогне
Plesk със Softaculous
Plesk - най-добрия контролен панел + APS автоматичен инсталатор с повече от 400 скрипта и 1000 PHP класа
jsp hosting Общи характеристики
Характеристики на всички предлагани jsp hosting планове
Безброй мейл акаунти
Безброй MySQL бази данни
PHP, PERL, C++, TCL, Python
Server Side Includes (SSI)
Бързи сървъри
Без такса за регистрация
SMTP, IMAP, POP3
Mailing Lists
Статистики на сайта
Webmail
Email Forwards
Email Auto Responders
jsp hosting Описание
JSP Hosting on Linux Servers.
JavaServer Pages (JSP) is a technology that helps software developers create dynamically generated web pages based on HTML, XML, or other document types. Released in 1999 by Sun Microsystems, JSP is similar to PHP and ASP, but it uses the Java programming language.
To deploy and run JavaServer Pages, a compatible web server with a servlet container, such as Apache Tomcat or Jetty, is required.
Architecturally, JSP may be viewed as a high-level abstraction of Java servlets. JSPs are translated into servlets at runtime, therefore JSP is a Servlet; each JSP servlet is cached and re-used until the original JSP is modified.
JSP can be used independently or as the view component of a server-side model–view–controller design, normally with JavaBeans as the model and Java servlets (or a framework such as Apache Struts) as the controller. This is a type of Model 2 architecture.
JSP allows Java code and certain pre-defined actions to be interleaved with static web markup content, such as HTML, with the resulting page being compiled and executed on the server to deliver a document. The compiled pages, as well as any dependent Java libraries, contain Java bytecode rather than machine code. Like any other Java program, they must be executed within a Java virtual machine (JVM) that interacts with the server's host operating system to provide an abstract, platform-neutral environment.
JSPs are usually used to deliver HTML and XML documents, but through the use of OutputStream, they can deliver other types of data as well.
The Web container creates JSP implicit objects like request, response, session, application, config, page, pageContext, out and exception. JSP Engine creates these objects during translation phase.
jsp hosting Свързани статии
Hosting plans, subscriptions and add-ons with Tomcat support
Our Java environment
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.
Which domains and subdomains can have Tomcat web apps
A domain or subdomain can have Tomcat web apps deployed if it:
- has hosting enabled
- is active, e.g. not suspended or disabled
Additionally, the domain or subdomain DocumentRoot
must be pointed to a directory which is directly under the subscription home directory. E.g.
- "/test" - (correct)
- "/httpdocs/test" - (NOT correct)
Before requesting deployment
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.
Where should you upload your Tomcat web apps
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:
- /docs/WEB-INF
- /docs/app1/WEB-INF
- /docs/app2/WEB-INF
With this layout the following contexts can be deployed:
- docs.mydomain.com/
- docs.mydomain.com/app1/
- docs.mydomain.com/app2/
Each tomcat context represents a separate web app with its own classes, libraries, JSP files, etc. E.g:
- /docs/app1/WEB-INF/web.xml
- /docs/app1/WEB-INF/lib/jar1.jar
- /docs/app1/WEB-INF/lib/jar2.jar
- /docs/app1/WEB-INF/classes/Class1.class
- /docs/app1/WEB-INF/classes/package1/subpackage1/OtherClass.class
WAR files
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 .
Requesting web app deployment
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:
- A list of deployable contexts
- A checkbox to request manual review of the web app
META-INF/context.xml
- A text area where you can add additional information to the person who will process your request
The list of deployable contexts is generated by scanning the DocumentRoot
. An entry in the list is created for:
- directories placed directly in the
DocumentRoot
and - containing a subdirectory
WEB-INF
and - having names which can be valid context path
META-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" .
Start, Stop and Reload of Tomcat web apps
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 log files
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.
Servlet/filter mappings
In order your mappings to work as expected two things must be done:
- As usual they have to be defined in
WEB-INF/web.xml
- Apache HTTPd frontend has to be configured to pass them to the Tomcat backend.
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]
Security policy
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:
- Each of your applications is granted read/write/delete permissions for all files and dirs under subscription's home dir
- Read permission is granted to all system properties
- New Socket connections are allowed
- Some additional package access is granted as well as Reflection permissions
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.
Read/Write/Delete files on the file system
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:
- Wrong paths
- Wrong file system permissions
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.
Java mail
In order to send mail from your Tomcat web app you could use the following settings:
Hostname: localhost
TCP port: 25
Username: [email protected]
Password: mailbox's password
mail.jar
and activation.jar
are pre-installed in $TOMCAT_HOME/lib
so you don't need to put them in your web app's WEB-INF/lib
.
Connecting to a database from your Tomcat web app
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.
Database connection pooling
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
Third party libraries pre-installed in Tomcat
- MySQL drivers - mysql-connector-java-bin.jar
- Java mail required JARs - mail.jar and activation.jar
- Standard libs that come in the default Tomcat distribution
Имаш въпрос относно нашите планове?
Хостинг за приложения
WordPress is web software you can use to create a beautiful website or blog. We like to say that WordPress is both free and priceless at the same time.
WordPress хостингYii is an open source, object-oriented, component-based MVC PHP web application framework.
Yii хостингJsPHP is a cross-browser JavaScript library designed to make the PHP application programming interface (API) available in JavaScript environments.
JsPHP хостингCannon.js is an open source JavaScript 3D physics engine.
Cannon.js хостингOpen Real Estate is a free software for building websites of real estate agencies and realtors. It is based on Yii CMF - one of the fast working modern frameworks.
Open Real Estate хостингLaravel is a free, open-source PHP web framework, intended for the development of web applications following the model–view–controller (MVC) architectural pattern.
Laravel хостингModernizr is a JavaScript library which is designed to detect HTML5 and CSS3 features in various browsers, which lets JavaScript avoid using unimplemented features or use a workaround such as a shim to emulate them.
Modernizr хостингХостинг за Java приложения
XWiki is a free wiki software platform written in Java with a design emphasis on extensibility.
XWiki хостингHippo CMS is an open-source, dual licensed, Content Management System.
Hippo CMS хостингApache Roller is a Java-based Open Source "full-featured, Multi-blog, Multi-user, and group-blog server suitable for blog sites large and small".
Apache Roller хостингTomcat Hosting on Linux Servers.
Tomcat хостингSmartClient 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 хостингGoogle 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 хостингJSP Hosting on Linux Servers.
JSP хостингdotCMS is an open source content management system (CMS) written in Java for managing content and content driven sites and applications.
dotCMS хостингAdult Java Hosting packages on Linux Servers.
Adult Java хостингJava Hosting packages on Linux servers.
Java хостинг