2 Things to Know

How Do You Access the Software from DVD?

You can obtain the Enterprise Manager Grid Control software from the product DVD that is available through Oracle Service Delivery Managers or Oracle Sales Representatives. The software may be available either on a single DVD or on multiple DVDs depending on the operating system.

This section covers the following:

• Accessing Software from DVD

• Setting Mount Point for DVD

How Do You Procure the Software from Oracle Technology Network?

You can procure the Enterprise Manager Grid Control software from OTN. The software available on OTN is archived using Info-ZIP's highly portable ZIP utility. The software may be available either in a single ZIP file or in multiple ZIP files depending on the operating system. After downloading the software, you will need the UNZIP utility to extract the files.

This section covers the following:

• Downloading Software

• Verifying File Size

• Extracting Contents

• Verifying Platform Information

<?xml version="1.0" standalone="yes" ?>
<ORACLEHOME_INFO>
<ARU_PLATFORM_INFO>
<ARU_ID>46</ARU_ID>
<ARU_ID_DESCRIPTION>Linux x86</ARU_ID_DESCRIPTION>
</ARU_PLATFORM_INFO>
</ORACLEHOME_INFO>

Automatically Downloading Management Agent Software Using Download Agent Software Application

This section describes how you can use the Download Agent Software application, which is available in Enterprise Manager Grid Control, to download the Management Agent software. In particular, this section covers the following:

• What Is Agent Download Application?

• What Prerequisites You Must Meet?

• How Do You Download the Management Agent Software?

Manually Downloading Management Agent Software from OTN

To manually download the Management Agent software from OTN, access the following URL:

http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html

What Different Installation Modes Can You Use?

You can install Enterprise Manager Grid Control or any of its core components either in an interactive, graphical mode or in a silent mode.

In both these modes, you can perform a software-only installation. A Software-Only installation is an approach that enables you to install only the software binaries of Enterprise Manager Grid Control or an OMS, that is, without any configuration to the installation. This is best suited when you want to install the software at one point and configure it later.

What Is Enterprise Manager Grid Control Installation Wizard?

Enterprise Manager Grid Control Installation Wizard is a Java-based wizard that helps you install or upgrade Enterprise Manager Grid Control or any of its core components in a graphical mode. If you are installing Enterprise Manager Grid Control or any of its core components for the first time, then Oracle strongly recommends you to use this installation wizard.

Figure 2-1 describes the key elements of the installation wizard.

Figure 2-1 Enterprise Manager Grid Control Installation Wizard

What Installation Types Are Offered by the Installation Wizard?

Table 2-2 describes the installation types offered by the Enterprise Manager Grid Control installation wizard.

What Ports Are Used for Installation?

This section describes the default ports that are honored while installing Enterprise Manager Grid Control. In particular, this section covers the following:

• What Default Ports Are Used?

• How Can You Customize Ports?

• What Precautions Must You Take While Customizing Port Numbers?

How Can You Change the Language Used in Enterprise Manager Grid Control Console?

By default, the Enterprise Manager Grid Control Installation Wizard installs Enterprise Manager Grid Control console with English language. If you want to view them in another language, then select the required languages in the Select Languages screen of the installation wizard.

When you select additional languages to install, the installation wizard also installs fonts required to display the languages.

For some components, languages are installed only if you select them during installation. In this case, if you access the application in a language that is not available, it reverts to the locale language.

For other components, available languages are installed regardless of what you select during installation. In this case, however, fonts are installed only for the languages that are explicitly selected. When you access the application, it uses text in your language because the language was installed. However, if you do not have the appropriate fonts to render the text, the text appears as square boxes. This usually applies to the Chinese, Japanese, and Korean languages.

What Data Files Are Created While Configuring Oracle Management Repository?

The following are the data files created while configuring Oracle Management Repository:

• mgmt_ecm_depot1.dbf

• mgmt.dbf

• mgmt_ad4j.dbf

How Do You Delete Data Files?

