Skip Headers

Oracle® Configuration Manager Installation and Administration Guide Release 10.3.5 Part Number E22050-01 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| PDF · Mobi · ePub

# 1 Introduction to Oracle Configuration Manager

Oracle Configuration Manager is used to personalize the support experience by collecting configuration information and uploading it to the Oracle repository.

When customer configuration data is uploaded on a regular basis, customer support representatives can analyze this data and provide better service to the customers. For example, when a customer logs a service request, he can associate the configuration data directly with that service request. The customer support representative can then view the list of systems associated with the customer and solve problems accordingly.

Some of the benefits of using Oracle Configuration Manager are as follows:

- Reduces time for resolution of support issues

- Provides pro-active problem avoidance

- Improves access to best practices and the Oracle knowledge base

- Improves understanding of customer's business needs and provides consistent responses and services

## 1.1 What's New in Oracle Configuration Manager 10.3.5.0.0

This section lists the new feature in this release.

- Configuring Oracle Configuration Manager in a cloned home

  A new command, deriveCCR, has been added to configure Oracle Configuration Manager in a cloned home.

- Oracle Remote Diagnostic Agent (RDA) now available from content server

  For ease of use, you can now download the Oracle Remote Diagnostic Agent (RDA) from the Oracle Configuration Manager content server. RDA updates are downloaded as part of the Oracle Configuration Manager automatic update.

- In Automatic Storage Management (ASM) 11.2 homes and Exadata Grid Infrastructure 11.2 homes, Oracle Configuration Manager can now be installed and configured by the oracle user as long as the base directory is owned by the root user or the oracle user.

  Previously, the Oracle Configuration Manager installations in Automatic Storage Management (ASM) 11.2 homes and Exadata Grid Infrastructure 11.2 homes ($ORACLE_HOME) were failing because the ORACLE_HOME owner was different from the owner of the $ORACLE_HOME/ccr directory and files. Oracle Configuration Manager required the ORACLE_HOME owner to be the same as the user performing the installation, but the Oracle Universal Installer (OUI) installation changed the base directory owner to the root user, while the $ORACLE_HOME/ccr directory and files continued to be owned by the oracle user.

  In Oracle Configuration Manager release 10.3.5, Oracle Configuration Manager can now be installed and configured by the oracle user as long as the base directory is owned by the root user or the oracle user.

  If Oracle Configuration Manager has not been installed in the ASM home and Exadata Grid Infrastructure home ($ORACLE_HOME), do the following:

  1. Log in as the root user and unzip the Oracle Configuration Manager kit into the ASM home or the Exadata Grid Infrastructure home

  2. Change the owner of the $ORACLE_HOME/ccr directory and its files to the oracle user:

         chown -R oracle:<group> $ORACLE_HOME/ccr
            where <group> is the user group for the oracle user

  3. Log in as the oracle user

  4. Setup Oracle Configuration Manager in the $ORACLE_HOME by executing:

         $ORACLE_HOME/ccr/bin/setupCCR

## 1.2 System Architecture

The Oracle Configuration Manager architecture is displayed in Figure 1-1.

Figure 1-1 Oracle Configuration Manager Architecture

Description of "Figure 1-1 Oracle Configuration Manager Architecture"

Figure 1-1 displays the following:

- Oracle Configuration Manager: This is the Oracle Configuration Manager infrastructure.

- Site 1: Systems that are directly connected to the Internet.

- Site 2: Systems that are connected to the Internet through a proxy server.

- Site 3: Systems that do not have direct access to the Internet but do have access to an Intranet proxy server which in turn has Internet connection through the Support Hub.

- Site 4: Systems that do not have direct access to the Internet but do have access to the Support Hub which in turn is connected to the Internet through a proxy server.

## 1.3 About Connected and Disconnected Modes

Oracle Configuration Manager can be installed in the following modes:

- Connected (Authenticated) Mode

  This mode is recommended if your server has direct connection to the Internet, connection through a proxy server, or connection using Oracle Support Hub. In this mode, configuration data is automatically collected and uploaded to the Oracle server. In addition, updates to Oracle Configuration Manager occur automatically.

