Skip Headers
Oracle® Enterprise Manager Grid Control Basic Installation Guide
11g Release 1 (11.1.0.1.0)

Part Number E15838-07
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

2 Installing Enterprise Manager System

This chapter describes how you can install a complete Enterprise Manager system using an existing, certified Oracle Database and Oracle WebLogic Server. In particular, this section covers the following:

Note:

Do NOT install the Enterprise Manager system on an OCFS file system. This file system is not supported.

Overview

The first installation type, Install a new Enterprise Manager system, offered by the installer enables you to install a complete Enterprise Manager system while utilizing an existing, certified Oracle Database to store Oracle Management Repository (Management Repository).

The existing, certified Oracle Database must be one of the databases listed in My Oracle Support note 412431.1.

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

Table 2-1 Installation Process for Installing Enterprise Manager System

Step 1

Installation of Oracle Management Service 11g Release 1

Creates an Oracle home in the Oracle Middleware Home location, and installs the Oracle Management Service (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 OMS Instance Base is created in the Oracle Middleware Home.

Step 6

Configuration of Core Components

Runs the Configuration Assistants to perform the following:

  1. Applying OMS-Related One-Off Patches: (Optional) Applies one-off patches to the Oracle home of the OMS (oms11g).

  2. Configuring SYSMAN Schema and MDS Schema: In the specified existing, certified Oracle Database, configures the SYSMAN schema and Metadata (MDS) schema, and creates these data files: mgmt.dbf, mgmt_ecm_depot1.dbf, mgmt_ad4j.dbf

  3. Configuring OMS: Configures the OMS and the independent instance where Enterprise Manager Grid Control is deployed.

  4. Add-on OMS Side Configuration: Configures the Virtualization Add-On detected in the Oracle home of the OMS (oms11g).

  5. Configures OCM (If Required): If you have chosen to configure Oracle Configuration Manager (OCM), then configures it in the Oracle home of the OMS (oms11g) and Oracle home of the Web tier (Oracle_WT).

  6. Applying Agent-Related One-Off Patches: (Optional) Applies one-off patches to the Oracle home of the Management Agent (agent11g).

  7. Configuring Management Agent: Configures the Management Agent to enable monitoring of targets, collection of information, and so on.

  8. Configures OCM (If Required): If you have chosen to configure Oracle Configuration Manager (OCM), then configures it in the Oracle home of the Management Agent (agent11g).

  9. Configures System Monitoring Plug-Ins: Configures the System Monitoring Plug-Ins detected in the Oracle home of the Management Agent (agent11g).


Note:

The installation process takes approximately 40 to 45 minutes to complete. The duration includes the time taken for running the prerequisite checks, placing the software binaries, creating the Oracle homes, and running the Configuration Assistants for configuring the core components.

Before You Begin

Before you begin, keep these points in mind:

Prerequisites

Before installing a complete Enterprise Manager system, 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 2-2 Prerequisites for Installing Enterprise Manager System

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 Enterprise Manager Grid Control only on certified operating systems as mentioned in My Oracle Support note 412431.1.

 

Package Requirements

Ensure that you install all the operating system-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.

 

Temporary Directory Space Requirements

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

 

File Descriptor Requirements

Ensure that you set the file descriptor 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

 

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.

Ensure that the existing, certified Oracle Database is not configured with Oracle Grid Infrastructure. This type of configuration is not supported.

(Optional) If you are installing using Oracle Database 11g Release 1 (11.1.0.7.0), then ensure that you apply the patch for bug# 9066130.

(Optional) If you are installing using Oracle Database 11g Release 2 (11.2.0.1.0), then ensure that you apply the patch for bug# 9002336 and 9067282.

Note: For information about these patches and their availability for different platforms, see My Oracle Support note 1073166.1.

 

Database Partitioning Requirements

Ensure that the existing, certified Oracle Database has the Partitioning Option enabled.

 

Existing Database Not to Be in QUIESCE Mode

Ensure that existing, certified Oracle Database is not in QUIESCE mode. To verify this, run the following SQL in the database:

select active_state from v$instance;

 

Existing Database Not to Have Database Control

(If you are upgrading from Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, which uses an Oracle Database where the Management Repository is already created, that is, where the Grid Control SYSMAN schema is already created, then ignore this prerequisite. This prerequisite applies only when you install Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0) using an existing, certified Oracle Database that has Database Control SYSMAN schema created, which you want to replace now with Grid Control SYSMAN schema.)

