4 Installing with a Single Enterprise Controller

These procedures describe how to install and configure an Enterprise Controller and one or more Proxy Controllers on Linux systems.

The first step in this process is to install the Enterprise Controller, using either a customer-managed remote database or an embedded database.

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:

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

  • An advanced deployment remotely installs and configures one or more Proxy Controllers on remote systems.

  • Installing Proxy Controllers outside of the configuration wizard lets you install and configure Proxy Controllers remotely or manually after configuring the Enterprise Controller.

  • Manual configuration lets you create a configuration file with the configuration details. You can enable the co-located Proxy Controller using manual configuration, but other Proxy Controllers must be configured separately.

If you decided to install Proxy Controllers outside of the configuration wizard, or if you need to install Proxy Controllers at a later date, use the procedures in the Installing Proxy Controllers chapter.

4.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) 7 Update 71 for the use of the Enterprise Controller and Proxy Controllers. Later versions of JRE are not affected.

Note:

If your environment includes Oracle VM Servers for x86, the Proxy Controllers that manage these systems must be modified to use JRE 6. This procedure is described in the Installing Proxy Controllers chapter.

4.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 correct Oracle Database 11g Enterprise Edition installation bundles for your environment.

  • Oracle Enterprise Manager Ops Center 12.2.0 and 12.2.1 use Oracle Database 11g Enterprise Edition version 11.2.0.3 installation bundles.

  • Oracle Enterprise Manager Ops Center 12.2.2 uses Oracle Database 11g Enterprise Edition version 11.2.0.4 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 the patch number for your version in the field next to Patch Name or Number.

    • For Oracle Database 11g Enterprise Edition version 11.2.0.3, enter 10404530.

    • For Oracle Database 11g Enterprise Edition version 11.2.0.4, enter 13390677.

  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 patch set of the appropriate version 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.2.2.808.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.2.2.808.zip
      # ls
      enterprise-controller.Linux.i686.12.2.2.808.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.2.2.808.tar.zip | tar xf -
      # ls
      enterprise-controller.Linux.i686.12.2.2.808.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.2.2.808 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.2.2.808 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 the Enterprise Controller User Interface section.

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

If you are reinstalling your Enterprise Controller as part of a restore, several steps related to the database have alternate procedures or must be skipped. These steps are indicated in the procedure.

Note:

