Introducing Google Cloud's Tomcat migration tooling

Apache Tomcat is among the mostly used net servers and servlet containers for operating Java purposes. Many enterprises run manufacturing Java net purposes on Tomcat servers, operating on digital machines and wish to modernize these purposes to run in containers and luxuriate in the advantages of containerized, cloud native environments reminiscent of Google Kubernetes Engine(GKE).

Whereas assessing and containerizing a single Java software to run in a container is feasible in a guide course of. Figuring out, assessing after which containerizing many such purposes at scale is time consuming, labor intensive and error susceptible. Having these obstacles will increase the prices of modernizing these apps and slows down the enterprise modernization journey.

We’ve lately launched a public preview model of our Tomcat modernization circulate which permits prospects to completely automate the modernization of current Tomcat Java apps into containers, able to be deployed on any Kubernetes cluster. As well as, we generate artifacts reminiscent of Dockerfiles, Deployment Descriptors, Kubernetes Secrets and techniques and Cloud Construct configuration for use in your Day2 operations. With these artifacts, you’ll be able to absolutely automate future builds and deployments of your legacy apps utilizing trendy CI/CD practices.

The Tomcat apps modernization course of is finished in four steps:

• Evaluation – You first run the Match Evaluation Device which routinely detects operating Tomcat situations and the purposes deployed on them. You then use the instrument to research the collected information and generate a report. The report will advocate a migration journey on your workload, in accordance with a set of predefined evaluation guidelines.

• Planning – On this step you create a migration plan on your Tomcat VM. The Migration plan will embrace all of the Tomcat situations that have been found within the earlier step along with all of the purposes and secrets and techniques reminiscent of keystores, certificates and truststores which are utilized by the Tomcat situations. You’ll be able to modify the plan to satisfy your necessities and add or take away purposes or extra information.

• Migrate & Modernize – That is the place we course of the migration and generate the artifacts in accordance with the migration plan. For every software we are going to generate a construct script, deployment yaml, volumes yaml(if any information volumes have been migrated) and cloudbuild yaml, all of which can be utilized in a CI/CD pipeline.

• Optimize – On this section you’ll be able to optimize your Tomcat containers by effective tunning reminiscence settings, apply updates and patches to your software and create automated pipelines for constructing, deploying and testing your migrated purposes.

If you want to be taught extra about modernizing legacy Java purposes operating on Tomcat, please go to our documentation or strive it your self by following the step-by-step information on our Github repository.