Skip Headers
Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
12c Release 2 (12.1.0.2)
E24089-21
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

4 Installing Enterprise Manager Software Now and Configuring Later

This chapter explains how you can install only the software binaries of Enterprise Manager Cloud Control at one point, and configure the installation at a later point. In particular, this chapter covers the following:


Note:

All general purpose file systems, including OCFS2 and ACFS, are acceptable for storing Enterprise Manager Cloud Control 12c software binaries and OMS instance home files (configuration files in gc_inst). However, OCFS is not considered a general purpose file system, and therefore is not considered acceptable for this use.

Overview

You can choose to install only the software binaries of Enterprise Manager Cloud Control at one point and configure it at a later point in time to work with an existing, certified Oracle Database. This approach enables you to divide the installation process into two phases, mainly the installation phase and the configuration phase. Understandably, the installation phase takes less time compared to the configuration phase because the installation phase involves only copying of binaries. This approach helps you plan your installation according to the time and priorities you have.

During the installation phase, you invoke the installer to create Oracle homes and install the following components in the Middleware home:

During the configuration phase, you invoke a configuration script to do the following:

Before You Begin

Before you begin, keep these points in mind:

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 describes the following:

Installing in Graphical Mode

This section explains how you can install only the software binaries of Enterprise Manager Cloud Control at one point in graphical mode, and configure the installation at a later point. In particular, this section covers the following:

Installing Software

