Jelastic

Virtuozzo Acquires Jelastic Virtuozzo has acquired the technology and business of Jelastic, a multi-cloud Platform-as-a-Service (PaaS) software company, following a 10-year partnership.Bringing Jelastic’s platform and application management capabilities in-house completes Virtuozzo’s core technology stack, delivering a fully integrated solution that supports all relevant anything-as-a-service (XaaS) use cases—from shared hosting to VPS to cloud infrastructure, software-defined storage and application management and modernization.Virtuozzo offers the first fully integrated, easy-to-use and cost-efficient cloud solution designed for Cloud Service Providers, Managed Service Providers, Hosting Service Providers and their small and medium-sized business (SMB) customers. Virtuozzo also helps service providers increase profitability by providing a comprehensive portfolio of services and management tools.Many PaaS vendors focus on a single-purpose offering. Jelastic, however, offers a robust, multi-purpose solution that, via the acquisition, will position Virtuozzo as a strong player in the PaaS market and further strengthen Virtuozzo’s position overall in the rapidly growing cloud services space.“Virtuozzo and Jelastic have been strong partners over the past 10 years because of our complementary technologies and products,” said Alex Fine, CEO of Virtuozzo. “Virtuozzo containers have been incorporated into Jelastic’s Platform-as-a-Service for virtualization since that solution’s inception. Together, our engineering teams have co-developed solutions to enable features required by the market throughout our partnership. And now, with Jelastic joining our team, Virtuozzo can offer a complete, enterprise-grade, turnkey cloud enablement platform with fully integrated orchestration and a single point of management.”Business continues as usual, with Jelastic now operating as a division of Virtuozzo—underscoring the value in Jelastic’s brand and technologies.

5.3.8. Deployment to Jelastic Cloud Below is an example of building and deployment application to the Jelastic cloud. Please note that only projects using PostgreSQL or HSQL databases are currently supported. First, create a free test account in the Jelastic cloud using a web browser. Create a new environment where the application WAR will be deployed: Click New Environment. Specify the settings in the window that appears: a compatible environment should have Java 8, Tomcat 8 and PostgreSQL 9.1+ (if the project uses PostgreSQL database). In the Environment Name field, specify a unique environment name and click Create. If the created environment uses PostgreSQL, you will receive an email with the database connection details. Go to the database administration web interface using the link in the email received after the creation of the environment and create an empty database. The database name should be specified later in the custom context.xml. Build Single WAR file using CUBA Studio: Select CUBA > Deployment > WAR Settings in the main menu. Select Build WAR checkbox. Enter .. in the Application home directory field. Select Include JDBC driver and Include Tomcat’s context.xml checkboxes. If your project uses PostgreSQL, press Generate button next to the Custom context.xml path field. Specify the database user, password, host, and name of the database that you created earlier in the Jelastic web interface. Select Single WAR for Middleware and Web Client checkbox. Press Generate button next to the Custom web.xml path field. Studio will generate a special web.xml of