Ensure that your existing, certified Oracle Database does NOT have Database Control SYSMAN schema. If it has, that is, if your existing database is configured with Database Control, then deconfigure it.

  1. Verify whether your database has Database Control SYSMAN schema.

    To do so, log in to the database as SYS user and run the following query:

    SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME='SYSMAN'

    If the result of this query is 1, then the database has this schema, so deconfigure it.

  2. Before deconfiguring the Database Control, set the environment variable ORACLE_HOME to the Oracle home of the database, and ORACLE_SID to the SID of the database.

    For example, in bash shell, you can set them in the following way:

    export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1

    export ORACLE_SID=orcl

  3. Deconfigure the Database Control.

    To deconfigure Database Control for a standalone database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.

    $<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>

    To deconfigure Database Control for a Real Application Cluster (RAC) database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.

    $<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>

    Note: If the deconfigure operation hangs, then refer to My Oracle Support note 375946.1.

 

Existing Database Not to Have SYSMAN and SYSMAN_MDS Schema

(If you are upgrading from Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, which uses an Oracle Database where the Management Repository is already created, that is, where the Grid Control SYSMAN schema is already created, then ignore this prerequisite. This prerequisite applies only when you install Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0) using an existing, certified Oracle Database that has Database Control SYSMAN schema created, which you want to replace now with Grid Control SYSMAN schema.)

Ensure that your existing, certified Oracle Database does NOT have Enterprise Manager Grid Control SYSMAN schema and Metadata (MDS) schema.

  1. Verify whether your database has Enterprise Manager Grid Control SYSMAN schema and MDS schema.

    To do so, log in to the database as SYS user and run the following query:

    SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS');

    If the result of this query is 1, then the database has these schemas, so drop them.

  2. Before dropping the schema, set the environment variable LD_LIBRARY_PATH to the ORACLE_HOME/lib directory of the OMS. Also set the ORACLE_HOME to the Oracle home of the OMS.

  3. Drop the schema by running the following command from the Oracle home of the OMS.

    $<ORACLE_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -action dropall -dbUser <repository_database_user> -dbPassword <repository_database_password> -dbRole <repository_database_user_role> -mwHome <middleware_home> -mwOraHome <oms_oracle_home> -oracleHome <oms_oracle_home>

    If you are dropping the schemas that belong to a 10g Release 2 (10.2.x.x) Management Repository, then run previous command without these arguments: -mwHome <middleware_home> -mwOraHome <middleware_ora_home> -oracleHome <oracle_home>

    Note:

    - For Microsoft Windows, invoke RepManager.bat.

    - RepManager 11.1 supports -action dropall (drops SYSMAN as well as SYSMAN_MDS) and -action drop (drops only SYSMAN)

    - RepManager 10.2.0.5 supports -action drop (drops only SYSMAN)

  4. After dropping the schema, manually delete the database files mgmt.dbf and mgmt_ecm_depot1.dbf.

    You can find these files by running the following command as SYS:

    SELECT FILE_NAME FROM DBA_DATA_FILES WHERE UPPER (TABLESPACE_NAME) LIKE 'MGMT%';

 

Database Initialization Parameters Requirements

Ensure that you have correctly set the database initialization parameters for the existing, certified Oracle Database so that the Management Repository can be created. For information about setting the parameters, see Setting Database Initialization Parameters.

 

Fine-Grained Access Control Requirements

Ensure that the fine-grained access control option is set to TRUE in the existing, certified Oracle Database so that the Management Repository can be created. To verify this, run the following command:

select value from v$option where parameter = 'Fine-grained access control';

 

UNDO Tablespace Size Requirements

Ensure that the UNDO tablespace has a minimum space of 200 MB. To verify this, run the following query:

SELECT SUM(DECODE(autoextensible,'YES',200*1024*1024+1,bytes)) total

FROM dba_data_files f, dba_tablespaces s

WHERE s.contents = 'UNDO'

AND s.tablespace_name = f.tablespace_name;

Note: The result of this query is in bytes.

If the minimum space is less than 200 MB, then set it to 200 MB by running the following command:

alter database datafile <location datafile> resize 200M;

 

UNDO Tablespace and Temporary Tablespace Settings Requirements

Ensure that the UNDO tablespace and the TEMP tablespace are autoextensible in the existing, certified Oracle Database. To verify this, run the following command:

select count(*) from  dba_temp_files where tablespace_name='TEMP' and AUTOEXTENSIBLE  <> 'YES';

select count(*) from dba_data_files where tablespace_name='UNDOTBS' and AUTOEXTENSIBLE <> 'YES';

If the result of the query is 0, then the tablespace is autoextensible. If the result it not 0, then refer to Oracle Database Administrator's Guide available in the following location to make the tablespace autoextensible.

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

 

Archive Logging Settings Requirements

(Recommended) Ensure that you turn on archive logging in the existing, certified Oracle Database for any environment where continuity of data is important. To verify this, run the following command:

select log_mode from v$database;

 

Tablespace-Related Hard Disk Space Requirements

Ensure that you allocate a minimum of 1 GB hard disk space for the following tablespaces:

  • Management Tablespace (mgmt.dbf)

  • Configuration Data Tablespace (mgmt_ecm_depot1.dbf)

  • JVM Diagnostics Data Tablespace (mgmt_ad4j.dbf)

Oracle also recommends that you keep the auto-extend feature enabled for the tablespace data files.

Note that the space requirement increases as the number of monitored targets increase, along with the input/output performance demands on the storage devices.

 

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 that host. Otherwise, the installation can fail on the product-specific prerequisite check page.

The recommended format of the /etc/hosts file is <ip> <fully_qualified_host_name> <short_host_name>.

For example,

141.81.5.71 host1.foo.com host1

IPv6 entries are supported in the file for fresh installations of 11g Release 1 (11.1). However, they are not supported for upgrade from 10g Release 4 (10.2.0.4) or higher to 11g Release 1 (11.1).

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 host1

nslookup host1.foo.com

nslookup 141.81.5.71

 

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 theOracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

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 the chapter on configuring Enterprise Manager for firewalls in the Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

 

Internet Connection Requirements

Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

 

Setting Database Initialization Parameters

As one of the prerequisites, ensure that you set the initialization parameters as described in Table 2-3 and Table 2-4 for your existing, certified Oracle Database so that the Management Repository can be created. For information on how you can set these initialization parameters, see My Oracle Support note 1073647.1.

Important:

After you set the parameters, restart the database.

Table 2-3 Setting Fixed Initialization Parameters

Fixed Initialization Parameter Value

cluster_database

(Only for Oracle RAC Database)

TRUE

compatible

10.2.0.1.0 or higher

max_commit_propogation_delay

(Only for Oracle RAC Database)

0

remote_login_passwordfile

SHARED or EXCLUSIVE

statistics_level

TYPICAL

timed_statistics

TRUE

undo_management

AUTO

workarea_size_policy

AUTO


Table 2-4 Setting Variable Initialization Parameters

Variable Initialization Parameter Value

db_block_size

8192 or greater

instance_groups

As described in Oracle Database Reference Guide available at:

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

job_queue_processes

(For Installation) 10 or greater

(For Upgrade) If you are upgrading Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, then ensure that you set the value to 0 before upgrading. And after upgrading, reset it to the original value that existed before upgrading the product.

log_buffer

10485760 or greater

memory_target

(Only for Oracle Database 11g Release 2 (11.2) and higher)

As described in Oracle Database Reference Guide available at:

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

open_cursors

300 or greater

parallel_instance_groups

As described in Oracle Database Reference Guide available at:

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

processes

500 or greater

session_cached_cursors

200 or greater

sga_target

As described in Oracle Database Reference Guide available at:

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


Installation Procedure