To delete the data files, you must drop the SYSMAN/MDS schema. To do so, run 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>

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%';

How Do I Install Oracle WebLogic Server?

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

How Do I Verify Whether Oracle WebLogic Server Is Installed?

As a prerequisite, you must have Oracle WebLogic Server 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1) for installing Enterprise Manager Grid Control.

To verify whether Oracle WebLogic Server is installed, check the following file in the Oracle home of the Oracle WebLogic Server:

$<ORACL_HOME>/logs/log.txt

The following is the sample output of the log.txt file:

release  10.3.2.0 [Added]
    |_____Common Infrastructure Engineering 6.8.0.0 [Added]
    |    |_____Uninstall [Added]
    |    |_____Patch Client [Added]
    |    |_____Patch Attachment Facility [Added]
    |    |_____Clone Facility [Added]
    |_____WebLogic Server 10.3.2.0 [Added]
    |    |_____Core Application Server [Added]
    |    |_____Administration Console [Added]
    |    |_____Configuration Wizard and Upgrade Framework [Added]
    .
    .
    .
    .

Is Oracle WebLogic Server Cluster Supported?

Oracle WebLogic Server cluster consists of multiple Oracle WebLogic Servers running simultaneously and working together to provide increased scalability and reliability. A cluster appears to be a single Oracle WebLogic Server instance. The server instances that constitute a cluster can run on the same host, or be located on different hosts.

You can install Enterprise Manager Grid Control on an Oracle WebLogic Server Cluster, however, you cannot take advantage of the cluster configurations.

Is the Existing Admin Server in Oracle WebLogic Server Used?

To install Enterprise Manager Grid Control, the Enterprise Manager Grid Control Installation Wizard uses the software binaries of the existing Oracle WebLogic Server, however, it does not use the existing Admin Server that is available. The Enterprise Manager Grid Control Installation Wizard create a new Admin Server and deploys the Enterprise Manager Grid Control software to it.

When and Why Do You Need Oracle WebLogic Server Credentials?

While installing or upgrading Enterprise Manager Grid Control and while upgrading an additional OMS, you are prompted to specify the Oracle WebLogic Server credentials (user name and password). The credentials are used for creating Oracle WebLogic Domain and other associated components such as the Admin Server, the managed server, and the node manager.

The WebLogic user name is the default user name that will be used as the administrative user for the WebLogic Domain. By default, the user name is weblogic. And the WebLogic password is the password for this default administrative user account.

When and Why Do You Need Node Manager Credentials?

While installing or upgrading Enterprise Manager Grid Control and while upgrading an additional OMS, you are prompted to specify the Node Manager password for the default Node Manager user account, which is nodemanager. The password is used for configuring 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.

How Do You Find Admin Server Port While Installing an Additional OMS

To install an additional OMS, you might need to know the port of the Admin Server that is used by the first OMS. To find the port, view the value set for the AS_HTTPS_PORT parameter in the emgc.properties file. This file is available in the Oracle Management Service Instance Base location.

For example,

/u01/app/Oracle/gc_inst/user_projects/domains/EMGC_DOMAIN/em/EMGC_OMS1/emgc.properties

How Do You Verify Whether Admin Server Is Running?

To install an additional OMS, the Admin Server that is used by the first OMS must be up and running. To verify whether the Admin Server is running, access the Admin Server console using the following URL:

http://host:port/console

Here, host and port are values specified in the EM_INSTANCE_HOST and AS_HTTPS_PORT parameters, respectively, in the emgc.properties file. This properties file is available in the following location, that is, in the Oracle home of the OMS (first OMS) that was initially installed:

<ORACLE_HOME>/gc_inst/user_projects/domains/EMGC_DOMAIN/em/EMGC_OMS1/emgc.properties

How Do You Start Admin Server?

To install an additional OMS, the Admin Server that is used by the first OMS must be up and running. If it is not running, then start the Admin Server using the instructions outlined in the Oracle Fusion Middleware Administrator's Guide 11g Release 1 (11.1.1).

Alternatively, you can start the Admin Server by running the following command. Although the command is used essentially to start the OMS, the command in turn starts the Admin Server on which that OMS is running. So run this command even if you know that the OMS is already running.

emctl start oms

What Is Oracle Inventory Directory?

If Enterprise Manager Grid Control is the first Oracle product that you are installing, then the Enterprise Manager Grid Control Installation Wizard prompts you to specify an inventory directory (also called the oraInventory directory).

This inventory directory is used by the installation wizard to place all the installer files and directories on the host. The installation wizard automatically sets up subdirectories for each Oracle product to contain the inventory data.

You can specify the OraInventory directory in two ways:

• While installing Enterprise Manager Grid Control using the installation wizard, you can specify the OraInventory directory in the Oracle Inventory screen. When you specify it in this screen, you must also select the appropriate operating system group name that will own the OraInventory directories. The group you select must have write permission on the OraInventory directories.

• While installing Enterprise Manager Grid Control in silent mode, that is, without using the installation wizard, you can specify the OraInventory directory using the -invPtrLoc parameter. This parameter considers the path to a location where the inventory pointer file (oraInst.loc) is available. For example, ./runInstaller -invPtrLoc /scratch/OracleHomes/oraInst.loc

If you already have an Oracle product installed on the host, then the installer uses the existing OraInventory directory that was created while installing that Oracle product. Ensure that you have write permission on that directory. To do so, run the installer as the same operating system user as the one who installed the other Oracle product.

What Is Oracle Middleware Home?

While installing Enterprise Manager Grid Control or an additional OMS using the Enterprise Manager Grid Control Installation Wizard, you are required to specify the Oracle Middleware Home location.

Oracle Middleware Home is the parent directory that has the Oracle WebLogic Server home, the Web tier instance files, and, optionally, one or more Oracle homes. This is where the OMS and the Management Agent are deployed.

The installation wizard uses its built-in algorithm to identify this location, and displays it for you to validate. By default, the following is the Oracle Middleware Home location:

/u01/app/Oracle/Middleware

You can either accept the default location or select another location that has write permission.

What Is Oracle Management Service Instance Base Location?

While installing Enterprise Manager Grid Control or an additional OMS using the Enterprise Manager Grid Control Installation Wizard, you are required to specify the Oracle Management Service Instance Base Location.

Oracle Management Service Instance Base Location is the directory under the parent directory of the Oracle Middleware Home, where the configuration files of OMS are stored. 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 itself.

The installation wizard uses its built-in algorithm to identify this location, and displays it for you to validate. If the Oracle Middleware Home was /u01/app/Oracle/Middleware/, then by default, the following is the Oracle Management Service Instance Base Location:

/u01/app/Oracle/gc_inst

You can either accept the default location or specify another location that has write permission.

What Is Oracle Home?

Oracle home is the directory where OMS and Management Agent are installed. By default, the Oracle home of OMS is oms11g and the Oracle home of Management Agent is agent11g. Both these Oracle homes are created in the Oracle Middleware Home.

For example, if you specify /u01/app/Oracle/Middleware as the Oracle Middleware Home, then the Oracle home of the OMS is created as /u01/app/Oracle/Middleware/oms11g, and the Oracle home of the Management Agent is created as /u01/app/Oracle/Middleware/agent11g.

What Is Installation Base Directory?

While installing a Management Agent using the Agent Deployment Wizard, you are required to specify an Installation Base Directory.

Installation Base Directory is the parent directory on the remote host where the Oracle home of the Management Agent is created.

For example, if you specify the installation base directory as /john/oracle/, then the Oracle home of the Management Agent is created as /john/oracle/agent11g.

What Is EMSTATE Directory?

While installing a Management Agent using the Shared Agent Deployment Wizard, you are required to specify an EMSTATE directory.

