3 Installing Enterprise Manager System in Silent Mode

This chapter describes how you can install Enterprise Manager Cloud Control while utilizing an existing, certified Oracle Database, in silent mode. In particular, this section covers the following:

• Overview

• Before You Begin

• Prerequisites

• Installation Procedure

• After You Install

Note:

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

Overview

If you are familiar with the way Enterprise Manager is installed, and if you want to install it without facing any interview screens of the installation wizard, then the best option is to install it in silent mode.

In silent mode, you use a response file that captures all the information you need to successfully complete an installation. This saves time and effort in one way because the installation details are captured just once, and in a single file that can be circulated and reused for installation on multiple other hosts.

However, whether you install Enterprise Manager in graphical mode or silent mode, the installation process, the installed components, and the configuration process remain the same. Therefore, silent mode of installing Enterprise Manager is only an option offered to you.

To understand what components are installed, what configuration assistants are run, and how the directory structure will look after installation, see the chapter on installing Enterprise Manager system in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Before You Begin

Before you begin, keep these points in mind:

• You must ensure that you have the latest Enterprise Manager Cloud Control software:

  • Ensure that you have the Enterprise Manager Cloud Control software released in February 2012 - Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) (With Bundle Patch 1). You can download it from the following URL:

    http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html

  • If you had downloaded and installed the Enterprise Manager Cloud Control software released in October 2011, then apply the following patches, which are part of the Bundle Patch 1 released in February 2012, on the OMS and the Management Agent. In this case, you do not have to download the one released in February 2012.

    • On OMS, apply the patch 13242773.

    • On Management Agent, apply the patches 13242776, 13491785, 13550565, and 13550561.

      To apply these patches, you can either read the My Oracle Support note 1395505.1 or the ReadMes packaged with the patches.

  • If you had downloaded the Enterprise Manager Cloud Control software released in October 2011, but not installed it yet, then discard that software and download the one released in February 2012 - Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) (With Bundle Patch 1. You can download it from the following URL:

    http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html

• (Only for Microsoft Windows) Ensure that there are no white spaces in the name of the directory where you download the Enterprise Manager Cloud Control software. For example, do not download the software to a directory titled Program Files because there is a white space between the two words of the directory name.

• You can install Enterprise Manager Cloud Control only on a single host—locally on the server where you invoke the installation wizard with a response file. You cannot install on multiple or remote hosts.

• Enterprise Manager Cloud Control 12c can communicate only with Oracle Management Agent 12c, and not with any earlier release of the Management Agent.

• You must not set the ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the Oracle directories do NOT appear in the PATH.

• The Enterprise Manager Cloud Control Installation Wizard installs Java Development Kit (JDK) 1.6 v24 and Oracle WebLogic Server 11g Release 1 (10.3.5), but only if they do not exist in your environment.

• If Oracle WebLogic Server 11g Release 1 (10.3.5) does not exist and if you choose to manually install it, then ensure that you install it using JDK 1.6 v24+ (64-bit version for 64-bit platforms and 32-bit version for 32-bit platforms).

  • Download JDK 1.6 v24+ for your platform from the platform vendor's Web site. For example, download SUN JDK 1.6 v24+ for Linux platforms from Oracle Web site. Similarly, download the JDK for other platforms from other vendors' trusted Web sites.

  • If you already have JDK, then verify its version by navigating to the <JDK_Location>/bin directory and running the following command:

    "./java -fullversion"

    To verify whether it is a 32-bit or a 64-bit JDK, run the following command:

    "file *"

  • JROCKIT is not supported.

  • If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.5) on Linux 64-bit platforms, first install the 64-bit JDK for your platform, and then download and use the wls1035_generic.jar file to install Oracle WebLogic Server.

    For example,

    <JDK home>/bin/java -d64 -jar <absolute_path _to_wls1035_generic.jar>

  • If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.5) on Linux 32-bit platforms, then download and use either the wls1035_linux32.bin file or the wls1035_generic.jar file.

    For example,

    <JDK home>/bin/java -jar <absolute_path _to_wls1035_generic.jar>

  • You must follow the instructions outlined in the Oracle® Fusion Middleware Installation Guide for Oracle WebLogic Server to install Oracle WebLogic Server. The guide is available in the Fusion Middleware documentation library available at:

    http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html

  • You must ensure that the Oracle WebLogic Server installation is a typical installation, and even if you choose to perform a custom installation, ensure that components chosen for custom installation are the same as the ones associated with a typical installation.

  • You must ensure that the user installing the WebLogic Server is the same as the one installing Enterprise Manager Cloud Control.

