Skip Headers
Oracle® Enterprise Manager Getting Started with Oracle Fusion Middleware Management
11g Release 1 (

Part Number E17558-05
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

A Configuration Directories and Files

This appendix lists and defines the files and directories available in ADP. Topics include:

Configuration Directories

After ADP is installed all the components of the application package are located in $CAMM_HOME directory.

Directory Structure

The following is the $CAMM_HOME directory structure once ADP is installed:

-darchive (created when manager first discovers monitored application servers)
-uninstall Oracle Composite Application Monitor and Modeler

Table A-1 Directories in $CAMM_HOME Directory

Directory Description


Tomcat server where ADP Web Application (GUI) is located. By default, Apache Tomcat is disabled.


Contains all the executable files to start and stop ADP, run deployer for Agent and ADP EJB, run export utility.


Contains all the ADP runtime configuration parameters that control execution logic, ADP schemas enablement, ADP GUI functionality, Service Level Objectives definition, export logic and many more.


Stores temporary images for Java EE applications that need to be monitored as well as the results of analysis and modeling of the Java EE application. This directory is created once ADP is up and running.


Contains agent libraries and configuration files, as well as ADP EJB and ADP Admin Web Application. These components are deployed on the remote host (Web or Application servers) using deployer utility found in bin directory of ADP package.


Contains minimum Java SDK sufficient to run ADP Server.


Has all the libraries required for ADP's proper functionality


Has all the diagnostics records of ADP performance metrics collection activities. Also logs indicating successful deployment of ADP Agents can be found here. This directory is created once ADP is up and running.


Contains internal base instrumentation configuration. Do not modify these files.


Contains all the metadata definitions used for ADP's needs.

Uninstall CAMM

Contains utility used to uninstall the ADP.


Contains saved custom views per user.

Config Directory

Config directory has many files that potentially can be configured and make ADP to run in a particular way. Any changes applied to files in this directory require restarting ADP server.

Most of the files never get touched directly by user. The following are the main three files which can be configured manually to achieve desired effect:

File Description This file is the main ADP configuration file customization of which helps to tune up ADP.
configuration.xml In this file you define location of Administration Server and credentials to access it. Usually you do not touch this file. The entire configuration is done through ADP GUI.
dbconfig.xml This file contains database configuration information for the ADP metric repository.
export.xml This file contains information that drives proper data export logic. It is used for manual and automatic export of performance metric and events data from the ADP Data Repository. This file is used to map server addresses to load balancer addresses. By default, this file is not available; it must be created by the user.

It is worth mentioning that Service Level Objective definitions and Actions associated with the SLOs are described in slo.xml and event.xml respectively. The content of these files is completely controlled by definitions applied from ADP GUI (configuration tab).

BIN Directory

The /bin directory has all the executable files to start and stop ADP, run deployer for Agent and ADP EJB, run export utility.

There are two main reasons why one would need to customize the content of the files in this directory:

  • To change the pointers to the location of Java Runtime Environment and ADP installation directory (ACSERA_HOME)

  • To configure ADP Server JVM parameters, e.g. memory.

Only the files that are frequently customized will be described in this chapter.

All the files in this directory should have these lines, pointing to the ADP Installation location:


For Windows: set ACSERA_HOME=C:\oracle\em11g\

In addition, should have a pointer to the JDK used by ADP:

  • For UNIX: JAVA_HOME=/home/oracle/em11g/j2sdk;export JAVA_HOME

  • For Windows: set JAVA_HOME=C:\oracle\em11g\j2sdk

ADP is a Java application and runs in its own JVM. Default size of JVM memory is 1024 MB. Should you want to change this value you can do so by modifying -Xms and -Xmx parameters in (.bat) file.

Bear in mind that if you have installed ADP as a Windows service and need to change the JVM Memory size, you need to change the size either by updating the Windows Registry or rerunning the createmanagerservice.bat utility with the new JVM parameters.

Deploy Directory

The /deploy directory contains the ADP Java Agent distributable, including configuration files as well as corresponding libraries. These files are copied to the target systems hosting the Managed Servers when running the deployer utility. Rarely one needs to modify configuration files in this directory. Remember though if you modify the files they will be distributed to ALL targets within single server/cluster.

apache-tomcat-5.5.20 Directory

The /apache-tomcat-5.5.20 directory has the same structure and content as the standard Tomcat distributable. One interesting point about it is that ADP GUI application acseraadimn.war is residing in em11g/apache-tomcat-5.5.20/webapps directory. File

The file contains global configuration parameters that define the operation of the ADP Manager.

Log Files Management

This section of file defines log rotation policies. Log.MaxFiles indicates max number of log files available at any given moment, whereas the Log.MaxFileSizeMB indicates maximum size of the log file.

Example A-1 Log Files Management Section

Log.CopyOut = false
Log.MaxFiles = 10
Log.MaxFileSizeMB = 30
Log.MergeLogs = true
Debug.CopyOut = false
Debug.LogLevel = all
Debug.MaxFiles = 10
Debug.MaxFileSizeMB = 30

Log files are stored in the log directory.

Multi-Domain Monitoring Configuration

One can limit number of domains to be monitored by setting resource limit parameter: ConfigurationManager.ResourceLimit=4

Example A-2 Multi-Domain Monitoring Configuration


The default is 2, this means that by default ADP is set to monitor no more than two Application Server domains.

ADP RMI Port Assignment

ADP uses RMI ports for communication with the agents and collects incoming performance metrics from a particular RMI port. By default, the RMI port is set on the same machine that hosts ADP. RMI.Registry.Host needs to be un-commented and have a value other than localhost if the host is multi-homed (such as, many network interfaces or has any ipv6 addresses) and you need to make sure that ADP listens to the incoming traffic on the particular interface.

You may need to change RMI.Registry.Port value in case the default 51099 port number has been allocated to an other application. Also if ADP is running in multi-instance mode, the port number will be different from instance to instance.

Example A-3 ADP RMI Port Assignment

#RMI.Registry.Host = localhost
RMI.Registry.Port = 51099

ADP Aggregation and Data Life Time Configuration

ADP has sophisticated multi-tiered logic for aggregation (or compression) of performance data. This helps to optimize performance of interaction with the internal data repository both when querying data for presentation or inserting new performance metrics.

Users who want to store longer term data should look for this section in

# Production setting
# NOTE: use Model.GlobalSamplingRateSecs to configure Metric.Grain.0
Metric.Grain.0 0s
Metric.TableInterval.0 = 4h
Metric.DataLife.0 = 8d

Metric.Grain.1 = 3m
Metric.TableInterval.1 =1d
Metric.DataLife.1 = 8d

#Metric.Grain.2 = 30m
#Metric.TableInterval.2 = 7d
#Metric.DataLife.2 = 420d

and uncomment the last 3 lines for the Metric.*.2 properties

Aggregating Incoming Metrics On the Fly

ADP by default aggregates data coming from multiple cluster members by application thus minimizing rate of insertion in to the data repository. This greatly improves performance of ADP in heavily loaded environments.

As a side effect of this approach though, the user is unable to see metrics from instrumentation (processes and portals) on per server level. If you need to enable this then set the JavaMIP.AggregateInserts to false.

Configuring List of Applications To Be Monitored or Excluded From Monitoring

To avoid overhead of unnecessary monitoring of certain applications, you can explicitly state which applications to monitor, or which applications to exclude from monitoring.

Users should append the name of their application to the property ComponentProvider.Application.Exclude.

Example A-4 Specifying Which Applications to Monitor

# Control which applications to analyze
ComponentProvider.Application.Exclude=WLI System EJBs,WLI-AI 

Firewall Mitigation (for Internal RMI Ports)

If there is a firewall between the ADP Manager and the monitored application servers, ports need to be opened between them especially in the case where multiple resources are configured. For example, if two resources are configured and the first one uses 55006 as the port, then the next resource must use 55007 as the port. Each additional resource increments the port by 1.

In addition to the application server's JMX access ports, the following two properties in indicate the ports used specifically by ADP:

  • RMI.Registry.Port (51099 by default)

  • RMI.JavaProvider.ServerPort (55003 by default)

SLO Dampening

There are times when you deliberately want to cut down on the number of repeated notifications should SLO violation persist for a given period of time. To suppress notifications of the same violation in a short period of time, ADP provides the SLO Dampening feature. Once enabled, should a SLO violation occur and be repeated several times in a short period, ADP will not fire the SLO violation notification for the time period defined in SLO.RearmDelay. To disable this feature, set the value of this parameter to 0.

SLO.SuppressDelayedAsserts indicates that if the violation still persists upon time period expiry ADP, should fire the SLO notification. By default it is false, for example, fire the notification.

Example A-5 SLO Dampening

# The following property is specified in units of
# minutes (m), hours (h) or days (d)
SLO.RearmDelay = 15m
SLO.SuppressDelayedAsserts = false

The file should be created in the ADP Manager's config directory and used to provide address mappings between load balancers and application servers. The format of this file is:

# Format:
#    $app_server_ip = $load_balancer_id
# E.g:
#    http\://localhost\:7001 = http\://localhost\:7005
# Note: ":" character need to be escaped with "\"
http\://\:7002 = http\://\:80
http\://\:7003 = http\://\:80
http\://\:7005 = http\://\:7011
http\://\:7006 = http\://\:7011