2 Understanding the Basics

What Different Installation Modes Can You Use?

You can install Enterprise Manager Cloud 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 Cloud Control or a Management Agent, 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 Cloud Control Installation Wizard?

Enterprise Manager Cloud Control Installation Wizard is a Java-based wizard that helps you install or upgrade to Enterprise Manager Cloud Control in graphical mode. If you are installing Enterprise Manager Cloud 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 Cloud Control Installation Wizard

What Installation Types Are Offered by the Installation Wizard?

The Enterprise Manager Cloud Control Installation Wizard offers the following installation types:

• Create a New Enterprise Manager System

• Upgrade an Existing Enterprise Manager System

• Install Software Only

What is a Deployment Size?

When you install Enterprise Manager Cloud Control with advanced configuration settings (Advanced installation type), you have an option of selecting the deployment size of your choice. This option is available in both graphical mode (Enterprise Manager Cloud Control Installation Wizard) and silent mode (response file).

The deployment size essentially indicates the number of targets you plan to monitor, the number Management Agents you plan to have, and the number of concurrent user sessions you plan have.

Table 2-1 describes each deployment size.

The prerequisite checks are run regardless of the selection you make, but the values to be set for the various parameters checked depend on the selection you make. For more information about these deployment sizes, and the database parameters set for each of them, refer to Chapter 11.

After installing Enterprise Manager Cloud Control with a particular deployment size, you can choose to increase or decrease the count of targets, Management Agents, or concurrent user sessions. However, if you do increase the count to a level that is not appropriate for the selected deployment size, then the performance might suffer. Under such circumstances, Oracle recommends you to modify the database parameters according to the desired deployment size, as described in Chapter 11.

What Is Add Host Target Wizard?

The Add Host Targets Wizard (Figure 2-2) is a GUI-rich application accessible from within the Cloud Control console, and used for installing Management Agents on unmanaged hosts and converting them to managed hosts in the Enterprise Manager system.

Using the Add Host Targets Wizard, you can do the following:

• Install a fresh Management Agent

• Clone an existing well-tested, pre-patched, and running Management Agent

• Install a Management Agent from an existing, centrally shared Management Agent

Figure 2-2 Add Host Target Wizard

Although the Add Host Targets Wizard can be used for remotely installing one Management Agent, the wizard is best suited for mass-deployment of Management Agents, particularly while mass-deploying Management Agents of different releases on hosts of different platforms. The wizard gives you the flexibility to select hosts on which you want to install a Management Agent. This helps you when you want to install the Management Agent on several hosts, in one attempt.

What Is Add Management Service Deployment Procedure?

A deployment procedure is a procedure that contains a hierarchal sequence of provisioning or patching steps, where each step may contain a sequence of other steps. In other words, the workflow of all tasks that need to be performed for a particular life cycle management activity is encapsulated in a deployment procedure.

Enterprise Manager Cloud Control offers deployment procedures, and all of these can be accessed from within the Cloud Control console. One of the deployment procedures that falls within the context of Enterprise Manager Cloud Control installation is the Add Management Service deployment procedure.

The Add Management Service deployment procedure (Figure 2-3) helps you meet high-availability requirements by enabling you to install an additional OMS using an existing OMS that is running on an AdminServer host.

Figure 2-3 Add Management Service Deployment Procedure

In simple words, the Add Management Service deployment procedure enables you to install additional OMS instances in your environment. The deployment procedure clones an existing OMS and replicates its configuration to the destination host.

The earlier releases of Enterprise Manager offered this installation type from the Enterprise Manager Installation Wizard. However, for the Enterprise Manager Cloud Control release, this installation type is offered as a deployment procedure.

For more information about the deployment procedure, see the chapter on adding additional management service in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

What Ports Are Used for Installation?

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

• What Default Ports Are Used?

• How Can You Customize Ports?

• What Precautions You Must Take While Customizing Port Numbers?

What Data Files Are Created While Configuring Oracle Management Repository?

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

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 OMS home.

$<OMS_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_home> -oracleHome <oms_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%';

Table 2-3 describes the -action options that are supported by the different versions of RepManager.

How Do I Verify Whether Oracle WebLogic Server Is Installed?

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

$<WLS_HOME>/logs/log.txt

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