• You must not install Enterprise Manager Cloud Control in a middleware home that is on an NFS-mounted drive. Installing Enterprise Manager on an NFS-mounted drive causes the Oracle HTTP Server to restart frequently, which in turn makes the OMS inaccessible. If you are forced to install on such a shared drive, then ensure that the OMS instance base directory (gc_inst) is created in a non-NFS-mounted location.

• You must ensure that the Oracle WebLogic Server 11g Release 1 (10.3.5) installed by the Enterprise Manager Cloud Control Installation Wizard or by you is dedicated for Enterprise Manager Cloud Control. You must not have any other Oracle Fusion Middleware product installed in that middleware home.

  Enterprise Manager Cloud Control cannot coexist with any Oracle Fusion Middleware product in the same middleware home because the ORACLE_COMMON property is used by both the products.

• By default, the software updates cannot be applied during installation because the INSTALL_UPDATES_SELECTION variable in the response file is set to "skip". However, if you want to apply them during installation, then you can modify this variable as described in Table 3-2.

• Oracle offers bug fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for bug fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:

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

  When determining supportability and certification combinations for an Enterprise Manager Cloud Control installation, you must consider Enterprise Manager Cloud Control's framework components as well as the targets monitored by Enterprise Manager Cloud Control. Oracle recommends keeping your Cloud Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license.

• You must upgrade all existing EMCLI clients of the earlier release to 12c Release 1 so that they can work with Enterprise Manager Cloud Control. This means, you must discard the old one and set up a new one.

  For information about setting up a new EMCLI client, see the Enterprise Manager Command Line Interface Download page within the Cloud Control console. To access that page, in Cloud Control, from the Setup menu, select My Preferences, and then, click Command Line Interface.

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

  On HPUNIX, HPia64, Solaris Sparc platforms, the entries are present in /var/opt/oracle/oragchomelist.

• As a prerequisite, you must have an existing Oracle Database to configure the Management Repository. This database can also have the Automatic Memory Management (AMM) feature enabled.

Prerequisites

Meet the prerequisites described in the chapter on installing Enterprise Manager system that is available in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Installation Procedure

This section covers the following:

• Installing Enterprise Manager

• Using Advanced Installer Options

• Understanding the Limitations

• Editing Response File for Installing Software

Installing Enterprise Manager

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

Note:

Oracle recommends you to run the EM Prerequisite Kit before invoking the installer to ensure that you meet all the repository requirements beforehand. This helps you set up your Management Repository beforehand without starting the installation or upgrade process. For information on the kit, to understand how to run it, and to know about the prerequisite checks it runs, see Oracle Enterprise Manager Basic Installation Guide.

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

   <Software_Location>/response/new_install.rsp

   In this command, <Software_Location> is either the DVD location or the location where you have downloaded the software kit.

2. Edit the response file and enter appropriate values for the variables described in Table 3-2.

3. Invoke the installer as a user who belongs to the oinstall group you created. For information about creating operating system groups and users, see the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

   • If this is the first Oracle product you are installing on the host, then run the following command:

     ./runInstaller -silent -responseFile <absolute_path>/new_install.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

     Note:

     The central inventory location you enter must NOT be on a shared file system. The -invPtrLoc parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

   • Otherwise, run the following command:

     ./runInstaller -silent -responseFile <absolute_path>/new_install.rsp

   Note:

   For information about the additional, advanced options you can pass while invoking the installer, refer to Using Advanced Installer Options.

Note:

• If any repository-related prerequisite check fails, then run the check manually. For instructions, see the appendix on EM Prerequisite Kit in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

• If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Resolve the issue and rerun the configuration assistant. For more information, see Appendix E.

Using Advanced Installer Options

The following are some additional, advanced options you can pass while invoking the installer:

• If you want to install on a host that has multiple host names (for examle, virtual hosts), then pass the fully qualified host name using the ORACLE_HOSTNAME argument while invoking the installer. Ensure that the host name you enter does not have underscores.

  For example:

  ./runInstaller ORACLE_HOSTNAME=example.com -silent -responseFile <absolute_path>/new_install.rsp

  Note:

  Ensure that the host name you enter does not have underscores.

• By default, a Provisioning Advisor Framework (PAF) staging directory is created for copying the Software Library entities related to the deployment procedures. By default, this location is the scratch path location (/tmp). The location is used only for provisioning activities—entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

  If you want to override this location with a custom location, then invoke the installer with the EM_STAGE_DIR option, and enter a unique custom location.

  For example,

  ./runInstaller EM_STAGE_DIR=/home/john/software/oracle/pafdir -silent -responseFile <absolute_path>/new_install.rsp

• 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 with START_OMS and b_startAgent options, and set them to TRUE or FALSE depending on what you want to control.

  For example, if you do not want the Management Agent to start automatically, then run the following command:

  ./runInstaller START_OMS=TRUE b_startAgent=FALSE -silent -responseFile <absolute_path>/new_install.rsp

  To understand the limitations involved with this advanced option, see Understanding the Limitations.

Understanding the Limitations

When you use START_OMS and b_startAgent as advanced options to control the way the OMS and the Management Agent start up automatically, sometimes the Management Agent and the host on which it was installed do not appear as targets in the Cloud Control console.

Table 3-1 lists the different combinations of these advanced options, and describes the workaround to be followed for each combination:

Table 3-1 Advanced Options and Workarounds

Advanced Option	Workaround
START_OMS=FALSE b_startAgent=FALSE	Start the OMS: $<OMS_HOME>/bin/emctl start oms Secure the Management Agent: $<AGENT_HOME>/bin/emctl secure agent Start the Management Agent: $<AGENT_HOME>/bin/emctl start agent Add the targets: $<AGENT_HOME>/bin/emctl config agent addinternaltargets Upload the targets: $<AGENT_HOME>/bin/emctl upload agent Manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface Guide.
START_OMS=TRUE b_startAgent=FALSE	Secure the Management Agent: $<AGENT_HOME>/bin/emctl secure agent Start the Management Agent: $<AGENT_HOME>/bin/emctl start agent Add the targets: $<AGENT_HOME>/bin/emctl config agent addinternaltargets Upload the targets: $<AGENT_HOME>/bin/emctl upload agent
START_OMS=FALSE b_startAgent=TRUE	Start the OMS: $<OMS_HOME>/bin/emctl start oms Secure the Management Agent: $<AGENT_HOME>/bin/emctl secure agent Add the targets: $<AGENT_HOME>/bin/emctl config agent addinternaltargets Upload the targets: $<AGENT_HOME>/bin/emctl upload agent Manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface Guide.

Editing Response File for Installing Software

Table 3-2 describes what variables you must edit and how you must edit them in the new_install.rsp response file for installing Enterprise Manager Cloud Control in silent mode.

Table 3-2 Editing Response File for Installing Enterprise Manager System

