Skip Headers
Oracle® Enterprise Manager Ops Center Installation Guide for Linux Operating Systems
12c Release 1 (12.1.4.0.0)

Part Number E25139-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

3 Installation and Configuration

These procedures describe how to install and configure an Enterprise Controller and one or more Proxy Controllers on Linux systems. Oracle Enterprise Manager Ops Center requires an Enterprise Controller and at least one Proxy Controller.

You can install the Enterprise Controller and the product database in one of three ways depending on the size and requirements of your environment:

Once you have installed the Enterprise Controller, you configure it. The configuration process specifies many characteristics of the Enterprise Controller, and can install and configure one or more Proxy Controllers based on your choice of deployment:

If you decided to install Proxy Controllers outside of the configuration wizard, or if you need to install Proxy Controllers at a later date, you can use one of two methods:

3.1 Installing an Enterprise Controller

In a typical initial installation, you install and configure an Enterprise Controller first, and install and configure Proxy Controllers as part of the configuration process. A Proxy Controller is automatically installed on the system where you install the Enterprise Controller, but you choose whether or not to enable it.

This installation installs, or upgrades to, Java Runtime Environment (JRE) 1.7_25 for the use of the Enterprise Controller and JRE 1.6_51 for the use of the Proxy Controllers. Later versions of JRE are not affected.

3.1.1 Installing an Enterprise Controller with an Embedded Database

This procedure describes the steps required to install Enterprise Controller software on a system that is running the Linux OS. This procedure also installs an embedded database.

The script that installs the Enterprise Controller also automatically installs a Proxy Controller on the same system, but it does not enable the Proxy Controller. In the configuration steps that follow this software installation procedure, you can choose to enable this Proxy Controller.

Before You Begin

Before you install Oracle Enterprise Manager Ops Center with an embedded database, you must download the required Oracle Database 11g Enterprise Edition version 11.2.0.3 installation bundles.

Note:

This procedure requires a valid My Oracle Support (MOS) account, which must be associated with a Customer Service Identifier (CSI) with a software contract.
  1. Create a /var/tmp/downloads directory on the Enterprise Controller system.

  2. Navigate to http://support.oracle.com, click Sign In, and sign in with your MOS credentials.

  3. Click the Patches & Updates tab.

  4. Enter 10404530 in the field next to Patch Name or Number.

  5. Click the Add Filter icon, then select your Enterprise Controller system's operating system and architecture in the drop-down menu next to Platform.

  6. Click Search.

    The Oracle Database 11g Enterprise Edition version 11.2.0.3 patch set is displayed.

  7. Click Download.

    The file download popup is displayed.

  8. Download the first two files. These files end with _1of7.zip and _2of7.zip.

  9. Copy or move the downloaded installation bundles to the /var/tmp/downloads directory on the Enterprise Controller system.

To Install an Enterprise Controller with an Embedded Database

This procedure installs the Enterprise Controller, co-located Proxy Controller, and embedded database.

  1. Create a temporary directory on your system, then copy or move the appropriate Oracle Enterprise Manager Ops Center archive for your system from delivery media to the temporary directory that you created. For example:

    # mkdir /var/tmp/OC
    # cp enterprise-controller.Linux.i686.12.1.0.0.zip /var/tmp/OC
    

    The installation archive consumes about 3.5 GBytes of disk space.

  2. Change to the directory where the installation archive is located on your system.

    # cd /var/tmp/OC
    #
    
  3. Expand the installation archive, then list the contents of the expanded directory.

    • If your installation archive has the .zip extension, use the unzip command to uncompress the archive. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.zip
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.zip
      xvmoc_full_bundle
      #
      
    • If your installation archive has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. The data extracted from the archive consumes about 1.5 GB of additional space. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.tar.zip | tar xf -
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.tar.zip
      xvmoc_full_bundle
      #
      
  4. Change directory to xvmoc_full_bundle, and run the install script. For example:

    # cd xvmoc_full_bundle
    # ./install
    
  5. The Oracle Configuration Manager installation text is displayed. Enter the My Oracle Support user name or email address that you want to associate with Oracle Enterprise Manager Ops Center.

    Provide your email address to be informed of security issues, install and
    initiate Oracle Configuration Manager. Easier for you if you use your My
    Oracle Support Email address/User Name.
    Visit http://www.oracle.com/support/policies.html for details.
    Email address/User Name:
    
  6. If you want security updates to appear on your My Oracle Support page, enter your My Oracle Support password.

    Provide your My Oracle Support password to receive security updates via your My Oracle Support account.
    Password (optional):
    

    The screen clears, then the install script displays a list of installation tasks that automatically updates as the installation proceeds. For example:

    Ops Center Enterprise Controller Installer
    (version 12.1.2.2140 on Linux)
     
    1. Check for installation prerequisites.                       [Not Completed]
    2. Configure file systems.                                     [Not Completed]
    3. Install prerequisite packages.                              [Not Completed]
    4. Install Agent components.                                   [Not Completed]
    5. Create Deployable Proxy Bundles.                            [Not Completed]
    6. Install application packages.                               [Not Completed]
    7. Run postinstall tasks.                                      [Not Completed]
    8. Install Expect.                                             [Not Completed]
    9. Install IPMI tool.                                          [Not Completed]
    10. Set database credentials.                                  [Not Completed]
    11. Install and Configure Oracle Database.                     [Not Completed]
    12. Seed Ops Center Database Schema                            [Not Completed]
    13. Install Service container components.                      [Not Completed]
    14. Install Core Channel components.                           [Not Completed]
    15. Install Proxy Core components.                             [Not Completed]
    16. Set Proxy database credentials.                            [Not Completed]
    17. Install Enterprise Controller components.                  [Not Completed]
    18. Install Update Connection - Enterprise.                    [Not Completed]
    19. Install Ops Center BUI components.                         [Not Completed]
    20. Install OS provisioning components.                        [Not Completed]
    21. Initialize and start services.                             [Not Completed]
    Executing current step:  Check for installation prerequisites...
    (version 12.1.0.0 on Linux)
    
  7. Review and correct any problems when the install script checks for installation prerequisites that are not met. For example, this install script detected insufficient disk space:

    Warning for Step: Check for installation prerequisites.
    The following is a portion of the installer
    log which may indicate the cause of the warning.
    If this does not indicate the cause of the
    warning, you will need to view the full log
    file. More information on how to do that is
    available below.
    You may choose to ignore this warning by selecting to continue.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    
    Ignoring job: 01checkRPMs.pl
    Ignoring job: 03removeEmptyDirs.pl
    
    
    Executing job: jobs/00checkPrereqs.pl --install
    
    WARNING: Installation prerequisites not met:
    Disk: / 72G needed, 24G available.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    Please fix the problem and then try this step again.
    For a full log of the failed install see the file: /var/tmp/installer.log.9361.
    
    t. Try this step again (correct the failure before proceeding)
    c. Continue (ignore the warning)
    x. Exit
    Enter selection: (t/c/x)
    

    You can enter t to try again, c to continue and ignore the warning, or x to exit the install script. You should exit the install script, correct the problem, and then run the install script again, which resumes from where it stopped. Choose to continue and ignore the warning only if you accept the impact that the error condition will have on your installation. Entering t typically produces the same error, unless you are able to correct the problem before trying the step again. If the install script finds that all prerequisites have been satisfied, or if you choose to continue despite the warning, the install script continues and installs all Enterprise Controller and Proxy Controller components.

    When complete, the install script displays a confirmation that all components have been installed. The /var/tmp/installer.log.latest file contains the installation log.

  8. Use the /opt/sun/xvmoc/bin/ecadm command to check the status of the Enterprise Controller services. If the installation has completed successfully, the services should be online. For example:

    # /opt/sun/xvmoc/bin/ecadm status
    online
    # 
    

When the installation is complete, configure the Enterprise Controller using one of the procedures in the Configuring an Enterprise Controller section.

3.1.2 Installing an Enterprise Controller with a Customer-Managed Database

This procedure describes the steps required to install Enterprise Controller software on a system that is running the Linux OS. This procedure also configures the software to use a customer-managed Oracle Database Enterprise Edition database. The customer-managed database must be installed and configured separately prior to the Oracle Enterprise Manager Ops Center installation.

See the Oracle Enterprise Manager Ops Center Certified Systems Matrix for a list of supported database versions and database options.

The script that installs the Enterprise Controller also automatically installs a Proxy Controller on the same system, but it does not enable the Proxy Controller. In the configuration steps that follow this software installation procedure, you can choose to enable this Proxy Controller.

Note:

The installation procedure requires database user name and password information. Work with your database administrator if you do not have access to this information.

Before You Begin

Complete this procedure before beginning the installation.

  1. Identify an existing Oracle Database 11g Enterprise Edition database to use, or install and configure a customer-managed database according to the Oracle Database 11g Enterprise Edition installation documentation.

