Use the table of contents below to quickly find the information you need within the guide:<\/p>\n
- \n
- Java Versions<\/a><\/li>\n
- Java Application Servers<\/a><\/li>\n
- Java Environment Creation<\/a><\/li>\n
- Java Application Deployment<\/a><\/li>\n
- Domains Management<\/a><\/li>\n
- Automatic Vertical Scaling<\/a><\/li>\n
- Horizontal Scaling: Manual and Automatic<\/a><\/li>\n
- Java Clusterization<\/a><\/li>\n
- Database Connection to Java Application<\/a><\/li>\n<\/ul>\n
<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nJava Versions<\/h2>\n
At present, the following Java distributions are accessible<\/p>\n
- \n
- Oracle OpenJDK<\/li>\n
- Alibaba Dragonwell<\/li>\n
- Amazon Corretto<\/li>\n
- Eclipse OpenJ9<\/li>\n
- Eclipse Temurin<\/li>\n
- GraalVM CE<\/li>\n
- Oracle JDK Dev<\/li>\n
- Zulu Community<\/li>\n<\/ul>\n
Furthermore, our platform exclusively offers the latest available Java<\/a> Engine versions. You can confirm the available versions from your account and make adjustments in the wizard during environment creation or through the topology<\/strong> tuning option.<\/p>\n
![\"Java](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-01-1.png\" "\\"Java")
<\/a><\/p>\nYou can select the preferred version when creating an environment or change it later. These procedures are detailed in the Java Versions document.<\/p>\n
Java Application Servers<\/h2>\n
The platform supports a diverse range of software stacks, including a pure Java Engine and the following Java application servers:<\/p>\n
- \n
- GlassFish<\/a><\/li>\n
- Jetty<\/a><\/li>\n
- Payara<\/a><\/li>\n
- Spring Boot<\/a><\/li>\n
- Tomcat<\/a><\/li>\n
- TomEE<\/a><\/li>\n
- WildFly<\/a><\/li>\n<\/ul>\n
Refer to the documentation below for more details on Java server specifics within the platform:<\/p>\n
- \n
- Java App Server Configuration<\/li>\n
- Java Garbage Collection<\/li>\n
- Java Agent<\/li>\n
- Java Tutorials<\/li>\n<\/ul>\n<\/div>\n\t\t\n\t\t\t
\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nJava Environment Creation<\/h2>\n
To host a Java application<\/a>, you need to create an appropriate environment. Open the topology wizard in your PaaS dashboard, navigate to the Java language tab, and select the desired Java<\/strong> application server, databases, and other stacks. If necessary, customize the settings (such as cloudlets, disk space, etc.) and click “Create.”<\/strong><\/p>\n
![\"Java](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-052-1.png\" "\\"Java")
<\/a><\/p>\nAll added servers are fully<\/strong> isolated containers<\/a> situated on different hosts to enhance availability. This isolation prevents the servers from interfering with one another. You can attach a public IP<\/a> address to any of these servers for direct access. Otherwise, if you use the default settings, incoming requests to your application will be proxied by a Shared Load Balancer.<\/p>\n
Java Application Deployment<\/h2>\n
After creating the environment, you can deploy your Java<\/a> application. The platform fully automates the deployment process, enabling you to get your project up and running effortlessly.<\/p>\n
The following deployment methods are supported:<\/p>\n
- \n
- Via application archives:<\/strong> .war, .zip, .jar, and .ear files<\/li>\n
- From a GIT\/SVN remote repository,<\/strong> using the Maven build node<\/li>\n<\/ul>\n
![\"Deploy](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-03.png\" "\\"Deploy")
<\/a><\/p>\nYou can read the appropriate documents to learn more about the deployment of Java applications:<\/p>\n
- \n
- Deployment Guide<\/li>\n
- Maven Build Node<\/li>\n
- Auto-Deploy Overview<\/li>\n
- Deployment Hooks<\/li>\n<\/ul>\n
There are also separate instructions for managing your projects via Gitblit<\/a> and WebDAV.<\/a><\/p>\n
<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nDomains Management<\/h2>\n
You can bind a custom domain<\/a> name to your application’s URL and use it instead of the default environment domain:<\/p>\n
- \n
- CNAME Redirect:<\/strong> Recommended for dev<\/strong> and test<\/strong> environments, this method is used when employing a Shared Load Balancer.<\/li>\n
- DNS A Record:<\/strong> Suitable for production<\/strong> environments, this method is used when a public IP is attached and can handle high traffic loads.<\/li>\n<\/ul>\n
Additionally, using the swapping domains<\/a> feature or the SwapExtIps<\/strong> API<\/a>\/CLI<\/a> method, you can upgrade and modify your application with zero downtime, ensuring no interruption for your users.<\/p>\n
![\"Domain](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-04.png\" "\\"Domain")
<\/a><\/p>\nAutomatic Vertical Scaling<\/h2>\n
The platform dynamically allocates the number of cloudlets (i.e., RAM and CPU resources) required by your application to handle the current load. Simply specify the maximum limit, and the platform will handle everything automatically\u2014no manual intervention is required. This feature, known as automatic vertical scaling<\/a>, ensures that you never overpay for unused capacities while preventing resource shortages.<\/p>\n
![\"Verticle](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-06.png\" "\\"Verticle")
<\/a><\/p>\nTo set or change the vertical scaling limit, simply use the appropriate slider within the topology wizard.<\/p>\n
<\/a><\/p>\nHorizontal Scaling: Manual and Automatic<\/h2>\n
If your application gains significant popularity and a single node is insufficient, consider scaling it horizontally. To enhance reliability and high availability, all newly added nodes are created on different hardware nodes.<\/p>\n
![\"Horizontal](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-07.png\" "\\"Horizontal")
<\/a><\/p>\nTo set the required number of nodes, click the +\/- buttons within the Horizontal Scaling section of the topology wizard. The load balancer will be added automatically.<\/p>\n
You can also adjust the preferred scaling mode:<\/p>\n
- \n
- Stateless: Simultaneously creates all new nodes from the base image template.<\/li>\n
- Stateful: Sequentially copies the file system of the master container into the new nodes.<\/li>\n<\/ul>\n
Horizontal scaling can be performed manually or automatically based on the current load on the node, which is monitored through tunable triggers.<\/p>\n
Within the Settings<\/strong> > Auto Horizontal Scaling<\/a> section, you can customize the scaling conditions according to your requirements. This includes setting the lower and upper limits (as a percentage) for specified resource types during specific periods. If the load exceeds or falls below the set limits, the process of adding or removing nodes will be triggered automatically.<\/p>\n
<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nThe platform monitors five different types of resources through triggers:<\/p>\n
- \n
- CPU<\/li>\n
- Memory (RAM)<\/li>\n
- Network<\/li>\n
- Disk I\/O<\/li>\n
- Disk IOPS<\/li>\n<\/ul>\n
![\"Auto](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-08.png\" "\\"Auto")
<\/a><\/p>\nThe trigger starts monitoring the resource consumption immediately after addition. When the usage level surpasses the specified limit, the trigger becomes activated. If the load persists beyond a defined period, the trigger will be executed, adjusting the number of nodes accordingly.<\/p>\n
Java Clusterization<\/h2>\n
The embedded application server clustering feature facilitates session replication between pairs of nodes, eliminating the need for additional software or Memcached usage to enhance application availability.<\/p>\n
The platform offers automated session replication between Tomcat and TomEE<\/strong> servers using multicast, ensuring high availability for web applications within the Java<\/a> cluster. This High-Availability feature can be enabled in the wizard during environment creation or topology tuning.<\/p>\n
- DNS A Record:<\/strong> Suitable for production<\/strong> environments, this method is used when a public IP is attached and can handle high traffic loads.<\/li>\n<\/ul>\n
- CNAME Redirect:<\/strong> Recommended for dev<\/strong> and test<\/strong> environments, this method is used when employing a Shared Load Balancer.<\/li>\n
- From a GIT\/SVN remote repository,<\/strong> using the Maven build node<\/li>\n<\/ul>\n
- Via application archives:<\/strong> .war, .zip, .jar, and .ear files<\/li>\n
- Jetty<\/a><\/li>\n
- GlassFish<\/a><\/li>\n
- Java Application Servers<\/a><\/li>\n
![\"Auto](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Java-Developers-Center-09-1.png\" "\\"Auto")
<\/a><\/p>\n![\"Modern](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/dev-center-img-.jpg\" "\\"Modern")
<\/a><\/p>\n