JADE / AD4J – Application Diagnostics for Java : Architecture / Installation and Configuration
AD4J – Application Diagnostics for Java
JADE – Java Application Diagnostics Expert
Application Diagnostics for Java (AD4J aka JADE – Java Application Diagnostics Expert) is lightweight application to diagnose performance issues in Java Applications (including Database Tier)
.
AD4J Architecture
1. AD4J Console : is web based console to setup/monitor performance of Java Virtual Machine (JVM) including Database.
AD4J Console listen on two ports
a) 3500 (80 for Windows) for requests from end user/Administrator
b) 3600 for requests from Agents (JVM Agent & DB Agent)
.
2. AD4J Repository : is database (Oracle or Postgres) to store JVM state. Postgres is default database for Console on windows
3. Agents : two type of Agents AD4J JVM Agent and AD4J DB Agent which collects JVM or Database state and pass on to Console to store it in Repository.
You need to install/configure 1 JVM agent per JVM and 1 DB Agent per Database.
.
Things good to know about AD4J
1. Default HTTP port for client requests is 3500 (Unix) or 80 (windows)
2. Default console login credentials is admin/welcome
3. Default repository database with windows is Postgres
4. AD4j Console is available on both Windows and Unix platform
5. For Solaris use bash or ksh shell while running configure.sh
.
Install Application Diagnostics for Java (AD4J)
1. Download and unzip software (jamserv-<os>.zip) from here
2. Configure AD4J by running configure.sh (Unix) or by double click on jamserv-win.exe (windows)
configure.sh $JDK_LOCATION
3. Start console by running jamserv/bin/apachectl start (jamserv is directory created after unzipping jamserv-<os>.zip) – This step is NOT required on windows.
If you can’t access console page as given in point 4 below then start Jserv using jamserv/bin/jservctl start
For steps on installing AD4J Console on Unix click here
For steps on installing AD4J Console on Windows click here
4. Access console and configure repository for AD4J console – This step is NOT required on windows
Access console using URL http://[servername]:3500 (Unix) orhttp://[servername] (Windows)
Setup -> click on link adminDB.properties
I created repository database user jamuser in database FUSION
SQL> create user jamuser identified by jamuser;
SQL> grant connect, resource to jamuser;
.
5. Download Agents for JVM & Database
a)Download JVM agents (available as war, ear or zip) for JVM’s you are planning to monitor Setup -> Download Agent
b) Download Database agents (specific to O.S. of your database) for Database you are planning to monitor Setup -> Download Agent
.
6. Install JVM Agents –
Use Application Server specific steps to deploy Agent on JVM you wish to monitor check here
7. Install Database Agents using Setup -> Database -> Register New DB ; more information here
Now you are ready to monitor your Database and Application Server (JVM – Java Virtual Machine)
Next step – Run load tests using software like LoadRunner against your Key transactions and analyze
a) JVM Activity – CPU, OSR, Locks, Threads, DB wait time , Heap Usage, Garbage Collection….
b) Database Activity – Locks, top SQL, I/O wait …..
.
Refarences