To Install an Enterprise Controller with a Customer-Managed Database

This procedure installs the Enterprise Controller and co-located Proxy Controller, and configures the software to use a customer-managed database.

  1. Create a temporary directory on your system, then copy or move the appropriate Oracle Enterprise Manager Ops Center archive for your system from delivery media to the temporary directory that you created. For example:

    # mkdir /var/tmp/OC
    # cp enterprise-controller.Linux.i686.12.1.0.0.tar.gz /var/tmp/OC
    

    The installation archive consumes about 3.5 GBytes of disk space.

  2. Change to the directory where the installation archive is located on your system.

    # cd /var/tmp/OC
    #
    
  3. Expand the installation archive, then list the contents of the expanded directory.

    • If your installation archive has the .zip extension, use the unzip command to uncompress the archive. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.zip
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.zip
      xvmoc_full_bundle
      #
      
    • If your installation archive has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. The data extracted from the archive consumes about 1.5 GB of additional space. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.tar.zip | tar xf -
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.tar.zip
      xvmoc_full_bundle
      #
      
  4. Copy the createOCSchema.sql script from the Enterprise Controller to the customer-managed database server. This script is in the/var/tmp/OC/xvmoc_full_bundle/Linux_i686/Product/installer/scripts directory.

    For example, on the customer-managed database server:

    # scp root@EnterpriseController:/var/tmp/OC/xvmoc_full_bundle/SunOS_i386/Product/installer/scripts/createOCSchema.sql .
    Password:
    createOCSchema.sql  100% |*********************| 1486     00:00
    
  5. As the customer-managed database administrator, run the createOCSchema_remote.sql script and enter the following information:

    • Oracle Enterprise Manager Ops Center user name – This is a database user that Oracle Enterprise Manager Ops Center uses to access the database.

    • Oracle Enterprise Manager Ops Center password – This is the password for the database user. See the Oracle Database 11g Enterprise Edition documentation for information about password length and character restrictions.

    • Oracle Enterprise Manager Ops Center read-only user name – This is a read-only database user that Oracle Enterprise Manager Ops Center uses to view the database.

    • Oracle Enterprise Manager Ops Center read-only password – This is the password for the read-only database user.

    • Default tablespace – This is the default tablespace for the Oracle Enterprise Manager Ops Center user.

    • Temporary tablespace – This is the temporary tablespace for the Oracle Enterprise Manager Ops Center user.

    • Oracle Enterprise Manager Ops Center dump directory – This directory must exist and must be owned by the oracle user.

    When you enter all of the required information, the createOCSchema_remote.sql script indicates completion and exits.

    For example:

    $ sqlplus / as sysdba @createOCSchema_remote.sql
     
    SQL*Plus: Release 11.2.0.3.0 Production on Thu Dec 15 16:55:34 2011
     
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
     
     
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
     
    Enter username for Ops Center database login: TESTSCHEMA
    Enter password for Ops Center database login:
    Enter username for read only Ops Center database login: TESTSCHEMA_RO
    Enter password for read only Ops Center database login:
    Enter default tablespace for Ops Center user: USERS
    Enter temporary tablespace for Ops Center user: TEMP
    Enter Oracle Data Pump destination directory: /var/tmp/ocdumpdir
     
    "Done creating OC_SYSTEM_ROLE and OC_RO_ROLE"
    "Done creating Schema 'TESTSCHEMA'. Roles and privileges have been granted."
    "Done creating Schema 'TESTSCHEMA_RO'. Roles and privileges have been granted."
    "Done creating OC_DUMP_DIR at /var/tmp/ocdumpdir"
    "Done granting privs to users and profiles"
    "Testing connectivity to the new schema: 'TESTSCHEMA'"
    Connected.
    "Testing connectivity to the new read only schema: 'TESTSCHEMA_RO'"
    Connected.
     
    "Create is Complete. OC can now be used with the new schema: 'TESTSCHEMA'"
     
     
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    $
    
  6. Create a database properties file on the Enterprise Controller system. The database properties file must contain the location of the customer-managed database and the same user and read-only user credentials supplied in the schema creation script.

    For example:

    # vi /var/tmp/RemoteDBProps.txt
    mgmtdb.appuser=user
    mgmtdb.password=userpass
    mgmtdb.roappuser=user
    mgmtdb.ropassword=userpass
    mgmtdb.dburl=jdbc:oracle:thin:@<database host name>:<port>/<database service name>
    
  7. Change directory to xvmoc_full_bundle, and run the install script with the --remoteDBprops=<path to database properties file> option. For example:

    # cd xvmoc_full_bundle
    # ./install --remoteDBprops=/var/tmp/RemoteDBProps.txt
    
  8. The Oracle Configuration Manager installation text is displayed. Enter the My Oracle Support user name or email address that you want to associate with Oracle Enterprise Manager Ops Center.

    Provide your email address to be informed of security issues, install and
    initiate Oracle Configuration Manager. Easier for you if you use your My
    Oracle Support Email address/User Name.
    Visit http://www.oracle.com/support/policies.html for details.
    Email address/User Name:
    
  9. If you want security updates to appear on your My Oracle Support page, enter your My Oracle Support password.

    Provide your My Oracle Support password to receive security updates via your My Oracle Support account.
    Password (optional):
    

    The screen clears, then the install script displays a list of installation tasks that automatically updates as the installation proceeds. For example:

    Ops Center Enterprise Controller Installer
    (version 12.1.2.2140 on Linux)
     
    1. Check for installation prerequisites.                       [Not Completed]
    2. Configure file systems.                                     [Not Completed]
    3. Install prerequisite packages.                              [Not Completed]
    4. Install Agent components.                                   [Not Completed]
    5. Create Deployable Proxy Bundles.                            [Not Completed]
    6. Install application packages.                               [Not Completed]
    7. Run postinstall tasks.                                      [Not Completed]
    8. Install Expect.                                             [Not Completed]
    9. Install IPMI tool.                                          [Not Completed]
    10. Set database credentials.                                  [Not Completed]
    11. Install and Configure Oracle Database.                     [Not Completed]
    12. Seed Ops Center Database Schema                            [Not Completed]
    13. Install Service container components.                      [Not Completed]
    14. Install Core Channel components.                           [Not Completed]
    15. Install Proxy Core components.                             [Not Completed]
    16. Set Proxy database credentials.                            [Not Completed]
    17. Install Enterprise Controller components.                  [Not Completed]
    18. Install Update Connection - Enterprise.                    [Not Completed]
    19. Install Ops Center BUI components.                         [Not Completed]
    20. Install OS provisioning components.                        [Not Completed]
    21. Initialize and start services.                             [Not Completed]
    Executing current step:  Check for installation prerequisites...
    (version 12.1.0.0 on Linux)
    
  10. Review and correct any problems when the install script checks for installation prerequisites that are not met. For example, this install script detected insufficient disk space:

    Warning for Step: Check for installation prerequisites.
    The following is a portion of the installer
    log which may indicate the cause of the warning.
    If this does not indicate the cause of the
    warning, you will need to view the full log
    file. More information on how to do that is
    available below.
    You may choose to ignore this warning by selecting to continue.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    
    Ignoring job: 01checkRPMs.pl
    Ignoring job: 03removeEmptyDirs.pl
    
    
    Executing job: jobs/00checkPrereqs.pl --install
    
    WARNING: Installation prerequisites not met:
    Disk: / 72G needed, 24G available.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    Please fix the problem and then try this step again.
    For a full log of the failed install see the file: /var/tmp/installer.log.9361.
    
    t. Try this step again (correct the failure before proceeding)
    c. Continue (ignore the warning)
    x. Exit
    Enter selection: (t/c/x)
    

    You can enter t to try again, c to continue and ignore the warning, or x to exit the install script. You should exit the install script, correct the problem, and then run the install script again, which resumes from where it stopped. Choose to continue and ignore the warning only if you accept the impact that the error condition will have on your installation. Entering t typically produces the same error, unless you are able to correct the problem before trying the step again. If the install script finds that all prerequisites have been satisfied, or if you choose to continue despite the warning, the install script continues and installs all Enterprise Controller and Proxy Controller components.

    When complete, the install script displays a confirmation that all components have been installed. The /var/tmp/installer.log.latest file contains the installation log.

  11. Use the /opt/sun/xvmoc/bin/ecadm command to check the status of the Enterprise Controller services. If the installation has completed successfully, the services should be online. For example:

    # /opt/sun/xvmoc/bin/ecadm status
    online
    # 
    
  12. Delete the database properties file that you created on the Enterprise Controller system.

    For example:

    # rm /var/tmp/RemoteDBProps.txt
    

When the installation is complete, configure the Enterprise Controller using one of the procedures in the Configuring an Enterprise Controller section.

3.1.3 Installing an Enterprise Controller with High Availability

This procedure describes the steps required to install Enterprise Controller software on systems that are running the Linux OS, with one Enterprise Controller configured as the primary and one or more Enterprise Controllers configured as standby systems. This enables you to switch to a different node to perform maintenance or avoid a loss of service if one node fails.

This procedure configures the software to use a remote Oracle Database. The customer-managed database must be installed and configured separately. See the Oracle Enterprise Manager Ops Center Certified Systems Matrix for a list of supported database versions and database options.

The script that installs the Enterprise Controller also automatically installs a Proxy Controller on the same system, but it does not enable the Proxy Controller. In the configuration steps perfomed as part of the primary Enterprise Controller installation, you can choose to enable this Proxy Controller.

When you have completed this procedure, configure only the primary Enterprise Controller as described in the Configuring an Enterprise Controller section.

Note:

The installation procedure requires database user name and password information. Work with your database administrator if you do not have access to this information.

3.1.3.1 Preparing for High Availability with Oracle Clusterware

Installing and configuring Oracle Clusterware is the first step in setting up High Availability in your environment.

To Configure Systems for High Availability

  1. Install Oracle Clusterware in your environment. The Oracle Clusterware installation documentation is available at http://download.oracle.com/docs/cd/B28359_01/install.111/b28263/toc.htm.

  2. Identify an existing Oracle Database 11g Enterprise Edition database to use, or install and configure a customer-managed database according to the Oracle Database 11g Enterprise Edition installation documentation.

    Note:

    Each node must use the same name service for validating local users and groups.

3.1.3.2 Installing the Enterprise Controller on the First Node

You must install the Enterprise Controller on each cluster node before configuring the software. The first node is initially configured as the active node.

To Install the Enterprise Controller on the First Node

  1. Create a temporary directory on your system, then copy or move the appropriate Oracle Enterprise Manager Ops Center archive for your system from delivery media to the temporary directory that you created. For example:

    # mkdir /var/tmp/OC
    # cp enterprise-controller.Linux.i686.12.1.0.0.tar.gz /var/tmp/OC
    

    The installation archive consumes about 3.5 GBytes of disk space.

  2. Change to the directory where the installation archive is located on your system.

    # cd /var/tmp/OC
    #
    
  3. Expand the installation archive, then list the contents of the expanded directory.

    • If your installation archive has the .zip extension, use the unzip command to uncompress the archive. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.zip
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.zip
      xvmoc_full_bundle
      #
      
    • If your installation archive has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. The data extracted from the archive consumes about 1.5 GB of additional space. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.tar.zip | tar xf -
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.tar.zip
      xvmoc_full_bundle
      #
      
  4. Identify an existing Oracle Database 11g Enterprise Edition database to use, or install and configure a customer-managed database according to the Oracle Database 11g Enterprise Edition installation documentation.

  5. Copy the createOCSchema.sql script from the Enterprise Controller to the customer-managed database server. This script is in the/var/tmp/OC/xvmoc_full_bundle/Linux_i686/Product/installer/scripts directory.

    For example, on the customer-managed database server:

    # scp root@EnterpriseController:/var/tmp/OC/xvmoc_full_bundle/SunOS_i386/Product/installer/scripts/createOCSchema.sql .
    Password:
    createOCSchema.sql  100% |*********************| 1486     00:00
    
  6. As the customer-managed database administrator, run the createOCSchema_remote.sql script and enter the following information:

    • Oracle Enterprise Manager Ops Center user name – This is a database user that Oracle Enterprise Manager Ops Center uses to access the database.

    • Oracle Enterprise Manager Ops Center password – This is the password for the database user. See the Oracle Database 11g Enterprise Edition documentation for information about password length and character restrictions.

    • Oracle Enterprise Manager Ops Center read-only user name – This is a read-only database user that Oracle Enterprise Manager Ops Center uses to view the database.

    • Oracle Enterprise Manager Ops Center read-only password – This is the password for the read-only database user.

    • Default tablespace – This is the default tablespace for the Oracle Enterprise Manager Ops Center user.

    • Temporary tablespace – This is the temporary tablespace for the Oracle Enterprise Manager Ops Center user.

    • Oracle Enterprise Manager Ops Center dump directory – This directory must exist and must be owned by the oracle user.

    When you enter all of the required information, the createOCSchema_remote.sql script indicates completion and exits.

    For example:

    $ sqlplus / as sysdba @createOCSchema_remote.sql
     
    SQL*Plus: Release 11.2.0.3.0 Production on Thu Dec 15 16:55:34 2011
     
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
     
     
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
     
    Enter username for Ops Center database login: TESTSCHEMA
    Enter password for Ops Center database login:
    Enter username for read only Ops Center database login: TESTSCHEMA_RO
    Enter password for read only Ops Center database login:
    Enter default tablespace for Ops Center user: USERS
    Enter temporary tablespace for Ops Center user: TEMP
    Enter Oracle Data Pump destination directory: /var/tmp/ocdumpdir
     
    "Done creating OC_SYSTEM_ROLE and OC_RO_ROLE"
    "Done creating Schema 'TESTSCHEMA'. Roles and privileges have been granted."
    "Done creating Schema 'TESTSCHEMA_RO'. Roles and privileges have been granted."
    "Done creating OC_DUMP_DIR at /var/tmp/ocdumpdir"
    "Done granting privs to users and profiles"
    "Testing connectivity to the new schema: 'TESTSCHEMA'"
    Connected.
    "Testing connectivity to the new read only schema: 'TESTSCHEMA_RO'"
    Connected.
     
    "Create is Complete. OC can now be used with the new schema: 'TESTSCHEMA'"
     
     
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    $
    
  7. Create a database properties file on the Enterprise Controller system. The database properties file must contain the location of the customer-managed database and the same user and read-only user credentials supplied in the schema creation script.

    For example:

    # vi /var/tmp/RemoteDBProps.txt
    mgmtdb.appuser=user
    mgmtdb.password=userpass
    mgmtdb.roappuser=user
    mgmtdb.ropassword=userpass
    mgmtdb.dburl=jdbc:oracle:thin:@<database host name>:<port>/<database service name>
    
  8. Change directory to xvmoc_full_bundle, and run the install script with the --remoteDBprops=<path to database properties file> option. For example:

    # cd xvmoc_full_bundle
    # ./install --remoteDBprops=/var/tmp/remoteDBProps.txt
    
  9. The Oracle Configuration Manager installation text is displayed. Enter the My Oracle Support user name or email address that you want to associate with Oracle Enterprise Manager Ops Center.

    Provide your email address to be informed of security issues, install and
    initiate Oracle Configuration Manager. Easier for you if you use your My
    Oracle Support Email address/User Name.
    Visit http://www.oracle.com/support/policies.html for details.
    Email address/User Name:
    
  10. If you want security updates to appear on your My Oracle Support page, enter your My Oracle Support password.

    Provide your My Oracle Support password to receive security updates via your My Oracle Support account.
    Password (optional):
    

    The screen clears, then the install script displays a list of installation tasks that automatically updates as the installation proceeds. For example:

    Ops Center Enterprise Controller Installer
    (version 12.1.2.2140 on Linux)
     
    1. Check for installation prerequisites.                       [Not Completed]
    2. Configure file systems.                                     [Not Completed]
    3. Install prerequisite packages.                              [Not Completed]
    4. Install Agent components.                                   [Not Completed]
    5. Create Deployable Proxy Bundles.                            [Not Completed]
    6. Install application packages.                               [Not Completed]
    7. Run postinstall tasks.                                      [Not Completed]
    8. Install Expect.                                             [Not Completed]
    9. Install IPMI tool.                                          [Not Completed]
    10. Set database credentials.                                  [Not Completed]
    11. Install and Configure Oracle Database.                     [Not Completed]
    12. Seed Ops Center Database Schema                            [Not Completed]
    13. Install Service container components.                      [Not Completed]
    14. Install Core Channel components.                           [Not Completed]
    15. Install Proxy Core components.                             [Not Completed]
    16. Set Proxy database credentials.                            [Not Completed]
    17. Install Enterprise Controller components.                  [Not Completed]
    18. Install Update Connection - Enterprise.                    [Not Completed]
    19. Install Ops Center BUI components.                         [Not Completed]
    20. Install OS provisioning components.                        [Not Completed]
    21. Initialize and start services.                             [Not Completed]
    Executing current step:  Check for installation prerequisites...
    (version 12.1.0.0 on Linux)
    
  11. Review and correct any problems when the install script checks for installation prerequisites that are not met. For example, this install script detected insufficient disk space:

    Warning for Step: Check for installation prerequisites.
    The following is a portion of the installer
    log which may indicate the cause of the warning.
    If this does not indicate the cause of the
    warning, you will need to view the full log
    file. More information on how to do that is
    available below.
    You may choose to ignore this warning by selecting to continue.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    
    Ignoring job: 01checkRPMs.pl
    Ignoring job: 03removeEmptyDirs.pl
    
    
    Executing job: jobs/00checkPrereqs.pl --install
    
    WARNING: Installation prerequisites not met:
    Disk: / 72G needed, 24G available.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    Please fix the problem and then try this step again.
    For a full log of the failed install see the file: /var/tmp/installer.log.9361.
    
    t. Try this step again (correct the failure before proceeding)
    c. Continue (ignore the warning)
    x. Exit
    Enter selection: (t/c/x)
    

    You can enter t to try again, c to continue and ignore the warning, or x to exit the install script. You should exit the install script, correct the problem, and then run the install script again, which resumes from where it stopped. Choose to continue and ignore the warning only if you accept the impact that the error condition will have on your installation. Entering t typically produces the same error, unless you are able to correct the problem before trying the step again. If the install script finds that all prerequisites have been satisfied, or if you choose to continue despite the warning, the install script continues and installs all Enterprise Controller and Proxy Controller components.

    When complete, the install script displays a confirmation that all components have been installed. The /var/tmp/installer.log.latest file contains the installation log.

  12. Delete the database properties file that you created on the Enterprise Controller system.

    For example:

    # rm /var/tmp/RemoteDBProps.txt
    

