Using AppDynamics with Red Hat OpenShift v3

In recent times, many organizations want their applications to migrate 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-launch images by inserting the application source into the Docker image and collecting the new Docker image. The new image, including the base image (builder) and the constructed source, is already ready for use with the docker launch command. S2I supports incremental builds that reuse previously loaded dependencies, previously created artifacts, etc.

Process

Complete process for using AppDynamics with RedHat OpenShift

Step 1: RedHat is already provided

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

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

Step 2: Creating the AppDynamics builder image

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

Step 3: Creating 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 -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 =  $ 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 into the controller and see the ticketmonster application in the application panel: