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:

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, see Installing Additional Oracle Management Services in Silent Mode in 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 see What is a Deployment Size for Enterprise Manager Cloud Control in an Advanced Configuration? in the 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 Introduction to Installing an Enterprise Manager System.

Note:

If you are cloning the OMS from a complete Enterprise Manager installation, then the Management Agent that was installed with the Enterprise Manager system is not cloned to the destination host.

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, is 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 Performing Postinstallation Tasks After Adding an Additional Oracle Management Service.

• You can find the OMS and Management Agent entries in the /etc/oragchomelist file for all UNIX platforms except HPia64 and Solaris Sparc.

On HPia64 and 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 2, 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).

Requirement Description

Hardware Requirements

Ensure that you meet the hard disk space and physical memory requirements as described in Hardware Requirements for Enterprise Manager Cloud Control.

Operating System Requirements

• Ensure that you install Enterprise Manager Cloud Control only on certified operating systems as mentioned in the Enterprise Manager certification matrix available on My Oracle Support.

To access the Enterprise Manager certification matrix, follow the steps outlined in Accessing the Enterprise Manager Certification Matrix.

For information about platforms receiving future support, refer to My Oracle Support note 793512.1.

Note: Solaris zones are not supported.

• Ensure that the destination host (that is, the host on which you are installing an additional OMS) is running on the same operating system as that of the source host (that is, the host from where you are cloning the first OMS).

Note: If you use Oracle Solaris 10, then ensure that you have update 10 or higher installed. To verify whether it is installed, run the following command:

cat /etc/release

You should see the output similar to the following. Here, s10s_u10 indicates that update 10 is already installed.

Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC

Package, Kernel Parameter, and Library Requirements

Ensure that you install all operating system-specific packages, kernel parameters, and libraries as described in Package, Kernel Parameter, and Library Requirements for Enterprise Manager Cloud Control.

Operating System Groups and Users Requirements

Ensure that you create the required operating system groups and users as described in Creating Operating System Groups and Users for Enterprise Manager Cloud Control.

NFS Mount Point Location Requirements

• If you are planning to install on an NFS-shared location, then do the following:

• Ensure that root squash is enabled with execute permission on that host where you want to perform the installation.

• Ensure that the Access Control List processing is disabled for the NFS mount point. In other words, the mount point must be defined with the noacl option in the /etc/fstab file. Otherwise, the installation can fail.

To verify this, run the following command as the install user to check the contents of the /etc/fstab file. Verify if the mount point on which you plan to install Enterprise Manager has the noacl option set.

cat /etc/fstab

For example, in the following output, the mount point /u01/app/share1 has the noacl option set. In this case, you are ready to proceed with the installation.

nas.example.com:/export/share1 /u01/app/share1 nfs rw,bg,rsize=32768,wsize=32768,hard,nointr,tcp,noacl,vers=3,timeo=600 0 0

If you do not have the noacl option set, then contact your System Administrator to make the required changes in the /etc/fstab file.

• If you are planning to install on an NFS-shared middleware location, and if that location is mounted with the option concurrent I/O (CIO), which allows multiple reads and writes to a file at the same time, then the installation will fail reporting linking errors.

If you verify the mounted file system, you will see the following CIO option enabled.

node mounted mounted over vfs date options

/dev/host1 /host1/oracle jfs2 Feb 14 18:20 rw,cio,log=/dev/xd891loglv

If you have the CIO option enabled, then unmount the drive, disable the CIO option, and then re-mount the drive.

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.

Existing High Availability Configuration Requirements

Ensure that you have met all Oracle-recommended high availability requirements in your environment. For more information, see Discovering and Adding Single Instance High Availability Service Targets 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.

• Create a shared directory on any server, and ensure that it is mounted and made visible on the host where your first OMS is running and also on other hosts where you plan to install additional OMS instances.

For the configuration to be successful, you can reserve approximately 400 MB of hard disk space for the shared directory. However, Oracle recommends that you scale it to at least 12 GB eventually, and ensure that it can be extended further in the future because the space utilization increases over a period of time as you install additional plug-ins and create more reports.

