6 Adding Additional Oracle Management Service

This chapter describes how you can install an additional Oracle Management Service (OMS) in silent mode. In particular, this section covers the following:

Overview
Before You Begin
Prerequisites
Installation Procedure

Note:

The additional OMS you are installing must be installed on the same operating system as the other OMSes. Also ensure that the operating system and the Oracle home of the OMS are patched to the same level as the other OMSes.
Do NOT install the additional OMS on an OCFS file system. This file system is not supported.
If your first OMS, which was installed as part of the complete Enterprise Manager system installation, has add-ons installed, then do NOT follow the instructions outlined in this chapter. Instead, follow the instructions outlined in Chapter 8, "Installing Oracle Management Service Software Only in Silent Mode and Configuring Later".

Overview

The installation type, Add an additional Management Service, enables you to install an additional OMS to your existing Enterprise Manager Grid Control environment. This option is appropriate when you already have Enterprise Manager Grid Control with a certified Oracle Database, and when you want to have another OMS for the following reasons:

When you want to balance the load on the existing OMS
When your existing OMS is running out of CPU or RAM resources

However, note that you can have multiple OMSes, and still connect to just one Oracle Management Repository (Management Repository).

Table 6-1 describes the installation process and the software components that are installed or configured for this installation type.

Table 6-1 Process for Adding an Additional Oracle Management Service in Silent Mode

Step 1	Installation of Oracle Management Service 11g Release 1 Creates an Oracle home in the Oracle Middleware Home location, and installs the OMS software binaries in the new home. Oracle Middleware Home consists of the Oracle WebLogic Server home, and, optionally, one or more Oracle homes. If the Oracle Middleware Home is `/u01/app/Oracle/Middleware`, then the Oracle home for OMS is `/u01/app/Oracle/Middleware/oms11g`
Step 2	Installation of Oracle Management Agent 11g Release 1 Creates an Oracle home in the Oracle Middleware Home location, and installs the Oracle Management Agent (Management Agent) software binaries in the new home. If the Oracle Middleware Home is `/u01/app/Oracle/Middleware`, then the Oracle home for Management Agent is `/u01/app/Oracle/Middleware/agent11g`
Step 3	Installation of Oracle Web Tier 11g Release 1 Creates an Oracle home in the Oracle Middleware Home location, and installs the Web tier software binaries in the new home. If the Oracle Middleware Home is `/u01/app/Oracle/Middleware`, then the Oracle home for Web tier is `/u01/app/Oracle/Middleware/Oracle_WT`
Step 4	Installation of Oracle Common Directory Creates a common directory in the Oracle Middleware Home location for storing configuration files. If the Oracle Middleware Home is `/u01/app/Oracle/Middleware`, then the common directory is `/u01/app/Oracle/Middleware/oracle_common`.
Step 5	Configuration of Oracle Management Service Instance Base Location Creates an instance home for Enterprise Manager Grid Control in the parent directory of the Oracle Middleware Home for storing all OMS-related configuration files. By default, the instance home is gc_inst. You can, however, edit this and specify a custom name. If the Oracle Middleware Home is `/u01/app/Oracle/Middleware` and if you choose to retain the default instance home name, then the instance home location is `/u01/app/Oracle/gc_inst` If the parent directory of the Oracle Middleware Home does not have write permission, then the Oracle Management Service Instance Base is created in the Oracle Middleware Home.
Step 6	Configuration of Core Components Runs the Configuration Assistant tools to perform the following: Applying OMS-Related One-Off Patches: (Optional) Applies one-off patches to the Oracle home of the OMS (oms11g). Configuring OMS: Configures the OMS and the independent instance where Enterprise Manager Grid Control is deployed. Add-on OMS Side Configuration: Configures the Virtualization Add-On detected in the Oracle home of the OMS (oms11g). Configures OCM (If required; Only if you have chosen to configure it): Configures Oracle Configuration Manager (OCM) in the Oracle home of the OMS (`oms11g`) and Oracle home of the Web tier (`Oracle_WT`). Applying Agent-Related One-Off Patches: (Optional) Applies one-off patches to the Oracle home of the Management Agent (agent11g). Configuring Management Agent: Configures the Management Agent to enable monitoring of targets, collection of information, and so on. Configures OCM (If required; Only if you have chosen to configure it): Configures Oracle Configuration Manager (OCM) in the Oracle home of the Management Agent (agent11g). Configures System Monitoring Plug-Ins: Configures the System Monitoring Plug-Ins detected in the Oracle home of the Management Agent (agent11g).