EMSTATE directory is the directory that is created on each of the remote hosts and is used for storing configuration files such as emd.properties, targets.xml, log files, and so on.

Every host that shares the Management Agent binaries has its own EMSTATE directory, and you can specify any name for it. For example, you can have an EMSTATE directory titled emstatedir_11_1.

The EMSTATE directory location must meet the following conditions:

• The EMSTATE directories of agents on different hosts should be local to the host instead of on the mounted drive, for security reasons.

• Since the EMSTATE directory contains the targets pertaining to each host, it is highly recommended to have it on a local host.

The EMSTATE directory must meet the following space requirements:

• The initial space required for EMSTATE directories is 1 MB.

• Since all the upload files, collection files, and log files are stored in this directory, the size of the directory will increase. Consequently, Oracle recommends that you allocate sufficient space for the EMSTATE directories after taking these factors into account.

What Is /TMP C:\Temp Directory Used For?

When you invoke the Enterprise Manager Grid Control Installation Wizard, it automatically copies some executable files and link files to a temporary directory on the host. For example, the default /tmp directory on UNIX hosts, and C:\Temp on Microsoft Windows hosts.

If the host is set to run cron jobs along with many other processes that may be running periodically, then these jobs attempt to clean up the default temporary directory, thereby deleting some files and causing the installation wizard to fail.

If there are any cron jobs or processes that are automatically run on the hosts to clean up the temporary directories, then ensure that you set the TMP or TEMP environment variable to a location that is different from the default location. Ensure that the non-default location you set is secure on the hard drive, that is, the non-default location is a location where cleanup jobs are not run. Also ensure that you have write permissions on this alternative directory.

This must be done before you run the installer to invoke the Enterprise Manager Grid Control Installation Wizard. (For UNIX operating systems, you invoke runInstaller, and for Microsoft Windows, you invoke setup.exe).

What Is Oracle Configuration Manager?

While installing Enterprise Manager Grid Control or any of its core components, you can choose to enable Oracle Configuration Manager. Alternatively, you can enable it after installing Enterprise Manager Grid Control.

Oracle Configuration Manager automatically collects configuration information from your environment at regular intervals and uploads it to Oracle repository. This helps Oracle maintain up-to-date information about your environment, identify security vulnerabilities, quickly diagnose support issues, and offer better solutions consistently.

However, no business or personal information is collected and uploaded, except for local contact name in the event of transmission problems. Oracle guarantees that all the information collected will be kept strictly confidential and under no circumstances will this information be shared with any other party.

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.

If the host from where you are running the installation wizard has a connection to the Internet, then on the Oracle Configuration Manager screen of the installation wizard, specify the My Oracle Support user name (or e-mail address) and password.

Otherwise, 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. To understand how the configuration information can be manually collected and uploaded, see the steps outlined in Manually Collecting and Uploading Configuration Information.

If you want to enable it after installation Enterprise Manager Grid Control, then see Enabling Oracle Configuration Manager After Installing Enterprise Manager Grid Control.

What Are Software Updates?

While installing or upgrading Enterprise Manager Grid Control or an additional OMS, you can choose to install software updates.

Software updates include interim patches, critical patch updates, prerequisite updates, install updates, and so on released by Oracle periodically.

What Are Configuration Assistants?

While installing or upgrading Enterprise Manager Grid Control or any of its core components using the Enterprise Manager Grid Control Installation Wizard, a set of Configuration Assistants are run at the end of the installation process to configure the installed components. Your installation process is complete only after all the installed components are configured using these Configuration Assistants.

What Configuration Assistants Are Run by the Installation Wizard?

The following are the Configuration Assistants run by the installation wizard:

What Is Agent Configuration Assistant Used For?

The Agent Configuration Assistant (agentca) is a Configuration Assistant that is run during the configuration phase to configure the Management Agent.