Parameter	Description
UNIX_GROUP_NAME	Enter the name of the UNIX group you belong to. For example, "dba" Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.
INVENTORY_LOCATION	Enter the absolute path to the Central Inventory. For example, /scratch/oracle/oraInventory Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.
SECURITY_UPDATES_VIA_MYORACLESUPPORT	Enter TRUE if you want to download and install security updates. Then, enter the credentials for the following variables: MYORACLESUPPORT_USERNAME MYORACLESUPPORT_PASSWORD Enter FALSE if you do not want to download and install security updates:
DECLINE_SECURITY_UPDATES	Enter TRUE if you want to decline the security updates. In this case, you should have entered False for SECURITY_UPDATES_VIA_MYORACLESUPPORT. Enter FALSE if you do not want to decline the security updates. In this case, you should have entered TRUE for SECURITY_UPDATES_VIA_MYORACLESUPPORT.
INSTALL_UPDATES_SELECTION	By default, this variable is set to "skip" indicating that the software updates will not be installed during installation. If you want to install the software updates from My Oracle Support, then set this variable to "download". Then, enter the credentials for the following parameters: MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES If you want to install the software updates from a staged location, then set this variable to "staged". Then, for the STAGE_LOCATION parameter, enter the absolute path, which leads to the Updates directory, where the software updates are available.
PROXY_USER	Enter the user name that can be used to access the proxy server. Note: Applies only if you have set the SECURITY_UPDATES_VIA_MYORACLESUPPORT variable to TRUE and/or the INSTALL_UPDATES_SELECTION variable to "download", and only if your connection to the Internet requires you to connect through a proxy.
PROXY_PWD	Enter the password that can be used to access the proxy server. Note: Applies only if you have set the SECURITY_UPDATES_VIA_MYORACLESUPPORT variable to TRUE and/or the INSTALL_UPDATES_SELECTION parameter to "download", and only if your connection to the Internet requires you to connect through a proxy.
PROXY_HOST	Enter the name of the proxy host. Note: Applies only if you have set the SECURITY_UPDATES_VIA_MYORACLESUPPORT variable to TRUE and/or the INSTALL_UPDATES_SELECTION parameter to "download", and only if your connection to the Internet requires you to connect through a proxy.
PROXY_PORT	Enter the port used by the proxy server. Note: Applies only if you have set the SECURITY_UPDATES_VIA_MYORACLESUPPORT variable to TRUE and/or the INSTALL_UPDATES_SELECTION parameter to "download", and only if your connection to the Internet requires you to connect through a proxy.
ORACLE_MIDDLEWARE_HOME_LOCATION	Enter the location where you want the installer to install Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 v24. For example, /u01/app/Oracle/Middleware. Ensure that the middleware location has write permission. And that this is not an NFS-mounted location. If you have already installed them manually, then enter the location where you have installed them. For more information about this location, see What Is Oracle Middleware Home?. Note: Ensure that the middleware home you enter here is used only for Enterprise Manager Cloud Control. Ensure that no other Oracle Fusion Middleware products or components are installed in the same middleware home.
WLS_ADMIN_SERVER_USERNAME	By default, weblogic is the name assigned to the default user account that is created for the Oracle WebLogic Domain. If you want to accept the default name, then skip this variable. However, if you want to have a custom name, then enter the name of your choice.
WLS_ADMIN_SERVER_PASSWORD	Enter a password for the WebLogic user account. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
WLS_ADMIN_SERVER_CONFIRM_PASSWORD	Confirm the password for the WebLogic user account.
NODE_MANAGER_PASSWORD	By default, nodemanager is the name assigned to the default user account that is created for the node manager. Enter a password for this node manager user account. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
NODE_MANAGER_CONFIRM_PASSWORD	Confirm the password for the node manager user account.
ORACLE_INSTANCE_HOME_LOCATION	By default, gc_inst is considered as the OMS Instance Base directory for storing all OMS-related configuration files, and it is created in the middleware home. If you want to accept the default location and the directory name, then skip this variable. However, if you want to have a custom location and a custom directory name, then enter the absolute path to the custom location leading up to the custom directory name. For more information about this location, see What Is Oracle Management Service Instance Base Location?. Note: If you have entered an NFS-mounted drive for the ORACLE_MIDDLEWARE_HOME_LOCATION parameter, then ensure that the location you enter for this parameter is a non-NFS-mounted location.
DATABASE_HOSTNAME	Enter the fully qualified name of the host where the existing database resides. Ensure that the host name does not have underscores. For example, example.com If you are connecting to an Oracle RAC Database, and if the nodes have virtual host names, then enter the virtual host name of one of its nodes. The connection to the database is established with a connect string that is formed using only this virtual host name, and the installation ends successfully. However, if you want to update the connect string with other nodes of the cluster, then after the installation, run the following command: $<OMS_HOME>/bin/emctl config oms -store_repos_details -repos_conndesc "(DESCRIPTION= (ADDRESS_LIST=(FAILOVER=ON) (ADDRESS=(PROTOCOL=TCP)(HOST=node1-vip.example.com)(PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=node2-vip.example.com)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=EMREP)))" -repos_user sysman If your Oracle RAC database is configured with Single Client Access Name (SCAN) listener, then you can enter a connection string using the SCAN listener.
LISTENER_PORT	Enter the listener port to connect to the existing database. For example, 1532
SERVICENAME_OR_SID	Enter the service name or the system ID (SID) of the existing database. For example, orcl
SYS_PASSWORD	Enter the SYS user account's password.
SYSMAN_PASSWORD	Enter a password for creating a SYSMAN user account. This password is used to create the SYSMAN user, which is the primary owner of the Management Repository schema. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
SYSMAN_CONFIRM_PASSWORD	Confirm the SYSMAN user account's password.
MANAGEMENT_TABLESPACE_LOCATION	Enter the absolute path to the location where the data file (mgmt.dbf) for management tablespace can be stored. Ensure that the specified path leads up to the file name. For example: If the database is on a file system, then the path must look like /u01/oracle/prod/oradata/mgmt.dbf If the database is on Automatic Storage Management (ASM), then the path must look like +<disk_group1>/prod/oradata/mgmt.dbf, where disk_group1 is a diskgroup created on ASM and prod is the Service ID (SID). If the database is on a raw device, then the path must look like </dev/raw1>/prod/oradata/mgmt.dbf, where /dev/raw1 is the raw device and prod is the SID. Enterprise Manager Cloud Control requires this data file to store information about the monitored targets, their metrics, and so on. Essentially, everything else other than configuration data, software library data, and audit data.
CONFIGURATION_DATA_TABLESPACE_LOCATION	Enter the absolute path to the location where the data file (mgmt_ecm_depot1.dbf) for configuration data tablespace can be stored. Ensure that the specified path leads up to the file name. For example, /home/john/oradata/mgmt_ecm_depot1.dbf Enterprise Manager Cloud Control requires this data file to store configuration information collected from the monitored targets.
JVM_DIAGNOSTICS_TABLESPACE_LOCATION	Enter the absolute path to a location where the data file (mgmt_ad4j.dbf) for JVM Diagnostics data tablespace can be stored. Ensure that the specified path leads up to the file name. For example, /home/john/oradata/mgmt_ad4j.dbf Enterprise Manager Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).
AGENT_REGISTRATION_PASSWORD	Enter a password to secure the communication between the OMS and the Management Agents. Note that you have to provide the same registration password for securing your Management Agents.
AGENT_REGISTRATION_CONFIRM_PASSWORD	Confirm the agent registration password.
STATIC_PORTS_FILE	By default, ports described in What Ports Are Used for Installation? are honored. If you want to accept the default ports, then leave this field blank. If you want to use custom ports, then enter the absolute path to the staticports.ini file that lists the custom ports to be used for the installation.
PLUGIN_SELECTION	By default, mandatory plug-ins such as Oracle Database Management Plug-In, Oracle Fusion Middleware Management Plug-In, Oracle My Oracle Support Management Plug-In, and Oracle Exadata Management Plug-In get automatically installed with the Enterprise Manager system. However, if you want to install any of the other optional plug-ins that are available in the software kit (DVD or downloaded software), then enter the names of those plug-ins for this variable. For example, PLUGIN_SELECTION={"oracle.sysman.empa","oracle.sysman.vt"} If you want to install any plug-in that is not available in the software kit, then do the following: Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location: http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html Update this variable (PLUGIN_SELECTION) to the names of those plug-ins you downloaded. Invoke the installer with the following option, and pass the location where you downloaded the plug-ins: ./runInstaller -pluginLocation <absolute_path_to_plugin_software_location>

After You Install

Perform the post-install steps as described in the chapter on installing Enterprise Manager system that is available in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.