Metawerx Java Hosting a complete range of management and Java Hosting options, suitable for any purpose.
The most suitable option will depend on the type of application(s) you want to host, how much control you want, and how much you want to leave to Metawerx.
- Suits: Customers on a budget who want performance, or customers who have had a site built by another company and who want an easy setup with no need to worry about the underlying Java system
- RAM: up to 2.7gb of physical RAM
- Management: Metawerx
- Tuning: Metawerx
- Upgrades: latest Tomcat upgrades are performed automatically within the same release (eg: 6.0.x is upgraded to later compatible 6.0.x revisions as they are released)
- Layout: a shared VM contains multiple <Host> entries, one allocated to each customer
- Applications: no limit set for the number of applications you can add. You have your own webapps folder and can add multiple web applications, each in their own folder (eg: ROOT, /forum, /wiki, /intranet)
- Deploy Apps: you can add multiple web applications, each in their own folder
- Reload Apps: you can easily redeploy/reload any application using the Tomcat Manager, on demand
- Restart VM: no - but generally not required unless your app does not restart with the Tomcat Manager
- Domains: you can add unlimited domain names, all pointing to the same website (eg: mycompany.com, mycompany.net, mycompany.org)
- Logs: you can view private logs for your <Host>, the system log, and Access Logs, and also use log4j etc...
- conf/server.xml Access: no, this is managed by metawerx
- Suits: Customers who want to be the only customer on the Java VM for increased security and reduced risk of other customers affecting performance - but don't want to worry about managing the Java VM themselves. Large well-written applications that work in a Metawerx Managed environment.
- RAM: depends on hosting plan
- Management: Metawerx
- Tuning: Metawerx
- Upgrades: latest Tomcat upgrades are performed automatically within the same release (eg: 6.0.x is upgraded to later compatible 6.0.x revisions as they are released)
- Layout: a dedicated VM contains one <Host> entry, dedicated to you
- Applications: no limit set for the number of applications you can add. You have your own webapps folder and can add multiple web applications, each in their own folder (eg: ROOT, /forum, /wiki, /intranet)
- Deploy Apps: you can add multiple web applications, each in their own folder
- Reload Apps: you can easily redeploy/reload any application using the Tomcat Manager, on demand
- Restart VM: you can restart the VM whenever you need to, you are the only customer
- Domains: you can add unlimited domains, each pointing to the same site or to multiple sites
- Logs: you can view private logs for your <Host>, the system log, and Access Logs, and also use log4j etc...
- conf/server.xml Access: no, this is managed by metawerx
- Suits: Large applications that don't work in a Metawerx Managed environment (eg: Confluence/Jira/OfBiz). Customers who want to host multiple sites for multiple customers of their own, so need complete control over the Tomcat configuration, but want Metawerx to manage automatic upgrades of the Tomcat binaries to reduce management costs and security risks. Most software companies should use this option.
- RAM: depends on hosting plan
- Management: Metawerx via monitoring, you configure your own server.xml etc..
- Tuning: Metawerx via startup options, you can tune other parameters in the conf folder
- Upgrades: latest Tomcat upgrades are performed automatically within the same release (eg: 6.0.x is upgraded to later compatible 6.0.x revisions as they are released)
- Layout: you have access to all dynamic Tomcat folders (/conf, /work, /temp, /logs). You can configure server.xml with multiple <Host> entries for multiple websites. Metawerx manages the binary folders (/bin, /common, /lib, /shared, /server).
- Applications: multiple apps, multiple hosts, multiple sites
- Deploy Apps: you can add multiple web applications, and multiple sites, each in their own folder
- Reload Apps: you can easily redeploy/reload any application using the Tomcat Manager, on demand
- Restart VM: you can restart the VM whenever you need to, you are the only customer
- Domains: you can add unlimited domains, each pointing to the same site or to multiple sites
- Logs: system logs are written automatically to your /home folder and you can configure access logs in any format by yourself as well as use log4j or other logging frameworks as usual
- conf/server.xml Access: yes, access to entire /conf folder
- Suits: Large applications that don't work in a Metawerx Managed environment (eg: Confluence/Jira/OfBiz). Customers who want to host multiple sites for multiple customers of their own, so need complete control over the Tomcat configuration, and want to manage the Tomcat binaries as well to perform their own upgrades to Tomcat versions, or install shared libraries in the Tomcat /lib or /common folders. Increased risk and management time, but full control.
- RAM: depends on hosting plan
- Management: Metawerx via monitoring, you configure your own server.xml etc..
- Tuning: Metawerx via startup options, you can tune other parameters in the conf folder
- Upgrades: you install your own Tomcat upgrades in the /bin, /common, /lib, /shared and /server folders
- Layout: you have access to all Tomcat folders (/bin, /common, /lib, /shared, /server, /webapps, /conf, /work, /temp, /logs). You can configure server.xml with multiple <Host> entries for multiple websites. You can add shared libraries in /lib (6.0.x) or /common (5.5.x and earlier) etc...
- Applications: multiple apps, multiple hosts, multiple sites
- Deploy Apps: you can add multiple web applications, and multiple sites, each in their own folder
- Reload Apps: you can configure Tomcat Manager or just restart the VM as required, on demand
- Restart VM: you can restart the VM whenever you need to, you are the only customer
- Domains: you can add unlimited domains, each pointing to the same site or to multiple sites
- Logs: system logs are written automatically to your /home folder and you can configure access logs in any format by yourself as well as use log4j or other logging frameworks as usual
- conf/server.xml Access: yes, access to entire /conf folder
- Suits: Java applications that run from a Linux shell, but are not Tomcat or JBoss. For example: CruiseControl, specialist scientific applications, share-trading services etc...
- RAM: depends on hosting plan
- Management: You
- Tuning: Metawerx via startup options
- Other: depends on the application
- Logs: system logs are written automatically to your /home folder and you can configure access logs in any format by yourself as well as use log4j or other logging frameworks as usual
If you have any questions, or need help deciding on the most suitable JVM type, please contact us.
There is no cost to change plan type.