3.1.3.3 Installing the Enterprise Controller on the Standby Nodes

Once you have installed the Enterprise Controller on the primary node, you can install on standby nodes.

To Install the Enterprise Controller on a Standby Node

  1. Create a temporary directory on your system, then copy or move the appropriate Oracle Enterprise Manager Ops Center archive for your system from delivery media to the temporary directory that you created. For example:

    # mkdir /var/tmp/OC
    # cp enterprise-controller.Linux.i686.12.1.0.0.tar.gz /var/tmp/OC
    

    The installation archive consumes about 3.5 GBytes of disk space.

  2. Change to the directory where the installation archive is located on your system.

    # cd /var/tmp/OC
    #
    
  3. Expand the installation archive, then list the contents of the expanded directory.

    • If your installation archive has the .zip extension, use the unzip command to uncompress the archive. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.zip
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.zip
      xvmoc_full_bundle
      #
      
    • If your installation archive has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. The data extracted from the archive consumes about 1.5 GB of additional space. For example:

      # unzip enterprise-controller.Linux.i686.12.1.2.2140.tar.zip | tar xf -
      # ls
      enterprise-controller.Linux.i686.12.1.2.2140.tar.zip
      xvmoc_full_bundle
      #
      
  4. Create a database properties file on the Enterprise Controller system. The database properties file must contain the location of the customer-managed database and a user name and password that can access the database.

    For example:

    # vi /var/tmp/RemoteDBProps.txt
    mgmtdb.appuser=user
    mgmtdb.password=userpass
    mgmtdb.roappuser=user
    mgmtdb.ropassword=userpass
    mgmtdb.dburl=jdbc:oracle:thin:@<database host name>:<port>/<database service name>
    
  5. Change directory to xvmoc_full_bundle, and run the install script with the --remoteDBprops <path to database properties file> and --standbyEC options. For example:

    # cd xvmoc_full_bundle
    # ./install --remoteDBprops=/var/tmp/remoteDBProps.txt --standbyEC
    
  6. The Oracle Configuration Manager installation text is displayed. Enter the My Oracle Support user name or email address that you want to associate with Oracle Enterprise Manager Ops Center.

    Provide your email address to be informed of security issues, install and
    initiate Oracle Configuration Manager. Easier for you if you use your My
    Oracle Support Email address/User Name.
    Visit http://www.oracle.com/support/policies.html for details.
    Email address/User Name:
    
  7. If you want security updates to appear on your My Oracle Support page, enter your My Oracle Support password.

    Provide your My Oracle Support password to receive security updates via your My Oracle Support account.
    Password (optional):
    

    The screen clears, then the install script displays a list of installation tasks that automatically updates as the installation proceeds. For example:

    Ops Center Enterprise Controller Installer
    (version 12.1.2.2140 on Linux)
     
    1. Check for installation prerequisites.                       [Not Completed]
    2. Configure file systems.                                     [Not Completed]
    3. Install prerequisite packages.                              [Not Completed]
    4. Install Agent components.                                   [Not Completed]
    5. Create Deployable Proxy Bundles.                            [Not Completed]
    6. Install application packages.                               [Not Completed]
    7. Run postinstall tasks.                                      [Not Completed]
    8. Install Expect.                                             [Not Completed]
    9. Install IPMI tool.                                          [Not Completed]
    10. Set database credentials.                                  [Not Completed]
    11. Install and Configure Oracle Database.                     [Not Completed]
    12. Seed Ops Center Database Schema                            [Not Completed]
    13. Install Service container components.                      [Not Completed]
    14. Install Core Channel components.                           [Not Completed]
    15. Install Proxy Core components.                             [Not Completed]
    16. Set Proxy database credentials.                            [Not Completed]
    17. Install Enterprise Controller components.                  [Not Completed]
    18. Install Update Connection - Enterprise.                    [Not Completed]
    19. Install Ops Center BUI components.                         [Not Completed]
    20. Install OS provisioning components.                        [Not Completed]
    21. Initialize and start services.                             [Not Completed]
    Executing current step:  Check for installation prerequisites...
    (version 12.1.0.0 on Linux)
    
  8. Review and correct any problems when the install script checks for installation prerequisites that are not met. For example, this install script detected insufficient disk space:

    Warning for Step: Check for installation prerequisites.
    The following is a portion of the installer
    log which may indicate the cause of the warning.
    If this does not indicate the cause of the
    warning, you will need to view the full log
    file. More information on how to do that is
    available below.
    You may choose to ignore this warning by selecting to continue.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    
    Ignoring job: 01checkRPMs.pl
    Ignoring job: 03removeEmptyDirs.pl
    
    
    Executing job: jobs/00checkPrereqs.pl --install
    
    WARNING: Installation prerequisites not met:
    Disk: / 72G needed, 24G available.
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    Please fix the problem and then try this step again.
    For a full log of the failed install see the file: /var/tmp/installer.log.9361.
    
    t. Try this step again (correct the failure before proceeding)
    c. Continue (ignore the warning)
    x. Exit
    Enter selection: (t/c/x)
    

    You can enter t to try again, c to continue and ignore the warning, or x to exit the install script. You should exit the install script, correct the problem, and then run the install script again, which resumes from where it stopped. Choose to continue and ignore the warning only if you accept the impact that the error condition will have on your installation. Entering t typically produces the same error, unless you are able to correct the problem before trying the step again. If the install script finds that all prerequisites have been satisfied, or if you choose to continue despite the warning, the install script continues and installs all Enterprise Controller and Proxy Controller components.

    When complete, the install script displays a confirmation that all components have been installed. The /var/tmp/installer.log.latest file contains the installation log.

  9. Create a password file containing the root user name and password for the primary Enterprise Controller. For example:

    # touch /tmp/creds.props
    # chmod 400 /tmp/creds.props
    # vi /tmp/creds.props
    # cat /tmp/creds.props
    username:root
    password:XXXXX
    
  10. Delete the database properties file that you created on the Enterprise Controller system.

    For example:

    # rm /var/tmp/RemoteDBProps.txt
    

3.1.3.4 Configuring the Primary Enterprise Controller

Once you have installed the primary and standby Enterprise Controllers, configure the primary Enterprise Controller to act as the primary.