To use any custom files/folders for configuring your application you can download/create them in the home directory which is used as a storage in your Java server.As a result you can make configurations specifying the path to your downloaded/created files in the variables.conf file (server folder).Note: Although the server’s directory, which refers to this folder, can be named temp for some servers, it is never automatically cleaned by the platform system.Back to the listWEBAPPS / WORKThe webapps (for Tomcat/TomEE) and work (for Jetty) folders are used for storing the unpacked application deployed to the environment.Back to the listJAVA_HOMEThe JAVA_HOME folder contains the java config files and libs. Here, you can edit java settings and upload additional java libraries.Back to the listLIBThe lib folder is used for storing default and uploading custom jar libraries.Back to the listCRONApp servers include a cron folder with the config file, where cronjobs can be configured.Detailed information on Cronjob configuration can be found in the Setting Up a Cronjob document.Back to the listKEYSThe keys directory is used as a location for uploading any private key which is needed for your application.Generate the key, save it as a simple file and upload to the key folder.It can be used for different cases by simply stating the path to your key:1/var/lib/jelastic/keys/{key_file_name}Back to the listCONTEXTSThe contexts folder contains XML config files for each deployed context. All of these files are open for editing.Back to the listSERVER_LIBThe server_lib folder is the GlassFish config directory with all available server libraries.Back to the listAPPSThe apps TomEE folder is used for storing the unpacked EE application deployed to the environment.Back to the listTomcatFolderFilePathconfcatalina.policycatalina.propertiescontext.xmljaspic-providers.xmljaspic-providers.xsdjelastic-ha.xmljelastic-ssl.xmllogging.propertiesserver.xmltomcat-env.shtomcat-users.xmltomcat-users.xsdvariables.confweb.xml/opt/tomcat/conftemp/opt/tomcat/tempwebapps/opt/tomcat/webappslatest/usr/java/latestlib/opt/tomcat/libcrontomcat/var/spool/cronkeys/var/lib/jelastic/keysBack to the listTomEEFolderFilePathservercatalina.policyserver.xmlcatalina.propertiestomcat-users.xmlcontext.xmlweb.xmlvariables.conflogging.propertiestomee.xmlsystem.properties/opt/tomcat/conf/home/opt/tomcat/tempwebapps/opt/tomcat/webappsapps/opt/tomcat/appsJAVA_HOME/usr/java/defaultlib/opt/tomcat/libcrontomcat/var/spool/cronkeys/var/lib/jelastic/keysBack to the listGlassFishFolderFilePathserverdefault-web.xmldomain.xmldomain.xml.bakdomain.xml.origlocal-passwordlogging.propertieslogging.properties.origlogin.confserver.policysun-acc.xmlwss-server-config-1.0.xmlwss-server-config-2.0.xml/opt/glassfish3/glassfish/domains/domain1/configgfcluster-config (in server folder)logging.properties/opt/glassfish3/glassfish/domains/domain1/config/gfcluster-confighome/opt/glassfish3/tempJAVA_HOME/usr/java/latestserver_lib/opt/glassfish3/glassfish/lib/cronglassfish/var/spool/cronkeys/var/lib/jelastic/keysBack to the listJettyFolderFilePathserverjdbcRealm.propertiesjetty-ajp.xmljetty-bio.xmljetty-jaas.xmljetty-jmx.xmljetty-logging.xmljetty-plus.xmljetty-rewrite.xmljetty-setuid.xmljetty-sslengine.xmljetty-ssl.xmljetty-stats.xmljetty.xmllogin.conflogin.propertiesrealm.propertiesspnego.propertiesvariables.confwebdefault.xml/opt/jetty/etchome/opt/jetty/homecontexts/opt/jetty/contexts/work/opt/jetty/workJAVA_HOME/usr/java/latestlib/opt/jetty/libcronjetty/var/spool/cronkeys/var/lib/jelastic/keysBack to the listWhat’s next?Tomcat ServerTomEEJettyGlassFishDatabase Configuration

The single WAR comprising the Middleware and Web Client application blocks. Add cuba.logDir property in the App properties field: appProperties = ['cuba.automaticDatabaseUpdate': true,'cuba.logDir': '${catalina.base}/logs'] Click the OK button. Studio adds the buildWar task to the build.gradle file. task buildWar(type: CubaWarBuilding) { includeJdbcDriver = true includeContextXml = true appProperties = ['cuba.automaticDatabaseUpdate': true, 'cuba.logDir' : '${catalina.base}/logs'] webXmlPath = 'modules/web/web/WEB-INF/single-war-web.xml' coreContextXmlPath = 'modules/core/web/META-INF/war-context.xml'} If your project uses HSQLDB, open the buildWar task in the build.gradle and add the hsqlInProcess = true property in order to run the embedded HSQL server while deploying the WAR file. Make sure that the coreContextXmlPath property is not set. task buildWar(type: CubaWarBuilding) { appProperties = ['cuba.automaticDatabaseUpdate': true, 'cuba.logDir': '${catalina.base}/logs'] includeContextXml = true webXmlPath = 'modules/web/web/WEB-INF/single-war-web.xml' includeJdbcDriver = true hsqlInProcess = true} Start build process by running buildWar from the command line: As a result, the app.war file will be created in the build\distributions\war project subdirectory. Use deployWar Gradle task to deploy your WAR file to Jelastic. task deployWar(type: CubaJelasticDeploy, dependsOn: buildWar){ email = **** password = **** hostUrl = 'app.j.layershift.co.uk' environment = 'my-env-1'} After the deployment process is completed, your application will be available in the Jelastic cloud. To open it, use a URL like . in the browser. For example: You can also open the application using the Open in Browser button located on the environments panel in Jelastic.