2 Installing Enterprise Manager System

Overview

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

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

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

Before You Begin

Before you begin, keep these points in mind:

• This installation type only supports installation of Enterprise Manager Grid Control locally on the server where the installer is invoked, and does not support installing on multiple or remote hosts.

• Do NOT install the additional OMS on an OCFS file system. This file system is not supported.

• Install Enterprise Manager Grid Control on a dedicated Oracle WebLogic Server instance (in a separate middleware home). Do NOT install Enterprise Manager Grid Control on an Oracle WebLogic Server instance that already has an Oracle Fusion Middleware product installed. For example, if the middleware home already has Oracle SOA Suite 11.1.1.2.0 installed, then do not install Enterprise Manager Grid Control in the same middleware home. Enterprise Manager Grid Control cannot co-exist with any Oracle Fusion Middleware product in the same middleware home because the ORACLE_COMMON property is used by both the products.

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

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

• While installing on hosts having multiple IP addresses, the host name is derived from the ORACLE_HOSTNAME variable that is passed while invoking the installer.

  For example:

  ./runInstaller ORACLE_HOSTNAME=host1.foo.com

  Note:

  Before passing this variable with the installer, ensure that you set the ORACLE_HOSTNAME environment variable.

• No environment variable specific to Enterprise Manager Grid Control needs to be set prior to installation. The ORACLE_HOME and ORACLE_SID variables should not be set; Oracle directories should not appear in the PATH.

• Oracle offers code fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for code 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 Grid Control installation, you must consider Enterprise Manager Grid Control's framework components as well as the targets monitored by Enterprise Manager Grid Control. Oracle recommends keeping your Grid Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license. For information about the certified combinations of Enterprise Manager Grid Control components and monitored targets, see My Oracle Support note.412431.1.

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

Prerequisites

Before installing a complete Enterprise Manager system, ensure that you meet the following prerequisites.If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.

Installation Procedure

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

1. Invoke the installer by running the following command:

   <Software_Location>/runInstaller

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

   Note:

   • For Microsoft Windows operating systems, run setup.exe instead of runInstaller.

   • In Microsoft Windows, if the path to the software download location contains a subdirectory name with two or more words and a space between each of the words, then ensure that the parent directory of such a subdirectory does not contain a file whose name matches with the first word of that subdirectory.

     For example, if the software is downloaded to C:\Documents and Settings, then before you invoke setup.exe, ensure that there are no files titled Documents (for example, shortcut files such as C:\Documents) in the C:\ drive.

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

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

     ./runInstaller SHARED_RECEIVE_DIRECTORY_LOCATION=<absolute_path_to_central_directory>

   • After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer using the following command:

     ./runInstaller START_OMS=false b_startAgent=false

     However, if you pass the START_OMS=false argument, the installation does not configure the EMCLI tool, and as a result, none of the EMCLI commands will work. Therefore, after the installation ends, you must manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface available at:

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

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

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

     ./runInstaller WLS_DOMAIN_NAME=<Custom_Domain_Name>

2. Specify My Oracle Support Details

   
   

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

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

   Note:

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

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

3. Click Next.

4. Check for Updates

   
   

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

   Note:

   If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Grid Control console and view the recommended security patches. To do so, log in to Enterprise Manager Grid Control, and click Preferences from the top-right corner of the screen. On the General page, from the left menu bar, click Preferred Credentials. On the Preferred Credentials page, from the My Oracle Support Preferred Credentials section, click Set Credentials. On the My Oracle Support Preferred Credentials page, specify the credentials and click Apply.

   • Select Download and install updates from My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there. Specify the My Oracle Support account user name and password to connect to the site.

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

     Note:

     After specifying the My Oracle Support details, when you click Next, the installation wizard connects to My Oracle Support and checks for new software updates. The installer displays the new software updates that are found. If you want to install them, click Download Updates. If you do not want to install them, click Skip Updates.

   • (Recommended) Select Install updates from a staging location if the software updates are already downloaded and available in an accessible location. You can either specify the location or click Browse to search the host and select the location. Ensure that the location you specify or select leads to the Updates directory where the software updates are available.

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

   Note:

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

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

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

5. Click Next.

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

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

6. Select Installation Type

   
   

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

7. Click Next.

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

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

   <system drive>\Program Files\Oracle\Inventory
   

8. Specify Inventory Details

   
   

   On the Oracle Inventory screen, do the following:

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

      Note:

      the central inventory location you specify must NOT be on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1

      Note:

      If this is the first Oracle product on the host, then the default central inventory location is /home/<user_name>/oraInventory. However, if you already have some Oracle products on the host, then the central inventory location can be found in the oraInst.loc file. The oraInst.loc file is located in the /etc directory for Linux and AIX, and in the /var/opt/oracle directory for Solaris, HP-UX, and Tru64.

   2. Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.

   Note:

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

9. Click Next.

10. Check for Prerequisites

    
    

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

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

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

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

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

11. Click Next.

