This chapter describes how you can install an additional Oracle Management Service (OMS) to your existing Enterprise Manager Cloud Control environment. In particular, this chapter covers the following:
Introduction to Adding an Additional Oracle Management Service
Before You Begin Adding an Additional Oracle Management Service
Prerequisites for Adding an Additional Oracle Management Service
Performing Postinstallation Tasks After Adding an Additional Oracle Management Service
Note:
This chapter describes how you can install an additional OMS in interactive, graphical mode. If you want to perform the same operation in silent way, then refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.Note:
On the source OMS, if you have deployed additional plug-ins that were not part of the Enterprise Manager software (DVD, or downloaded software), then follow the instructions outlined in Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.WARNING:
Do not install Enterprise Manager Cloud Control 13c on servers of SPARC series: T1000, T2000, T5xx0, and T3-*. For more information, see My Oracle Support note 1590556.1.
Oracle Management Service (OMS) is one of the core components of Enterprise Manager Cloud Control that orchestrates with Oracle Management Agents (Management Agents) and plug-ins to discover targets, monitor and manage them, and store the collected information in a repository for future reference and analysis.
When you install Enterprise Manager for the very first time, by default, the installer installs one OMS along with one Management Agent. While this default configuration suits smaller environments, typically in larger production environments, you may have the need to install additional OMS instances to help reduce the load on a single OMS and improve the efficiency of the data flow.
Note:
You can have multiple OMS instances and still connect to just one Oracle Management Repository (Management Repository).The Add Management Service deployment procedure helps you meet such high-availability requirements. The deployment procedure offers a wizard that enables you to install an additional Oracle Management Service 13c by cloning an existing OMS that is running on an AdminServer host. The entire Middleware home of the source OMS is cloned to the destination host. For information about the contents of the Middleware home of an OMS, see Section 5.1.
Before you begin adding an additional Oracle Management Service (OMS), keep these points in mind:
You can clone only an existing, running Oracle Management Service 13c that is associated with an AdminServer host. The patches applied on the source OMS are automatically carried over to the cloned instance.
You can clone only one OMS at a time and to only one destination host at a time. If you want to add multiple OMS instances, then you must repeat the installation procedure on each host.
You can clone only when the source host and the destination host are running on the same operating system and architecture. For example, if the source host is a Linux 32-bit host, then the destination host must also be a Linux 32-bit host. Similarly, if the source host is a Linux 64-bit host, then the destination host must also be a Linux 64-bit host.
All general purpose file systems, including OCFS2 and ACFS, are acceptable for storing Enterprise Manager Cloud Control 13c software binaries and OMS instance home files (configuration files in gc_inst). However, OCFS is not considered a general purpose file system, and therefore is not considered acceptable for this use.
If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, see Section 7.5.
You can find the OMS and Management Agent entries in the /etc/oragchomelist file for all UNIX platforms except HPUNIX, HPia64, Solaris Sparc.
On HPUNIX, HPia64, Solaris Sparc platforms, the entries are present in /var/opt/oracle/oragchomelist.
Oracle BI Publisher that is installed and configured on the first OMS is automatically carried over to the additional OMS. However, as a prerequisite for installing an additional OMS, you must ensure that the Oracle BI Publisher installed on the first OMS is configured with a shared storage location for cluster volume and configuration volume. If a shared storage location is configured, then the same shared location is used by the additional OMs as well. Otherwise, you must configure a shared storage location first and then proceed with installing an additional OMS.
On Microsoft Windows, Oracle BI Publisher is not available on additional OMS instances.
Starting with 13c Release 1, as part of the Oracle Fusion Middleware Plug-in deployment, one Java Virtual Machine Diagnostics (JVMD) Engine is installed by default on the first OMS. Therefore, when you install an additional OMS using the first OMS as the source, you receive one JVMD Engine by default with the additional OMS as well.
Do not discover any Oracle ZFS Storage Appliance target in 13c environment.
Table 7-1 lists the prerequisites you must meet before adding an additional Oracle Management Service (OMS).
Table 7-1 Prerequisites for Adding an Additional Oracle Management Service
| Requirement | Description |
|---|---|
|
Hardware Requirements |
Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 1. |
|
Operating System Requirements |
|
|
Package, Kernel Parameter, and Library Requirements |
Ensure that you install all operating system-specific packages, kernel parameters, and libraries as described in Chapter 2. |
|
Operating System Groups and Users Requirements |
Ensure that you create the required operating system groups and users as described in Chapter 3. |
|
|
|
Existing Oracle Management Service Requirements |
Ensure that Oracle Management Service 13c is already installed and is available for cloning. Also ensure that the AdminServer on which the OMS is configured is up and running. Also ensure that it is not installed on a symlink. Installing in such a location may impact lifecycle operations such as patching and scaling out. |
|
Existing Oracle Management Service Backup Requirements |
Ensure that regular back-ups are scheduled for the existing Oracle Management Service 13c that you want to clone. |
|
Ensure that you have met all Oracle-recommended high availability requirements in your environment. For more information, refer to the chapter on high availability requirements in the Oracle Enterprise Manager Cloud Control Administrator's Guide. |
|
|
Shared Storage Location Requirements |
(For UNIX Only) Ensure that Oracle BI Publisher installed on the first OMS is configured with a shared storage location for cluster volume and configuration volume. Ensure that the shared storage location is mounted and is visible on the host where you are about to install the additional OMS. The shared storage location is required for storing report catalogs and associated management information for not only the first OMS but also for the additional OMS instances. If Oracle BI Publisher installed on the firs OMS is not configured with a shared storage location, then configure one now.
|
|
Existing Oracle Management Agent Requirements |
Ensure that the destination host already has a Management Agent installed, and ensure that it is up and running.
|
|
|
Check the number of OMS instances already installed in your environment, check the Typically, the parameter value to be set is computed in the following manner: (Current OMS Count + 1) x Processes Parameter Value Per OMS for the Current Deployment Size To check the number of OMS instances currently available in your environment, run the following query:
To check the For example, if you have one OMS in your environment, and if the deployment size is SMALL, then the |
|
(Only for Microsoft Windows) In the existing OMS, if Oracle Configuration Manager is configured, then make sure it is stopped from both the OMS home and the Web Tier home by following these steps.
|
|
|
Temporary Stage Directory Space Requirements on Source and Destination Hosts |
Ensure that you have 10 GB of space on the source as well as the destination host for creating a temporary stage directory. The temporary directory created by default is The temporary stage directory on the source host is used for temporarily staging the files related to backup or cloning steps of the deployment procedure. The temporary stage directory on the destination host is used for temporarily staging the cloned image and other related files. |
|
If you choose to transfer the software and configuration files to a central, shared location, then ensure that you have 4 GB of space for that shared directory. |
|
|
On the destination host, an Oracle home (absolute path) identical to the one on the source host is created, and then, the source OMS is cloned to that location. Ensure that this Oracle home does not already exist on the destination host. For example, if the Oracle home on the source host is |
|
|
Oracle Management Service Instance Base Location Space Requirements |
Ensure that you have 1 GB of space on the destination host for the Oracle Management Service Instance Base directory where the configuration files of the OMS will be created. |
|
Management Agent Installation Status Requirements |
(Only for Microsoft Windows) If the installation of a Management Agent using the Add Host Targets Wizard is in progress on the source OMS, then ensure that it is completed before you start cloning the OMS. To verify whether a Management Agent installation using the Add Host Targets Wizard is in progress, search for
|
|
|
|
On the SLB, using its administration console, create the following SLB pools and add the first OMS host to them:
|
|
|
On the SLB, using its administration console, create the following virtual servers and associate them with the SLB pools.
For instructions, see Oracle Enterprise Manager Cloud Control Administrator's Guide. |
|
|
On the SLB, using its administration console, create the following SLB monitors and associate the first OMS host with them:
|
|
|
Ensure that the directories where you have configured the Software Library are accessible (read/write) from the destination hosts. If you have configured an OMS Shared Storage location to use a local file system path, then you must migrate this location to another OMS Shared Storage location that uses a shared file system path. For instructions, refer to the Oracle Enterprise Manager Cloud Control Administrator's Guide. |
|
|
Installing User Requirements |
Ensure that you meet the following requirements:
|
|
Ensure that you are able to access and read/write in the following locations:
|
|
|
Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond. |
|
|
If you have a firewall in your environment, then refer to the chapter on configuring Enterprise Manager for firewalls in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
|
|
Unique Host Name and Static IP Address Requirements |
Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network. Note: Oracle recommends that you use static IP address. If you use dynamic IP address, and if the host is rebooted, then the host might receive a new IP, and as a result, the OMS startup will fail. |
|
|
|
Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file. For example:
|
|
|
|
|
Ensure that the host name specified in the Ensure that localhost is pingable and resolves to The following is the recommended format of the
For example,
According to RFC 952, the following are the assumptions: A name (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of domain style names. No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. Also, if DNS server is configured in your environment, then you should be able to use DNS to resolve the name of the host on which you want to install the OMS. For example, all these commands must return the same output:
If alias host names are implemented in |
|
|
To add an additional Oracle Management Service (OMS), follow these steps:
From the Enterprise menu, select Provisioning and Patching, then select Procedure Library.
On the Deployment Procedure Manager page, in the Procedure Library tab, from the table, select Add Oracle Management Service, and then, click Launch.
On the Getting Started page, complete the preinstallation tasks listed there. Once you are done, select each of the tasks you have completed, and then, click Next.
On the Select Destination page, do the following:
For Destination Host, select or enter the name of the managed host (a host managed by the first OMS using a Management Agent) on which you want to install the additional OMS.
For example, myhost.example.com
For Destination Instance Base Location, accept the default location to the OMS instance base directory or enter the absolute path to another location of your choice where OMS-related configuration files can be stored. As a best practice, this directory path should be the same as the directory path on the first OMS. Ensure that this directory has 100 MB of space. Also ensure that the directories and subdirectories you mention in the path already exist.
For example, /apps/john/oracle/prod
In the Source Credentials section and in the Destination Credentials section, select the credential type you want to use for accessing the source host. For more information, see Section 7.4.1.
Click Next.
On the Options page, do the following:
In the File Transfer Option section, select a suitable protocol to transfer the cloned ZIP files to a staging location. FTP is the default transfer mode.
If you want to transfer the files to a shared, NFS-mounted network location, then you can select Shared Directory, and enter the absolute path to the shared location. Ensure that this shared directory has read/write access from source and destination hosts, and has 4 GB of space.
For example, /net/myhost.example.com/scratch/john
Note:
If you have an SFTP set up, then select FTP as the file transfer mode.
If you choose to use a shared location as the file transfer mode, then ensure that the shared location has read/write permission and is accessible from the source host as well as the destination host.
If you select FTP, then ensure that FTP software is installed on the source host as well as the destination host. Also ensure that your temporary location (/tmp on Unix) has at least 10 GB of space.
If you select HTTP(S), then ensure that your temporary location (/tmp on Unix or C:\Temp on Microsoft Windows) has at least 10 GB of space.
This location is used for archiving the software binaries and the configuration details of the source OMS. The archive is then copied over to the source staging location, and then transferred to the destination staging location eventually, as described in the next step.
If the temporary location required for FTP and HTTP(S) options does not have 10 GB of space, then either increase the space as required, or provide another location that has 10 GB of space. To provide another location, do the following:
From the Targets menu, select All Targets.
On the All Targets page, click the name of the Management Agent that is running on the source OMS host.
On the home page, from the Agent menu, select Properties.
On the Properties page, from the Show list, select Advanced Properties.
In the Add Custom Property section, for the Name field, enter emStageDir. And for the Value field, enter the absolute path the a temporary location that has at least 10 GB of space.
In the Staging Locations section, for Source Staging, enter a location on the source host where the cloned ZIP files can be created and placed temporarily. Ensure that this temporary directory has 10 GB of space.
For example, /myhost.example.com/shared
Similarly, for Destination Staging, enter a location on the destination host where the cloned ZIP files can be copied to temporarily. Ensure that this temporary directory has 10 GB of space.
For example, /myhost.example.com/shared
Note:
Once the OMS is installed on the destination host, the cloned ZIP files are automatically deleted from both the staging locations.In the Destination Ports section, validate the ports displayed by default.
These default ports are based on the ports already assigned and used by the OMS that you are cloning. Oracle recommends you to use the same ports as your source OMS so that you have a homogeneous environment.
You can choose to retain the ports displayed by default or enter a custom port. Ensure that the custom port you enter is within the recommended range as shown in the Recommended Port Range column. If you want to check the availability of a custom port, then click Check Ports.
Click Next.
On the Post Creation Steps page, enter one or more e-mail IDs (separate by a comma) where the details of the postinstallation tasks to be performed can be sent, and then, click Next.
For your e-mail to work, you must have already configured the mail server. For instructions, see Oracle Enterprise Manager Cloud Control Administrator Guide.
On the Review page, review the details and click Finish.
Note:
If the installation fails, particularly in the Install Homes step, then before you retry installing the OMS, clean up the Oracle home on the destination host where the installation failed.You can select one of the following credential types for accessing the source and the destination hosts:
Table 7-2 Selecting Credential Type
| Credential Type | Description |
|---|---|
|
Select this if you want to use the credentials that are already registered as preferred credentials with Enterprise Manager. In this case, from the Preferred Credential Name list, select either Normal Host Credentials or Privileged Host Credentials depending on the type of preferred credentials you want to use for accessing the host. |
|
|
Select this if you want to use the credentials of a named profile created in Enterprise Manager. In this case, from the Credential Name list, select the profile whose credentials you want to use. On selection, you will see the credentials details. For more information on the credentials associated with the selected profile, click More Details. If you want to test connecting to the host with those credentials, click Test. |
|
|
Select this if you want to enter a new set of credentials that will override the preferred credentials or the named credentials registered with Enterprise Manager. In this case, enter the credentials you want to override with. If you want to register the new set of credentials with Enterprise Manager, then click Save As, and either accept the default profile name or enter a custom name for it. Further, if you want to save them as preferred credentials, then select Set as Preferred Credentials, and select an option to indicate whether they should be saved as normal credentials or privilege credentials. If you want to test connecting to the host with those credentials, click Test. |
After you install the additional OMS, ensure that you do NOT create symlinks in the middleware home or in any of the homes within the middleware home. Also, follow these steps:
(Applicable only if you had stopped the Oracle Configuration Manager as a prerequisite on Microsoft Windows) Start Oracle Configuration Manager:
Set the environment variable ORACLE_CONFIG_HOME to the following location:
$<OMS_INSTANCE_HOME>/em/EMGC_OMS1
For example,
set ORACLE_CONFIG_HOME=/u01/software/em13c/gc_inst/em/EMGC_OMS1
Navigate to the following location:
$<ORACLE_HOME>/oracle_common/ccr/bin
For example,
cd /u01/software/em13c/oraclehome/oracle_common/ccr/bin
Start OCM by running the following script:
emCCR.bat start
Set the environment variable ORACLE_CONFIG_HOME to the following location:
$<OMS_INSTANCE_HOME>/WebTierIH1
For example,
set ORACLE_CONFIG_HOME=/u01/software/em13c/gc_inst/WebTierIH1
Navigate to the following location:
$<ORACLE_HOME>/Oracle_WT/ccr/bin
For example,
cd /u01/software/em13c/oraclehome/Oracle_WT/ccr/bin
Start OCM by running the following script:
emCCR.bat start
(Optional) If you installed the additional OMS using a source OMS that was already behind a Server Load Balancer (SLB), then the SLB configuration from the source OMS is automatically carried over to the newly installed additional OMS.
However, if the source OMS was not behind any SLB, and if you now want the additional OMS and the source OMS to be configured behind an SLB, then perform the following steps on the additional OMS as well as the source OMS:
Using the SLB's administration console, add the additional OMS host to the following SLB pools:
Secured Upload Pool (add the host using the port configured for the Secured Upload service)
(Optional) Agent Registration Pool (add the host using the port configured for the Agent Registration service)
Secure Console Pool (add the host using the port configured for the Secure Console service)
(Optional) Unsecure Console Pool (add the host using the port configured for the Unsecure Console service)
Using the SLB's administration console, associate the additional OMS host with the following monitors:
Secure Upload Monitor (associate the host using the port configured for the Secure Upload service)
(Optional) Agent Registration Monitor (associate the host using the port configured for the Agent Registration service)
Secure Console Monitor (associate the host using the port configured for the Secure Console service)
(Optional) Unsecure Console Monitor (associate the host using the port configured for the Unsecure Console service)
Secure the additional OMS and the Management Agent that is installed on the host where the additional OMS has been installed.
Secure the additional OMS. After securing it, restart the OMS.
$<ORACLE_HOME>/bin/emctl secure oms -sysman_pwd <sysman_pwd> -reg_pwd <agent_reg_password> -host <host_name> -slb_port <slb_upload_port> -slb_console_port <slb_console_port> [-console -lock -lock_console]
For example,
/u01/software/em13c/oraclehome/bin/emctl secure oms -sysman_pwd <password> -reg_pwd <password> -host example.com -secure_port 4904 -slb_port 4900 -slb_console_port 7788 -console -lock -lock_console
Secure the Management Agent.
$<AGENT_INSTANCE_HOME>/bin/emctl secure agent $AGD_REGISTRATIO_PWD –emdWalletSrcUrl <emd_wallet_source_url>
For example,
/u01/software/em13c/agentbasedir/agent_inst/bin/emctl secure agent $AGD_REGISTRATIO_PWD –emdWalletSrcUrl https://example.com:4900/em
Confirm the SLB repository URL in the output of the following command:
$<AGENT_INSTANCE_HOME>/bin/emctl status agent
For example,
//u01/software/em13c/agentbasedir/agent_inst/bin/emctl status agent
Note:
For information about configuring SLB, refer to the Oracle Enterprise Manager Administration Guide.(Only for UNIX Platforms) Run <ORACLE_HOME>/root.sh as a root user on the destination host.
If you installed on an NFS-mounted drive and created the OMS instance base directory (gc_inst) on that NFS-mounted drive, then move the lock files from the NFS-mounted drive to a local file system location. To do so, modify the lock files location in the httpd.conf file to map to a location on a local file system.
Stop the OMS:
<ORACLE_HOME>/bin/emctl stop oms
Open the following file in the runtime directory:
Note:
Oracle recommends you to take a backup of this file before editing it.<WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs<#>/httpd.conf.emctl_secure
For example,
/u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs2/httpd.conf.emctl_secure
Search for sections related to the modules mpm_prefork_module and mpm_worker_module. In both these sections, modify the value for the LockFile parameter so that the path leads to a location on the local file system. If the directory does not already exist, then create it first, and then provide the path to that directory.
<IfModule mpm_prefork_module> StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 AcceptMutex fcntl LockFile /u01/em/ohs_locks/http_lock </IfModule> .... <IfModule mpm_worker_module> StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0 AcceptMutex fcntl LockFile /u01/em/ohs_locks/http_lock </IfModule>b
Save the changes.
In the runtime directory, copy the httpd.conf.emctl_secure file to the httpd.conf file:
cp <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs<#>/httpd.conf.emctl_secure <WEBTIER_INSTANCE_HOME>/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs<#>/httpd.conf
For example,
cp /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs2/httpd.conf.emctl_secure /u01/software/em13c/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs2/httpd.conf
Start the OMS:
<ORACLE_HOME>/bin/emctl start oms
By default, the following targets get automatically discovered and monitored in the Enterprise Manager Cloud Control Console:
Oracle WebLogic Server, where the additional OMS is deployed
Oracle Web Tier
Application deployments, one for the Enterprise Manager Cloud Control console and one for the platform background services.
Oracle Management Service
Oracle Management Agent
The host on which you installed Enterprise Manager Cloud Control
However, the other targets running on that host and other hosts do not get automatically discovered and monitored. To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.
For information about discovering targets in Enterprise Manager Cloud Control, refer to the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
An encryption key is generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the Management Repository becomes unusable. Therefore, back up the Management Service configuration including the emkey, and maintain the backup on another host.
To back up the Management Service configuration including the emkey, run the following command:
<ORACLE_HOME>/bin/emctl exportconfig oms -dir <path_to_backup_location>
Before accessing the Enterprise Manager Cloud Control Console in a browser, install a security certificate from a trusted certification authority on the browser.
This is to ensure that the Enterprise Manager Cloud Control Console that you are accessing over HTTPS protocol is recognized as a genuine and secure Web site.
For instructions to install a security certificate on your browser and avoid security certificate alerts, refer to Oracle Enterprise Manager Cloud Control Administrator's Guide.
(Optional) If you had enabled Oracle BI Publisher on the source OMS, then Oracle BI Publisher is automatically enabled on the additional OMS as well. On the other hand, if you had not enabled Oracle BI Publisher on the source OMS, then Oracle BI Publisher is not enabled on the additional OMS, either, although it is installed and configured with the shared storage location. Thus, the state of Oracle BI Publisher is automatically inherited from the source OMS.
To verify whether or not Oracle BI Publisher is enabled on the source OMS, run the following command from the bin directory of the Oracle home of the source OMS.
$<ORACLE_HOME>/bin/emctl status oms -bip_only
For example,
/u01/software/em13c/oraclehome/bin/emctl status oms -bip_only
To enable Oracle BI Publisher on the additional OMS now, run the following command from the bin directory of the Oracle home of the additional OMS. You can run the same command on the source OMS if you want to enable Oracle BI Publisher on the source OMS as well.
$<ORACLE_HOME>/bin/emctl config oms -enable_bip
For example,
/u01/software/em13c/oraclehome/bin/emctl config oms -enable_bip
The preceding command only enables Oracle BI Publisher, but does not start it. To start it, run the following command from the bin directory of the Oracle home of the OMS.
$<ORACLE_HOME>/bin/emctl start oms -bip_only
For example,
/u01/software/em13c/oraclehome/bin/emctl start oms -bip_only