To Configure the Primary Enterprise Controller

  1. Use the /opt/sun/xvmoc/bin/ecadm command with the ha-configure-primary subcommand to configure the system as the active Enterprise Controller.

    If the clusterware crsctl command is not in the /u01 directory, use the --crsctl_basepath <location> option to specify its location.

    For example:

    # /opt/sun/xvmoc/bin/ecadm ha-configure-primary
    INFO: HAECClusterwareAdapter/doConfigurePrimary() Stopping Ops Center ...
    INFO: HAECClusterwareAdapter/doConfigurePrimary() Ops Center stopped
    INFO: HAECClusterwareAdapter/createActionScript() created Resource Action Script='/var/opt/sun/xvm/ha/EnterpriseController'
    INFO: HAECClusterwareAdapter/doConfigurePrimary() created Clusterware Action Script='/var/opt/sun/xvm/ha/EnterpriseController'
    INFO: HAECClusterwareAdapter/doConfigurePrimary() created Clusterware Resource='EnterpriseController'
    INFO: HAECClusterwareAdapter/doHAStart() starting resource='EnterpriseController' on node='primary-system'
    INFO: HAECClusterwareAdapter/doHAStart()statusSB='CRS-2672: Attempting to start 'EnterpriseController' on 'primary-system'
    CRS-2676: Start of 'EnterpriseController' on 'primary-system' succeeded'
    INFO: HAECClusterwareAdapter/doHAStart() started resource='EnterpriseController' on node='primary-system'
    INFO: HAECClusterwareAdapter/doConfigurePrimary() Ops Center started on node='primary-system'
    ecadm:    --- Enterprise Controller successfully configured HA primary node
    # 
    
  2. Use the /opt/sun/xvmoc/bin/ecadm command with the status option to check the status of the Enterprise Controller services. For example:

    # /opt/sun/xvmoc/bin/ecadm status
    online
    # 
    
  3. Use the /opt/sun/xvmoc/bin/ecadm command with the ha-status -d option to check the status of the standby Enterprise Controller. For example:

    # /opt/sun/xvmoc/bin/ecadm ha-status -d
    INFO: HAECClusterwareAdapter/doHAStatus() Status:
    # HAEC Cluster Info: Thu Sep 29 15:49:09 MDT 2011
    haec.cluster.active.node=active
    haec.cluster.nodes=active
    haec.ec.public.nics=nge1
    haec.ec.status=ONLINE
    <output omitted>
    haec.cluster.script=/var/opt/sun/xvm/ha/EnterpriseController
    haec.cluster.crsctl=/u01/app/11.2.0/grid/bin/crsctl
    # End of Cluster Info
    ecadm:    --- Enterprise Controller ha-status command succeeded
    Status stored in file: /var/opt/sun/xvm/ha/HAECStatus
    # 
    
  4. Go to Configuring an Enterprise Controller and follow the steps to configure the active Enterprise Controller.

3.1.3.5 Configuring the Standby Enterprise Controllers

Once you have configured the primary Enterprise Controller, configure the standby Enterprise Controllers to act as standbys.

To Configure a Standby Enterprise Controller

  1. Use the /opt/sun/xvmoc/bin/ecadm command with the ha-configure-standby and -p <password file> subcommands to configure the system as a standby Enterprise Controller.

    If the clusterware crsctl command is not in the /u01 directory, use the --crsctl_basepath <location> option to specify its location.

    For example:

    # /opt/sun/xvmoc/bin/ecadm ha-configure-standby -p /tmp/creds.props
    INFO: HAECClusterwareAdapter/doConfigureStandby() Stopping Ops Center ...
    INFO: HAECClusterwareAdapter/doConfigureStandby() Ops Center stopped
    INFO: remoteFileCopy() copied '/etc/passwd' from remoteHostname='primary-system' to local file='/tmp/activeNodepw'
    <output omitted>
    ecadm:    --- Enterprise Controller successfully configured HA standby node
    
  2. Use the /opt/sun/xvmoc/bin/ecadm command with the ha-status -d option to check the status of the standby Enterprise Controller. For example:

    # /opt/sun/xvmoc/bin/ecadm ha-status -d
    INFO: HAECClusterwareAdapter/doHAStatus() Status:
    # HAEC Cluster Info: Thu Sep 29 15:49:09 MDT 2011
    haec.cluster.active.node=primary
    haec.cluster.nodes=standby, primary
    haec.ec.public.nics=nge1
    haec.ec.status=ONLINE
    <output omitted>
    haec.cluster.script=/var/opt/sun/xvm/ha/EnterpriseController
    haec.cluster.crsctl=/u01/app/11.2.0/grid/bin/crsctl
    # End of Cluster Info
    ecadm:    --- Enterprise Controller ha-status command succeeded
    Status stored in file: /var/opt/sun/xvm/ha/HAECStatus
    # 
    

3.2 Configuring an Enterprise Controller

After you install the Enterprise Controller, you must configure it. During the configuration process, you specify how Oracle Enterprise Manager Ops Center operates.

The following tasks are part of the configuration process:

  • Supplying Enterprise Controller information

  • Deploying one or more Proxy Controllers (optional in this wizard, but must be performed before using the software)

  • Registering the Enterprise Controller (optional)

  • Creating libraries

  • Choosing a connection mode and configuring services (optional in this wizard, but must be performed before using the software)

This procedure describes the complete Enterprise Controller configuration process, including Proxy Controller deployment, asset discovery, connection mode selection, and registration.

Three types of configuration are described in this section:

  • Simple deployment - A simple deployment configures the co-located Proxy Controller on the Enterprise Controller system. This deployment is effective for small environments.

  • Advanced deployment - An advanced deployment installs and configures one or more Proxy Controllers on remote systems. This deployment is effective for larger environments.

  • Deploy without installing a Proxy Controller - This deployment configures the Enterprise Controller without installing or configuring any Proxy Controllers. This deployment is appropriate if you intend to install and configure Proxy Controllers after configuration. Oracle Enterprise Manager Ops Center cannot function without at least one Proxy Controller.

Note:

You should not install a Proxy Controller in an environment where there is a web proxy which requires authentication between the Enterprise Controller and the Proxy Controller. Many OS update functions are not usable for systems managed by such a Proxy Controller.

3.2.1 Configuring an Enterprise Controller with a Simple Deployment

A simple deployment configures the co-located Proxy Controller on the Enterprise Controller system.

Before You Begin

  • If you intend to operate in Disconnected Mode, acquire an update bundle:

    1. Download https://updates.oracle.com/OCDoctor/harvester_bundle-latest.zip on an Internet-facing system.

    2. Unzip the bundle.

    3. Run the harvester script on an Internet-facing Oracle Solaris or Linux system. The script connects to the Oracle Datacenter and creates an update bundle. For example:

      # ./harvester --user <MOS user name> --password-file <password file location> --kb-only
      Directory /export/home/public not found. This directory will be created.
      Setting up local directory structure at: /export/home/public
      Initialization: Downloading channels.xml
      Tue Jan 17 05:08:01 MST 2012 Clearing cookies to initialize new session.
      Distributions:
      Identifying and Downloading the Notifications and Seeker scripts
      Creating tarball...
      
      Tarball successfully created at /discon/standalone-0127.tar.gz
      
      Start time: Tue Jan 17 05:08:00 MST 2012
      Completion time: Tue Jan 17 05:08:01 MST 2012
      <output omitted>
      
    4. Copy the resulting bundle back to the Enterprise Controller system.

  • If you intend to operate in Connected Mode, go to https://support.oracle.com/ and log in to verify that you have a valid set of My Oracle Support (MOS) credentials.

To Configure the Enterprise Controller with a Simple Deployment

  1. In a browser, navigate to https://<Enterprise Controller>:9443.

    The Login page is displayed.

  2. Enter the system's root user name and password and select Ops Center as the source, then click Log In.

  3. If the configuration detects any prerequisites that are not met, the Prerequisite Checklist page is displayed. If the Prerequisite Checklist is not displayed, skip this step.

    If the Prerequisite Checklist is displayed, review the prerequisites. If necessary, cancel the configuration and make changes to the system as suggested by the checklist. Click Next.

    The Enterprise Controller Setup page is displayed.

  4. Enter the Enterprise Controller setup information, then click Next. Configuration information includes:

    • Enterprise Controller name – The Enterprise Controller name that is displayed in the masthead.

    • Administrative User – The Administrative User is given the Enterprise Controller Admin and All Assets Admin roles. Until other users are added, the Administrative User is the only user recognized by Oracle Enterprise Manager Ops Center. Select Set the Currently Logged In User as Administrative User to make the current user the Administrative User, or select Set the Following User as the Administrative User and enter a user name and password to make that user the Administrative User.

    • Proxy Controller Setup – This option sets the initial Proxy Controller configuration. Select Co-located Proxy Controller.

      A popup is displayed indicating that the local Proxy Controller is being configured. Click Close to close the popup, then click Next.

    The Proxy Controller Status page is displayed.

  5. View the status of the configured Proxy Controller and verify that the Proxy Controller you installed and configured is online.

    (Optional) Click Refresh to refresh the list of Proxy Controllers.

    (Optional) Click Check, then enter a host name or IP address. The connectivity and status of the specified host is checked.

    Click Next.

    The Connection Mode page is displayed.

  6. Select a connection mode option:

    • Connected Mode – Oracle Enterprise Manager Ops Center downloads patches from Oracle and other vendors. The Enterprise Controller must be able to access the Internet, either directly or through an HTTP Proxy, to use Connected Mode.

      If you select Connected Mode, you can also enable or disable Automated Service Requests (ASRs).

    • Disconnected Mode – Oracle Enterprise Manager Ops Center operates autonomously, and patches must be manually downloaded and supplied to the Enterprise Controller.

    Click Next.

  7. If you selected Connected Mode, the Connecting to My Oracle Support page is displayed. Enter your My Oracle Support (MOS) user name and password. You must have a valid MOS Account. If the Enterprise Controller requires an HTTP Proxy to reach the Internet, check Use HTTP Proxy and enter the HTTP Proxy information:

    • Server – The HTTP Proxy server.

    • Port – The port used to access the HTTP Proxy server.

    • (Optional) Authorized user name – The authorized user name is required if the HTTP Proxy can only be accessed by an authorized user.

    • (Optional) Password – The password is required if the HTTP Proxy can only be accessed by an authorized user.

    Click Next.

  8. If you enabled Automated Service Requests (ASRs), the Automated Service Request Contact page is displayed. Enter the default contact information for ASRs:

    • First Name – The first name of the ASR contact.

    • Last Name – The last name of the ASR contact.

    • Phone – The phone number for the ASR contact.

    • Email – The email address for the ASR contact.

    • Country – The country where the assets are located.

    • Address 1 – The address where the assets are located.

    • (Optional) Address 2 – The second line of the address where the assets are located.

    • City – The city where the assets are located.

    • State/Province – The state or province where the assets are located.

    • (Optional) Zip/Postal Code – The zip or postal code where the assets are located.

    • Time Zone – The time zone where the assets are located.

    Click Next.

  9. The Create Software Libraries page is displayed. Oracle Enterprise Manager Ops Center either creates the libraries or connects to NAS libraries in the locations that you specify. If you are using High Availability for the Enterprise Controller, these libraries must not be created locally.

    Enter a location for each library:

    • Software Library – This library stores firmware images, ISOs, and flash archives.

    • Linux and Oracle Solaris 8-10 Library – This library stores Linux and Oracle Solaris 8-10 OS images.

    Click Next.

  10. If you are configuring in Disconnected Mode, the Linux/Oracle Solaris 8-10 Software Bundle page is displayed. Enter the location of the update bundle that you downloaded before beginning this procedure.

    Click Next.

  11. The Configure DHCP page is displayed. To perform OS provisioning, you must configure DHCP on your Proxy Controllers.

    To configure DHCP for a Proxy Controller, select a Proxy Controller, then select a DHCP type from the drop-down list. Add one or more interfaces to the list of selected interfaces, then click Configure DHCP.

    The Summary page is displayed.

  12. Click Finish.

    Oracle Enterprise Manager Ops Center is configured, and you are logged in to the UI.

