This chapter explains how you can install only the software binaries of Enterprise Manager Grid Control in silent mode, and configure the installation later. In particular, this chapter covers the following:
Note:
Do NOT install the Enterprise Manager system on an OCFS file system. This file system is not supported.Installing Enterprise Manager Software Only and Configuring Later is an approach that enables you to install only the software binaries of Enterprise Manager Grid Control at one point and configure it at a later point in time to work with an existing, certified Oracle Database. Essentially, the approach has two phases, mainly the installation phase and the configuration phase.
The existing, certified Oracle Database must be one of the databases listed in My Oracle Support note 412431.1.
During the installation phase, this approach creates the following in the Oracle Middleware Home:
Oracle homes and installs the software binaries for Oracle Management Service (OMS) (Deployed to the existing, certified Oracle WebLogic Server), Oracle Management Agent (Management Agent), and Oracle Web Tier.
A common directory (oracle_common) for storing configuration files.
During the configuration phase, this approach does the following:
Creates an Oracle Management Service Instance Base (gc_inst or any other custom name you specify) in the parent directory of the Oracle Middleware Home.
Applies OMS-related and Management Agent-related one-off patches.
Configures Oracle Management Repository (Management Repository) in the existing, certified Oracle Database; OMS; Management Agent; Oracle Configuration Manager if you chose to configure it, and System Monitoring Plug-Ins if they were detected.
Before you begin, keep in mind the points described in Before You Begin.
Before installing the software binaries of Enterprise Manager Grid Control in silent mode, ensure that you meet the prerequisites described in Prerequisites.
To install only the software binaries of Enterprise Manager Grid Control in silent mode, follow these steps:
Copy the following response file to an accessible location on your local host:
<Software_Location>/response/em_using_existing_db.rsp
In this command, <Software_Location> is either <DVD> or <Software_Downloaded_Location>.
Edit the response file and specify appropriate values for the parameters described in Table 3-5.
Invoke the installer:
./runInstaller -noconfig -silent -responseFile <absolute_path_to_response_file>/em_using_existing_db.rsp -force
Note:
For Microsoft Windows, invoke setup.exe instead of runInstaller.
In Microsoft Windows, if the path to the software download location contains a subdirectory name with two or more words and a space between each of the words, then ensure that the parent directory of such a subdirectory does not contain a file whose name matches with the first word of that subdirectory.
For example, if the software is downloaded to C:\Documents and Settings, then before you invoke setup.exe, ensure that there are no files titled Documents (for example, shortcut files such as C:\Documents) in the C:\ drive.
If you are planning to have multiple OMSes, then Oracle strongly recommends you to configure a shared file system loader so that a common location is maintained to store all the metric data files uploaded by the Management Agents. If you configure the central directory now, then all subsequent additional OMS installations, which connect to the same Oracle Database, will automatically be mapped to this central directory.
To configure a shared file system loader, invoke the installer using the following command. Ensure that the location you specify is accessible and wirtable by all the OMSes.
./runInstaller -noconfig -silent -responseFile <absolute_path_to_response_file>/em_using_existing_db.rsp -force SHARED_RECEIVE_DIRECTORY_LOCATION=<absolute_path_to_central_directory>
By default, GCDomain is the default name used for creating the WebLogic Domain.
To override this, invoke the installer using the following command and specify a unique custom WebLogic Domain name:
./runInstaller WLS_DOMAIN_NAME=<Custom_Domain_Name>
(For UNIX Only) After you install the software binaries of Enterprise Manager Grid Control, log in as a root user in a new terminal and run the allroot.sh script from the Oracle home of the OMS (for example, oms11g):
$<ORACLE_HOME>/allroot.sh
To configure Enterprise Manager Grid Control, do the following:
If the environment variable PERL5LIB is set in your environment, then unset it.
Run the ConfigureGC.pl script from the Oracle home of the OMS (oms11g):
$<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl
Note:
If any of the Configuration Assistants fail, then review the relevant log files, resolve the issues, and rerun the Configuration Assistants as described in What Do You Do When Configuration Assistants Fail?.
To understand the optional arguments that can be passed with the ConfigureGC.pl script, see Appendix J, "Understanding Optional Arguments Run with ConfigureGC.pl Script".
After configuring Enterprise Manager Grid Control, follow the steps outlined in After You Configure.