{"id":1339,"date":"2009-09-19T06:26:25","date_gmt":"2009-09-19T10:26:25","guid":{"rendered":"http:\/\/onlineappsdba.com\/index.php\/2009\/09\/19\/jade-ad4j-application-diagnostics-for-java-architecture-installation-and-configuration\/"},"modified":"2009-09-21T10:38:21","modified_gmt":"2009-09-21T14:38:21","slug":"jade-ad4j-application-diagnostics-for-java-architecture-installation-and-configuration","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2009\/09\/19\/jade-ad4j-application-diagnostics-for-java-architecture-installation-and-configuration\/","title":{"rendered":"JADE \/ AD4J – Application Diagnostics for Java : Architecture \/ Installation and Configuration"},"content":{"rendered":"

<\/a><\/p>\n

AD4J<\/strong> – Application Diagnostics for Java
\nJADE<\/strong> – Java Application Diagnostics Expert<\/p>\n

Application Diagnostics for Java (AD4J aka JADE – Java Application Diagnostics Expert) is lightweight application to diagnose performance issues in Java Applications (including Database Tier)<\/p>\n

.<\/p>\n

AD4J Architecture<\/strong><\/u><\/p>\n

1. AD4J Console<\/strong> : is web based console to setup\/monitor performance of Java Virtual Machine (JVM) including Database.<\/p>\n

AD4J Console listen on two ports
\na)<\/strong> 3500 (80 for Windows) for requests from end user\/Administrator
\nb)<\/strong> 3600 for requests from Agents (JVM Agent & DB Agent)
\n
<\/p>\n

\"ad4j<\/a><\/p>\n

.<\/p>\n

2. AD4J Repository<\/strong> : <\/strong>is database (Oracle or Postgres) to store JVM state.\u00a0 Postgres is default database for Console on windows<\/p>\n

3. Agents<\/strong> : two type of Agents AD4J JVM Agent<\/strong> and AD4J DB Agent<\/strong> which collects JVM or Database state and pass on to Console to store it in Repository.
\nYou need to install\/configure 1 JVM agent<\/strong> per JVM and 1 DB Agent<\/strong> per Database.<\/p>\n

.<\/p>\n

Things good to know about AD4J<\/strong><\/u><\/p>\n

1.<\/strong> Default HTTP port for client requests is 3500 (Unix) or 80 (windows)
\n2. <\/strong>Default console login credentials is admin\/welcome<\/strong>
\n3.<\/strong> Default repository database with windows is Postgres
\n4. <\/strong>AD4j Console is available on both Windows<\/strong>\u00a0and Unix<\/strong> platform
\n5.<\/strong> For\u00a0Solaris<\/strong> use bash<\/strong> or ksh<\/strong> shell while running configure.sh
\n<\/strong><\/p>\n

.<\/p>\n

Install Application Diagnostics for Java (AD4J)<\/strong><\/u><\/p>\n

1.<\/strong>\u00a0Download and unzip software (jamserv-<os>.zip) from here<\/a><\/p>\n

2.<\/strong> Configure AD4J\u00a0 by running configure.sh<\/strong> (Unix) or by double click on jamserv-win.exe<\/strong> (windows)<\/p>\n

configure.sh $JDK_LOCATION\u00a0 <\/strong><\/p>\n

3. <\/strong>Start console by running jamserv\/bin\/apachectl start\u00a0 <\/strong>(jamserv <\/strong>is directory created after unzipping jamserv-<os>.zip) – This step is\u00a0NOT required on windows<\/font>.<\/p>\n

If you can’t access console page as given in point 4 below then start Jserv using jamserv\/bin\/jservctl start <\/strong><\/font><\/p>\n

For steps on installing AD4J Console on\u00a0Unix click here<\/a>\u00a0
\n<\/font>For steps on installing AD4J Console on\u00a0Windows click here<\/a>\u00a0<\/font><\/p>\n

4.<\/strong> Access console and configure repository for AD4J console<\/strong> – This step is\u00a0NOT required on windows<\/font><\/p>\n

Access console using URL http:\/\/[servername]:3500<\/strong>\u00a0(Unix)\u00a0 orhttp:\/\/[servername]<\/strong> (Windows)<\/p>\n

Setup<\/strong> -> click on link adminDB.properties<\/strong><\/p>\n

I created repository database user jamuser<\/strong>\u00a0in database FUSION<\/strong><\/p>\n

SQL> create user jamuser identified by jamuser;
\nSQL> grant connect, resource to jamuser;<\/strong><\/p>\n

<\/a><\/p>\n

<\/a><\/p>\n

<\/a><\/p>\n

<\/a><\/p>\n

.<\/p>\n

5. <\/strong>Download Agents for JVM & Database<\/p>\n

a)<\/strong>Download JVM agents (available as war, ear or zip) for JVM’s you are planning to monitor\u00a0 Setup -> Download Agent<\/strong><\/p>\n

b) <\/strong>Download Database agents (specific to O.S. of your database) <\/strong>for\u00a0Database you are planning to monitor\u00a0 Setup -> Download Agent<\/strong><\/p>\n

<\/a><\/p>\n

.<\/p>\n

\u00a06.<\/strong> Install JVM Agents –
\nUse Application Server specific steps to deploy Agent on JVM you wish to monitor check here<\/a><\/p>\n

7.<\/strong> Install Database Agents using Setup<\/strong> -> Database<\/strong> -> Register New DB<\/strong> ;\u00a0\u00a0more information \u00a0here<\/a><\/p>\n

Now you are ready to monitor your Database<\/strong> and Application Server<\/strong> (JVM – Java Virtual Machine)<\/p>\n

Next step <\/strong>– Run load tests using software like <\/font>LoadRunner<\/font><\/a>\u00a0against your Key transactions and analyze <\/font><\/p>\n

a) JVM Activity<\/strong> – CPU, OSR, Locks, Threads, DB wait time , Heap Usage, Garbage Collection….
\nb) Database Activity<\/strong> – Locks, top SQL, I\/O wait …..<\/font><\/p>\n

.<\/font><\/p>\n

Refarences<\/u><\/strong><\/p>\n