A
Directory Structure

This appendix describes important directories and files that are created upon the installation of Oracle Enterprise Manager.

Useful Directories

While there are numerous directories created upon installation of Enterprise Manager and its components, the most important and useful directories for you to be aware of include the following:

$ORACLE_HOME/sysman/

This directory will be described in detail below.

$ORACLE_HOME/relnotes/em/

Contains any readme files specific to Enterprise Manager and its management applications. Such readme files identify differences between the delivered Oracle Enterprise Manager product and its documented functionality.

$ORACLE_HOME/doc/em/

Contains any documentation (selected for installation from the Documentation CD-ROM) specific to Enterprise Manager and its management applications. By default, this directory also includes the complete diagnostics help system in HTML format for use as a guide to Oracle performance metrics.

$ORACLE_HOME/oem_webstage/

Contains the Enterprise Manager web site component. By default, the web site is installed with the Management Server in this directory. The component enables you to run Enterprise Manager and its management applications from a web browser.

$ORACLE_HOME/sysman/ Directory

The $ORACLE_HOME/sysman/ directory contains several subdirectories with which you should be familiar:

• admin
• config
• expert
• ifiles
• jlib
• log
• mesg
• report
• reporting
• temp

admin/

Contains SQL scripts and registry files that are used by the Enterprise Manager Configuration Assistant to perform configuration of the Management Server and repository. The contents of this directory must not be altered.

config/

Contains several configuration files for Enterprise Manager components. Only the following files contained in this directory can be modified:

• dbappscfg.properties

  Contains configuration settings specific to SQL*Plus Worksheet.

• ClientConfig.properties

  Contains a list of machines that run Management Servers. This file also lets you enable tracing of the Enterprise Manager Console and management applications.

• clientconfig.properties.template

  Contains configuration details for enabling tracing of Change Manager.

• omsconfig.properties

  Contains configuration details of the local Management Server including database repository connection information. This file also lets you enable tracing and logging of the middle tier Management Server.

• omsexternalregistry.registry.template

  Lets you add an External Service registry file. This file currently contains the External Service registry settings for Management Server integration with Oracle Internet Directory Server. You must copy this file to omsexternalregistry.registry and restart the Management Server if you wish the Management Server to connect to a Directory Server. Oracle Internet Directory requires a Management Server External Service as it uses native libraries in your Oracle Home.

• paging.cfg.template

  Lets you enable tracing of the Enterprise Manager Paging Server. This file is generated only when the Paging Server has been installed on a Windows NT or Windows 2000 machine. The Paging Server is not available on any other platform.

Any other files located in the $ORACLE_HOME/sysman/config/ directory must not be altered. For example, oemclient.properties contains information about all event tests and job tasks as well as details for starting applications in context. It must not be altered.

expert/

The expert directory is NT-specific. It contains the expert rule files. You must not edit any file located in this directory.

ifiles/

Contains saved init.ora parameters from Instance Management. Initially, this directory is empty but after accessing Instance Management to save init.ora parameters, it will become populated with files.

jlib/

Contains needed jar files for Enterprise Manager components to function properly. The contents of this directory must not be altered.

log/

Contains tracing information that has been redirected to log files. Initially, this directory is empty; the directory is populated with the oms.nohup file. The oms.nohup file contains information corresponding to when the Management Server is started and stopped (and if the Management Server restarts itself for any reason). Any critical error messages (for example, running out of sessions, SQL exceptions, etc.) would also be logged to this file. Any other tracing information would be directed to the oms.log files if tracing and logging is enabled for the Management Server.

Once tracing and logging are enabled, this directory would be populated with additional log files (e.g. oms.log).

mesg/

Contains message files specific to Enterprise Manager applications that have not been written in Java, including Trace Data Viewer, Oracle Expert, and SQL Analyze. This directory is created only on Windows-based platforms, not on UNIX based platforms. The contents of this directory must not be altered.

report/

Contains HTML formatted reports generated from Enterprise Manager Console and various management applications. Initially, this directory is empty but after generating a report from Enterprise Manager, it will become populated with HTML files. The contents of this directory should not be altered.

reporting/

Contains GIF files for generated HTML reports. The contents of this directory should not be altered.

temp/

This is a scratch directory used by the Management Server, as well as Enterprise Manager applications that have not been written in Java (e.g Trace Data Viewer, Oracle Expert and SQL Analyze), for creating temporary files. The contents of this directory should not be altered.