3.2.2 Configuring an Enterprise Controller with an Advanced Deployment

An Advanced Deployment installs and configures one or more Proxy Controllers on remote systems.

Before You Begin

  • If you intend to operate in Disconnected Mode, acquire an update bundle:

    1. Download https://updates.oracle.com/OCDoctor/harvester_bundle-latest.zip on an Internet-facing system.

    2. Unzip the bundle.

    3. Run the harvester script on an Internet-facing Oracle Solaris or Linux system. The script connects to the Oracle Datacenter and creates an update bundle. For example:

      # ./harvester --user <MOS user name> --password-file <password file location> --kb-only
      Directory /export/home/public not found. This directory will be created.
      Setting up local directory structure at: /export/home/public
      Initialization: Downloading channels.xml
      Tue Jan 17 05:08:01 MST 2012 Clearing cookies to initialize new session.
      Distributions:
      Identifying and Downloading the Notifications and Seeker scripts
      Creating tarball...
      
      Tarball successfully created at /discon/standalone-0127.tar.gz
      
      Start time: Tue Jan 17 05:08:00 MST 2012
      Completion time: Tue Jan 17 05:08:01 MST 2012
      <output omitted>
      
    4. Copy the resulting bundle back to the Enterprise Controller system.

  • If you intend to operate in Connected Mode, go to https://support.oracle.com/ and log in to verify that you have a valid set of My Oracle Support (MOS) credentials.

To Configure the Enterprise Controller with an Advanced Deployment

  1. In a browser, navigate to https://<Enterprise Controller>:9443.

    The Login page is displayed.

  2. Enter the system's root user name and password and select Ops Center as the source, then click Log In.

  3. If the configuration detects any prerequisites that are not met, the Prerequisite Checklist page is displayed. If the Prerequisite Checklist is not displayed, skip this step.

    If the Prerequisite Checklist is displayed, review the prerequisites. If necessary, cancel the configuration and make changes to the system as suggested by the checklist. Click Next.

    The Enterprise Controller Setup page is displayed.

  4. Enter the Enterprise Controller setup information, then click Next. Configuration information includes:

    • Enterprise Controller name – The Enterprise Controller name that is displayed in the masthead.

    • Administrative User – The Administrative User is given the Enterprise Controller Admin and All Assets Admin roles. Until other users are added, the Administrative User is the only user recognized by Oracle Enterprise Manager Ops Center. Select Set the Currently Logged In User as Administrative User to make the current user the Administrative User, or select Set the Following User as the Administrative User and enter a user name and password to make that user the Administrative User.

    • Proxy Controller Setup – This option sets the initial Proxy Controller configuration. Select Remote Proxy Controllers.

  5. The Remote Proxy Controllers page is displayed. Enter credentials for one or more remote systems, then click Next. Proxy Controllers are installed and configured on these systems.

    • Hostname or IP address – The host names or IP addresses of the Proxy Controller systems.

    • SSH User name – The SSH user name to be used to log into the systems. If root SSH access is allowed on the target system, enter the root user name and password in the SSH User and SSH Password fields.

    • SSH Password – The password associated with the SSH user name.

    • (Optional) Privileged User name – The privileged user name to be used to log in. If root SSH access is not allowed on the target system, enter the login user name and password in the SSH User and SSH Password fields, then enter the root user name and password in the Privileged Role and Role Password fields.

    • (Optional) Privileged Password – The password associated with the Privileged user name. Click Add to add fields for another Proxy Controller, then enter credentials for it.

    The Proxy Controller Status page is displayed.

  6. View the status of the configured Proxy Controllers and verify that the Proxy Controllers you installed and configured are online.

    (Optional) Click Refresh to refresh the list of Proxy Controllers.

    (Optional) Click Check, then enter a host name or IP address. The connectivity and status of the specified host is checked.

    Click Next.

    The Connection Mode page is displayed.

  7. Select a connection mode option:

    • Connected Mode – Oracle Enterprise Manager Ops Center downloads patches from Oracle and other vendors. The Enterprise Controller must be able to access the Internet, either directly or through an HTTP Proxy, to use Connected Mode.

      If you select Connected Mode, you can also enable or disable Automated Service Requests (ASRs).

    • Disconnected Mode – Oracle Enterprise Manager Ops Center operates autonomously, and patches must be manually downloaded and supplied to the Enterprise Controller.

    Click Next.

  8. If you selected Connected Mode, the Connecting to My Oracle Support page is displayed. Enter your My Oracle Support (MOS) user name and password. You must have a valid MOS Account. If the Enterprise Controller requires an HTTP Proxy to reach the Internet, check Use HTTP Proxy and enter the HTTP Proxy information:

    • Server – The HTTP Proxy server.

    • Port – The port used to access the HTTP Proxy server.

    • (Optional) Authorized user name – The authorized user name is required if the HTTP Proxy can only be accessed by an authorized user.

    • (Optional) Password – The password is required if the HTTP Proxy can only be accessed by an authorized user.

    Click Next.

  9. If you enabled Automated Service Requests (ASRs), the Automated Service Request Contact page is displayed. Enter the default contact information for ASRs:

    • First Name – The first name of the ASR contact.

    • Last Name – The last name of the ASR contact.

    • Phone – The phone number for the ASR contact.

    • Email – The email address for the ASR contact.

    • Country – The country where the assets are located.

    • Address 1 – The address where the assets are located.

    • (Optional) Address 2 – The second line of the address where the assets are located.

    • City – The city where the assets are located.

    • State/Province – The state or province where the assets are located.

    • (Optional) Zip/Postal Code – The zip or postal code where the assets are located.

    • Time Zone – The time zone where the assets are located.

    Click Next.

  10. The Create Software Libraries page is displayed. Oracle Enterprise Manager Ops Center either creates the libraries or connects to NAS libraries in the locations that you specify. If you are using High Availability for the Enterprise Controller, these libraries must not be created locally.

    Enter a location for each library:

    • Software Library – This library stores firmware images, ISOs, and flash archives.

    • Linux and Oracle Solaris 8-10 Library – This library stores Linux and Oracle Solaris 8-10 OS images.

    Click Next.

  11. If you are configuring in Disconnected Mode, the Linux/Oracle Solaris 8-10 Software Bundle page is displayed. Enter the location of the update bundle that you downloaded before beginning this procedure.

    Click Next.

  12. The Configure DHCP page is displayed. To perform OS provisioning, you must configure DHCP on your Proxy Controllers.

    To configure DHCP for a Proxy Controller, select a Proxy Controller, then select a DHCP type from the drop-down list. Add one or more interfaces to the list of selected interfaces, then click Configure DHCP.

    The Summary page is displayed.

  13. Click Finish.

    Oracle Enterprise Manager Ops Center is configured, and you are logged in to the UI.