To install a complete Enterprise Manager system, follow these steps:

  1. Invoke the installer by running the following command:

    <Software_Location>/runInstaller

    In this command, <Software_Location> is either <DVD> or <Software_Downloaded_Location>.

    Note:

    • For Microsoft Windows operating systems, run 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.

    • If you are planning to have multiple OMSes, then Oracle strongly recommends you to configure a shared file system loader so that a common location is maintained to store all the metric data files uploaded by the Management Agents. If you configure the central directory now, then all subsequent additional OMS installations, which connect to the same Oracle Database, will automatically be mapped to this central directory.

      To configure a shared file system loader, invoke the installer using the following command. Ensure that the location you specify is accessible and writable by all the OMSes.

      ./runInstaller SHARED_RECEIVE_DIRECTORY_LOCATION=<absolute_path_to_central_directory>

    • 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 following command:

      ./runInstaller START_OMS=false b_startAgent=false

      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

    • By default, GCDomain is the default name used for creating the WebLogic Domain.

      To override this, invoke the installer using the following command and specify a unique custom WebLogic Domain name:

      ./runInstaller WLS_DOMAIN_NAME=<Custom_Domain_Name>

  2. Specify My Oracle Support Details

    Specifying My Oracle Support Details

    (Optional) On the My Oracle Support Details screen, specify your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).

    If the host from where you are running the installation wizard does not have a connection to the Internet, then specify only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support.

    Note:

    For information about manually collecting the configuration information and uploading it to My Oracle Support, refer to the Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

  3. Click Next.

  4. Check for Updates

    Chedck for Software Updates

    On the Check for Updates screen, select one of the following sources from where the software updates can be automatically downloaded and installed while the installation of Enterprise Manager Grid Control is in progress. If you do not want to apply them now, then select Skip Software Updates.

    Note:

    If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Grid Control console and view the recommended security patches. To do so, log in to Enterprise Manager Grid Control, and click Preferences from the top-right corner of the screen. On the General page, from the left menu bar, click Preferred Credentials. On the Preferred Credentials page, from the My Oracle Support Preferred Credentials section, click Set Credentials. On the My Oracle Support Preferred Credentials page, specify the credentials and click Apply.
    • Select Download and install updates from My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there. Specify the My Oracle Support account user name and password to connect to the site.

      If a connection from your network to the Internet requires you to connect through a proxy, then select Proxy Settings and provide the proxy connection details. To test the connection, click Test Connection.

      Note:

      After specifying the My Oracle Support details, when you click Next, the installation wizard connects to My Oracle Support and checks for new software updates. The installer displays the new software updates that are found. If you want to install them, click Download Updates. If you do not want to install them, click Skip Updates.
    • (Recommended) Select Install updates from a staging location if the software updates are already downloaded and available in an accessible location. You can either specify the location or click Browse to search the host and select the location. Ensure that the location you specify or select leads to the Updates directory where the software updates are available.

      For example, if the software updates are available in /scratch/OracleHomes/Updates, then specify /scratch/OracleHomes/Updates.

    Note:

    For more information about software updates, and how you can manually download them, see the Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

    For information about the auto update feature and to know what patches are available in auto update, see My Oracle Support notes 1101208.1 and 1099123.1.

  5. Click Next.

    If you specified the My Oracle Support details in Step (4), the installer connects to My Oracle Support and checks for new software updates. The installer displays the new software updates that are found. If you want to install them, click Download Updates. If you do not want to install them, click Skip Updates.

    Similarly, if any patches (including one-off patches) were found, then the installer displays the Product Updates screen. On the Product Updates screen, select Apply Software Updates and click Next if you want to apply all the patches. Otherwise, deselect that option and click Next.

  6. Select Installation Type

    Select Installation Type

    On the Select Installation Type screen, select Install a new Enterprise Manager system.

  7. Click Next.

    If Enterprise Manager Grid Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears. For details, see step (8). Otherwise, the Check Prerequisites screen appears. For details, see step (10).

    If Enterprise Manager Grid Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:

    <system drive>\Program Files\Oracle\Inventory
    
  8. Specify Inventory Details

    Specify Inventory Details

    On the Oracle Inventory screen, do the following:

    1. Specify the full path to a directory where the inventory files and directories can be placed.

      Note:

      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

      Note:

      If this is the first Oracle product on the host, then the default central inventory location is /home/<user_name>/oraInventory. However, if you already have some Oracle products on the host, then the central inventory location can be found in the oraInst.loc file. The oraInst.loc file is located in the /etc directory for Linux and AIX, and in the /var/opt/oracle directory for Solaris, HP-UX, and Tru64.
    2. Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.

    Note:

    You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.
  9. Click Next.

  10. Check for Prerequisites

    Check for Prerequisites

    On the Check Prerequisites screen, check the status of the prerequisite checks run by the installation wizard is shown.

    The prerequisite checks can result in either Warning, Failed, or Succeeded status. If all the prerequisite checks succeed, then click Next to proceed to the next screen. However, if some checks result in Warning or Failed status, then do the following:

    • For the prerequisite checks with Failed status and Warning status, investigate and correct the problems before you proceed with the installation. You can also update the prerequisites with the latest software updates, if they have been released by Oracle, and rerun them. To understand how you can manually download the software updates to update the prerequisites, see Step (4).

    • After you correct the problems in your environment, you can return to this screen and click Check Again to check the prerequisites once again.

    • If you prefer to ignore all these checks and proceed, then select Ignore All. However, ignoring the prerequisite checks with Failed and Warning status might result in an unsuccessful installation, and therefore, Oracle recommends you to correct the problem and then proceed only after all the checks succeed.

  11. Click Next.

  12. Specify Installation Locations

    Specify Installation Locations

    On the Specify Install Locations screen, provide the information required for installing the core components of Enterprise Manager Grid Control and for storing the configuration files.

    • For Oracle Middleware Home Location, validate and accept the default middleware location, or select or specify another middleware location, which is present on the host where you are installing the product. 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.

      Note:

      Ensure that the Middleware Home you accept, select, or 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.
    • For OMS Instance Base Location, validate and accept the default instance base location, or specify another instance base location, which is present on the host where you installing the product and has write permission to store the configuration files of OMS.

      By default, the instance base is under the parent directory of the Oracle Middleware Home. And, by default, the instance home name is gc_inst. You can, however, edit this and specify a custom name.

      For example, 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 instance base is created in the Oracle Middleware Home itself.

    Note:

    For information about Oracle Middleware Home and OMS Instance Base Location, see the Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

  13. Click Next.

  14. Create WebLogic Server Domain

    Create WebLogic Server Domain

    On the Create WebLogic Server Domain screen, specify the WebLogic credentials and the Node Manager credentials.

    By default, the WebLogic Domain name is GCDomain, and the Node Manager name is nodemanager. These are non-editable fields. The installer uses this information for creating Oracle WebLogic Domain and other associated components such as the admin server, the managed server, and the node manager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.

  15. Click Next.

  16. Connect to Oracle Database

    Connect to Oracle Database

    On the Connect to Oracle Database screen, specify the fully-qualified name of the host where the existing database resides, the database's listener port and its service name or system ID (SID), and the SYS user account's password.

    The installer uses this information to connect to the existing, certified Oracle Database where the Management Repository can be configured.

  17. Click Next.

    Note:

    If you are connecting to an Oracle RAC database, and if you have specified the virtual IP address of one of its nodes, then the installation wizard prompts you with a Connection String dialog and requests you to update the connection string with information about the other nodes that are part of the cluster. Update the connection string and click OK. If you want to test the connection, click Test Connection.
  18. Configure Oracle Management Repository

    Configure Oracle Management Repository

    On the Configure Oracle Management Repository screen, do the following:

    1. For SYSMAN Password, specify a password for creating the SYSMAN user account. The SYSMAN user account is used for creating the SYSMAN schema, which holds most of the relational data used in managing Enterprise Manager Grid Control. SYSMAN is also the super administrator for Enterprise Manager Grid Control.

      Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value, one lowercase letter, and one uppercase letter.

    2. For Management Tablespace, specify the full path to the location where the data file for management tablespace (mgmt.dbf) can be stored. The installer uses this information for storing data about the monitored targets, their metrics, and so on. Ensure that the specified path leads up to the file name.

      For example, /u01/oracle/prod/oradata/mgmt.dbf

    3. For Configuration Data Tablespace, specify the full path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1.dbf) can be stored. This is required for storing configuration information collected from the monitored targets. Ensure that the specified path leads up to the file name.

      For example, /u01/oracle/prod/oradata/mgmt_ecm_depot1.dbf

    4. For JVM Diagnostics Data Tablespace, specify the full path to a location where the data file for JVM diagnostics data tablespace (mgmt_ad4j.dbf) can be stored. Ensure that the specified path leads up to the file name. Enterprise Manager Grid Control requires this data file to store JVM-related monitoring data.

      For example, /u01/oracle/prod/oradata/mgmt_ad4j.dbf

    Note:

    If you are configuring the Management Repository on a database that uses Oracle Automatic Storage Management (Oracle ASM) for storage, then when you specify the data file location, only the disk group is used for creating the tablespaces. For example, if you specify +DATA/a.dbf, then only +DATA is used for creating the tablespaces on Oracle ASM, and the exact location of the data file on the disk group is decided by Oracle Managed Files.
  19. Click Next.

  20. Secure Oracle Management Service

    Securing OMS

    On the Secure Oracle Management Service screen, do the following:

    1. For Registration Password, specify a password that can be used for authenticating new Management Agents that join the Enterprise Manager Grid Control system, and for permitting only secure Management Agents to communicate with the OMS, which is in locked state, via HTTPS protocol.

    2. Select Allow only secure agents to communicate with the OMS if you want to further enhance the security of communication between the OMS and the Management Agents.

      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 HTTP and HTTPS protocols, respectively. However, in a locked state, only secure Management Agents communicate with the OMS using HTTPS protocol.

      Select this option to turn the OMS to a locked state.

    3. Select Allow only secure access to the console if you want to secure the access and allow users to access the Enterprise Manager Grid Control console only using HTTPS protocol.

  21. Click Next.

  22. Customize Ports

    Customize Ports

    On the Customize Ports screen, customize the ports to be used for various components, and click Next.

    If staticports.ini file is passed during installation, then by default, the ports defined in the staticports.ini file are displayed. Otherwise, the first available port from the recommended range is displayed.

    Note:

    For information about the default ports that are assigned and the possibility of using custom ports instead of default ports, see the Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

    You can choose to retain the default port or customize it. To customize the ports, edit the port value in the Port column of the table, and specify a free custom port as recommended in the Recommended Port Range column.

  23. Click Next.

  24. Review

    Review

    On the Review screen, review the details you provided for the selected installation type.

    • If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

    • After you verify the details, if you are satisfied, click Install to begin the installation process.

  25. Once the software binaries are copied, you are prompted to run the allroot.sh script, and the oraInstRoot.sh script if this is the first Oracle product installation on the host. Open another window, log in as root, and manually run the scripts.

    If you are installing on Microsoft Windows operating system, then you will not be prompted to run this script. You will directly reach the Configuration Assistants screen as described in Step (26).

  26. On the Configuration Assistants screen, you should see the Configuration Assistants run for this installation type. If you see any failed Configuration Assistants and if you want to rerun them, then after rectifying the issues, select the failed ones and click Retry. If you prefer to rerun them later in standalone mode, then click Cancel to exit the installer.

    Note:

    If the Configuration Assistants fail, then review the relevant log files, resolve the issues, and rerun the Configuration Assistants as described in the Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide avaiable at:

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

    You can also refer to the Master Note for Enterprise Manager Grid Control Installation and Upgrade available in the same location. Once you access the URL, click the Release Notes tab, and from the Master Support Notes section, click HTML.

  27. On the End of Installation screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.

    For more information about this installation, refer to the following file available in the Oracle home of the OMS:

    $<ORACLE_HOME>/install/setupinfo.txt

After You Install

After you install, do the following:

  1. Verify the installation:

    1. Navigate to the Oracle home of the OMS 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 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 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

  2. To use a secure protocol (HTTPS) to connect to the Enterprise Manager Administration Server, do the following:

    1. Specify additional SSL arguments in the environment. To do so, set JAVA_OPTIONS to append the appropriate SSL arguments to use before invoking the ocmrepeaterctl script.

      For information about these JAVA options, access these URLs:

      http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/security.html#wp1077561

      http://download-llnw.oracle.com/docs/cd/E12840_01/wls/docs103/config_scripting/using_WLST.html#wp1093943

      Depending on whether a Demo or a Custom Trust certificate is used by the SSL realm, the SSL arguments will include the following:

      [
        [
          <
             -Dweblogic.security.TrustKeyStore=DemoTrust
            [ -Dweblogic.security.JavaStandardTrustKeystorePassPhrase=password ]   
          >
          |
          <
             -Dweblogic.security.CustomTrustKeyStoreFileName=filename          
             -Dweblogic.security.TrustKeystoreType=CustomTrust     
             [ -Dweblogic.security.CustomTrustKeystorePassPhrase=password ]
          >
        ]
        [  
          < -Dweblogic.security.SSL.hostnameVerifier=classname >
         |
          < -Dweblogic.security.SSL.ignoreHostnameVerification=true >
        ]
      ]
      
    2. Ensure that HTTP tunneling is enabled in the Administration Server. To verify this, log in to Oracle WebLogic Server Administration Console, and do the following:

      (i) From the Domain Structure panel on the left side of the Home page, expand Environment and click Servers.

      (ii) On the Summary of Servers page, from the Servers table, click the Admin Server.

      (iiI) On the Settings for <Admin_Server> page, click the Protocols tab, and then click the HTTP subtab.

      (iv) On the HTTP page, select Enable Tunneling, and click Save.

  3. 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".

  4. Configure your proxy server as described in Appendix H, "Setting Up Proxy Configuration for Oracle Management Service".

  5. For accessing the Enterprise Manager Grid Control console, ensure that you use only certified browsers as mentioned in My Oracle Support note 412431.1.

  6. (Optional) If you had not configured a shared file system loader while installing a complete Enterprise Manager system, and if you want to configure a shared location for it now, then run the following command from the Oracle home of the 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

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

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

  9. (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 and to know how you can reconfigure the Management Agent and discover all new targets, see Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

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