Besides configuring the Management Agent when it is first installed, you use the agentca script to discover the newly installed targets, convert a standalone Management Agent to a cluster-based Management Agent, discover the targets installed on the new nodes of a cluster, and reconfigure a cluster-based Management Agent. To understand how you can perform these operations, see Appendix I, "Reconfiguring Oracle Management Agent and Discovering New Targets".

Table 2-4 shows the arguments you can pass with the agentca script.

What Do You Do When Configuration Assistants Fail?

Table 2-5 describes what you must do when Configuration Assistants fail.

What Prerequisite Checks Are Run by Default?

Table 2-6 lists the default prerequisite checks that are run by the Enterprise Manager Grid Control Installation Wizard for different installation types.

How Can You Run Prerequisite Checks in Standalone Mode?

You can run the prerequisite checks in standalone mode before invoking the installation wizard. This helps you identify and resolve issues that might otherwise cause the installation to fail.

Table 2-7 shows the commands you need to run to run the prerequisite checks in standalone mode:

Can You Access Unlicensed Components?

Although the installation media in your media pack contain many Oracle components, you are permitted to use only those components for which you have purchased licenses. Oracle Support Service does not provide support for components for which licenses have not been purchased.

For more information, access the Enterprise Manager documentation library at the following URL and view the Oracle Enterprise Manager Licensing Information Guide:

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

What Are the Limitations with DHCP-Enabled Machines?

Do NOT run the OMS on a computer that is DHCP enabled. Oracle strongly suggests that you use a static host name or IP address assigned on the network for Enterprise Manager Grid Control components to function properly.

For more information, refer to My Oracle Support Note 428665.1 at:

https://metalink.oracle.com/

What Is a Host List File?

While using the Agent Deployment Wizard, you can specify the hosts on which you want to install Oracle Management Agent, in two ways:

• Specify either the host name or the IP address. Separate multiple host names using a comma, a white space, or a new line.

• Select an external file that contains a list of hosts mentioned.

  If you choose to select an external file that contains a list of all required host names, then ensure that the file format is similar to /etc/hosts file. The following is the recommended format of the /etc/hosts file.

  154.87.3.229 host1.foo.com host1
  154.87.3.109 host2.foo.com host2
  154.80.5.218 host3.foo.com host3 
  

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

  Note:

  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.

  The Agent Deployment Wizard picks up only the values in the first column of the Host List file that you select. Ensure that the host list format is appropriate because the Agent Deployment Wizard does not validate this format on the selected file.

  WARNING:

  Ensure that you do not specify duplicate entries of the hosts. If there are duplicate host entries in the list, then the application hangs. Also ensure that you use the same host names for which the SSH has been set.

What SYSDBA Privileges Are Required for Creating Repository Schema?

Table 2-8 lists the SYSDBA privileges required by the existing DBA to create the Management Repository schema:

What Scripts Are Run During the Installation Process?

At least once during or after the installation of Enterprise Manager Grid Control or Management Agent, you are prompted to log in as a root user and run oraInstRoot.sh, allroot.sh, or root.sh. You must log in as a root user because the scripts edit files in the /etc directory and create files in the local bin directory (/usr/local/bin, by default).

After every installation, a check is performed to identify the Central Inventory (oraInventory) directory. The Central Inventory directory is a directory that is automatically created by the installation wizard when an Oracle product is installed on a host for the very first time.

• If you have NOT installed an Oracle product before on the host, then run the oraInstRoot.sh script from the Central Inventory:

  $Home/oraInventory/oraInstRoot.sh

  The oraInstRoot.sh script is run to create the oraInst.loc file. The oraInst.loc file contains the Central Inventory location.

• However, if you already have an Oracle product on the host, then run the following:

  • If you are installing Enterprise Manager Grid Control or an additional OMS, then run allroot.sh script from the Oracle home of the OMS (oms11g):

    <Oracle_Home>/allroot.sh

  • If you are installing a Management Agent, then run root.sh script from the Oracle home of the Management Agent (agent11g):

    <Oracle_Home>/root.sh