To install only the software binaries of Enterprise Manager Cloud Control in graphical 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. Even if you do not run it manually, the installer anyway runs it in the background while installing the product. However, running it manually beforehand sets up your Management Repository even before you can start 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. Invoke the Enterprise Manager Cloud Control Installation Wizard

    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.

    <Software_Location>/runInstaller [-invPtrLoc <absolute_path_to_oraInst.loc>]


    Note:

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

    • To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

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

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



    Note:

    When you invoke runInstaller or setup.exe, if the Enterprise Manager Cloud Control Installation Wizard does not appear, then it is possible that you do not have read and write access to the /stage subdirectory, which a subdirectory in the Disk1 directory of the Enterprise Manager software.

    There is a classpath variable that the installation wizard computes for OPatch as ../stage/Components/, and when the TEMP variable is set to /tmp, the installation wizard tries to look for the opatch JAR file in the /tmp/../stage directory, which is equivalent to /stage. However, if you do not have read and write permission on /stage, then the installation wizard can hang. Under such circumstances, verify if you have read and write access to the /stage directory. If you do not have, then set the TEMP variable to a location where the install user has access to, and then relaunch the installation wizard.


  2. Enter My Oracle Support Details

    My Oracle Support Details Screen

    On the My Oracle Support Details screen, enter 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 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.


    Note:

    For information about manually collecting the configuration information and uploading it to My Oracle Support, see Manually Collecting and Uploading Configuration Information.

  3. Click Next.

  4. Install Software Updates

    Software Updates Screen

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

    • (Recommended) Select Search for Updates, then select Local Directory if you have already manually downloaded the software updates to an accessible local or remote location.


      Note:

      For instructions to manually download the software updates, refer to How Can You Download the Software Updates?.

      Enter the location where the updates are available, and click Search for Updates. To search the computer and select the location, click Browse. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.

      • If the updates have been downloaded to the default location, then select or enter the full path to the scratch path location. For example, if the scratch path location is /scratch/OracleHomes and if the software updates are available in /scratch/OracleHomes/Updates, then enter /scratch/OracleHomes/Updates.

      • If the software updates have been downloaded to a custom location, then select or enter the full path to the custom location. For example, if the custom location is /scratch/john and if the software updates are available in /scratch/john/Updates, then enter /scratch/john/Updates.

    • Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.

      Enter the My Oracle Support account user name and password, and click Search for Updates. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch


    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 Cloud Control console and view the recommended security patches. To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, click Set MOS Credentials and register the credentials.

  5. Click Next.

    If Enterprise Manager Cloud 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 (6). Otherwise, the Check Prerequisites screen appears. For details, see step (8).

    If Enterprise Manager Cloud 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
    
  6. Enter Oracle Inventory Details

    On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.

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


      Note:

      • The central inventory location you enter 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

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

  7. Click Next.

  8. Check Prerequisites

    Prerequisite Checks Screen

    On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.

    The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.

    The status of the prerequisite check can be either Warning, Failed, or Succeeded.

    • If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.

    • However, all package requirements must be met or fixed before proceeding any further. Otherwise, the installation might fail.

  9. Click Next.

  10. Select Installation Type

    Surrounding text describes install_types_sw.gif.

    On the Installation Types screen, select Install software only.

  11. Click Next.

  12. Enter Installation Details

    On the Installation Details screen, do the following:

    1. Enter or validate or enter the Middleware home where you want to install the OMS and other core components.


      Note:

      • If Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 are already installed in your environment, then the installer automatically detects them and displays the absolute path to the Middleware home where they are installed. In this case, validate the Middleware home location 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 location you select or enter is a Middleware home location that does not have any Oracle homes for Oracle Management Service and Oracle Management Agent.

      • If Oracle WebLogic Server 11g Release 1 (10.3.5) and Java Development Kit 1.6 are NOT already installed in your environment, then the installer automatically installs them for you while installing the Enterprise Manager system. In this case, enter the absolute path to a directory where you want to have them installed. For example, /oracle/software/. Ensure that the directory you enter does not contain any files or subdirectories.

      • (Only for Microsoft Windows) Ensure that the number of characters in the middleware home path does not exceed 25 characters.

        For example, the middleware home path C:\Oracle\MW\EM containing only 15 characters is acceptable. However, C:\Oracle\MW\new\EM\dir\a123 containing more than 25 characters is not acceptable.


    2. Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed. For example, /oracle/agent. Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the Oracle Middleware home.


      Note:

      (Only for Microsoft Windows) Ensure that the number of characters in the agent base directory path does not exceed 25 characters.

      For example, the agent base directory path C:\Oracle\Agent\ containing only 16 characters is acceptable. However, C:\Oracle\ManagementAgent\12c\new containing more than 25 characters is not acceptable.


    3. Validate the name of the host where you want to configure the OMS.

      The host name appears as a fully qualified name. The host name can also appear as a virtual host name if your host is configured with virtual machine.

      You can choose to accept the default host name and proceed with the installation. Alternatively, you can change the name if it is incorrect, or enter another host name for this host. Ensure that the host name you enter is accessible from other hosts in the network (other hosts must be able to ping this host).

  13. Click Next.

  14. Review and Install

    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.

  15. Track the Progress

    On the Install Progress screen, view the overall progress (in percentage) of the installation.

  16. End the Installation

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

Using Advanced Installer Options

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

  • By default, GCDomain is the default name used for creating the WebLogic Domain. To override this and use a custom WebLogic Domain name, invoke the installation wizard with the WLS_DOMAIN_NAME option, and enter a unique custom name.


    Note:

    Ensure that the WLS_DOMAIN_NAME option is used even when the ConfigureGC.sh is invoked to configure the software binaries as described in Configure Software.

    For example, if you want to use the custom name EMDomain, then run the following command:

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh WLS_DOMAIN_NAME=EMDomain

  • If you want to set the Central Inventory, then pass 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 -silent -responseFile <absolute_path_response_file>

  • After you install the software binaries, you will configure the binaries. And after the configuration ends successfully, by default, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installation wizard with START_OMS and b_startAgent options, and set them to true or false depending on what you want to control.


    Note:

    Ensure that the START_OMS and b_startAgent options are used even when the ConfigureGC.sh is invoked to configure the software binaries as described in Configure Software.

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

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh START_OMS=true b_startAgent=false

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

Running Root Script

