This chapter explains how you can install only the software binaries of Oracle Management Service (OMS) in graphical mode, and configure the installation later. In particular, this chapter covers the following:
Note:
The additional OMS you are installing must be installed on the same operating system as the other OMSes. Also ensure that the operating system and the Oracle home of the OMS are patched to the same level as the other OMSes.Also, do not install the additional OMS on an OCFS file system. This file system is not supported.
Installing Oracle Management Service Software Only and Configuring Later is an approach that enables you to install only the software binaries of the OMS at one point and configure it at a later point in time to work with an existing, certified Oracle Database that is already configured with Oracle Management Repository (Management Repository). 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 the 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 OMS 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 the OMS, the Management Agent, the Oracle Configuration Manager (OCM) if you chose to configure it, and the System Monitoring Plug-Ins if they were detected.
This approach is best suited for the following reasons:
If you want to install only the software binaries now and configure it later.
If your first OMS, which was installed as part of the complete Enterprise Manager system installation, has add-ons.
Before you begin, keep these points in mind:
Oracle Management Service 11g Release 1 is supported only with Enterprise Manager 11g Grid Control Release 1.
If you are installing an additional Oracle Management Service 11g Release 1 to an existing Enterprise Manager 11g Grid Control environment, then follow the installation steps outlined in this chapter.
If you are installing an additional Oracle Management Service 11g Release 1 to an existing Enterprise Manager 10g Grid Control Release 2 (10.2.X.X) environment, then first upgrade Enterprise Manager 10g Grid Control to Enterprise Manager 11g Grid Control, and then install the additional Oracle Management Service 11g.
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.
You cannot install more than one OMS on a host.
Do NOT install the additional OMS on an OCFS file system. This file system is not supported
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.
The presence or absence of EMKEY in Oracle Management Repository (Management Repository) does not matter, and the installation will proceed either way without any issues.
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 OMS in graphical mode, ensure that you meet the prerequisites described in Prerequisites.
To install only the software binaries of OMS 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.
Enterprise Manager Grid Control Installation Wizard appears. The wizard guides you through the installation process. Select the second installation type, that is, Add an additional Management Service, 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 the OMS.
For information about the values you need to specify on each screen, follow the instructions outlined for installing an additional OMS, in the Oracle Enterprise Manager Grid Control Basic Installation Guide available at:
Note:
Follow the steps outlined in this section only if you want to install add-ons to your additional OMS. Otherwise, skip this section and move to the next section.After you install the software binaries of OMS, follow these steps to install the 11g Release 1 add-ons:
Install the add-ons by running the following command from the Oracle home of the OMS:
$<ORACLE_HOME>/oui/bin/runInstaller -noconfig
When the installer prompts you to specify the location of the products.xml file, specify the full path to the /Disk1/stage/ directory where the products.xml file is available. Ensure that the path leads up to the products.xml file. The /Disk1/stage/ directory is available in the add-on software you downloaded.
For example, if you downloaded an add-on to /scratch/<AddOn_Name>/, then specify the path as /scratch/<AddOn_Name>/Disk1/stage/products.xml.
Note:
When you proceed with the installation, you will be prompted to select the add-on OMS component, the Oracle home of the OMS in which you want to install the add-ons. You will also be prompted to specify the Management Repository-related details.(For UNIX Only) Log in as a root user in a new terminal and run the allroot.sh script from the Oracle home of the OMS:
$<ORACLE_HOME>/allroot.sh
To configure the OMS, 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 you configure the additional OMS, follow these steps:
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
Refresh the Oracle WebLogic Server Domain, which hosts the Enterprise Manager application, so that the configuration changes made to the domain as a result of adding an additional OMS are reflected in the Grid Control console. To refresh the Oracle WebLogic Server Domain, follow these steps:
In Enterprise Manager Grid Control, navigate to the Home page for the Oracle WebLogic Server Domain that hosts the Enterprise Manager application. In most cases, the following is the direct URL to the Home page. If your domain name is not GCDomain, then replace that string with your domain name:
[protocol]://[host]:[port]/em/faces/as/as/domainHome?target=/secFarm_GCDomain/GCDomain&type=weblogic_domain
From the WebLogic Domain menu, click Refresh WebLogic Domain.
On the Refresh WebLogic Domain page, click Continue.
Note:
This submits a WebLogic Domain Refresh job, which captures the domain configuration changes and reflects them in the Enterprise Manager Grid Control console. The job repeats itself once a day, and therefore, if you add any more additional OMSes or remove OMSes from your Enterprise Manager system in the future, this job automatically captures the configuration changes to the Oracle WebLogic Server Domain. You do NOT have to repeat this procedure every time you add an additional OMS.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".
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: