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

# 4 Advanced Deployment Tasks

This chapter describes the different ways in which Oracle Configuration Manager can be deployed.

## 4.1 Mass Deployment of Oracle Configuration Manager

Oracle Configuration Manager can be deployed into every `<ocm_install_root>` that must be monitored. In a large enterprise, this may require hundreds or thousands of installations. To facilitate ease of deployment, the Oracle Configuration Manager distribution file should be present in a central location. The different options that can be used to deploy Oracle Configuration Manager are as follows:

- Section 4.1.1, "Mass Deployment Utility"

- Section 4.1.2, "Network File System"

- Section 4.1.3, "Secure Copy (SCP) and Secure Shell (SSH)"

- Section 4.1.4, "Oracle Enterprise Manager Grid Control"

### 4.1.1 Mass Deployment Utility

The Oracle Configuration Mass Deployment Utility provides a mechanism by which you can distribute Oracle Configuration Manager to any Oracle home where the Oracle Configuration Manager is not installed, or installed but not configured.

The Mass Deployment utility also updates existing homes where Oracle Configuration Manager installations are out of date, reconfigures existing installations, and instruments the database located in that Oracle home.

For the complete description of the Mass Deployment utility, refer to the Oracle Configuration Manager Companion Distribution Guide.

### 4.1.2 Network File System

The Oracle Configuration Manager distribution file can be made available through a network file system (NFS). Once the Oracle Configuration Manager distribution file is available on each host, it can be unzipped into the required `<ocm_install_root>` directory and the `setupCCR.sh` script can be executed.

1. On UNIX based systems, issue the following command to protect the unzipped files:

       umask 077

2. Then execute the unzip command as follows:

       % unzip -d <ocm_install_root> /nfsdisk/ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip
       OR
       % unzip -d <ocm_install_root> /net/hostname/directory/ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip

The name of the platform-specific distribution file for Oracle Configuration Manager is `ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip` where `OS_NAME` refers to the name of the operating system such as Linux, AIX, Windows and <`CHIP_ARCH`> refers to the base architecture such as `i386`, `x86,` and so on.

### 4.1.3 Secure Copy (SCP) and Secure Shell (SSH)

Oracle Configuration Manager can also be deployed from a central trusted host.

The system administrator can create an installation script to unzip the Oracle Configuration Manager distribution file and invoke the installation script. (In the following example, `ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip` is the Oracle Configuration Manager distribution file and `installscript`.`sh` is the name of the administrator created installation script.)

Both the Oracle Configuration Manager distribution file and the installation script are copied to the remote system and the installation script is executed. For a truly secure environment, the scp command appears as follows. Note: This command prompts for a password:

    % scp ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip \ <user>@<hostname>:ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip
    % ssh <user>@<hostname> installscript.sh -s
    where <user> is a remote username on the host denoted by <hostname>

The `installscript`.`sh` script contains the following commands:

1. On UNIX based systems, the umask command protects the unzipped files:

       umask 077

2. Then the unzip command follows:

       > unzip -d <ocm_install_root> ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip
       > <ocm_install_root>/ccr/bin/setupCCR -s <CSI> <MyOracleSupportUserName>

   - `OS_NAME` refers to the name of the operating system such as Linux, AIX, Windows and <`CHIP_ARCH`> refers to the base architecture such as `i386`, `x86,` and so on.

   - `CSI` is the Customer Support Identifier.

   - `MyOracleSupportUserName` is the My Oracle Support User Name.

### 4.1.4 Oracle Enterprise Manager Grid Control

You can deploy Oracle Configuration Manager using Oracle Enterprise Manager Grid Control in two ways:

- Copy the Oracle Configuration Manager distribution file (`ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip`) to the `<ocm_install_root>/sysman/agent_download/ccr/<OS>` directory (where OS is the operating system).

- You can also deploy Oracle Configuration Manager by using the built-in Enterprise Manager Grid Control functions that allows it to run on monitored hosts. To use this method, the following must be true:

  - The Oracle Management Agent must be deployed on all the host machines.

  - The Oracle Configuration Manager distribution file must be available to the agent on every remote host machine (this can be done using NFS or by using a Web server).

You can then create an OS script that will copy, unzip, and set up Oracle Configuration Manager on all the systems. For example:

    #!/bin/sh
    cd <ocm_install_root>;
    wget http://oms_machinename:4889/agent_download/ccr/OS ccr-Production-10.3.5.0.0-<OS_NAME>-<CHIP_ARCH>.zip;
    umask 077
    unzip -d . ccr-Production-10.3.5.0.0-Linux-x86.zip;
    /ccr/bin/setupCCR -s <CSI> <MyOracleSupportUserName>;
    exit

#### 4.1.4.1 Additional Information for Database Homes

When you deploy Oracle Configuration Manager into a database home, you must run a database configuration script. Enter the following commands:

    $setenv <ocm_install_root>;
    $setenv ORACLE_SID <oracle sid>;
    <ocm_install_root>/ccr/admin/scripts/installCCRSQL.sh collectconfig;
    <ocm_install_root>/ccr/bin/emCCR collect;

The `setenv` command may not work in all UNIX shells. For Oracle E-Business databases, you must run installCCRSQL with the `ebs_collectconfig` option. For details, refer to Instrumenting the Database for Configuration Collection.