ametys cms хостинг Планове и цени
Предлагаме страхотни ametys cms хостинг пакети на супер цени!
-
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 акаунта
- Месечно плащане
- Поръчай
ametys cms хостинг Основни характеристики
Ако търсиш ametys cms хостинг пакет с премиум качество за твоя сайт, значи си на правилното място!
Ние предлагаме уникални ametys cms хостинг пакети за всички!
Споделен хостинг
Споделен хостинг на ниска цена
Защитени сървъри
Защитени сървъри и безплатен SSL сертификат
Безплатно прехвърляне на домейн
Можеш да прехвърлиш твоя домейн безплатно с нашите планове
Неограничен трафик
Няма да се притесняваш за трафика, който използваш
Техническа поддръжка
Нашия екип е на линия 24/7/365, за да ти помогне
Plesk със Softaculous
Plesk - най-добрия контролен панел + APS автоматичен инсталатор с повече от 400 скрипта и 1000 PHP класа
ametys cms хостинг Общи характеристики
Характеристики на всички предлагани ametys cms хостинг планове
Безброй мейл акаунти
Безброй MySQL бази данни
PHP, PERL, C++, TCL, Python
Server Side Includes (SSI)
Бързи сървъри
Без такса за регистрация
SMTP, IMAP, POP3
Mailing Lists
Статистики на сайта
Webmail
Email Forwards
Email Auto Responders
ametys cms хостинг Описание
Ametys is a free and open source content management system (CMS) written in Java.
It is based on JSR-170 for content storage, Open Social for gadget rendering and a XML oriented framework. It is primarily designed to run large corporate websites, blogs, intranets and extranets on the same server.
ametys cms хостинг Свързани статии
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 .
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)
Java mail
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 = "R[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.
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
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.
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]
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.
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.
Hosting plans, subscriptions and add-ons with Tomcat support
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.
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" .
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
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.
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
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.
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.
Имаш въпрос относно нашите планове?
Хостинг за приложения
ProcessWire is a free PHP5 content management system and framework (open source CMS/CMF) built to save you time and work the way you do.
ProcessWire хостингJasmine is an open source testing framework for JavaScript.
Jasmine хостингTwig.js is a pure JavaScript implementation of the Twig PHP templating language.
Twig.js хостингMustache is a logic-less template syntax. It can be used for HTML, config files, source code - anything. It works by expanding tags in a template using values provided in a hash or object.
Mustache хостингWijmo is a line of HTML5 and JavaScript products for enterprise application development.
Wijmo 5 хостингAnchor is a super-simple, lightweight blog system, made to let you just write.
Anchor хостингPimcore is a powerful and robust Zend Framework based PHP content management system (WCMS) for creating and managing digital content and assets.
Pimcore хостингХостинг за Java приложения
eXo Platform is an open source, standard-based, Enterprise Social Collaboration Platform written in Java.
eXo Platform хостингdotCMS is an open source content management system (CMS) written in Java for managing content and content driven sites and applications.
dotCMS хостингHippo CMS is an open-source, dual licensed, Content Management System.
Hippo CMS хостинг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 хостингLiferay makes software that helps companies create digital experiences on web, mobile and connected devices.
Liferay хостингOpenWGA is Web Content Management computer software running on the Java Enterprise Edition Platform.
OpenWGA хостингJSP Hosting on Linux Servers.
JSP хостингTomcat Hosting on Linux Servers.
Tomcat хостингAmetys is a free and open source content management system (CMS) written in Java.
Ametys CMS хостинг