Before You Begin

Before you begin, keep these points in mind:

Oracle Management Service 11g Release 1 is supported only with Enterprise Manager 11g Grid Control Release 1.
- If you are installing an additional Oracle Management Service 11g Release 1 to an existing Enterprise Manager 11g Grid Control environment, then follow the installation steps outlined in this chapter.
- If you are installing an additional Oracle Management Service 11g Release 1 to an existing Enterprise Manager 10g Grid Control Release 2 (10.2.X.X) environment, then first upgrade Enterprise Manager 10g Grid Control to Enterprise Manager 11g Grid Control, and then install the additional Oracle Management Service 11g.
You can install add-ons to this additional OMS only if the first OMS, which was installed as part of the complete Enterprise Manager system installation, has add-ons installed. And if your first OMS has add-ons installed, then do NOT follow the instructions outlined in this chapter. Instead, follow the instructions outlined in Chapter 8, "Installing Oracle Management Service Software Only in Silent Mode and Configuring Later".
This installation type only supports installation of OMS locally on the server where the installer is invoked, and does not support installing on multiple or remote hosts.
Do NOT install the additional OMS on an OCFS file system. This file system is not supported
You cannot install more than one OMS on a host.
By default, the upload ports and console ports as described in What Ports Are Used for Installation? are used.

However, if you want to use custom ports instead, then update the staticports.ini file as described in What Ports Are Used for Installation?, and pass the -staticPortsIniFile parameter while invoking setup.exe or runInstaller.

For example:

./runInstaller -silent -staticPortsIniFile <absolute_path_to_ini_file_location>/staticports.ini -responseFile <absolute_path_to_response_file> [-invPtrLoc <absolute_path_to_inventory_directory>]
By default, the software updates cannot be applied during installation because the INSTALL_UPDATES_SELECTION parameter in the response file is set to "skip". However, if you want to apply them during installation, then modify this parameter as described in Table 6-3.
Do not set the DISPLAY environment variable.
No environment variable specific to Enterprise Manager Grid Control needs to be set prior to installation. The ORACLE_HOME and ORACLE_SID variables should not be set; Oracle directories should not appear in the PATH.
Oracle offers code fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for code fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:

http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf

When determining supportability and certification combinations for an Enterprise Manager Grid Control installation, you must consider Enterprise Manager Grid Control's framework components as well as the targets monitored by Enterprise Manager Grid Control. Oracle recommends keeping your Grid Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license. For information about the certified combinations of Enterprise Manager Grid Control components and monitored targets, see My Oracle Support note.412431.1.
The presence or absence of EMKEY in the Management Repository does not matter, and the installation will proceed either way without any issues.
For accessing the Enterprise Manager Grid Control console, ensure that you use only certified browsers as mentioned in My Oracle Support note 412431.1.

Prerequisites

Before adding an additional OMS in silent mode, ensure that you meet the following prerequisites.

If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.

Table 6-2 Prerequisites for Adding an Additional Oracle Management Service in Silent Mode