release  10.3.5.0 [Added]
    |_____Common Infrastructure Engineering 7.1.0.0 [Added]
    |    |_____Uninstall [Added]
    |    |_____Patch Client [Added]
    |    |_____Patch Attachment Facility [Added]
    |    |_____Clone Facility [Added]
    |_____WebLogic Server 10.3.5.0 [Added]
    |    |_____Core Application Server [Added]
    |    |_____Administration Console [Added]
    |    |_____Configuration Wizard and Upgrade Framework [Added]
    |    |_____Web 2.0 HTTP Pub-Sub Server [Added]
    |    |_____WebLogic SCA [Added]
    |    |_____WebLogic JDBC Drivers [Added]
    |    |_____Third Party JDBC Drivers [Added]
    |    |_____WebLogic Server Clients [Added]
    |    |_____WebLogic Web Server Plugins [Added]
    |    |_____UDDI and Xquery Support [Added]
    |    |_____Server Examples [Added]
    |    |_____Evaluation Database [Added]
    |    |_____Workshop Code Completion Support [Added]
    |_____Oracle Configuration Manager 10.3.3.1 [Added]
    |    |_____Data Collector [Added]
    |_____Oracle Coherence 3.6.0.3 [Not Installed]
         |_____Coherence Product Files [Not Installed]
         |_____Coherence Examples [Not Installed]

Is Oracle WebLogic Server Cluster Supported?

Oracle WebLogic Server cluster consists of 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 Cloud Control on an Oracle WebLogic Server Cluster, however, you cannot take advantage of the cluster configurations.

If Oracle WebLogic Server Already Exists, Is the Existing Domain Used?

If Oracle WebLogic Server already exists, then the existing domain is NOT used. Instead, the Enterprise Manager Cloud Control Installation Wizard creates a new domain and deploys the Enterprise Manager Cloud Control software to it.

When and Why Do You Need Oracle WebLogic Server Credentials?

While installing or upgrading to Enterprise Manager Cloud Control, you are prompted to enter the Oracle WebLogic Server credentials (user name and password). The credentials are used for creating the 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 to Enterprise Manager Cloud Control, you are prompted to enter 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 After Installing Enterprise Manager?

To find the Admin Server 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,

/DATA/oracle/Middleware/gc_inst/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:

https://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 OMS home (first OMS) that was initially installed:

$<MIDDLEWARE_HOME>/gc_inst/em/EMGC_OMS1/emgc.properties

How Do You Start Admin Server?

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 Cloud Control is the first Oracle product that you are installing, then the Enterprise Manager Cloud Control Installation Wizard prompts you to enter 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 enter the oraInventory directory in two ways:

• While installing Enterprise Manager Cloud Control using the installation wizard, you can enter the oraInventory directory in the Oracle Inventory screen. When you enter 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 Cloud Control in silent mode, that is, without using the installation wizard, you can enter the oraInventory directory using the -invPtrLoc parameter. This parameter considers the path to a location where the inventory pointer file (oraInst.loc) is available. However, this parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

  For example

  ./runInstaller -invPtrLoc /scratch/OracleHomes/oraInst.loc

If you already have an Oracle product installed on the host, then the installation wizard 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 or upgrading to Enterprise Manager Cloud Control, you are required to enter the Oracle Middleware home.

Oracle Middleware home (Middleware home) is the parent directory that has the Oracle WebLogic Server home, the Java Development Kit, the Web tier instance files, one or more Oracle homes, the OMS instance base directory, and other relevant files. This is where the OMS and the plug-ins are deployed.

For example,

/u01/app/Oracle/Middleware

If you are installing or upgrading to Enterprise Manager Cloud Control, then:

• If Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24+ are already installed in your environment, then the installation wizard automatically detects them and displays the absolute path to the Middleware home where they are installed.

  In this case, validate the Middleware home that is detected and displayed by default. If the location is incorrect, then enter the path to the correct location. Ensure that the Middleware home you select or enter is a Middleware home that does not have any Oracle homes for the OMS and the Management Agent.

• If Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24+ are NOT already installed in your environment, then the installation wizard automatically installs them for you while installing Enterprise Manager Cloud Control.

  In this case, enter the absolute path to a directory where you want to have them installed. Ensure that the directory you enter does not contain any files or subdirectories.

  For example,

  /u01/app/Oracle/Middleware/

What Is Oracle Management Service Instance Base Location?

While installing Enterprise Manager Cloud Control, you are required to enter the Oracle Management Service Instance Base Location.

Oracle Management Service Instance Base Location is a directory (gc_inst) inside the Middleware home where the configuration files of the OMS are stored.

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

/u01/app/Oracle/Middleware/gc_inst

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

What Is Oracle Home?

Oracle Home or Oracle home is the directory where the OMS, the Management Agent, and the plug-ins are installed. Table 2-4 lists the default Oracle homes are created.

What Is Agent Base Directory?

While installing Enterprise Manager Cloud Control and a standalone Management Agent using the Add Host Targets Wizard, you are required to enter an installation base directory, which is essentially the agent base directory.

Agent Base Directory is a directory outside the Oracle Mdidleware Home, where the Management Agent home is created.

For example, if the agent base directory is /u01/app/Oracle/agent, then the Management Agent home is created as /u01/app/Oracle/agent/core/12.1.0.2.0.

What is Agent Instance Directory?

Agent Instance Directory is a directory (agent_inst) created for storing all Management Agent-related configuration files.

Agent Instance Directory is created inside the agent base directory.

For example, if the agent base directory is /u01/app/Oracle/agent, then by default, the following is the agent instance directory:

/u01/app/Oracle/agent/agent_inst

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

When you invoke the Enterprise Manager Cloud 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 Cloud Control Installation Wizard. (For UNIX operating systems, you invoke runInstaller, and for Microsoft Windows, you invoke setup.exe).

What Is Oracle Configuration Manager?

With Enterprise Manager Cloud Control, you can choose to enable Oracle Configuration Manager. Alternatively, you can enable it after installing Enterprise Manager Cloud 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, enter the My Oracle Support user name (or e-mail address) and password.

Otherwise, enter 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 installing Enterprise Manager Cloud Control, then see Enabling Oracle Configuration Manager After Installing Enterprise Manager Cloud Control.

What Are Software Updates?

While installing or upgrading Enterprise Manager Cloud Control, 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 to Enterprise Manager Cloud Control in either GUI mode (using the installation wizard) or silent mode (using a response file), a set of configuration assistants are run at the end of the installation process to configure the installed or upgraded components. Your installation or upgrade process is complete only after all the components are configured using these configuration assistants.

What Configuration Assistants Are Run by the Installation Wizard?

This section lists the configuration assistants run by the installation wizard for the different installation types.

• Configuration Assistants Run While Installing a New Enterprise Manager

• Configuration Assistants Run While Upgrading an Existing Enterprise Manager

• Configuration Assistants Run While Upgrading an Additional Oracle Management Service

What Do You Do When Configuration Assistants Fail?

If an optional configuration assistant fails, then the installation wizard ignores the failure and runs to the next configuration assistant automatically. However, if a mandatory configuration assistant fails, then the installation wizard stops the installation process. In this case, you are expected to resolve the issue and rerun the configuration assistant.

For information about the log files to review when a configuration assistant fails, and the actions to be taken to resolve the issue, see Appendix G.

What Prerequisite Checks Are Run by Default?

The following are the default prerequisite checks that are run for different installation types—Creating a New Enterprise Manager System and Upgrading an Existing Enterprise Manager System:

• Prerequisite check for verifying whether the installation is being done on a certified operating system.

• Prerequisite check for verifying whether all the certified packages and libraries have been installed.

• Prerequisite check for verifying whether the glibc package has been installed. (Not applicable for Management Agent installation)

• Prerequisite check for verifying whether there is sufficient disk space in the temp directory. (Not applicable for Management Agent installation)

• Prerequisite check for verifying whether there is sufficient disk space in the inventory directory.

• Prerequisite check for verifying whether there is write permission in the inventory directory.(Not applicable for OMS installation)

• Prerequisite check for verifying whether the software is compatible with the current operating system.

• Prerequisite check for verifying whether there is sufficient physical memory.

• Prerequisite check for verifying the required ulimit value. (Not applicable for Management Agent installation)

• Prerequisite check for verifying the host name.

• Prerequisite check for verifying whether the LD_ASSUME_KERNEL environment variable is set. (Not applicable for Management Agent installation)

• Prerequisite check for verifying whether proper timezone is set.

• Prerequisite check for verifying whether there is 4 GB of swap space. (Not applicable for Management Agent installation)

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-5 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/technetwork/indexes/documentation/index.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 Cloud Control components to function properly.

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

https://support.oracle.com/

What Is a Host List File?

While using the Add Host Targets Wizard, you can enter the hosts on which you want to install Oracle Management Agent, in two ways — you can either enter the host name or the IP address, or select an external file that contains a list of hosts mentioned.

If you choose to select an external file, then ensure that the file contains only the host name (Example 2-1), or the host name followed by the platform name (Example 2-2).

host1.example.com
host2.example.com

host1.example.com linux
host2.example.com aix

What Scripts Are Run During the Installation Process?

At least once during or after the installation of Enterprise Manager Cloud 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 allroot.sh script from the OMS home:

  <OMS_HOME>/allroot.sh