• Configure the shared storage location by running the following command. Provide the path to the shared storage location you just created. Ensure that the shared location you provide is owned by the user account that was used for installing the first OMS. Also ensure that the user account has read and write permission to the shared location. You will be prompted for administrator user account password and SYSMAN account password.

emctl config oms -bip_shared_storage -cluster_volume <shared_location> -config_volume <shared_location>

For example,

emctl config oms -bip_shared_storage -cluster_volume /scratch/aime/examplehost/BIP/cluster -config_volume /scratch/aime/examplehost/BIP/config

Existing Oracle Management Agent Requirements

Ensure that the destination host already has a Management Agent installed, and ensure that it is up and running.

• If this OMS is being installed using an alias host name, ensure the Management Agent was installed using the alias host name.

• If this Management Agent was manually installed on the destination host, then ensure that the installation was completed by running the root.sh script. Otherwise, the Add Management Service deployment procedure will not be able to run some scripts that require root permission.

Processes Parameter Value Requirement

Check the number of OMS instances already installed in your environment, check the Processes parameter value that is required for the current deployment size (SMALL, MEDIUM, or LARGE), and set the Processes parameter in the Management Repository to a value that is appropriate for the additional OMS you are now installing.

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:

SELECT count(*) AS count FROM gc_oms_info

To check the Processes parameter value required per OMS for your deployment size, see the small configuration, medium configuration, and large configuration sections of the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

For example, if you have one OMS in your environment, and if the deployment size is SMALL, then the Processes parameter value to be set is computed this way: (1 + 1) x 300 = 600.

Status of Oracle Configuration Manager

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

1. Set the environment variable ORACLE_CONFIG_HOME to the following location:

$<OMS_INSTANCE_HOME>/em/EMGC_OMS1 For example, set ORACLE_CONFIG_HOME=C:\win0224\emgc\gc_inst\em\EMGC_OMS1 2. Navigate to the following location: $<ORACLE_HOME>/oracle_common/ccr/bin

3. Stop OCM by running the following script:

emCCR.bat stop

4. Set the environment variable ORACLE_CONFIG_HOME to the following location:

$<OMS_INSTANCE_HOME>/WebTierIH1 For example, set ORACLE_CONFIG_HOME=C:\win0224\emgc\gc_inst\WebTierIH1 5. Navigate to the following location: $<ORACLE_HOME>/Oracle_WT/ccr/bin

6. Stop OCM by running the following script:

emCCR.bat stop

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 ADD_MANAGEMENT_SERVICE_<TimeStamp>.

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.

Shared Directory Space Requirements

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.

Middleware home Location Requirement

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 /u01/software/em13c/oraclehome/, ensure that the same path does not already exist on the destination host.

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 .lck files in the Oracle home. Presence of such files indicates that there are installation operations in progress.