The installation procedure requires database user name, password, and URL 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.

  2. Create a directory on the database system that can be used as the Oracle Enterprise Manager Ops Center dump directory. This directory must be owned by the Oracle user. If you are using Oracle RAC, this directory must be shared between all Oracle RAC nodes.

    Note:

    If you are using Oracle Real Application Cluster (Oracle RAC) on the database system, the dump directory must be mounted over NFS using the following NFS settings:
    rw,bg,hard,nointr,rsize=131072,wsize=131072,tcp,vers=3, suid
    

    See the Configuring Storage for Grid Infrastructure for a Cluster and Oracle Real Application Clusters (Oracle RAC) chapter of the Oracle® Grid Infrastructure Installation Guide for more information.

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.2.2.808.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.2.2.808.zip
      # ls
      enterprise-controller.Linux.i686.12.2.2.808.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.2.2.808.tar.zip | tar xf -
      # ls
      enterprise-controller.Linux.i686.12.2.2.808.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/Linux_i686/Product/installer/scripts/createOCSchema.sql .
    Password:
    createOCSchema.sql  100% |*********************| 1486     00:00
    

    If you are reinstalling your Enterprise Controller as part of a restore, skip this step.

  5. Create the following tablespaces on the database:

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

    • Report tablespace: This is the tablespace used for report data. Create this tablespace with the name OC_RM_RESOURCE_TS.

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

    If you are reinstalling your Enterprise Controller as part of a restore, skip this step.

  6. As the customer-managed database administrator, run the createOCSchema_remote.sql script. This script creates the Oracle Enterprise Manager Ops Center users, assigns the default and temporary tablespaces, and assigns the dump directory.

    If you are reinstalling your Enterprise Controller as part of a restore, skip this step.

    The script prompts you for the following information:

    • Oracle Enterprise Manager Ops Center user name: This is a database user that is created by the script, which Oracle Enterprise Manager Ops Center uses to access the database.

    • Oracle Enterprise Manager Ops Center password: This is the password for the database user.

    • Oracle Enterprise Manager Ops Center read-only user name: This is a read-only database user, which 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.

    • Report tablespace: This is the tablespace used for report data.

    • 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. If you are using Oracle RAC, this directory must be shared between all Oracle RAC nodes.

    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 report tablespace for Ops Center user: OC_RM_RESOURCE_TS
    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. Within the file, specify the location of the customer-managed database and the same user and read-only user credentials supplied in the schema creation script. The following properties must be specified:

    • mgmtdb.appuser=<user name>: This is a database user that Oracle Enterprise Manager Ops Center uses to access the database.

    • mgmtdb.password=<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.

    • mgmtdb.roappuser=<read-only user name>: This is a read-only database user that Oracle Enterprise Manager Ops Center uses to view the database.

    • mgmtdb.ropassword=<read-only password>: This is the password for the read-only database user.

    • mgmtdb.dburl=jdbc:oracle:thin:@<database access data>: This is the URL, port, and service name for the database. You can use any of these formats for this information:

      mgmtdb.dburl=jdbc:oracle:thin:@<database host name>:<port>/<database service name>
      mgmtdb.dburl=jdbc:oracle:thin:@<database host name>:<port>:<SID>
      mgmtdb.dburl=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=<host>)(PORT=<port>))(CONNECT_DATA=(SERVICE_NAME=<service>)))
      

    For example:

    # vi /var/tmp/RemoteDBProps.txt
    mgmtdb.appuser=user
    mgmtdb.password=userpass
    mgmtdb.roappuser=user
    mgmtdb.ropassword=userpass
    mgmtdb.dburl=jdbc:oracle:thin:@hostname:1521/OCDB
    
  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
    

    If you are reinstalling your Enterprise Controller as part of a restore, use the --preserveDB option to preserve the existing Oracle Enterprise Manager Ops Center database application schema.

    For example:

    # cd xvmoc_full_bundle
    # ./install --preserveDB --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.2.2.808 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.2.2.808 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. 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
    # 
    
  13. 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 the Enterprise Controller User Interface section.

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

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

  • Configuring an Enterprise Controller manually: This deployment configures the Enterprise Controller according to a configuration profile that you create. You can enable the co-located Proxy Controller using manual configuration, but other Proxy Controllers must be configured separately.

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.

Note:

Oracle Enterprise Manager Ops Center has self-signed certificates that it uses for authentication between its components. If you prefer to use certificates authenticated by a Certificate Authority, see the Oracle Enterprise Manager Ops Center Security Guide and perform the Substitute Certificates procedure before you install any Proxy Controllers.

4.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 a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well. See the Using Disconnected Mode guide or the Oracle Enterprise Manager Ops Center Administration Guide for more information.

    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.

      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 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 Auto Service Request (ASR).

    • 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 Auto Service Request (ASR), the Auto 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 for OS Provisioning 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.

4.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 a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well. See the Using Disconnected Mode guide or the Oracle Enterprise Manager Ops Center Administration Guide for more information.

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

  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 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 Auto Service Request (ASR).

    • 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 Auto Service Request (ASR), the Auto Service Request Contact page is displayed. Enter the default contact information for ASR:

    • 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 for OS Provisioning 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.

4.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 a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well. See the Using Disconnected Mode guide or the Oracle Enterprise Manager Ops Center Administration Guide for more information.

    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 Auto Service Request (ASR).

    • 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 Auto Service Request (ASR), the Auto Service Request Contact page is displayed. Enter the default contact information for ASR:

    • 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 for OS Provisioning 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.

4.2.4 Configuring an Enterprise Controller Manually