Requirement	Description	Yes/No
Hardware Requirements	Ensure that you meet the hard disk space and physical memory requirements as described in Appendix A, "Meeting Hardware Requirements".
Operating System Requirements	Ensure that you install the OMS only on certified operating systems as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support. To access this matrix, follow these steps: Log in to My Oracle Support, and click the Certifications tab. On the Certifications page, in the Certification Search region, from the Product list, select Enterprise Manager Base Platform - OMS. From the Release list, select 11.1.0.1.0, and click Search. Ensure that you install the additional OMS on the same operating system as the other OMSes. Also ensure that the operating system and the Oracle home of the OMS arepatched to the same level as the other OMSes.
Package Requirements	Ensure that you install all the platform-specific packages as described in Appendix B, "Meeting Package, Kernel Parameter, and Library Requirements ".
Operating System Groups and Users Requirements	Ensure that you create the required operating system groups and users as described in Appendix C, "Creating Operating System Groups and Users Requirements".
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: You must use only a static IP address. If you use a dynamic IP address, the installation will fail.
File Descriptor Requirements	Ensure that you set the file descriptors to a minimum of 4096. To verify the current value set to the file descriptors, run the following command: `/bin/sh -c "ulimit -n`" If the current value is not 4096, then as a root user, update the `/etc/security/limits.conf` file with the following entries: `<UID> soft nofile 4096` `<UID> hard nofile 4096`
System Parameter Value Requirements for AIX	Ensure that the value set for the system parameter ncarg is 1024. To verify the value of ncarg, run the following command: `-lsattr -EH -l sys0 \| grep ncargs` If the value is less than 1024, then increase it to 1024 by running the following command: `chdev -l sys0 -a ncargs=1024`
Temporary Directory Space Requiremens	Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. For example, `/tmp` on UNIX hosts and `c:\Temp` on Microsoft Windows hosts.
Central Inventory Requirements	Ensure that you allocate 100 MB of space for the central inventory directory. Also ensure that the central inventory directory is not on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1.
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`
Shared File System Loader Location Requirements	If you have configured shared file system loader on the first OMS, ensure that the shared location is accessible and writable from the host where you are about to install an additional OMS. If you have not configured the shared filesystem loader on the first OMS, and want to configure it now, then do the following: Run the following command from the Oracle Home of the first OMS: `$<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir <Loader_Directory>` For example, `$<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir /share/recv` Note: If you already have additional OMSes, then run the same command on the hosts where those additional OMSes are running and specify the same shared location. Ensure that the shared location is accessible and writable from the host where you are about to install an additional OMS. To verify this, run the following command: On the first OMS, use a text editor to create a test file in the shared location, one for each additional OMS: `$ echo "test" > <oms name>.test` For example, `$ echo "test" > oms1.test` On the additional OMS host, verify that the above file is visible in the shared location and can be read and deleted: `$ cat <oms name>.test` `$ rm <oms name>.test` For example, `$ cat oms1.test` `$ rm oms1.test`
JDK Requirements	Ensure that you have the following version of JDK installed on the host where you are planning to install Enterprise Manager Grid control. Linux Platform (64 Bit): SUN JDK 1.6_18+ (On Linux 32-bit platforms, you need not install JDK because it is packaged by default with Oracle WebLogic Server) Solaris Platform: SUN JDK 1.6_18+ HP-UX Platform: JDK 6.0.05+ AIX Platform: JDK 1.6.0 SR6 Microsoft Windows Platform (64 Bit): SUN JDK 1.6_18 Download the JDK version for your platform from the platform vendor's Web site. For example, download SUN JDK 1.6_18+ for Linux platforms from Oracle Web site. Similarly, download the JDK for other platforms from other vendors' trusted Web sites. You can also refer to My Oracle Support note 1063587.1 for an example on installing JDK 1.6_18+ on Linux x86_64 platform. If you already have a JDK installed, then verify its version by navigating to the `<jdk>/bin` directory and running the following command. The output of this query should give you the complete version number. `java -fullversion` Note: JROCKIT is not supported.
Oracle WebLogic Server Requirements	Ensure that Oracle WebLogic Server 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1) is already installed on the host where you plan to install Enterprise Manager Grid Control. Ensure that the installation was a typical installation, and even if it was a custom installation, ensure that components chosen for custom installation were the same as the ones associated with a typical installation. Ensure that the installation was under the Middleware Home directory. For example, `/scratch/aime/Oracle/Middleware1/wlserver_10.3`. Ensure that no other Oracle Fusion Middleware products or components are installed in the Middleware Home directory where Oracle WebLogic Server 10.3.2 is installed. Enterprise Manager Grid Control will create a new domain in this Oracle WebLogic Server, and not use any of the existing domains. For information on installing Oracle WebLogic Server, see My Oracle Support note 1063762.1. For more information, downloads, demos, access the following URL: `http://www.oracle.com/technology/products/weblogic/index.html`
Oracle WebLogic Server Patch Requirements	Ensure that you apply patch ID `WDJ7` on Oracle WebLogic Server using the Oracle Smart Update utility. This patch fixes bugs 8990616, 9100465, and 9221722. For information on applying this patch, see My Oracle Support note 1072763.1. For information on Oracle Smart Update utility, see Oracle Smart Update Installing Patches and Maintenance Packs documentation available at: `http://www.oracle.com/technology/products/weblogic/index.html`
Existing Database Version Requirements	Ensure that the existing, certified Oracle Database is one of the databases listed in My Oracle Support note 412431.1. The database can reside either on the host where you are installing the product or on a remote host.
Existing Database Configuration Requirements	Ensure that Oracle Management Repository 11g Release 1 is already configured in your existing, certified Oracle Database.
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 write in the following locations: Oracle Middleware Home location Oracle Management Service Instance Base location Oracle Inventory Directory For more information about these locations, see Understanding Installation Directories. Ensure that you have write permission on the temporary directory where the executables will be copied. For example, `/tmp` or `c:\Temp.`
Oracle Inventory Location Requirements	Ensure that the Oracle Inventory (`oraInventory`) is not in a shared location. When you use the `oraInst.loc` file, ensure that the inventory location specified there is not pointing to a shared location. If it is, change it to a non-shared location.
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, then see Chapter 19, "Configuring Enterprise Manager for Firewalls".
Internet Connection Requirements	Oracle recommends that the host from where you are running the installation wizard have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