(For UNIX Only) After you install the software binaries of Enterprise Manager Cloud Control, log in as a root user in a new terminal and run the following scripts:

  • If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.

    For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:

    $HOME/oraInventory/oraInstRoot.sh


    Note:

    If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

    /usr/local/bin/sudo $HOME/oraInventory/oraInstRoot.sh


  • Run the allroot.sh script from the OMS home:

    $<OMS_HOME>/allroot.sh


    Note:

    If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

    /usr/local/bin/sudo $<OMS_HOME>/allroot.sh


Configure Software

To configure Enterprise Manager Cloud Control, follow these steps:

  1. Invoke the Enterprise Manager Cloud Control Installation Wizard

    Invoke the installation wizard 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.

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh [-invPtrLoc <absolute_path_to_oraInst.loc>]


    Note:

    • While installing the software binaries as described in Installing Software, if you had passed the argument -invPtrLoc, then pass the same argument here as well.

    • The -invPtrLoc parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

    • For information about the additional, advanced options you can pass while invoking the script, refer to Using Advanced Script Options.

    • The only way to configure a software-only installation is to run the ConfigureGC.sh (or ConfigureGC.bat on Microsoft Windows) script. DO NOT run the individual configuration assistants to configure a software-only installation. If you want to run the individual configuration assistants to configure the installation for some reason, then contact Oracle Support.

    • If you have already configured a software-only installation (the Oracle home) using the ConfigureGC.sh script (or ConfigureGC.bat on Microsoft Windows, then DO NOT try to reconfigure it—either using the script or using the individual configuration assistants.


  2. Select Installation Type

    Install Types Screen

    In the installation wizard, on the Installation Types screen, select Create a New Enterprise Manager System.

  3. Click Next.

  4. Deploy Plug-Ins

    Surrounding text describes plugin_select.GIF.

    On the Plug-In Deployment screen, select the optional plug-ins you want to install from the software kit (DVD, downloaded software) while installing the Enterprise Manager system.

    The pre-selected rows are mandatory plug-ins that will be installed by default. Select the optional ones you want to install.


    Note:

    During installation, if you want to install a plug-in that is not available in the software kit, then refer to the point about installing additional plug-ins in Using Advanced Installer Options.

  5. Click Next.

  6. Enter WebLogic Server Configuration Details

    WebLogic Server Configuration Details Screen

    On the WebLogic Server Configuration Details screen, enter the credentials for the WebLogic Server user account and the Node Manager user account, and validate the path to the Oracle Management Service instance base location.


    Note:

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

    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.

    By default, the Oracle Management Service instance base location is gc_inst, which is created in the Middleware home for storing all configuration details related to the OMS.

  7. Click Next.

  8. Enter Database Connection Details

    Surrounding text describes db_config_dtls.gif.

    On the Database Connection Details screen, do the following:

    1. Provide details of the existing, certified database where the Management Repository needs to be created. If you have already created a database instance with a preconfigured Management Repository using the database templates offered by Oracle, then provide details about that database instance.

      The installer uses this information to connect to the existing database for creating the SYSMAN schema and plug-in schemas. If you provide details of a database that already has a preconfigured Management Repository, then the installer only creates plug-in schemas.


      Note:

      • For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Oracle Enterprise Manager Cloud Control Basic Installation Guide.

      • If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter on the Repository Configuration Details screen (as described in Step (10)).

      • To identify whether your database is a certified database listed in the certification matrix, access the certification matrix as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide.

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

      • Oracle Real Application Cluster (Oracle RAC) nodes are referred to by their virtual IP (vip) names. The service_name parameter is used instead of the system identifier (SID) in connect_data mode, and failover is turned on. For more information, refer to Oracle Database Net Services Administrator's Guide.


    2. Select the deployment size from the Deployment Size list to indicate 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.

      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 on deployment sizes, the prerequisite checks that are run, the database parameters that are set, and how you can modify the deployment size after installation, refer to What is a Deployment Size?.

      Table 4-1 describes each deployment size.

      Table 4-1 Deployment Size

      Deployment Size Targets Count Management Agents Count Concurrent User Session Count

      Small

      Up to 999

      Up to 99

      Up to 10

      Medium

      Between 1000 and 9999

      Between 100 and 999

      Between 10 and 24

      Large

      10,000 or more

      1000 or more

      Between 25 and 50


  9. Click Next.


    Note:

    If you connect to a database instance that was created using the database template offered by Oracle, then you will be prompted that the database parameters need to be modified to suit the deployment size you selected. This is because the templates are essentially designed for simple installation, and the database parameters are set as required for simple installation. Since it is used for advanced installation, the parameters must be set to different values. You can confirm the message to proceed further. The installation wizard will automatically set the parameters to the required values.

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

    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.

    Oracle Real Application Cluster (Oracle RAC) nodes are referred to by their virtual IP (vip) names. The service_name parameter is used instead of the system identifier (SID) in connect_data mode, and failover is turned on. For more information, refer to Oracle Database Net Services Administrator's Guide.


  10. Enter Repository Configuration Details

    Repository Configuration Details Screen

    On the Repository Configuration Details screen, do the following:

    1. For SYSMAN Password, enter 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 Cloud Control. SYSMAN is also the super administrator for Enterprise Manager Cloud Control.


      Note:

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

      • If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter on this screen.


    2. For Registration Password, enter a password for registering the new Management Agents that join the Enterprise Manager system.


      Note:

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

    3. For Management Tablespace, enter the absolute 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

    4. For Configuration Data Tablespace, enter the absolute 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

    5. For JVM Diagnostics Data Tablespace, enter the absolute 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 Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).

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

  11. Click Next.

  12. Customize Ports

    Port Configuration Details Screen

    On the Port Configuration Details screen, customize the ports to be used for various components.

    You can enter a free custom port that is either within or outside the port range recommended by Oracle.

    To verify if a port is free, run the following command:

    • On Unix:

      netstat -anp | grep <port no>

    • On Microsoft Windows:

      netstat -an|findstr <port_no>

    However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini file and if you want to use those ports, then click Import staticports.ini file and select the file.


    Note:

    If the 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.

    The staticports.ini file is available in the following location:

    <Software_Extracted_Location>/response


  13. Click Next.

  14. Review and Configure

    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 Configure to begin the installation process.

  15. Track the Progress

    On the Install Progress screen, view the overall progress (in percentage) of the installation.


    Note:

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

    • If you accidently exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script from the OMS home to rerun the Configuration Assistant in silent mode. For Microsoft Windows platforms, invoke runConfig.bat script.

      $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<absolute_path_to_OMS_home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

      If the runConfig.sh script fails, then clean up your environment and redo the installation.


  16. End the Installation

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

Using Advanced Script Options

The following are some additional, advanced options you can pass while invoking the configureGC.sh script (or configureGC.bat on Microsoft Windows):

  • By default, GCDomain is the default name used for creating the WebLogic Domain. To override this and use a custom WebLogic Domain name, invoke the script with the WLS_DOMAIN_NAME option, and enter a unique custom name.


    Note:

    Ensure that the WLS_DOMAIN_NAME option was used even when the installation wizard was invoked to install the software binaries as described in Installing Software.

    For example, if you want to use the custom name EMDomain, then run the following command:

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh WLS_DOMAIN_NAME=EMDomain

  • If you want to install some plug-ins that are not in the software kit, then follow these steps:

    1. 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/oem-upgrade-console-502238.html

    2. Invoke the ConfigureGC.sh script (or ConfigureGC.bat on Microsoft Windows) with the following option, and pass the location where the plug-ins you want to install are available:

      ./ConfigureGC.sh -pluginLocation <absolute_path_to_plugin_software_location>

      The Plug-In Deployment screen of the installation wizard displays a list of plug-ins available in the software kit as well as the plug-ins available in this custom location. You can choose the ones you want to install.

  • After the configuration ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the script with START_OMS and b_startAgent options, and set them to true or false depending on what you want to control.


    Note:

    Ensure that the START_OMS and b_startAgent options are used even when the installation wizard was invoked to install the software binaries as described in Installing Software.

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

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh START_OMS=true b_startAgent=false

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

Performing Post-Configuration Tasks

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.

Installing in Silent Mode

This section explains how you can install only the software binaries of Enterprise Manager Cloud Control at one point in silent mode, and configure the installation at a later point. In particular, this section covers the following:

Installing Software

To install only the software binaries of Enterprise Manager Cloud Control 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. Even if you do not run it manually, the installer anyway runs it in the background while installing the product. However, running it manually beforehand sets up your Management Repository even before you can start 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/software_only.rsp

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

  2. Edit the response file and enter appropriate values for the variables described in Table 4-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>/software_only.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

    • Otherwise, run the following command:

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


    Note:

    • To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.

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

    • For information about the additional, advanced options you can pass while invoking the installer, refer to Using Advanced Installer Options. The central inventory location you enter must NOT be on a shared file system.



    Note:

    When you invoke runInstaller or setup.exe, if the Enterprise Manager Cloud Control Installation Wizard does not appear, then it is possible that you do not have read and write access to the /stage subdirectory, which a subdirectory in the Disk1 directory of the Enterprise Manager software.

    There is a classpath variable that the installation wizard computes for OPatch as ../stage/Components/, and when the TEMP variable is set to /tmp, the installation wizard tries to look for the opatch JAR file in the /tmp/../stage directory, which is equivalent to /stage. However, if you do not have read and write permission on /stage, then the installation wizard can hang. Under such circumstances, verify if you have read and write access to the /stage directory. If you do not have, then set the TEMP variable to a location where the install user has access to, and then relaunch the installation wizard.


Editing Response File for Installing Software

Table 4-2 describes what variables you must edit and how you must edit them in the software_only.rsp response file for installing the software binaries.

Table 4-2 Editing Response File for Installing Enterprise Manager Software

Parameter Description

UNIX_GROUP_NAME

(Required only when central inventory does not exist) 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

(Required only when central inventory does not exist) 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.

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 to create the OMS home.

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.

Note: (Only for Microsoft Windows) Ensure that the number of characters in the middleware home path does not exceed 25 characters. For example, the middleware home path C:\Oracle\MW\EM containing only 15 characters is acceptable. However, C:\Oracle\MW\new\EM\dir\a123 containing more than 25 characters is not acceptable.

AGENT_BASE_DIR

Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed.

For example, /oracle/agent.

Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the Oracle Middleware home.

Note: (Only for Microsoft Windows) Ensure that the number of characters in the agent base directory path does not exceed 25 characters. For example, the agent base directory path C:\Oracle\Agent\ containing only 16 characters is acceptable. However, C:\Oracle\ManagementAgent\12c\new containing more than 25 characters is not acceptable.

ORACLE_HOSTNAME

Enter the fully qualified name of the host where you want to configure the OMS. The host name can also be a virtual host name if your host is configured with virtual machine. Ensure that the host name you enter is accessible from other hosts in the network (other hosts must be able to ping this host).

If you do not mention the host name, the installation wizard will proceed further, honoring the host name it automatically detects for that host.


Running Root Script

(For UNIX Only) After you install the software binaries of Enterprise Manager Cloud Control, log in as a root user in a new terminal and run the following scripts:

  • If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.

    For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:

    $HOME/oraInventory/oraInstRoot.sh


    Note:

    If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

    /usr/local/bin/sudo $HOME/oraInventory/oraInstRoot.sh


  • Run the allroot.sh script from the OMS home:

    $<OMS_HOME>/allroot.sh


    Note:

    If you are not a root user, then use SUDO to change to a root user. For example, run the following command:

    /usr/local/bin/sudo $<OMS_HOME>/allroot.sh


Configuring Software

