1 Oracle AD4J Console Administration Guide

Oracle AD4J Console Setup

If you have followed the default installation, then the console should be accessible from the URL

http://myconsole.mycompany.com:3500

Where myconsole.mycompany.com is the name of the server you have installed the console on.You can also access the console using the IP address zzz.zzz.zzz.zzz for the server.

http://zzz.zzz.zzz.zzz:3500

Assumptions

This guide assumes that you have installed and configured your console with a valid repository. It further assumes that you have set up the DB and agents and they are able to communicate with the console. Also, the console is setup and running and some Oracle AD4J Agents are connected to it.

For details on how to set up the console and agents, refer to Oracle AD4J Installation Notes.

JVM Console Diagnostics

When you first access the console, it will take you to the Admin tab and run Diagnostics. Here, you can see the information about the configuration of the console and the errors (if any). For example, if a database connection cannot be established for some reason, it would show up here along with some debug information.

Figure 1-1 JVM Console Diagnostics

Console Login Screen

You are taken to the Login screen if you want to modify any admin information on the Oracle AD4J console. Login with the administrator password to continue.

Figure 1-2 Console Login Screen

You get the following screen if you try logging in again before timeout.

Figure 1-3 Login Screen Before Timeout

DB Connection Information

The adminDB.properties file stores connection information about the repository database. The file resides in the location specified by the start up parameter jampropfilepath.

Click on the adminDB.properties link to create the file :

Figure 1-4 DB Connection Information

Enter the fields with a valid DB Connection Information. Refer to the Oracle AD4J Console Install Note for details.

Repository DB Page

From this page you can create and/or view the tables and indexes in the database that are being used by the Oracle AD4J console.

Figure 1-5 Repository DB Page

Console Setup Page

This page is used to set console parameters and reset lost passwords.

Figure 1-6 Console Setup Page

Console Log Level, Cross Tier Log Level: Verbosity of console log messages. Increase only when advised by Oracle Support.

Agent Request Timeout, Agent Loop Request Timeout: Increase if the monitored JVMs are extremely busy and the console times out and disconnects waiting for their response.

Require login for Java tab: Enable this checkbox to restrict access to other (non-setup Tabs). Users's will need to login with valid accounts (created from the Users screen) and will have access to all non-setup screens. The setup screens can only be accessed by the ADMIN user.

Enable Monitoring: With this checkbox enabled, JVMs belonging to selected pools will be polled for active requests periodically. This data is available on the NOC and in the last 90 seconds/24 hrs charts.

Email Alerts: Email alerts based upon threshold violations (requires monitoring to be enabled).

Email Prefix for UserName, SMTP Mail Host, Send Mail As: Parameters used for emailing alerts.

SNMP Alerts: Send SNMP traps for threshold violations (requires monitoring to be enabled).

SNMP Host for Alerts: SNMP Host to send alerts to.

Reset Password Screen can be used to reset lost passwords and does not require old password.

JVM Pool Info

You can use this page to list the available JVM Pools, delete existing pools or add new pools. Default and other pools cannot be deleted. Any user defined pools can be deleted.

Figure 1-7 Available JVM Pools

Updating a JVM Pool

Figure 1-8 Updating a JVM Pool

Poll interval (ms): Sample interval for JVMs belonging to this pool when monitoring (Poll) is enabled.

Poll Enabled: Enable monitoring for this pool.

Email Alerts to: Email Alias/list to email this pool's alerts to.

Update Pool Thresholds

Threshold violations are defined as the baseval being exceeded for the TriggerSamples % of samples. Baseval units are % CPU Utilization for Machine CPU (CPU), JVM CPU (CPU), % Heap Utilization for Heap, number of threads in that state for others.

So, 3-5 threads active in DB for more than 50% of the samples will cause an amber (Y) alert for DB, while 6+ threads active in DB wait state for more than 50% of the samples will cause a red alert for DB.

Figure 1-9 Update Pool Thresholds

Database Information

Use this screen to view information about the databases being monitored/profiled currently or to add additional databases for the same.

Figure 1-10 Database Information

Register New Database/Update Screen

Figure 1-11 Register New Database Screen

Registered DB Name: Provide a user friendly name for Oracle AD4J to display.

DB Hostname: Database server for this monitored instance.

Actual DB Name: Actual Oracle SID for the monitored DB.

DB Port: Oracle Net Listener Port on the DB Server.

DB User: DB User to use for querying database information.

Password: (only in update/new mode) : The password for the DB User.

DB User (Explain Plan): Application DB User account to use for explain plan analysis.

DB OS User: Operating System User which owns the database.

JVM Information Page

Figure 1-12 JVM Registered for Monitoring/Profiling

Lists all the JVMs that have connected to the console. You can edit the JVM parameters using the edit icon, or delete old JVMs that no longer connect to the console.

Figure 1-13 Editing JVM Information

You can assign a JVM to a different pool, change it's log level (if recommended by Support) or change the temporary directory where the heap snapshots are dumped.

Monitoring

Once you have updated a JVM pool with polling enabled, you can monitor the JVMs in that pool.

Figure 1-14 Monitoring

Click on the Start Monitoring link above to start monitoring. This can also be done from the Console Setup Screen.

Manage Trace Files

Use this screen to:

• delete trace files from the traces you have run.

• Load a trace file into the database so it can be seen from the Trace tab (this happens automatically when you run a trace).

• Load a trace file from another console. You'll need to move the trace file(s) to the jamserv/trace directory for them to visible in this screen.

Figure 1-15 Manage Trace Files

Manage Users

From this screen, you can create non-admin user accounts for accessing the Oracle AD4J console.

Figure 1-16 Manage Users

Download Agent

Use this screen to download agent with console parameters for deploying on a remote monitored JVM.

Figure 1-17 Download Agent