AppDynamics Installation Guide
Activating AppDynamics for Openbravo
AppDynamics for Openbravo is activated by Openbravo Support team. Once this process is done, you will receive:
- Access to install AppDynamics for Openbravo module with your license.
- AppDynamics controller details, which includes:
- Controller URL
- Credentials to operate the controller
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.
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.
To apply this configuration:
ob-appdynamics-config.xmlfile from AppDynamics for Openbravo module sources directory. It is in:
- Go to AppDynamics controller. URL and credentials are provided during the activation process.
- From home page click on View All Applications in Applications widget.
- Click on Import Application icon in the toolbar.
- In the dialog:
- Select downloaded file.
- Select a name for the Application. (see note below)
- Click Import button. This process can take several minutes.
- In Openbravo server create
/opt/AppDynamicsdirectory (this might require root privileges, if so, change owner to
openbravouser after creation:
chown openbravo:openbravo /opt/AppDynamics).
openbravouser, copy the contents of
cp -r [Openbravo-Source-Path]/modules/org.openbravo.utility.monitoring.appdynamics/AppDynamics/* /opt/AppDynamics
/opt/AppDynamics/AppAgent/conf/controller-info.xmlfile to change the following properties:
application-name: it will identify the Openbravo instance in AppDynamics. This name must exactly match in AppAgent, MachineAgent and AppDymics controller
account-access-key: these settings are provided when activating AppDynamics account.
controller-host: Provided in the activation process
/opt/AppDynamics/MachineAgent/conf/controller-info.xmlfile. Same settings as described in above should be set. They must have the exact same values
/etc/profile.d/tomcat.shfile (this might require root privileges) to add these lines at the bottom:
# AppDynamics support export CATALINA_OPTS="$CATALINA_OPTS -javaagent:/opt/AppDynamics/AppAgent/javaagent.jar"
- Grant execution permission to machine agent daemon:
chmod +x /opt/AppDynamics/MachineAgent/appdynamics
- Create a symlink to appdynamics machine agent script (this step requires root privileges):
ln -s /opt/AppDynamics/MachineAgent/appdynamics/etc/init.d/appdynamics
- Restart Tomcat: /etc/init.d/tomcat restart
openbravo.logto ensure it started correctly
- Execute Machine Agent:
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.
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
- If proxy requires password create a new text file in ie.
/opt/AppDynamics/MachineAgent/conf/proxy-credentials.txtwith a single line with the password.
- Edit the line for
EXTRA_JAVA_PARAMSto make it look like: EXTRA_JAVA_PARAMS="-Dappdynamics.http.proxyHost=192.168.100.1 -Dappdynamics.http.proxyPort=8080 -Dappdynamics.http.proxyUser=proxyUserName -Dappdynamics.http.proxyPasswordFile=$APPDYN/MachineAgent/conf/proxy-credentials.txt"</code>. Note bold parameter values should be replaced with your actual proxy settings.
- Edit the line for
/etc/profile.d/tomcat.shto add the following properties to
-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.