12. Specify Installation Locations

    
    

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

    • For Oracle Middleware Home Location, validate and accept the default middleware location, or select or specify another middleware location, which is present on the host where you are installing the product. Ensure that the middleware location has write permission to create the Oracle home for OMS and the Oracle home for Management Agent.

      For example, if you accept the default location /u01/app/Oracle/Middleware, then the Oracle home for OMS is created as /u01/app/Oracle/Middleware/oms11g, and the Oracle home for Management Agent is created as /u01/app/Oracle/Middleware/agent11g.

      Note:

      Ensure that the Middleware Home you accept, select, or specify here is used only for Enterprise Manager Grid Control. Ensure that no other Oracle Fusion Middleware products or components are installed in the same Middleware Home that is designated for Enterprise Manager Grid Control.

    • For OMS Instance Base Location, validate and accept the default instance base location, or specify another instance base location, which is present on the host where you installing the product and has write permission to store the configuration files of OMS.

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

      For example, if the Oracle Middleware Home is /u01/app/Oracle/Middleware and if you choose to retain the default instance home name, then the instance home location is /u01/app/Oracle/gc_inst.

      If the parent directory of the Oracle Middleware Home does not have write permission, then the instance base is created in the Oracle Middleware Home itself.

    Note:

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

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

13. Click Next.

14. Create WebLogic Server Domain

    
    

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

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

15. Click Next.

16. Connect to Oracle Database

    
    

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

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

17. Click Next.

    Note:

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

18. Configure Oracle Management Repository

    
    

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

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

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

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

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

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

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

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

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

    Note:

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

19. Click Next.

20. Secure Oracle Management Service

    
    

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

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

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

       OMS always runs in a secure mode, and can further have a locked or an unlocked state. In an unlocked state, the Management Agents that are secure and the Management Agents that are not secure communicate with the OMS using HTTP and HTTPS protocols, respectively. However, in a locked state, only secure Management Agents communicate with the OMS using HTTPS protocol.

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

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

21. Click Next.

22. Customize Ports

    
    

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

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

    Note:

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

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

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

23. Click Next.

24. Review

    
    

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

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

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

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

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

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

    Note:

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

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

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

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

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

    $<ORACLE_HOME>/install/setupinfo.txt

After You Install

After you install, do the following:

1. Verify the installation:

   1. Navigate to the Oracle home of the OMS and run the following command to see a message that confirms that OMS is up and running.

      $<ORACLE_HOME>/bin/emctl status oms

   2. Navigate to the Oracle home of the Management Agent and run the following command to see a message that confirms that the Management Agent is up and running.

      $<ORACLE_HOME>/bin/emctl status agent

   3. Navigate to the Oracle home of the Management Agent and run the following command to see a message that confirms that EMD upload completed successfully.

      $<ORACLE_HOME>/bin/emctl upload

   Note:

   By default, you can access Enterprise Manager Grid Control only using the HTTPS protocol. If you want to use the HTTP protocol, then unlock it by running the following command from the Oracle home of the OMS:

   emctl secure unlock -console

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

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

      For information about these JAVA options, access these URLs:

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

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

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

      [
        [
          <
             -Dweblogic.security.TrustKeyStore=DemoTrust
            [ -Dweblogic.security.JavaStandardTrustKeystorePassPhrase=password ]   
          >
          |
          <
             -Dweblogic.security.CustomTrustKeyStoreFileName=filename          
             -Dweblogic.security.TrustKeystoreType=CustomTrust     
             [ -Dweblogic.security.CustomTrustKeystorePassPhrase=password ]
          >
        ]
        [  
          < -Dweblogic.security.SSL.hostnameVerifier=classname >
         |
          < -Dweblogic.security.SSL.ignoreHostnameVerification=true >
        ]
      ]
      

   2. Ensure that HTTP tunneling is enabled in the Administration Server. To verify this, log in to Oracle WebLogic Server Administration Console, and do the following:

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

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

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

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

3. Configure the Oracle Database and Oracle Automatic Storage Management (Oracle ASM) target for monitoring as described in Appendix G, "Configuring Database and ASM Targets for Monitoring".

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

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

6. (Optional) If you had not configured a shared file system loader while installing a complete Enterprise Manager system, and if you want to configure a shared location for it now, then run the following command from the Oracle home of the OMS:

   $<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir <Loader_Directory>

   For example,

   $<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir /share/recv

7. (Optional) If you want to connect to another Management Repository, then shut down the OMS, run the following command, and then restart the OMS.

   emctl config oms -store_repos_details (-repos_host <host> -repos_port <port> -repos_sid <sid> | -repos_conndesc <connect descriptor>) -repos_user <username> [-repos_pwd <pwd>] [-no_check_db]

   Note:

   On Linux, you need to double escape the connect descriptor using single and double quotes. However, on Microsoft Windows, you need not.

   For example, on Linux:

   emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc '"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb)))"' -repos_user sysman

   For example, on Microsoft Windows:

   emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb))) -repos_user sysman

8. (Optional) If you want to change the SYSMAN password, then shut down the OMS, run the following command, and then restart the OMS.

   emctl config oms -change_repos_pwd

9. (Optional) If you want to discover the newly installed targets, if you want to convert the standalone Management Agent to a cluster-based Management Agent, if you want to discover the targets on the new nodes of the cluster, or if you want to reconfigure the cluster-based Management Agent, you must run the agentca script to reconfigure and discover all new targets. For information about the agentca script and to know how you can reconfigure the Management Agent and discover all new targets, see Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide available at:

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

10. (Optional) If you want to enable the Request Monitoring feature for tracing transaction requests in WLS, you need JVM Diagnostics as well as Application Dependency and Performance (ADP) managers and agents configured against the target to be monitored.

    For information about installing JVM Diagnostics and enabling the Request Monitoring feature, refer to the Oracle Enterprise Manager Administration Guide.

    For information about enabling the ADP feature in Enterprise Manager Grid Control, refer to the Oracle Enterprise Manager Getting Started with Management Pack Plus for SOA.

    Both these guides are available at:

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