Skip Headers
Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
12c Release 4 (12.1.0.4)

E24089-33
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Installing Additional Oracle Management Services in Silent Mode

Oracle recommends you to use the Add Management Service deployment procedure to install an additional Oracle Management Service (OMS). The Add Management Service deployment procedure offers a GUI-rich, interactive way of installing an additional OMS. For instructions, refer to 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 follow these steps to manually install an additional OMS in silent, non-interactive mode.

WARNING:

Do not install Enterprise Manager Cloud Control 12c on servers of SPARC series: T1000, T2000, T5xx0, and T3-*. For more information, see My Oracle Support note 1590556.1.

  1. 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 Software Library is read-write accessible from the remote host where you plan to install the additional OMS.

    • 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.

  2. On the remote host, perform a software-only installation of the additional OMS as described in Section 4.4.1.

    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.

  3. Deploy the plug-ins:

    • In GUI Mode (using the installer screen)

      Invoke the PluginInstall.sh script from the following location:

      $<OMS_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:

      $<OMS_HOME>/sysman/install/PluginInstall.sh -silent PLUGIN_SELECTION="{PLUGIN_ID1,PLUGIN_ID2}"

      For example,

      $<OMS_HOME>/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:

      1. 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

      2. 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:

      1. Manually download the plug-ins from the Enterprise Manager Download page on OTN, and store them in an accessible location.

        http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html

      2. Invoke the script with the following option, and pass the location where the plug-ins you want to install are available:

        In GUI Mode (using the installer screen):

        $<OMS_HOME>/sysman/install/PluginInstall.sh -pluginLocation <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):

        $<OMS_HOME>/sysman/install/PluginInstall.sh -silent PLUGIN_SELECTION="{PLUGIN_ID1,PLUGIN_ID2}"-pluginLocation <absolute_path_to_plugin_software_location>

  4. 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

  5. Export the configuration details from the first OMS. To do so, run the following command from the Oracle home of the first OMS, and pass the location where the configuration details can be exported as a file.

    $<OMS_HOME>/bin/emctl exportconfig oms -dir <absolute_path_to_directory>

  6. Copy the exported configuration details file from the first OMS host to the additional OMS host.

  7. Recover the configuration details onto the additional OMS. To do so, run the following command from the Oracle home of the additional OMS:

    $<OMS_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>]

    For example,

    $<OMS_HOME>/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_INSTANCE_HOST example.com

  8. (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 OMS home:

    $<AGENT_HOME>/sysman/install/agentDeploy.sh AGENT_BASE_DIR=<middleware_home>/agent OMS_HOST=<second_oms_host_name> EM_UPLOAD_PORT=<second_oms_port> AGENT_REGISTRATION_PASSWORD=<password> -configOnly

    Note:

    If you have Server Load Balancer (SLB) configured, then directly enter the host name and port number of the SLB. If SLB is not configured, then enter the secure upload port of the first OMS.
  9. Deploy the required plug-ins on the Management Agent.

    For information about deploying plug-ins, refer to the section Deploying Plug-Ins on Oracle Management Agent in the chapter Managing Plug-Ins, in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

  10. Import the trusted certificate on the additional OMS host, where you configured the Management Agent as described in Step (8). When prompted for a password, enter welcome.

    $<AGENT_HOME>/bin/emctl secure add_trust_cert_to_jks

  11. Manually discover the Oracle WebLogic Server target.

    1. Ensure that both the first and the additional OMS instances are up and running.

    2. In the Cloud Control console, from the Targets menu, select All Targets.

    3. On the All Targets page, search and click /EMGC_GCDomain/GCDomain/.

    4. On the EMGC_GCDomain home page, from the WebLogic Domain menu, select Refresh WebLogic Domain.

    5. 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, refer to the chapter 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, refer to Oracle Enterprise Manager Cloud Control Administrator's Guide.