$<ORACLE_HOME>/sysman/prov/agentpush/ Server Load Balancer Requirements • Ensure that you have installed a Server Load Balancer (SLB) in your network and configured it to work with the first OMS. All Management Agents communicating with the first OMS must be uploading data only through this SLB. If you have not configured the SLB yet to work with the first OMS, then configure it now. For information about configuring an SLB, see Configuring an SLB in the Oracle Enterprise Manager Cloud Control Administrator's Guide. • In order to configure your OMS instances in an active/active configuration behind an SLB, your SLB must meet the following requirements: (a) Supports multiple virtual server ports - Enterprise Manager typically requires that up to 4 ports are configured on the SLB (Secure Upload, Agent Registration, Secure Console, Unsecure Console). (b) Supports persistence - HTTP and HTTPS traffic between the browser and the OMS requires persistence. (c) Supports application monitoring - The SLB must be capable of monitoring the health of the OMS instances and detecting failures, so that requests will not be routed to OMSes that are not available. SLB Pools and Their Association with the First OMS On the SLB, using its administration console, create the following SLB pools and add the first OMS host to them: • Secure Upload Pool (add the host using the port configured for the Secure Upload service) • 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 Secured Console service) • (Optional) Unsecure Console Pool (add the host using the port configured for the Unsecured Console service) Virtual Servers and Their Association with the SLB Pools On the SLB, using its administration console, create the following virtual servers and associate them with the SLB pools. • Secure Upload Virtual Server with port 1159 (associate it with Secure Upload Pool) • Agent Virtual Server with port 4889 (associate it with Agent Registration Pool) • Secure Console Virtual Server with port 7788 (associate it with Secure Console Pool) • (Optional) Unsecure Console Virtual Server with port 80 (associate it with Unsecure Console Pool) For instructions, see Oracle Enterprise Manager Cloud Control Administrator's Guide. SLB Monitors and Their Association with the First OMS On the SLB, using its administration console, create the following SLB monitors and associate the first OMS host with them: • Secure Upload Monitor (associate the host using the port configured for the Secure Upload service) • 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 Secured Console service) • (Optional) Unsecure Console Monitor (associate the host using the port configured for the Unsecured Console service) Software Library Accessibility Requirements 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, see Configuring a Software Library in the Oracle Enterprise Manager Cloud Control Administrator's Guide. Installing User Requirements Ensure that you meet the following requirements: • (For UNIX only) The installation must NOT be run by a root user. • (For Microsoft Windows only) User must be part of the ORA-DBA group and have administrator permissions. • (For Microsoft Windows only) User must belong to the DBA group, and have permissions to perform the following: Act as part of the operating system, Create a token object, Log on as a batch job, and Adjust memory quotas for a process. To verify whether the agent user has these rights, from the Start menu, click Settings and then select Control Panel. From the Control Panel window, select Administrative Tools, and from the Administrative Tools window, select Local Security Settings. In the Local Security Settings window, from the tree structure, expand Local Policies, and then expand User Rights Assignment. Permission Requirements Ensure that you are able to access and read/write in the following locations: • Oracle Middleware home Oracle Middleware home is a directory on the source host that contains the OMS you are cloning, the Oracle WebLogic Server home, the Web tier instance files, and so on. • Oracle Management Service Instance Base location Oracle Management Service Instance Base is a directory on the source host that contains configuration files related to the OMS. The instance base is typically under the parent directory of the Middleware home. • Source Staging location Source staging location is a location on the source host that is used for staging the cloned ZIP files before copying them to the destination host. • Destination Staging location Destination staging location is a location on the destination host that is used for staging the cloned ZIP files when they are copied over from the source host. • Temporary directory on the source host where the executables will be copied. For example, /tmp or c:\Temp. Proximity Requirements 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. Firewall Requirements If you have a firewall in your environment, see 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. Central Inventory Requirements • Ensure that you allocate 100 MB of space for the central inventory directory. • For a typical non-HA environment, the Central Inventory (oraInventory) can be in a shared or non-shared location. If you use a shared location, then ensure that only one shared location is maintained per host, and no two hosts update the same shared location. One inventory file is meant only for one host, so it must not be shared and edited by other hosts. When you use the /etc/oraInst.loc file, ensure that the inventory location specified there is not pointing to such a location. If you have configured a shared location that is common for two or more hosts, then switch over to a non-shared location. • For a typical HA environment with primary and standby disaster recovery sites using storage replication and alias host names, the Central Inventory (oraInventory) for software installed on the shared storage using the alias host name should be located in a shared location that is common between the OMS host in the primary site and the OMS host in the standby site. This shared location should be located on the replicated storage so that the oraInventory can be accessed from the active site for software maintenance activities. UMASK Value Requirements Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file. For example: • Bash Shell $ . ./.bash_profile

• Bourne or Korn Shell