3.2.3 Configuring an Enterprise Controller Without Installing a Proxy Controller

This procedure configures the Enterprise Controller without installing or configuring a Proxy Controller. You can either provision one or more Proxy Controllers through the user interface or manually install and configure one or more Proxy Controllers. You must install and configure at least one Proxy Controller before using the software to manage assets.

Before You Begin

  • If you intend to operate in Disconnected Mode, acquire an update bundle:

    1. Download https://updates.oracle.com/OCDoctor/harvester_bundle-latest.zip on an Internet-facing system.

    2. Unzip the bundle.

    3. Run the harvester script on an Internet-facing Oracle Solaris or Linux system. The script connects to the Oracle Datacenter and creates an update bundle. For example:

      # ./harvester --user <MOS user name> --password-file <password file location> --kb-only
      Directory /export/home/public not found. This directory will be created.
      Setting up local directory structure at: /export/home/public
      Initialization: Downloading channels.xml
      Tue Jan 17 05:08:01 MST 2012 Clearing cookies to initialize new session.
      Distributions:
      Identifying and Downloading the Notifications and Seeker scripts
      Creating tarball...
      
      Tarball successfully created at /discon/standalone-0127.tar.gz
      
      Start time: Tue Jan 17 05:08:00 MST 2012
      Completion time: Tue Jan 17 05:08:01 MST 2012
      <output omitted>
      
    4. Copy the resulting bundle back to the Enterprise Controller system.

  • If you intend to operate in Connected Mode, go to https://support.oracle.com/ and log in to verify that you have a valid set of My Oracle Support (MOS) credentials.

To Configure the Enterprise Controller Without Installing a Proxy Controller

  1. In a browser, navigate to https://<Enterprise Controller>:9443.

    The Login page is displayed.

  2. Enter the system's root user name and password and select Ops Center as the source, then click Log In.

  3. If the configuration detects any prerequisites that are not met, the Prerequisite Checklist page is displayed. If the Prerequisite Checklist is not displayed, skip this step.

    If the Prerequisite Checklist is displayed, review the prerequisites. If necessary, cancel the configuration and make changes to the system as suggested by the checklist. Click Next.

    The Enterprise Controller Setup page is displayed.

  4. Enter the Enterprise Controller setup information, then click Next. Configuration information includes:

    • Enterprise Controller name – The Enterprise Controller name that is displayed in the masthead.

    • Administrative User – The Administrative User is given the Enterprise Controller Admin and All Assets Admin roles. Until other users are added, the Administrative User is the only user recognized by Oracle Enterprise Manager Ops Center. Select Set the Currently Logged In User as Administrative User to make the current user the Administrative User, or select Set the Following User as the Administrative User and enter a user name and password to make that user the Administrative User.

    • Proxy Controller Setup – This option sets the initial Proxy Controller configuration. Select Manual Setup.

    The Connection Mode page is displayed.

  5. Select a connection mode option:

    • Connected Mode – Oracle Enterprise Manager Ops Center downloads patches from Oracle and other vendors. The Enterprise Controller must be able to access the Internet, either directly or through an HTTP Proxy, to use Connected Mode.

      If you select Connected Mode, you can also enable or disable Automated Service Requests (ASRs).

    • Disconnected Mode – Oracle Enterprise Manager Ops Center operates autonomously, and patches must be manually downloaded and supplied to the Enterprise Controller.

    Click Next.

  6. If you selected Connected Mode, the Connecting to My Oracle Support page is displayed. Enter your My Oracle Support (MOS) user name and password. You must have a valid MOS Account. If the Enterprise Controller requires an HTTP Proxy to reach the Internet, check Use HTTP Proxy and enter the HTTP Proxy information:

    • Server – The HTTP Proxy server.

    • Port – The port used to access the HTTP Proxy server.

    • (Optional) Authorized user name – The authorized user name is required if the HTTP Proxy can only be accessed by an authorized user.

    • (Optional) Password – The password is required if the HTTP Proxy can only be accessed by an authorized user.

    Click Next.

  7. If you enabled Automated Service Requests (ASRs), the Automated Service Request Contact page is displayed. Enter the default contact information for ASRs:

    • First Name – The first name of the ASR contact.

    • Last Name – The last name of the ASR contact.

    • Phone – The phone number for the ASR contact.

    • Email – The email address for the ASR contact.

    • Country – The country where the assets are located.

    • Address 1 – The address where the assets are located.

    • (Optional) Address 2 – The second line of the address where the assets are located.

    • City – The city where the assets are located.

    • State/Province – The state or province where the assets are located.

    • (Optional) Zip/Postal Code – The zip or postal code where the assets are located.

    • Time Zone – The time zone where the assets are located.

    Click Next.

  8. The Create Software Libraries page is displayed. Oracle Enterprise Manager Ops Center either creates the libraries or connects to NAS libraries in the locations that you specify. If you are using High Availability for the Enterprise Controller, these libraries must not be created locally.

    Enter a location for each library:

    • Software Library – This library stores firmware images, ISOs, and flash archives.

    • Linux and Oracle Solaris 8-10 Library – This library stores Linux and Oracle Solaris 8-10 OS images.

    Click Next.

  9. If you are configuring in Disconnected Mode, the Linux/Oracle Solaris 8-10 Software Bundle page is displayed. Enter the location of the update bundle that you downloaded before beginning this procedure.

    Click Next.

  10. The Configure DHCP page is displayed. To perform OS provisioning, you must configure DHCP on your Proxy Controllers.

    To configure DHCP for a Proxy Controller, select a Proxy Controller, then select a DHCP type from the drop-down list. Add one or more interfaces to the list of selected interfaces, then click Configure DHCP.

    The Summary page is displayed.

  11. Click Finish.

    Oracle Enterprise Manager Ops Center is configured, and you are logged in to the UI.

3.3 Installing and Configuring a Proxy Controller Remotely

The Deploy Proxy Wizard can be used to deploy and configure one or more remote Proxy Controllers, and to configure the co-located Proxy Controller. Proxy Controllers can be deployed at any time; however, Oracle Enterprise Manager Ops Center requires at least one Proxy Controller.

This installation installs, or upgrades to, Java Runtime Environment (JRE) 1.6_51. Later versions of JRE are not affected.

You must not install a Proxy Controller in an environment where there is a web proxy which requires authentication between the Enterprise Controller and the Proxy Controller. Many OS update functions are not usable for systems managed by such a Proxy Controller.

To install a Proxy Controller through the UI, the Enterprise Controller must be able to reach the Proxy Controller with an SSH connection using port 22 during the update process. This connection is used to transfer Proxy Controller bundles and execute commands on the Proxy Controller system. If your security restrictions do not allow this connection, install the Proxy Controller from the command line.

Note:

To provision an Oracle VM Server for SPARC, the Proxy Controller that performs the provisioning must be installed on Oracle Solaris.

To Deploy a Proxy Controller

You can use the Deploy Proxy Wizard to deploy and configure one or more Proxy Controllers.

  1. Click the Enterprise Controller in the Administration section of the Navigation Pane.

  2. Click Deploy Proxy in the Actions pane. The Proxy Controller Deployment page is displayed.

  3. Choose a deployment option:

    • Co-located Proxy – Configures the colocated Proxy Controller.

    • Remote Proxies – Lets you remotely install and configure one or more Proxy Controllers. Click Next.

    • If you select Co-located Proxy, a popup is displayed indicating that the local Proxy Controller is being configured. Click Close to close the popup.

      Skip the Proxy Controllers and Remote Proxy Controllers pages and proceed to the Proxy Controller Status page.

    • If you select Remote Proxies, Proxy Controller deployment steps are displayed. Proceed to the next step.

  4. If you selected Remote Proxies, the Proxy Controllers page is displayed. Select an option:

    • Deploy Automatically – Lets you deploy a remote Proxy Controller through the wizard.

    • Deploy Manually – Lets you install and configure a Proxy Controller manually.

  5. If you selected Remote Proxies, the Remote Proxy Controllers page is displayed. Click the add and remove icons to create an entry for each new Proxy Controller, then enter credentials for each remote system. Proxy Controllers are installed and configured on these systems.

    • Hostname or IP address – The host name or IP address of the target system.

    • SSH User name – If root SSH access is allowed on the target system, enter the root user name and password in the SSH User and SSH Password fields.

    • SSH Password – The password associated with the SSH user name.

    • (Optional) Privileged Role – If root SSH access is not allowed on the target system, enter the login user name and password in the SSH User and SSH Password fields, then enter the root user name and password in the Privileged Role and Role Password fields.

    • (Optional) Role Password – If you entered the root user name in the Privileged Role field, enter the root password.

    • Create Tunnel – Check this box to create a tunnel to the Proxy Controller.

    • Port – If you want the Proxy Controller to use a port other than the default, enter that port number.

    • Maintenance Mode – Check this box to start the Proxy Controller in maintenance mode.

    Click Next.

    The Proxy Controller Status page is displayed.

  6. View the status of the configured Proxy Controllers. Each Proxy Controller that you enabled or provisioned should be online.

    (Optional) Click Refresh to refresh the list of Proxy Controllers.

    (Optional) Click Check, then enter a host name or IP address. The connectivity and status of the specified host is checked.

    Click Next.

    The Summary page is displayed.

  7. Click Finish.