Installation Procedure

To add an additional OMS in silent mode, follow these steps:

Copy the following response file to an accessible location on your local host:

<Software_Location>/response/additional_mgmt_service.rsp

In this command, <Software_Location> is either <DVD> or <Software_Downloaded_Location>.
Edit the response file and specify appropriate values for the parameters described in Table 6-3.
Invoke the installer:
- If this is the first Oracle product you are installing on the host, then run the following command:
  
  ./runInstaller -silent -responseFile <absolute_path_to_response_file>/additional_mgmt_service.rsp [-invPtrLoc <absolute_path_to_inventory_directory>]
  Note:
  - For Microsoft Windows, invoke setup.exe instead of runInstaller.
  - In Microsoft Windows, if the path to the software download location contains a subdirectory name with two or more words and a space between each of the words, then ensure that the parent directory of such a subdirectory does not contain a file whose name matches with the first word of that subdirectory.
    
    For example, if the software is downloaded to C:\Documents and Settings, then before you invoke setup.exe, ensure that there are no files titled Documents (for example, shortcut files such as C:\Documents) in the C:\ drive.
  - The central inventory location you specify must NOT be on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1.
- Otherwise, run the following command:
  
  ./runInstaller -silent -responseFile <absolute_path_to_response_file>/additional_mgmt_service.rsp
Note:
- For Microsoft Windows platforms, run setup.exe instead of runInstaller
- After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer using the START_OMS=false and b_startAgent=false arguments.
  
  However, if you pass the START_OMS=false argument, the installation does not configure the EMCLI tool, and as a result, none of the EMCLI commands will work. Therefore, after the installation ends, you must manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface available at:
  
  http://www.oracle.com/technology/documentation/oem.html
- If any of the Configuration Assistants fail, then review the relevant log files, resolve the issues, and rerun the Configuration Assistants as described in What Do You Do When Configuration Assistants Fail?. You can also review the log files described in Appendix L, "Installation and Configuration Log Files".

Table 6-3 Response File Parameters for Adding an Additional Oracle Management Service

