Oracle recommends that you install additional Oracle Management Services (OMS) in your environment to ensure high availability of your Enterprise Manager system. This chapter describes how you can install an additional OMS in silent mode. In particular, this chapter covers the following:
Oracle recommends that you install additional OMS instances in your environment to ensure high availability of your Enterprise Manager system. To install an additional OMS, you can use the Add Management Service deployment procedure. The Add Management Service deployment procedure offers a GUI-rich, interactive way of installing an additional OMS. For instructions, see Adding Additional Oracle Management Services in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.
However, if you have any security restrictions or audit demands in your environment, or if you are not permitted to use Oracle credentials to log in over the network for installation, then you can install in silent, non-interactive mode. Before you start the silent installation, meet all the prerequisites listed in Adding Additional Oracle Management Services in the Oracle Enterprise Manager Cloud Control Basic Installation 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.
To install an additional OMS in silent mode, follow these steps:
If Oracle Software Library (Software Library) is configured on the main OMS, which comes with Enterprise Manager Cloud Control, then do the following:
On Unix Platforms:
Ensure that the Software Library is read-write accessible from the remote host where you plan to install the additional OMS.
Ensure the BI Publisher shared storage volumes, both the config volume and cluster volume, are mounted onto the remote host where you plan to install the additional OMS. Ensure that all the files system permissions allow reading and writing to these volumes.
Although it is acceptable to have a single volume with separate config and cluster subdirectories, having two separate and dedicated volumes provides extra reliability in the case of failure scenarios.
On Microsoft Windows Platforms: If you do not have an option to share or mount the Software Library, then copy the Software library from the main, source OMS host to the destination host where you plan to install the additional OMS.
In this procedure, for easy understanding, the OMS that comes with Enterprise Manager Cloud Control is referred to as the first OMS, and the additional OMS you install is referred to as the additional OMS.
On the remote host, perform a software-only installation of the additional OMS as described in Installing Enterprise Manager Using the Software-Only Method in Graphical Mode.
Note:
Ensure that you install the software binaries as the same user as the one used for installing the first OMS. You must be able to access the Software Library files.
Ensure that you install the software binaries in the same middleware location as that of the first OMS.
At the end of the software-only installation, do NOT run the ConfigureGC.sh (for Unix platforms) or ConfigureGC.bat script (for Microsoft Windows) as prompted by the installer. That file must be run only when you are performing a fresh installation.
Deploy the plug-ins:
In GUI Mode (using the installer screen)
Invoke the PluginInstall.sh script from the following location:
$<ORACLE_HOME>/sysman/install/PluginInstall.sh
On the Plug-In Deployment screen, select the optional plug-ins you want to install.
The screen displays only those plug-ins that were available in the software kit (DVD, downloaded software) you used in the previous step for installing the software binaries.
The pre-selected rows on this screen are mandatory plug-ins that will be installed by default. Select the optional ones you want to install.
In Silent Mode (command line):
Invoke the PluginInstall.sh script from the following location:
$<ORACLE_HOME>/sysman/install/PluginInstall.sh -silent PLUGIN_SELECTION="{PLUGIN_ID1,PLUGIN_ID2}"
For example,
/u01/software/em13c/oraclehome/sysman/install/PluginInstall.sh -silent PLUGIN_SELECTION="{oracle.sysman.emfa,oracle.sysman.vt}"
Note:
On Microsoft Windows, run PluginInstall.bat.
Ensure that you select the same set of plug-ins as the ones on the source OMS (or first OMS).
To identify the plug-ins installed on the source OMS (or first OMS), follow these steps:
Connect to the Management Repository and run the following SQL query to retrieve a list of plug-ins installed:
SELECT epv.plugin_id, epv.version, epv.rev_version FROM em_plugin_version epv, em_current_deployed_plugin ecp WHERE epv.plugin_type NOT IN ('BUILT_IN_TARGET_TYPE', 'INSTALL_HOME') AND ecp.dest_type='2' AND epv.plugin_version_id = ecp.plugin_version_id
Make a note of the additional plug-ins you installed.
To install the additional plug-ins that are installed on the source OMS (or first OMS), or to install any additional plug-ins that are not in the software kit you used for installing the binaries, follow these steps:
Manually download the required plug-ins from the following location:
http://www.oracle.com/technetwork/oem/extensions/index.html
In addition, if you want to download any partner or customer plug-ins, then download from the following location:
Invoke the script with the following parameter, and pass the location where the additional plug-ins have been downloaded:
In GUI Mode (using the installer screen):
$<ORACLE_HOME>/sysman/install/PluginInstall.sh PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>
The Plug-In Deployment screen displays a list of plug-ins that were available in the software kit as well as the downloaded plug-ins available in this custom location. You can choose the ones you want to install.
In Silent Mode (command line):
$<ORACLE_HOME>/sysman/install/PluginInstall.sh -silent PLUGIN_SELECTION="{PLUGIN_ID1,PLUGIN_ID2}" PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>
On the additional OMS, apply all the patches you applied on the first OMS so that both OMS instances are identical and are in sync. Patches include patches that modified the Enterprise Manager system, the Software Library, the OMS files, the Management Repository, and so on.
To identify the patches you applied on the first OMS, run the following commands from the platform home:
$<Platform Home>/OPatch/opatchauto lspatches
This command displays the installed patches and Oracle home relationships. Map the installed patches to the patch .zip files on My Oracle Support site (https://support.oracle.com/). Download the files and unzip the archives on the additional OMSs. If patches are already available in the file system or a shared area, reuse those patches to apply it on other OMSs.
Note:
For more details on installed patches in the platform, and Plug-in homes, run the command $ORACLE_HOME/OPatch/opatch lsinventory -details -oh <desired home path>.
To apply the patches, run the following commands:
For each system patch:
<Platform Home>/OPatch/opatchauto apply <patch location> -bitonly -oh <Platform Home> -invPtrLoc <Platform Home>/oraInst.loc
<Platform Home>/OPatch/opatchauto commit -id 17513525 -oh <Platform Home> -invPtrLoc <Platform Home>/oraInst.loc
Note:
A patch is a system patch if it has a <system patch location>/bundle.xml file. The system patch ID is the top level directory patch ID number. This ID is also available in the <System patch location>/bundle.xml file. For example, <system_patch_bundle_xml type_version="2.0" bundle_type="ENGSYSTEM" patch_abstract="sample System Patch description" patch_id="1111115"> clearly indicates the patch ID as 1111115.
For each one-off patch specifically for the platform homes:
<Platform Home>/OPatch/opatch napply <one-off location> -oh <Platform Home> -invPtrLoc <Platform Home>/oraInst.loc
Export the configuration details from the first OMS. To do so, run the following command from the Oracle home of the first OMS host, and pass the location where the configuration details can be exported as a file.
$<ORACLE_HOME>/bin/emctl exportconfig oms -dir <absolute_path_to_directory>
Copy the exported configuration details file from the first OMS host to the additional OMS host.
If the additional OMS is being installed using an alias host name, then set the ORACLE_HOSTNAME environment variable to the alias host name.
Recover the configuration details onto the additional OMS. To do so, run the following command from the Oracle home of the additional OMS host:
$<ORACLE_HOME>/bin/omsca recover -ms -backup_file <absolute_path_to_the_file_copied_in_step4> [-AS_HTTPS_PORT <port> -MSPORT <port> -MS_HTTPS_PORT <port> -EM_NODEMGR_PORT <port> -EM_UPLOAD_PORT <port> -EM_UPLOAD_HTTPS_PORT <port> -EM_CONSOLE_PORT <port> -EM_CONSOLE_HTTPS_PORT <port> -config_home <absolute_path_to_instance_dir> -EM_INSTANCE_HOST <second_oms_host_name>] -EM_BIP_PORT <port> -EM_BIP_HTTPS_PORT <port> -EM_BIP_OHS_PORT <port> -EM_BIP_OHS_HTTPS_PORT <port>
For example,
/u01/software/em13c/oraclehome2/bin/omsca recover -ms -backup_file /opt/oracle/product/backup/opf_ADMIN_20120504_031016.bka -AS_HTTPS_PORT 7101 -MSPORT 7202 -MS_HTTPS_PORT 7301 -EM_NODEMGR_PORT 7403 -EM_UPLOAD_PORT 4889 -EM_UPLOAD_HTTPS_PORT 4900 -EM_CONSOLE_PORT 7788 -EM_CONSOLE_HTTPS_PORT 7799 -config_home /opt/oracle/product/omsmdw/gc_inst -EM_BIP_PORT 9701 -EM_BIP_HTTPS_PORT 9702 -EM_INSTANCE_HOST example.com -EM_BIP_OHS_PORT 9788 -EM_BIP_OHS_HTTPS_PORT 9851
Note:
If the additional OMS is being installed using an alias host name, then set the EM_INSTANCE_HOST parameter to the alias host name that is defined in the /etc/hosts file on all the OMS instances at this site.
(Applicable only if you do not already have a Management Agent on the host) Configure the Management Agent on the additional OMS host by running the following command from the agent home:
$<AGENT_HOME>/sysman/install/agentDeploy.sh AGENT_BASE_DIR=<agent_base_dir> OMS_HOST=<oms_host_name> EM_UPLOAD_PORT=<oms_port> AGENT_REGISTRATION_PASSWORD=<password> -configOnly
Note:
If you have a Server Load Balancer (SLB) configured, then directly enter the host name and the port number of the SLB for the OMS_HOST and EM_UPLOAD_PORT parameters. If an SLB is not configured, then enter the host name and the secure upload port of the first OMS for the OMS_HOST and EM_UPLOAD_PORT parameters.
If the additional OMS is being installed using an alias host name, then add the ORACLE_HOSTNAME=<alias host name> parameter to the command and set the parameter to the alias host name that is defined in the /etc/hosts file on all the OMS instances at this site.
Deploy the required plug-ins on the Management Agent.
For information about deploying plug-ins, see Managing Plug-Ins in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Import the trusted certificate on the additional OMS host, where you configured the Management Agent as described in Step (9). When prompted for a password, enter welcome.
$<AGENT_HOME>/bin/emctl secure add_trust_cert_to_jks
Review and perform the applicable postinstallation steps. See Performing Postinstallation Tasks After Adding an Additional Oracle Management Service in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.
Manually discover the Oracle WebLogic Server target.
Ensure that both the first and the additional OMS instances are up and running.
In the Cloud Control console, from the Targets menu, select All Targets.
On the All Targets page, search and click /EMGC_GCDomain/GCDomain/.
On the EMGC_GCDomain home page, from the WebLogic Domain menu, select Refresh WebLogic Domain.
On the Refresh WebLogic Domain page, click Add / Update Targets, and follow the steps guided by the wizard.
Enterprise Manager Cloud Control refreshes the WebLogic Domain and discovers the second managed server on the additional OMS host.
For information about discovering the other targets and adding targets, see Overview of Discovering and Adding Targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
For configuring the shared Oracle Software Library location and the Server Load Balancer, see Configuring a Software Library in the Oracle Enterprise Manager Cloud Control Administrator's Guide.