Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 2 (12.1.0.2) Part Number E24089-17 |
|
|
PDF · Mobi · ePub |
Before you perform maintenance and advanced configuration tasks, you must be familiar with the directories and files that are copied to disk when you install Enterprise Manager. Understanding where specific files are located can help you if you need to troubleshoot installation or configuration problems.
When installing Enterprise Manager, if you select a location that does not contain WebLogic Server, then JDK will be installed in the jdk16
directory before installation of WebLogic Server.
Use the following sections to become familiar with the directories that are created on your disk when you install Enterprise Manager:
Understanding the Enterprise Manager Directories Installed with Oracle Enterprise Manager Cloud Control 12c
Understanding the Enterprise Manager Directories Installed with an Oracle Management Service
Understanding the Enterprise Manager Directories Installed with Management Agent
When you install Oracle Enterprise Manager Cloud Control 12c, you install the Oracle Management Service. With the Oracle Management Service, you install the following Oracle home directories:
The Oracle Management Service is a J2EE application that is installed and deployed using the Oracle WebLogic Server.
The installation procedure installs the Enterprise Manager components within the Cloud Control Home, including the Oracle Management Service.
Information about the directories that are specific to the Fusion Middleware installation can be found in the Fusion Middleware documentation.
The Oracle Management Service is a J2EE application that is installed and deployed using the Oracle WebLogic Server.
The installation procedure installs the Enterprise Manager components within the Cloud Control Home, including the Oracle Management Service. For more details about the OMS directories, see About the Oracle Management Service Home Directory.
Information about the directories that are specific to the Fusion Middleware installation can be found in the Fusion Middleware documentation.
The Business Intelligence Publisher is a J2EE application that is installed and configured as described in Chapter 14.
Figure A-1 shows some of the important directories you should be familiar with in a typical Cloud Control installation. You can use this information as you begin to maintain, troubleshoot, and configure the Oracle Management Service installation.
Table A-1 Directories Installed with Enterprise Manager
Directory | Description |
---|---|
wlserver_10.3, logs, utils, modules |
These directories contain Fusion Middleware files. |
jdk16 |
This directory contains JDK configuration files. |
oms |
This directory contains OMS configuration files. For more information, see Section 10.2.2. |
plugins |
This directory contains metadata plug-ins configuration files installed on the OMS. |
agent |
This directory contains agent configuration files. For more details, see Section 10.2.3. |
[optional] Oracle_BI1 |
This directory contains the Oracle Business Intelligence Publisher configuration files. |
oracle_WT |
This directory contains Oracle WebTier configuration files. |
oracle_common |
This directory contains common files used by OMS, Oracle WebTier, and WebLogic Server directories. |
Table A-2 describes in detail the Oracle Management Service directories installed with Oracle Management Service. In the table, ORACLE_HOME refers to the Oracle Management Service home directory in which the Oracle Management Service is installed and deployed.
Table A-2 Important Directories in the Management Service Oracle Home
Directory | Description |
---|---|
|
The bin directory in the Management Service home contains commands used to control the components of the Cloud Control installation. |
|
This directory contains configuration files for OMS home. The default |
|
This directory contains WebTier instance Oracle Home corresponding to |
|
This directory contains WebLogic Node Manager properties, logs, and domain information. |
|
This is the OMS instance directory and contains emgc.properties and Enterprise Manager log files. |
|
This directory contains E |
|
This directory contains schema log files. The repository log files are under |
The Oracle Management Agent is installed automatically when you install Oracle Management Service. This local instance of the Oracle Management Agent gathers management information about the targets on the Oracle Management Service host. You can then manage those targets, such as the host itself, from the Cloud Control Console.
You can install additional Oracle Management Agents using different installation methods. This enables you to install the Oracle Management Agent on the hosts throughout your enterprise. The Oracle Management Agent can then gather management data about the targets on each host so those targets can be managed from the Cloud Control Console.
Specifically, the Oracle Management Agent files are installed into the same directory structure shown in the agent directory when you install the Oracle Management Service (Figure A-1).
The agent directory structure, when you install a standalone agent or install the OMS is the same. The AGENT_BASE_DIR is the directory where agent is installed and contains the following main directories:
AGENT_HOME
AGENT_INSTANCE_HOME
SBIN_HOME
PLUGIN_HOME
The directory that contains the files required to run the Oracle Management Agent is referred to as the AGENT_INSTANCE_HOME
directory. For example, to start or stop an Oracle Management Agent, you use the emctl command located in the bin directory of the AGENT_INSTANCE_HOME.
Similarly, to configure files for the Oracle Management Agent, you modify the configuration files in the sysman/config
directory of the AGENT_INSTANCE_HOME.
See Figure A-2 for the agent directory structure.
Table A-3 describes some of the important agent directories.
Table A-3 Important Directories in Oracle Management Agent Home
Directory | Description |
---|---|
|
The The default This directory serves as the Oracle Home for the Oracle Management Agent. |
|
This directory contains binaries for the Oracle Management Agent. |
|
This directory contains installation-related files for deploying the agent. |
|
This directory contains prerequisite files for EMPrereqKit. |
|
This directory contains files related to the installer framework. |
|
This directory contains agent deployment and configuration log files. |
|
This directory is used by the provisioning framework for provisioning activities. |
|
This directory contains the files used by the Oracle Management Agent to define agent core target types (such as databases, hosts, and so on), to run configuration scripts, and other administrative tasks. |
|
The The default |
|
The You use the following emctl commands in this directory to start and stop the Oracle Management Agent on this host:
|
|
This directory contains the configuration files for the Oracle Management Agent. For example, this is where Enterprise Manager stores the |
|
This directory contains the log files for the Oracle Management Agent. |
|
The emd directory contains information about targets discovered on hosts. |
|
This directory contains set UIDs for the agent. The default location is |
|
This directory contains all the discovery and monitoring plugins required for the agent. The default location is |
When you install Cloud Control, the resulting directory structure can often include multiple subdirectories with the same name. For example, you can have a bin directory within the agent_instance_home directory. Use the emctl
command within the agent_instance_home/bin
directory to control the Oracle Management Agent.
In addition, you can have a bin directory within the Oracle Management Service Oracle home. Use the emctl
command in this directory to control the Oracle Management Service.
To quickly identify the Agent Instance home that is controlled by the files in a particular bin directory, use the following command:
$PROMPT> emctl getemhome
This command displays the path to the current Agent Instance home that will be affected by commands executed by this instance of the emctl
command.