$. ./.profile • C Shell % source ./.login File Descriptor Requirements • Ensure that the maximum user process limit is set to greater than 13312. To verify the current value set, run the following command: ulimit -u If the current value is not 13312 or greater, then contact your system administrator to set it to at least 13312. • Ensure that you set the soft limit of file descriptor to a minimum of 4096 and hard limit less then or equal to 16384. To verify the current value set, run the following commands: For Soft Limit: /bin/sh -c "ulimit -n" For Hard Limit: /bin/sh -c "ulimit -Hn" If the current value is not 4096 or greater, then as a root user, update the /etc/security/limits.conf file with the following entries: <UID> soft nofile 4096 <UID> hard nofile 16384 Host File Requirements Ensure that the host name specified in the /etc/hosts file is unique, and ensure that it maps to the correct IP address of the host. Ensure that localhost is pingable and resolves to 127.0.0.1 (or resolves to ::1 for IPv6 hosts). The following is the recommended format of the /etc/hosts file: <ip> <fully_qualified_host_name> <short_host_name> For example, 127.0.0.1 localhost.localdomain localhost 172.16.0.0 myhost.example.com myhost 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: nslookup myhost nslookup myhost.example.com nslookup 172.16.0.0 If alias host names are implemented in /etc/hosts, then it is not necessary to be able to use DNS to resolve the alias host name on which you want to install the OMS. Browser Requirements • Ensure that you use a certified browser as mentioned in the Enterprise Manager certification matrix available on My Oracle Support. To access the Enterprise Manager certification matrix, follow the steps outlined in Accessing the Enterprise Manager Certification Matrix. • If you use Microsoft Internet Explorer 8 or higher, do the following: • Turn off the compatibility view mode. To do so, in Microsoft Internet Explorer, from the Tools menu, click Compatibility View to disable it if it is enabled. Also, click Compatibility View Settings and deregister the Enterprise Manager Cloud Control console URL. • Enable XMLHTTP. To do so, from the Tools menu, click Internet Options. Click the Advanced tab, and under the Security heading, select Enable native XMLHTTP support to enable it. ## 7.4 Adding an Additional Oracle Management Service To add an additional Oracle Management Service (OMS), follow these steps: 1. From the Enterprise menu, select Provisioning and Patching, then select Procedure Library. 2. On the Deployment Procedure Manager page, in the Procedure Library tab, from the table, select Add Oracle Management Service, and then, click Launch. 3. 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. 4. On the Select Destination page, do the following: 1. 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 Note: Do NOT enter the IP address of the managed host. Enter a fully qualified domain name that is registered in the DNS and is accessible from other network hosts, or enter an alias host name that is defined in the /etc/hosts file on all the OMS instances at this site. 2. 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 3. 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 Selecting Credentials. 4. Click Next. 5. On the Options page, do the following: 1. 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: 1. From the Targets menu, select All Targets. 2. On the All Targets page, click the name of the Management Agent that is running on the source OMS host. 3. On the home page, from the Agent menu, select Properties. 4. On the Properties page, from the Show list, select Advanced Properties. 5. 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. 2. 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. 3. 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. 4. Click Next. 6. 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 Getting Started with Oracle SuperCluster in the Oracle Enterprise Manager Cloud Control Administrator Guide. 7. 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. ### 7.4.1 Selecting Credentials 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 Preferred Credential 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. Named Credential 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. New Credentials 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. ## 7.5 Performing Postinstallation Tasks After Adding an Additional Oracle Management Service 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: 1. (Applicable only if you had stopped the Oracle Configuration Manager as a prerequisite on Microsoft Windows) Start Oracle Configuration Manager: 1. 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

2. Navigate to the following location:

$<ORACLE_HOME>/oracle_common/ccr/bin For example, cd /u01/software/em13c/oraclehome/oracle_common/ccr/bin 3. Start OCM by running the following script: emCCR.bat start 4. 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

5. Navigate to the following location:

$<ORACLE_HOME>/Oracle_WT/ccr/bin For example, cd /u01/software/em13c/oraclehome/Oracle_WT/ccr/bin 6. Start OCM by running the following script: emCCR.bat start 2. (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> -slb_jvmd_http_port [-console -lock -lock_console]

Note:

For secure connections (HTTPS) use the -slb_jvmd_https_port option instead of -slb_jvmd_http_port.

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 -slb_jvmd_http_port -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, see Configuring an SLB in the Oracle Enterprise Manager Administration Guide.

3. (Only for UNIX Platforms) Run <ORACLE_HOME>/root.sh as a root user on the destination host.

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

1. Stop the OMS:

<ORACLE_HOME>/bin/emctl stop oms

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

3. 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
MaxRequestsPerChild 0
AcceptMutex fcntl
LockFile /u01/em/ohs_locks/http_lock
</IfModule>b

4. Save the changes.

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

6. Start the OMS:

<ORACLE_HOME>/bin/emctl start oms

5. 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, see Discovering and Adding Host and Non-Host Targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

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

7. 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, see EMCTL Security Commands in the Oracle Enterprise Manager Cloud Control Administrator's Guide.

8. (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