3 Advanced Deployment Tasks

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 ORACLE_HOME directory and the setupCCR.sh script can be executed.

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

The name of the platform-specific distribution file for Oracle Configuration Manager is ccr-Production-10.2.4.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.

Remote Copy (RCP) and Remote Shell (RSH)

Oracle Configuration Manager can also be deployed from a central trusted host. To do this, the system administrator must configure the RCP and RSH protocols by creating the .rhosts file that contains a list of trusted host names and user names. The remote host can then be accessed using the RCP or RSH protocols without a password.

After the RCP and RSH protocols have been configured, 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.2.4.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. The commands are as follows:

% rcp ccr-Production-10.2.4.0.0-<OS_NAME>-<CHIP_ARCH>.zip remoteuser@remotehost:path_to_oracle_home
% rsh remotehost installscript.sh -s 

The installscript.sh script contains the following commands:

unzip -d <ORACLE_HOME> ccr-Production-10.2.4.0.0-<OS_NAME>-<CHIP_ARCH>.zip
<ORACLE_HOME>/ccr/bin/setupCCR -s <CSI> <MetaLinkUserName> <Country_Code>

• 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.

• MetaLinkUserName is the Oracle MetaLink User Name.

• Country Code is the customer's country code. For a list of valid country codes, refer to Appendix A.

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.2.4.0.0-<OS_NAME>-<CHIP_ARCH>.zip) to the $ORACLE_HOME/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 <ORACLE_HOME>;
wget http://oms_machinename:4889/agent_download/ccr/linux/ccr-Production-10.2.4.0.0-<OS_NAME>-<CHIP_ARCH>.zip;
unzip -d . ccr-Production-10.2.4.0.0-<OS_NAME>-<CHIP_ARCH>.zip;
<ORACLE_HOME>/ccr/bin/setupCCR -s <CSI> <MetaLinkUserName> <Country_Code>;
exit

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