This chapter explains how you can install only the software binaries of Enterprise Manager Grid Control in graphical 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. The existing, certified Oracle Database must be one of the databases listed in My Oracle Support note 412431.1. Therefore, this approach has two phases, mainly the installation phase and the configuration phase.
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; Oracle Management Agent; Oracle Configuration Manager if you chose to configure it, and System Monitoring Plug-Ins if they were detected.
Before you begin, keep these points in mind:
This installation type installs the components only on a single host, and only on that host from where the installer and the configuration script are invoked. Installation on multiple hosts and remote hosts is not supported.
Do NOT install the additional OMS on an OCFS file system. This file system is not supported
Install Enterprise Manager Grid Control on a dedicated Oracle WebLogic Server instance (in a separate middleware home). Do NOT install Enterprise Manager Grid Control on an Oracle WebLogic Server instance that already has an Oracle Fusion Middleware product installed. For example, if the middleware home already has Oracle SOA Suite 11.1.1.2.0 installed, then do not install Enterprise Manager Grid Control in the same middleware home. Enterprise Manager Grid Control cannot co-exist with any Oracle Fusion Middleware product in the same middleware home because the ORACLE_COMMON property is used by both the products.
For information about the default ports that are assigned and the possibility of using custom ports instead of default ports, see What Ports Are Used for Installation?.
While installing on hosts having multiple IP addresses, the host name is derived from the ORACLE_HOSTNAME variable that is passed while invoking the installer.
For example:
./runInstaller ORACLE_HOSTNAME=foo.us.oracle.com
Note:
Before passing this variable with the installer, ensure that you set theORACLE_HOSTNAME environment variable.Do NOT set the DISPLAY environment variable.
No environment variable specific to Enterprise Manager Grid Control needs to be set prior to installation. The ORACLE_HOME and ORACLE_SID variables should not be set; Oracle directories should not appear in the PATH.
Oracle offers code fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for code fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:
http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf
When determining supportability and certification combinations for an Enterprise Manager Grid Control installation, you must consider Enterprise Manager Grid Control's framework components as well as the targets monitored by Enterprise Manager Grid Control. Oracle recommends keeping your Grid Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license. For information about the certified combinations of Enterprise Manager Grid Control components and monitored targets, see My Oracle Support note.412431.1.
For accessing the Enterprise Manager Grid Control console, ensure that you use only certified browsers as mentioned in My Oracle Support note 412431.1.
Before installing the software binaries of Enterprise Manager in graphical mode, ensure that you meet the prerequisites described in Prerequisites.
To install only the software binaries of Enterprise Manager Grid Control in graphical mode, follow these steps:
Invoke the installer by running the following command:
<Software_Location>/runInstaller -noconfig
In this command, <Software_Location> is either <DVD> or <Software_Downloaded_Location>.
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 writable by all the OMSes.
./runInstaller -noconfig SHARED_RECEIVE_DIRECTORY_LOCATION=<absolute_path_to_central_directory>
After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer using the START_OMS=false and b_startAgent=false arguments.
However, if you pass the START_OMS=false argument, the installation does not configure the EMCLI tool, and as a result, none of the EMCLI commands will work. Therefore, after the installation ends, you must manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface available at:
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>
Enterprise Manager Grid Control Installation Wizard appears. The wizard guides you through the installation process. Select the first installation type, that is, Install a new Enterprise Manager system, and specify the information required on each of the screens. Click Next on each screen until you reach the final screen. On the final screen, click Install to install Enterprise Manager Grid Control.
For information about the values you need to specify on each screen, follow the instructions outlined for installing a complete Enterprise Manager system, in the Oracle Enterprise Manager Grid Control Basic Installation Guide available at:
Note:
If you are connecting to an existing Oracle RAC database, and if you have specified the virtual IP address of one of its nodes in the Connect to Oracle Database screen of the installation wizard, then when you click Next, the installation wizard prompts you with a Connection String dialog and requests you to update the connection string with information about the other nodes that are part of the cluster. Update the connection string and click OK. If you want to test the connection, click Test Connection.(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 (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 these steps:
Verify the installation:
Navigate to the Oracle home of the OMS (oms11g) and run the following command to see a message that confirms that OMS is up and running.
$<ORACLE_HOME>/bin/emctl status oms
Navigate to the Oracle home of the Management Agent (agent11g) and run the following command to see a message that confirms that the Management Agent is up and running.
$<ORACLE_HOME>/bin/emctl status agent
Navigate to the Oracle home of the Management Agent (agent11g) and run the following command to see a message that confirms that EMD upload completed successfully.
$<ORACLE_HOME>/bin/emctl upload
Note:
By default, you can access Enterprise Manager Grid Control only using the HTTPS protocol. If you want to use the HTTP protocol, then unlock it by running the following command from the Oracle home of the OMS:emctl secure unlock -console
Configure your proxy server as described in Appendix H, "Setting Up Proxy Configuration for Oracle Management Service".
Configure the Oracle Database and Oracle Automatic Storage Management (Oracle ASM) target for monitoring as described in Appendix G, "Configuring Database and ASM Targets for Monitoring".
(Optional) If you had not configured a shared file system loader while installing a complete Enterprise Manager system, and if you want to configure a shared location for it now, then run the following command from the Oracle home of the OMS:
$<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir <Loader_Directory>
For example,
$<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir /share/recv
For accessing the Enterprise Manager Grid Control console, ensure that you use only certified browsers as mentioned in My Oracle Support note 412431.1.
(Optional) If you want to connect to another Management Repository, then shut down the OMS, run the following command, and then restart the OMS.
emctl config oms -store_repos_details (-repos_host <host> -repos_port <port> -repos_sid <sid> | -repos_conndesc <connect descriptor>) -repos_user <username> [-repos_pwd <pwd>] [-no_check_db]
Note:
On Linux, you need to double escape the connect descriptor using single and double quotes. However, on Microsoft Windows, you need not.For example, on Linux:
emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc '"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb)))"' -repos_user sysman
For example, on Microsoft Windows:
emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb))) -repos_user sysman
(Optional) If you want to change the SYSMAN password, then shut down the OMS, run the following command, and then restart the OMS.
emctl config oms -change_repos_pwd
(Optional) If you want to discover the newly installed targets, if you want to convert the standalone Management Agent to a cluster-based Management Agent, if you want to discover the targets on the new nodes of the cluster, or if you want to reconfigure the cluster-based Management Agent, you must run the agentca script to reconfigure and discover all new targets.
For information about the agentca script, see What Is Agent Configuration Assistant Used For?.
For information about reconfiguring the Management Agent and discovering all new targets, see Appendix I, "Reconfiguring Oracle Management Agent and Discovering New Targets".
(Optional) If you want to enable the Request Monitoring feature for tracing transaction requests in WLS, you need JVM Diagnostics as well as Application Dependency and Performance (ADP) managers and agents configured against the target to be monitored.
For information about installing JVM Diagnostics and enabling the Request Monitoring feature, refer to the Oracle Enterprise Manager Administration Guide.
For information about enabling the ADP feature in Enterprise Manager Grid Control, refer to the Oracle Enterprise Manager Getting Started with Management Pack Plus for SOA.
Both these guides are available at: