Using AppDynamics with Red Hat OpenShift v3

In recent times, many organizations want their applications to move from monoliths to microservices using "platform as a service" (PaaS), such as RedHat OpenShift v3, AppDynamics has made significant investments in providing first-class integration with such providers.



AppDynamics integrates its agents with RedHat OpenShift v3 using Source-to-Image (S2I) methodologies. S2I is a tool for building reproducible Docker images. It creates ready-to-run images by injecting the application source into a Docker image and building a new Docker image. The new image, includes the base image (builder) and the built source, ready to be used with the docker run command. S2I supports incremental builds that reuse previously downloaded dependencies, previously built artifacts, etc.

Process

Complete process for using AppDynamics with RedHat OpenShift

Step 1: RedHat already provided

To complete steps 2 and 3, you can use the S2I scripts in the following GitHub repository and instructions on how to create enhanced builder images for JBoss Wildfly and EAP servers. follow the link
Consider everything on a specific example and use the application template follow the link.

Prerequisites:

• Make sure OC is installed ( link)
• Make sure sti is installed ( link)
• Make sure you have a dockerhub account ( link)

Step 2: Create the AppDynamics Builder Image

 $ git clone https://github.com/Appdynamics/sti-wildfly.git
$ cd sti-wildfly
$ make build VERSION=eap6.4 

Step 3: Create an application image

 $ s2i build  -e “APPDYNAMICS_APPLICATION_NAME=os3-ticketmonster,APPDYNAMICS_TIER_NAME=os3-ticketmonster-tier,APPDYNAMICS_ACCOUNT_NAME=customer1_xxxxxxxxxxxxxxxxxxf,APPDYNAMICS_ACCOUNT_ACCESS_KEY=xxxxxxxxxxxxxxxxxxxxx,APPDYNAMICS_CONTROLLER_HOST=xxxx.saas.appdynamics.com,APPDYNAMICS_CONTROLLER_PORT=443,APPDYNAMICS_CONTROLLER_SSL_ENABLED=true” https://github.com/jim-minter/ose3-ticket-monster appdynamics/sti-wildfly-eap64-centos7:latest pranta/appd-eap-ticketmonster
$ docker tag openshift-ticket-monster pranta/openshift-ticket-monster:latest
$ docker push pranta/openshift-ticket-monster 

Step 4: Deploy the application in OpenShift

$ oc login 10.0.32.128:8443
$ oc new-project wildfly
$ oc project wildfly
$ oc new-app –docker-image=pranta/appd-eap-ticketmonster:latest –name=ticketmonster-demo

Now you can log in to the controller and view the ticketmonster app in the app drawer:

Source: habr.com