In the first use case in this blog series, we looked at building workflows around IST (Intersight Services for Terraform) automations to provision IKS infrastructure and deploy a sample cloud native application with ICO (Intersight Cloud Orchestrator).
In today’s blog we’ll take a look at deploying a legacy micro services Java app on VM based infrastructure with IST and AppDynamics.
For several decades now, Apache Tomcat has been the application platform of choice for Java applications deployment. Enterprises are modernizing their applications as well as deployment methodologies. However, modernization of applications is an iterative process and some of them may well continue to exist in their legacy form for some time to come. This will not prevent Infrastructure and Operations teams from modernization of their deployment methodologies using tools like Terraform and IST.
Let’s take a look at a use case of deploying a multi-service Tomcat application leveraging IST. As a value add, we will also enable AppDynamics Insights for this legacy application leveraging AppDynamics Zero Friction Installer (ZFI) or AppDynamics Agent Installer.
In the above diagram, each of the blocks refer to a TFCB (Terraform for Cloud Business) workspace. As you can see, there is a dependency in the execution of the various workspaces:
- set up the global variables,
- set up the DB server,
- set up the base infrastructure and Tomcat application platform,
- connect with AppDynamics SAAS Controller and retrieve the ZFI artifacts,
- set up the RBAC in the Controller and execute AppDynamics Zero Agent in the application server,
- deploy the application microservices on the Tomcat Application Platform and
- finally send some sample application load so application services can be visualized in the AppDynamics Platform.
Visit DevNet Code Exchange for the details
For the details on how to deploy a legacy micro services Java app on VM based infrastructure with IST and AppDynamics
see the repo on DevNet Code Exchange.
In the next blog, we will explore ICO (Intersight Cloud Orchestrator) workflows to capture the above dependency of the workspaces.
We’d love to hear what you think. Ask a question or leave a comment below.
And stay connected with Cisco DevNet on social!