Parameter	Description
SECURITY_UPDATES_VIA_MYORACLESUPPORT	Specify `TRUE` if you want to download and install security updates. Then, specify the credentials for the following parameters: `MYORACLESUPPORT_USERNAME` `MYORACLESUPPORT_PASSWORD` Specify FALSE if you do not want to download and install security updates:
DECLINE_SECURITY_UPDATES	Specify `TRUE` if you want to decline the security updates. In this case, you should have specified False for `SECURITY_UPDATES_VIA_MYORACLESUPPORT`. SpecifyFALSE if you do not want to decline the security updates. In this case, you should have specified TRUE for `SECURITY_UPDATES_VIA_MYORACLESUPPORT`.
INSTALL_UPDATES_SELECTION	By default, this parameter is set to "skip" indicating that software updates cannot be installed during installation. However, if you want to install the software updates during installation, then set this parameter to "staged". Then, for the following parameter, specify the full path, which leads to the `Updates` directory, where the software updates are available: `STAGE_LOCATION`
ORACLE_MIDDLEWARE_HOME_LOCATION	Specify the location that was specified while installing Oracle WebLogic Server. For example, `u01/app/Oracle/Middleware`. Ensure that the middleware location has write permission to create the Oracle home for OMS and the Oracle home for Management Agent For example, if you accept the default location `/u01/app/Oracle/Middleware`, then the Oracle home for OMS is created as `/u01/app/Oracle/Middleware/oms11g`, and the Oracle home for Management Agent is created as `/u01/app/Oracle/Middleware/agent11g`. For more information about this location, see What Is Oracle Middleware Home?. Note: Ensure that the Middleware Home you specify here is used only for Enterprise Manager Grid Control. Ensure that no other Oracle Fusion Middleware products or components are installed in the same Middleware Home that is designated for Enterprise Manager Grid Control.
ORACLE_INSTANCE_HOME_LOCATION	By default, `gc_inst` is considered as the OMS Instance Base directory for storing all OMS-related configuration files. If you want to accept the default directory, then leave this field blank. However, if you want to have a custom directory, then specify the name of the custom directory. Whether you accept the default directory or specify a custom one, by default, the directory is created under the parent directory of the Oracle Middleware Home. For example, if the Oracle Middleware Home is `/u01/app/Oracle/Middleware`, then the directory is is `/u01/app/Oracle/gc_inst`. For more information about this location, see What Is Oracle Management Service Instance Base Location?.
ADMIN_SERVER_HOSTNAME	Specify the name of the host where the Admin Server is running. Admin Server is the server that was created when you installed the first Oracle Management Service 11g Release 1.
ADMIN_SERVER_PORT	Specify the port on which the Admin Server is running.
WLS_ADMIN_SERVER_USERNAME	Specify the default user name that will be used as the administrative user for the WebLogic Domain. By default, the user name is `weblogic`.
WLS_ADMIN_SERVER_PASSWORD	Specify the password for the WebLogic user account.
NODE_MANAGER_PASSWORD	Specify the node manager password.
DATABASE_HOSTNAME	Specify the fully-qualified name of the host where the existing database resides. For example, db.host.com.
LISTENER_PORT	Specify the listener port to connect to the existing database.
SERVICENAME_OR_SID	Specify the System ID (SID) of the existing database.
SYSMAN_PASSWORD	Specify the SYSMAN user account's password.
AGENT_REGISTRATION_PASSWORD	To secure the communication between the OMS and the Management Agents, specify a password. Note that you have to provide the same registration password for securing your Management Agents.
AGENT_REGISTRATION_CONFIRM_PASSWORD	Confirm the agent registration password.
LOCK_ORACLE_MANAGMENT_SERVICE	OMS always runs in a secure mode, and can further have a locked or an unlocked state. In an unlocked state, the Management Agents that are secure and the Management Agents that are not secure communicate with the OMS using HTTPS and HTTP protocols, respectively. However, in a locked state, only secure Management Agents communicate with OMS using HTTPS protocol. Specify `TRUE` if you want to lock the OMS running in a secure mode and further enhance the security of communication between the OMS and the Management Agents. Specify `FALSE` if you do NOT want to further enhance the security of communication between the OMS and the Management Agent.
ALLOW_ONLY_SECURE_ACCESS_TO_CONSOLE	By default, you can use either HTTP or HTTPS protocol to access the Enterprise Manager Grid Control console. Specify TRUE if you want to secure the access and allow users to access the console only using HTTPS protocol. Specify FALSE if you do NOT want to secure the access and allow users to access the console only using HTTPS protocol.
START_OMS	Specify TRUE if you want the OMS to start automatically after installation. Specify FALSE if you do NOT want it to start automatically.

After You Install

After you add an additional OMS, do these:

Verify the installation:
1. Navigate to the Oracle home of the OMS (oms11g) and run the following command to see a message that confirms that OMS is up and running.
  
  $<ORACLE_HOME>/bin/emctl status oms
2. Navigate to the Oracle home of the Management Agent (agent11g) and run the following command to see a message that confirms that the Management Agent is up and running.
  
  $<ORACLE_HOME>/bin/emctl status agent
3. Navigate to the Oracle home of the Management Agent (agent11g) and run the following command to see a message that confirms that EMD upload completed successfully.
  
  $<ORACLE_HOME>/bin/emctl upload