This procedure configures the Enterprise Controller using a configuration file. You specify the configuration parameters, including MOS credentials, ASR status, co-located Proxy Controller activation, and HTTP proxy settings.

Note:

The manual configuration process does not configure libraries. If you configure your Enterprise Controller manually, you must configure libraries through the UI. See the Libraries chapter of the Oracle Enterprise Manager Ops Center Feature Reference Guide for more information.

Before You Begin

  • If you intend to operate in Disconnected Mode, acquire a Knowledge Base (KB) bundle. The example below downloads the KB bundle. The KB bundle is the only required component, but you can download OS content such as patches and baselines as well. See the Using Disconnected Mode guide or the Oracle Enterprise Manager Ops Center Administration Guide for more information.

    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 Manually

  1. As root, log on to the Enterprise Controller system.

  2. Change to the directory used for the installation and create a configuration file. For example:

    # cd /var/tmp/OC
    # touch EC-config
    
  3. Edit the configuration file to contain the parameters of your environment. The allowed parameters are:

    • username=<user name>: This user is configured as the Oracle Enterprise Manager Ops Center administrative user. The user must be present on the local file system.

    • update.username=<MOS user name>: This MOS user name is used to download update content in connected mode.

    • update.password=<password>: The password for the update MOS user. This parameter is required if the update.username parameter is set.

    • register.username=<MOS user name>: This MOS user name is used to register the Enterprise Controller with Oracle.

    • register.password=<password>: The password for the registration MOS user. This parameter is required if the register.username parameter is set.

    • mos.username=<MOS user name>: This MOS user name is used to connect to Oracle, download product updates and other content, and enable service request creation.

    • mos.password=<password>: The password for the primary MOS user. This parameter is required if the mos.username parameter is set.

    • asr.mode=<enabled | disabled>: Specifies whether Auto Service Request (ASR) should be enabled or disabled. ASR is disabled by default.

    • httpproxy.hostname=<host name>: If your environment requires an HTTP proxy to reach the internet, enter the HTTP proxy host name.

    • httpproxy.port=<port>: If your environment requires an HTTP proxy to reach the internet, enter the HTTP proxy port number.

    • httpproxy.username=<user name>: If your environment requires an HTTP proxy to reach the internet, and the HTTP proxy requires authentication, enter a user name for the HTTP proxy.

    • httpproxy.password=<password>: The password for the HTTP proxy user. This parameter is required if the httpproxy.username parameter is set.

    • local.controlproxy=<enabled | disabled>: This setting enables or disables the co-located Proxy Controller on the Enterprise Controller system.

    • local.controlproxy.ip=<IP>: This IP address is used by the co-located Proxy Controller if it is enabled. This parameter is required if the local.controlproxy parameter is set to enabled.

    • local.controlproxy.wait=<true | false>: This variable specifies whether the configuration process should wait until the co-located Proxy Controller is enabled before completing.

    Here is an example configuration file:

    # Configuration file
    username=root
    update.username=user@company.com
    update.password=companypass
    register.username=user@company.com
    register.password=companypass
    mos.username=user@company.com
    mos.password=companypass
    asr.mode=enabled
    httpproxy.hostname=http.proxy.company.com
    httpproxy.port=80
    local.controlproxy=enabled
    local.controlproxy.ip=10.10.24.28
    local.controlproxy.wait=true
    
  4. Run the /opt/sun/xvmoc/bin/ecadm command with the configure subcommand and the --config <configuration file> option. For example:

    ./ecadm configure --config /var/tmp/EC-config
    ecadm:    --- Enterprise Controller registered
    # 
    

    The Enterprise Controller is configured. If you plan to use remote Proxy Controllers, you can install and configure them manually or through the UI.

  5. Delete the configuration file. For example:

    # cd /var/tmp/OC
    # rm EC-config
    

4.3 Related Resources

For more information about Enterprise Controller Administration or Agent Controller installation, go to one of the following resources.