To configure the software binaries of Enterprise Manager Cloud Control, follow these steps:

  1. Copy the following response file to an accessible location on the host where you copied the software binaries of Enterprise Manager Cloud Control:

    <Software_Location>/response/new_install.rsp

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

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

  3. Configure the software binaries by invoking the ConfigureGC.sh script (or ConfigureGC.bat on Microsoft Windows) passing the response you edited in the previous step:

    $<MIDDLEWARE_HOME>/oms/sysman/install/ConfigureGC.sh -silent -responseFile <absolute_path>/new_install.rsp [-invPtrLoc <absolute_path_to_inventory_directory>]


    Note:

    • While installing the software binaries as described in Installing Software, if you had passed the argument -invPtrLoc, then pass the same argument here as well.

    • The -invPtrLoc parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

    • For information about the additional, advanced options you can pass while invoking the script, refer to Using Advanced Script Options.

    • The only way to configure a software-only installation is to run the ConfigureGC.sh script (or ConfigureGC.bat on Microsoft Windows). DO NOT run the individual configuration assistants to configure a software-only installation. If you want to run the individual configuration assistants to configure the installation for some reason, then contact Oracle Support.

    • If you have already configured a software-only installation (the Oracle home) using the ConfigureGC.sh script (or ConfigureGC.bat on Microsoft Windows), then DO NOT try to reconfigure it—either using the script or using the individual configuration assistants.

    • If you connect to a database instance that was created using the database template offered by Oracle, then you will be prompted that the database parameters need to be modified to suit the deployment size you selected. This is because the templates are essentially designed for simple installation, and the database parameters are set as required for simple installation. Since it is used for advanced installation, the parameters must be set to different values. You can confirm the message to proceed further. The installation wizard will automatically set the parameters to the required values.



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


Editing Response File for Configuring Software

Table 4-3 describes what variables you must edit and how you must edit them in the new_install.rsp file for configuring the software binaries.

Table 4-3 Editing Response File for Configuring Enterprise Manager Software

Parameter Description

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:

  1. 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/oem-upgrade-console-502238.html

  2. Update this variable (PLUGIN_SELECTION) to the names of those plug-ins you downloaded.

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

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 blank. 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. If you want to accept the default directory, then blank. However, if you want to have a custom directory, then enter the name of the custom directory.

Whether you accept the default directory or enter a custom one, by default, the directory is created under the parent directory of the Middleware home.

For example, if the Middleware home is /u01/app/Oracle/Middleware, then the directory is /u01/app/Oracle/gc_inst.

For more information about this location, see What Is Oracle Management Service Instance Base 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 have already created a database instance with a preconfigured Management Repository using the database templates offered by Oracle, then provide details about that database instance.

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.

Note: If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter for the SYSMAN_PASSWORD parameter.

LISTENER_PORT

Enter the listener port to connect to the existing database.

For example, 1521

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.

DEPLOYMENT_SIZE

Set one of the following values to indicate 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.

  • Small, to monitor up to 999 targets, with up to 99 Management Agents and up to 10 concurrent user sessions

  • Medium, to monitor about 1000 to 9999 targets, with about 100 to 999 Management Agents and about 10 to 24 concurrent user sessions

  • Large, to monitor 10,000 or more targets, with 1000 or more Management Agents, and with about 25 to 50 concurrent user sessions

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 on deployment sizes, the prerequisite checks that are run, the database parameters that are set, and how you can modify the deployment size after installation, refer to What is a Deployment Size?.

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.

Note: If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter for this parameter.

SYSMAN_CONFIRM_PASSWORD

Confirm the SYSMAN user account's password.

MANAGEMENT_TABLESPACE_LOCATION

Enter the absolute path to the location where the data file for management tablespace (mgmt.dbf) 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 for configuration data tablespace (mgmt_ecm_depot1.dbf) 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 for JVM Diagnostics data tablespace (mgmt_ad4j.dbf) 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.


Performing Post-Configuration Tasks

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.