- Connected (Unauthenticated) Mode

  This mode, though not recommended, is used when only the e-mail address is specified but no password. Though this mode allows you to register and upload data, you are not able to view or use the data collected in the My Oracle Support interface.

- Disconnected Mode

  This mode is required when your server does not have a connection to the Internet and you cannot configure an Oracle Support Hub. In this mode, you can collect configuration data manually by using the emCCR collect command. When you run this command, the collected configuration data is stored in the <`OCM_CONFIG_HOME>/state/upload/``ocmconfig`.`jar` file. If problems occur, you can then upload this file to Oracle by way of a Service Request and My Oracle Support from another system that has Internet access.

  Refer to Section 6.3, "emCCR collect" for details. In this mode, the only commands supported are: `emCCR collect`, `emCCR status`, `emCCR enable_target`, `emCCR` `disable_target`, `emCCR update_components`, `configCCR`, and `emCCR help`.

You can switch between Connected and Disconnected modes by using the configCCR command. Refer to Section 6.19, "configCCR" for details.

## 1.4 Support for Shared Homes

A shared home is an installation of an Oracle product that can be used and accessed by multiple hosts, or across multiple configurations on a single host. There are shared homes that require special Oracle Configuration Manager setup, and those that do not.

### 1.4.1 Shared Homes That Do Not Require Special Oracle Configuration Manager Setup

Examples of shared homes that do not require special Oracle Configuration Manager setup are:

- When multiple database instances are created on the same host, from a single software installation.

- When a single installation is shared across multiple hosts and each host has one or more database instances. In this case, though Oracle Configuration Manager requires no special setup, the collector must be setup separately on each host.

### 1.4.2 Shared Homes That Do Require Special Oracle Configuration Manager Setup

Some software products allow for the installation of the executables to be placed in a shared directory structure. Each use of the product requires a separate directory to segregate the product's runtime specific information.

An example of this is the Oracle Fusion Middleware installation with its separate directories. Typically the product-specific information collected by Oracle Configuration Manger is found in files in each of these separate directories.

To support this type of shared home, Oracle Configuration Manager treats each separate runtime state directory as an ORACLE_CONFIG_HOME.

If you have a software installation of this type, read Appendix A, "Shared Homes" before deciding whether you absolutely need shared homes.

Typically, most Oracle homes are not shared Oracle homes, therefore special Oracle Configuration Manager setup is not required.

Important:

If you are upgrading from an existing version of Oracle Configuration Manager that is prior to release 10.2.7, you cannot take advantage of the Shared Homes functionality. This functionality is only available with a new installation of Oracle Configuration Manager release 10.2.7 or later.

To use this feature, you must deinstall the current installation of Oracle Configuration Manager and then reinstall Oracle Configuration Manager release 10.2.7 or later.

## 1.5 Oracle Support Hub

The Oracle Support Hub conveys the configuration payload from individual Oracle Configuration Manager instances to the repository maintained at Oracle. The Oracle Support Hub is situated inside the customer network, so that it becomes the only point of access needed between inside the network and the outside Internet.

For the complete description of the Oracle Support Hub, refer to the Oracle Configuration Manager Companion Distribution Guide.

## 1.6 Oracle Harvester

Oracle Harvester (Harvester) collects target configuration data from the Enterprise Manager Grid Control Management Repository (Grid Control Repository) and uploads it to Oracle.

When Oracle Configuration Manager is configured in Grid Control release 10.2.0.5 or higher, it enables the Harvester functionality. The Harvester job runs every 24 hours and collects configuration data from the Management Repository which Oracle Configuration Manager uploads to Oracle as part of its next collection. Some target types for which data is collected include: Oracle Database, Host, Oracle Home, Oracle Virtual Machine, Oracle Real Application Cluster, Oracle Application Server, and Web Logic Server.

If Oracle Configuration Manager is also installed in the actual target home, the data collected by Oracle Configuration Manager in this home overrides data collected by the Harvester from the Grid Control Repository.