3.4 Installing and Configuring a Proxy Controller Manually

This section describes the steps required to install and configure Proxy Controller software on a Linux system that meets the recommended specifications for this installation. Proxy Controllers can be installed at any time; however, Oracle Enterprise Manager Ops Center requires at least one Proxy Controller. Use this procedure only to install and configure a Proxy Controller on a system other than the system on which the Enterprise Controller is installed.

3.4.1 Installing a Proxy Controller Manually

This installation installs, or upgrades to, Java Runtime Environment (JRE) 1.6_51. Later versions of JRE are not affected.

You can use the OC Doctor to verify that the system is prepared for the installation. See http://java.net/projects/oc-doctor for more information about the OC Doctor.

You must not install a Proxy Controller in an environment where there is a web proxy which requires authentication between the Enterprise Controller and the Proxy Controller. Many OS update functions are not usable for systems managed by such a Proxy Controller.

Note:

To provision an Oracle VM Server for SPARC, the Proxy Controller that performs the provisioning must be installed on Oracle Solaris.

Before You Begin

Before proceeding with the Proxy Controller installation, check that your system's resources meet the system requirements using the OC Doctor or using the manual procedure.

To Install a Proxy Controller

  1. Create a temporary directory on your system, then copy or move the appropriate Oracle Enterprise Manager Ops Center archive for your system from delivery media to the temporary directory that you created. The installation archive consumes about 700 MBytes of disk space. You must use the same Oracle Enterprise Manager Ops Center archive version as the one used to install the Enterprise Controller. For example:

    # mkdir /var/tmp/OC
    # cp proxy-controller.Linux.i686.12.1.2.2140.tar.zip /var/tmp/OC
    
  2. Change to the directory where the archive is located on your system. For example:

    # cd /var/tmp/OC
    #
    
  3. Use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. The data extracted from the archive consumes about 1 GB of additional space. For example:

    # unzip proxy-controller.Linux.i686.12.1.2.2140.tar.zip
    # tar xf proxy-controller.Linux.i686.12.1.2.2140.tar
    # ls
    xvmoc_full_bundle
    proxy-controller.Linux.i686.12.1.2.2140.tar
    #
    
  4. Change to the xvmoc_full_bundle directory, and run the install script with the -p option. Each installation archive only contains an install script that is appropriate for its intended OS and platform. The -p option causes the install script to only install the Proxy Controller-related components. For example:

    # cd xvmoc_full_bundle
    # ./install -p
    

    The screen clears, then the install script displays a list of installation tasks that automatically updates as the installation proceeds. For example:

    Ops Center Proxy Controller Installer
         (version 12.1.2.2140 on Linux)
     
    1. Check for installation prerequisites.                            [Completed]
    2. Install prerequisite packages.                                   [Completed]
    3. Install Expect.                                              [Not Completed]
    4. Install IPMI tool.                                           [Not Completed]
    5. Install Agent components.                                    [Not Completed]
    6. Install application packages.                                [Not Completed]
    7. Install Core Channel components.                             [Not Completed]
    8. Set Proxy database credentials.                              [Not Completed]
    9. Install Proxy Controller components.                         [Not Completed]
    10. Install UCE Http proxy.                                     [Not Completed]
    11. Install OS provisioning components.                         [Not Completed]
    12. Initialize (but do not start) services.                     [Not Completed]
    
    Executing current step:  Install Expect...
    

    When complete, the install script indicates that all components have been installed, and indicates that the Proxy Controller is ready to be configured.

  5. Use the /opt/sun/xvmoc/bin/proxyadm command to check the status of the Proxy Controller services. If the installation has completed successfully, the services should be online. For example:

    # /opt/sun/xvmoc/bin/proxyadm status
    online
    # 
    

3.4.2 Configuring a Proxy Controller Manually

Once a Proxy Controller has been installed, it must be configured to connect it with the Enterprise Controller. Use this procedure to configure a Proxy Controller with an Enterprise Controller.

Consult with Oracle Support to determine what Oracle Enterprise Manager Ops Center updates are required. Install all required updates before you register the Proxy Controller with the Enterprise Controller.

Note:

If you designated an alternative Administrative User for the Enterprise Controller, use the same user name to register your Proxy Controller with the Enterprise Controller. Otherwise, use the root user to register your Proxy Controller with the Enterprise Controller.

To Register a Proxy Controller With an Enterprise Controller

  1. Create a temporary directory, for example, /var/tmp/OC, to hold the password file that you create in this procedure.

    # mkdir -p /var/tmp/OC
    
  2. Create an empty file named /var/tmp/OC/mypasswd, and set its permission mode to 400.

    # touch /var/tmp/OC/mypasswd
    # chmod 400 /var/tmp/OC/mypasswd
    
  3. Edit the /var/tmp/OC/mypasswd file so that it contains the password of the user that you designated the administrator of your Enterprise Controller. The following echo command appends the password to the /var/tmp/OC/mypasswd file. Replace password with the correct password. For example:

    # echo 'password' > /var/tmp/OC/mypasswd
    
  4. Use the /opt/sun/xvmoc/bin/proxyadm command with the configure subcommand to associate the Proxy Controller with the Enterprise Controller. The example commands below use the following options:

    • -s – Specify the host name or IP address of the Enterprise Controller with which to register the Proxy Controller.

    • -u – Specify the user that you designated the administrator of your Enterprise Controller.

    • -p – Specify the absolute path name of the file that contains the password for the user you specified with the -u option.

    • -a – Specify the IP address that the Proxy Controller should use. This option is required if you want the Proxy Controller to be identified on a specific NIC by the Enterprise Controller. Accept any certificates that are presented. The co-located Proxy Controller configuration does not display certificate information.

    For example:

    # /opt/sun/xvmoc/bin/proxyadm configure -s enterprise-controller.company -u droot -p /var/tmp/OC/mypasswd
    
    Certificate:
    Serial Number: 270256981
    Version: 3
    Issuer: CN=enterprise-controller_ca
    Subject: CN=enterprise-controller_agent
    Not valid before: Wed Jul 02 19:32:56 MDT 1969
    Not valid after: Mon Apr 02 19:32:56 MDT 2029
    
    Certificate:
    Serial Number: 1062961758
    Version: 3
    Issuer: CN=enterprise-controller_ca
    Subject: CN=enterprise-controller_ca
    Not valid before: Wed Jul 02 19:32:54 MDT 1969
    Not valid after: Mon Apr 02 19:32:54 MDT 2029
    
    Accept server's certificate? (y|n)
    y
    Connection registered successfully.
    #
    

    If you are manually configuring the co-located Proxy Controller because your Enterprise Controller has more than one active network interface, use the -a option to identify the particular interface that you want the Proxy Controller to use. Specify the IP address that is assigned to the interface that you want to use. For example:

    # /opt/sun/xvmoc/bin/proxyadm configure -s enterprise-controller.company -u droot -p /var/tmp/OC/mypasswd -a 172.20.25.18
    (output omitted)
    
  5. Use the /opt/sun/xvmoc/bin/proxyadm command with the start subcommand and the -w option to start the Proxy Controller services. For example:

    # /opt/sun/xvmoc/bin/proxyadm start -w
    proxyadm: Starting proxy with SMF...
    proxyadm: Proxy services have started
    #
    
  6. To verify the connection that has been established for this Proxy Controller configuration, run the sc-console list-connections command. For example:

    # sc-console list-connections
    scn-proxy https://enterprise-controller.company:443 urn:scn:clregid:18a0206a-a5c4-4c8c-90f2-d4eb1d2b623b:20090419213707452
    #
    

    The sc-console list-connections command lists the connection that is established with the Enterprise Controller. If you are enabling a co-located Proxy Controller, the command also lists a connection for localhost. For example:

    # sc-console list-connections
    scn-proxy https://enterprise-controller.company:443 urn:scn:clregid:6d0ec2ab-b868-46ab-8475-4a5d726dee69:20090419214450735
    localhost https://localhost:443 urn:scn:clregid:a9f5243e-f46e-4b32-85ca-76e2c12c0707:20090403015601612
    #
    

For more information about the proxyadm command, see the Oracle Enterprise Manager Ops Center Administration Guide.