View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

AppDynamics Installation Guide

Contents

Activating AppDynamics for Openbravo

AppDynamics for Openbravo is activated by Openbravo Support team. Once this process is done, you will receive:

Installation

AppDynamics consists of two agents (Application and Machine) and a controller (UI to visualize performance data). Agents are in charge of collecting information about the Openbravo instance and sending it to the controller.

Controller and agent are configured separately. Controller is configured from AppDynamics UI whereas agents must be configured in Openbravo server.


Installing the Module

AppDynamics for Openbravo module is a convenience module which contains the two controllers and the configuration files they require as well the pre packaged application to be applied in the controller. Note it requires of extra configuration, by itself it is not able to send data to AppDynamics controller.

This can be installed as a regular Openbravo module.


Controller

AppDynamics Controller configuration is done from AppDynamics UI.

Openbravo provides a packaged default configuration that makes easier to configure AppDynamics to work with Openbravo by defining some standard Business transaction, data collectors, error detection, etc.

Warn-icon.png   Important Note: packaged configuration can be applied just once per application (Openbravo instance) at creation time. If this is not done at this stage, all configuration needs to be manually done. It is important to execute this step before Openbravo Server is configured to send data to AppDynamics controller.


To apply this configuration:

Appdyn-view-all-apps.png
Appdyn-import-app-button.png
Appdyn-import-app-dialog.png


Warn-icon.png   Important Note: Application Name will be used to identify the application (Openbravo instance) in the AppDynamics controller. It cannot be changed in future and it must exactly match (including upper/lower case) with the settings configured in Openbravo Server.

Openbravo Server

# AppDynamics support
export CATALINA_OPTS="$CATALINA_OPTS -javaagent:/opt/AppDynamics/AppAgent/javaagent.jar"
Bulbgraph.png   Configuring machine agent to run on system boot: run as root the following command update-rc.d appdynamics defaults, which will create the needed symlinks to integrate the script into the boot process.

After few minutes you should start seeing data in AppDynamics controller.

To check if machine agent is running, /etc/init.d/appdynamics status can be executed.

Note that machine agent is not started by default, after subsequent machine restarts command /etc/init.d/appdynamics start should be executed. To add this command to startup process not to have to execute it manually read following note.

Bulbgraph.png   Configuring machine agent to run on system boot: run as root the following command update-rc.d appdynamics defaults, which will create the needed symlinks to integrate the script into the boot process.
Bulbgraph.png   Important Note: These steps can be done first in a testing environment to ensure everything works as expected.

If done in this way, it is important to do following steps before rolling it up to production environment:

  • Rollback changes in /etc/profile.d/tomcat.sh file
  • Restart (or stop) tomcat
  • Stop Machine Agent: /etc/init.d/appdynamics stop


Working with clones

When a clone of production instance is done, it is important to ensure before Tomcat is started configuration in /etc/profile.d/tomcat.sh does not include javaagent line in order to prevent sending data from this clone. Also the machine agent is not active.

If data for different clones is desired to be collected by AppDynamics each of them needs to be configured with a different application name.


Working with proxies

When the openbravo server connects Internet via proxy

-Dappdynamics.http.proxyHost=192.168.100.1 \
-Dappdynamics.http.proxyPort=8080 \
-Dappdynamics.http.proxyUser=proxyUserName \
-Dappdynamics.http.proxyPasswordFile=/opt/AppDynamics/MachineAgent/conf/proxy-credentials.txt"

Checking Agents Status

From controller, it is possible to check the status of the two agents.


From left menu, Servers > AppServers in AppServers>Health tab. Information about the uptime can be seen.

Agents-status.png

Retrieved from "http://wiki.openbravo.com/wiki/AppDynamics_Installation_Guide"

This page has been accessed 4,602 times. This page was last modified on 8 April 2015, at 11:42. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.