Note:
By default, you can access Enterprise Manager Grid Control only using the HTTPS protocol. If you want to use the HTTP protocol, then unlock it by running the following command from the Oracle home of the OMS:
emctl secure unlock -console
(Only for UNIX Operating Systems) Run the following scripts as a root user:
- If you have not specified the inventory location while invoking the installer and if this is the first Oracle product you just installed on the host, then run the oraInstRoot.sh script from the Central Inventory:
  
  $HOME/oraInventory/oraInstRoot.sh
  
  For example, if you are using SUDO to change to a root user, then you will run the following command:
```
/usr/local/bin/sudo $Home/oraInventory/oraInstRoot.sh
```
- Run the allroot.sh script from the Oracle home of the OMS (oms11g):
  
  <ORACLE_HOME>/allroot.sh
  
  For example, if you are using SUDO to change to a root user, then you will run the following command:
```
/usr/local/bin/sudo /scratch/OracleHomes/oms11g/allroot.sh
```
Refresh the Oracle WebLogic Server Domain, which hosts the Enterprise Manager application, so that the configuration changes made to the domain as a result of adding an additional OMS are reflected in the Grid Control console. To refresh the Oracle WebLogic Server Domain, follow these steps:
1. In Enterprise Manager Grid Control, navigate to the Home page for the Oracle WebLogic Server Domain that hosts the Enterprise Manager application. In most cases, the following is the direct URL to the Home page. If your domain name is not GCDomain, then replace that string with your domain name:
  
  [protocol]://[host]:[port]/em/faces/as/as/domainHome?target=/secFarm_GCDomain/GCDomain&type=weblogic_domain
2. From the WebLogic Domain menu, click Refresh WebLogic Domain.
3. On the Refresh WebLogic Domain page, click Continue.
Note:
This submits a WebLogic Domain Refresh job, which captures the domain configuration changes and reflects them in the Enterprise Manager Grid Control console. The job repeats itself once a day, and therefore, if you add any more additional OMSes or remove OMSes from your Enterprise Manager system in the future, this job automatically captures the configuration changes to the Oracle WebLogic Server Domain. You do NOT have to repeat this procedure every time you add an additional OMS.
Configure your proxy server as described in Appendix H, "Setting Up Proxy Configuration for Oracle Management Service".
Configure the Oracle Database and Oracle Automatic Storage Management (Oracle ASM) target for monitoring as described in Appendix G, "Configuring Database and ASM Targets for Monitoring".
For accessing the Enterprise Manager Grid Control console, ensure that you use only certified browsers as mentioned in My Oracle Support note 412431.1.
To view details related to the Management Repository, run the following command, as emoms.properties file is no longer supported.

emctl config oms -list_repos_details
(Optional) If you want to connect to another Management Repository, then shut down the OMS, run the following command, and then restart the OMS.

emctl config oms -store_repos_details (-repos_host <host> -repos_port <port> -repos_sid <sid> | -repos_conndesc <connect descriptor>) -repos_user <username> [-repos_pwd <pwd>] [-no_check_db]

Note:
On Linux, you need to double escape the connect descriptor using single and double quotes. However, on Microsoft Windows, you need not.
For example, on Linux:

emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc '"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb)))"' -repos_user sysman

For example, on Microsoft Windows:

emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb))) -repos_user sysman
(Optional) If you want to change the SYSMAN password, then shut down the OMS, run the following command, and then restart the OMS.

emctl config oms -change_repos_pwd
(Optional) If you want to discover the newly installed targets, if you want to convert the standalone Management Agent to a cluster-based Management Agent, if you want to discover the targets on the new nodes of the cluster, or if you want to reconfigure the cluster-based Management Agent, you must run the agentca script to reconfigure and discover all new targets.

For information about the agentca script, see What Is Agent Configuration Assistant Used For?.

For information about reconfiguring the Management Agent and discovering all new targets, see Appendix I, "Reconfiguring Oracle Management Agent and Discovering New Targets".
(Optional) If you want to enable the Request Monitoring feature for tracing transaction requests in WLS, you need JVM Diagnostics as well as Application Dependency and Performance (ADP) managers and agents configured against the target to be monitored.

For information about installing JVM Diagnostics and enabling the Request Monitoring feature, refer to the Oracle Enterprise Manager Administration Guide.

For information about enabling the ADP feature in Enterprise Manager Grid Control, refer to the Oracle Enterprise Manager Getting Started with Management Pack Plus for SOA.

Both these guides are available at:

http://www.oracle.com/technology/documentation/oem.html