1. Cloud Control Advanced Installation and Configuration Guide
  2. Installing Enterprise Manager System - Advanced Installation Modes
  3. Installing Enterprise Manager in Silent Mode

3 Installing Enterprise Manager in Silent Mode

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

Note:

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

WARNING:

Do not install Enterprise Manager Cloud Control 13c on servers of SPARC series: T1000, T2000, T5xx0, and T3-*. For more information, see My Oracle Support note 1590556.1.

Introduction to Installing Enterprise Manager in Silent Mode

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

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

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

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

Before You Begin Installing Enterprise Manager in Silent Mode

Before you begin installing an Enterprise Manager system in silent mode, familiarize yourself with the key aspects of installation described in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

Prerequisites for Installing Enterprise Manager in Silent Mode

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

Installing Enterprise Manager in Silent Mode

This section covers the following:

Installing Enterprise Manager in Silent Mode

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

Note:

Oracle recommends you to run the EM Prerequisite Kit before invoking the installer to ensure that you meet all the repository requirements beforehand. Even if you do not run it manually, the installer anyway runs it in the background while installing the product. However, running it manually beforehand sets up your Management Repository even before you can start the installation or upgrade process. For information on the kit, to understand how to run it, and to know about the prerequisite checks it runs, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.

However, if you plan to use a database instance that was created with a preconfigured Management Repository using the database templates offered by Oracle, then make sure you pass the following parameter while invoking the EM Prerequisite Kit.

-componentVariables repository:EXECUTE_CHECKS_NOSEED_DB_FOUND:false

  1. Invoke the installer and generate the response file you need to use for performing a silent installation.

    ./em13500_<platform>.bin -getResponseFileTemplates -outputLoc <absolute_path_to_a_directory_to_store_the_generated_response_file>

    Note:

    The command generates multiple response files. You must use only the new_install.rsp file for this silent installation.

  2. Edit the new_install.rsp file and enter appropriate values for the parameters described in Table 3-2.
  3. Invoke the installer in silent mode and pass the updated response file.

    (On Unix, make sure you invoke the installer as a user who belongs to the oinstall group you created. For information about creating operating system groups and users, see the Oracle Enterprise Manager Cloud Control Basic Installation Guide.)

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

      ./em13500_<platform>.bin -silent -responseFile <absolute_path_to_the_directory_where_the_generated_and_updated_response_file_is_stored>/new_install.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]

    • Otherwise, run the following command:

      ./em13500_<platform>.bin -silent -responseFile <absolute_path_to_the_directory_where_the_generated_and_updated_response_file_is_stored>/new_install.rsp

    Note:

    • To invoke the installation wizard on UNIX platforms, run em13500_<platform>.bin. To invoke on Microsoft Windows platforms, run setup_em13500_win64.exe.

    • The installer requires about 14 GB of hard disk space in the temporary directory. If your temporary directory does not have this space, then pass the -J-Djava.io.tmpdir parameter and provide an alternative directory where there is 14 GB of space.

      The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

      For example,

      ./em13500_linux64.bin -J-Djava.io.tmpdir=/u01/software/em13c/stage/

    • Ensure that there are no white spaces in the name of the directory where you download and run the Enterprise Manager Cloud Control software from. For example, do not download and run the software from a directory titled EM Software because there is a white space between the two words of the directory name.

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

    • For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options Supported for Installing an Enterprise Manager System in Silent Mode.

    Note:

    If a Server Load Balancer (SLB) is configured in your environment, and the upload port is locked, then configure the SLB for JVMD Engines, and then secure the OMS.

    If an SLB is configured in your environment, but the upload port is unlocked, then decide whether you want to route the JVMD traffic through the SLB. If you do, then configure the SLB for JVMD Engines, and then secure the OMS.

    To secure the OMS, run the following command from the Oracle home of the OMS host:

    <ORACLE_HOME>/bin/emctl secure oms -host <SLB host>-slb_jvmd_http_port <JVMD_SLB_HTTP_Port> -slb_jvmd_https_port <JVMD_SLB_HTTPS_Port> -sysman_pwd <system_password> -reg_pwd <agent_registration_password>

Advanced Installer Options Supported for Installing an Enterprise Manager System in Silent Mode

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

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

    If you want to override this location with a custom location, then invoke the installer with the -J-Djava.io.tmpdir option, and enter a unique custom location.

    For example,

    ./em13500_linux64.bin -J-Djava.io.tmpdir=/u00/install/em/STAGE/ -silent -responseFile /u01/software/em/response/new_install.rsp

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

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

    ./em13500_<platform>.bin START_OMS=true START_AGENT=false -silent -responseFile <absolute_path>/new_install.rsp

    To understand the limitations involved with this advanced option, see Limitations with the Advanced Options Supported for Installing an Enterprise Manager System in Silent Mode.

Limitations with the Advanced Options Supported for Installing an Enterprise Manager System in Silent Mode

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

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

Table 3-1 Advanced Options and Workarounds

Advanced Option Workaround

START_OMS=false

START_AGENT=false

  1. Start the OMS:

    $<ORACLE_HOME>/bin/emctl start oms

  2. Secure the Management Agent:

    $<AGENT_HOME>/bin/emctl secure agent

  3. Start the Management Agent:

    $<AGENT_HOME>/bin/emctl start agent

  4. Add the targets:

    $<AGENT_HOME>/bin/emctl config agent addinternaltargets

  5. Upload the targets:

    $<AGENT_HOME>/bin/emctl upload agent

START_OMS=true

START_AGENT=false

Start the Management Agent:

$<AGENT_HOME>/bin/emctl start agent

START_OMS=false

START_AGENT=true

  1. Start the OMS:

    $<ORACLE_HOME>/bin/emctl start oms

  2. Secure the Management Agent:

    $<AGENT_HOME>/bin/emctl secure agent

  3. Add the targets:

    $<AGENT_HOME>/bin/emctl config agent addinternaltargets

  4. Upload the targets:

    $<AGENT_HOME>/bin/emctl upload agent

Editing the new_install.rsp Response File for Installing an Enterprise Manager in Silent Mode

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

Table 3-2 Editing the new_install.rsp Response File for Installing Enterprise Manager System in Silent Mode

Parameter Data Type Double Quotes Required for Value? Description

UNIX_GROUP_NAME

String

Yes

(Required only when central inventory does not exist) Enter the name of the UNIX group you belong to.

For example, "dba"

Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

INVENTORY_LOCATION

String

Yes

(Required only when central inventory does not exist) Enter the absolute path to the Central Inventory. Ensure that you have read, write, and execute permissions on the default inventory directory.

For example, "/scratch/oracle/oraInventory".

Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.

INSTALL_UPDATES_SELECTION

String

Yes

By default, this variable is set to skip indicating that the software updates will not be installed during installation.

Enter skip if you want to skip the software updates.

Enter staged if you have already downloaded the software updates and you want to install the software updates from a staged location.

STAGE_LOCATION

String

Yes

(Required only if INSTALL_UPDATES_SELECTION=staged)

Enter the absolute path of the stage location where the software updates are available.

MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES

String

Yes

Enter the username of the My Oracle Support account to download the updates during the installation.

If you want to download the updates during the installation, make sure you provide MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES and MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES, and set INSTALL_UPDATES_SELECTION="download".

MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES

String

Yes

Enter the password of the My Oracle Support account to download the updates during the installation.

If you want to download the updates during the installation, make sure you provide MYORACLESUPPORT_USERNAME_FOR_SOFTWAREUPDATES and MYORACLESUPPORT_PASSWORD_FOR_SOFTWAREUPDATES, and set INSTALL_UPDATES_SELECTION="download".

PROXY_USER

String

Yes

Enter the user name that can be used to access the proxy server.

Note: Applies only if you have set the INSTALL_UPDATES_SELECTION variable to "download", and only if your connection to the Internet requires you to connect through a proxy.

PROXY_PWD

String

Yes

Enter the password that can be used to access the proxy server.

Note: Applies only if you have set the INSTALL_UPDATES_SELECTION parameter to "download", and only if your connection to the Internet requires you to connect through a proxy.

PROXY_HOST

String

Yes

Enter the name of the proxy host.

Note: Applies only if you have set the INSTALL_UPDATES_SELECTION parameter to "download", and only if your connection to the Internet requires you to connect through a proxy.

PROXY_PORT

String

Yes

Enter the port used by the proxy server.

Note: Applies only if you have set the INSTALL_UPDATES_SELECTION parameter to "download", and only if your connection to the Internet requires you to connect through a proxy.

ORACLE_MIDDLEWARE_HOME_LOCATION

String

Yes

Enter the location where you want the installer to install Oracle WebLogic Server 12c Release 2 (12.2.1.4.0) and Java Development Kit (JDK) 1.8.0_261. Ensure that the middleware location has write permission. Note that the middleware location is essentially the one and only Oracle home in 13c release.

For example, "/u01/software/em13c/oraclehome"

Note: Ensure that the number of characters in the middleware home path does not exceed 70 characters for Unix platforms and 25 characters for Microsoft Windows platforms.

For example, the middleware home path C:\sw\em13c\oraclehome containing only 22 characters is acceptable. However, C:\OracleSoftware\OracleMiddleware\OracleEnterpriseManager\OMS\newrelease\oms containing more than 25 characters is not acceptable for Microsoft Windows platforms.

ORACLE_HOSTNAME

String

Yes

Enter a fully qualified domain name that is registered in the DNS and is accessible from other network hosts, or enter an alias host name that is defined in the /etc/hosts file on all the OMS instances at this site.

The host name must resolve to the local host because the host name is used for the local Oracle WebLogic Server as well as the Oracle Management Service. Do not provide a remote host or a load balancer virtual host in this field. Do not enter an IP address. Do not use underscores in the name. Short names are allowed, but you will see a warning, so Oracle recommends that you enter a fully qualified domain name instead.

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

AGENT_BASE_DIR

String

Yes

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

For example, "/u01/software/em13c/agentbasedir".

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

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

WLS_ADMIN_SERVER_USERNAME

String

Yes

By default, weblogic is the name assigned to the default user account that is created for the Oracle WebLogic Domain. If you want to accept the default name, then skip this variable. However, if you want to have a custom name, then enter the name of your choice.

WLS_ADMIN_SERVER_PASSWORD

String

Yes

Enter a password for the WebLogic user account.

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

WLS_ADMIN_SERVER_CONFIRM_PASSWORD

String

Yes

Confirm the password for the WebLogic user account.

NODE_MANAGER_PASSWORD

String

Yes

By default, nodemanager is the name assigned to the default user account that is created for the node manager. Enter a password for this node manager user account.

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

NODE_MANAGER_CONFIRM_PASSWORD

String

Yes

Confirm the password for the node manager user account.

ORACLE_INSTANCE_HOME_LOCATION

String

Yes

By default, gc_inst is considered as the OMS Instance Base directory for storing all OMS-related configuration files. Enter the absolute path to a location outside the middleware home leading up to the directory name.

For more information about this location, see What Is an Oracle Management Service Instance Base Location?.

Note: If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. For instructions, refer to Performing Postinstallation Tasks After Installing an Enterprise Manager System in Silent Mode.

CONFIGURE_ORACLE_SOFTWARE_LIBRARY

Boolean

 No

If you want to configure the Software Library at the time of installation, set this parameter to TRUE. Otherwise, set it to FALSE.

Even if you do not configure it at the time of installation, your installation will succeed, and you can always configure it later from the Enterprise Manager Cloud Control Console.

Oracle recommends toconfigure it at the time of installation therefore it's automatically configured by the installer which saves time and effort.

For example, CONFIGURE_ORACLE_SOFTWARE_LIBRARY=true

SOFTWARE_LIBRARY_LOCATION

String

 Yes

Required if you set CONFIGURE_ORACLE_SOFTWARE_LIBRARY=true

If you have set CONFIGURE_ORACLE_SOFTWARE_LIBRARY to TRUE, then enter the absolute path leading up to a unique directory name on the OMS host where the Software Library can be configured.

Ensure that the location you enter is a shared location on the OMS host. This helps when you install additional OMS instances that can use the same shared Software Library location.

DATABASE_HOSTNAME

String

Yes

Enter the fully qualified name of the host where the existing database resides. Ensure that the host name does not have underscores.

For example, "example.com".

If you have already created a database instance with a preconfigured Management Repository using the database templates offered by Oracle, then provide details about that database instance.

If you are connecting to an Oracle RAC Database, and if the nodes have virtual host names, then enter the virtual host name of one of its nodes.

The connection to the database is established with a connect string that is formed using only this virtual host name, and the installation ends successfully.

However, if you want to update the connect string with other nodes of the cluster, then after the installation, run the following command:

$<ORACLE_HOME>/bin/emctl config oms -store_repos_details -repos_conndesc "(DESCRIPTION= (ADDRESS_LIST=(FAILOVER=ON) (ADDRESS=(PROTOCOL=TCP)(HOST=node1-vip.example.com)(PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=node2-vip.example.com)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=EMREP)))" -repos_user sysman

If your Oracle RAC database is configured with Single Client Access Name (SCAN) listener, then you can enter a connection string using the SCAN listener.

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

LISTENER_PORT

String

Yes

Enter the listener port to connect to the existing database.

For example, "1521".

SERVICENAME_OR_SID

String

Yes

Enter the service name or the system ID (SID) of the existing database.

For example, "orcl".

If you are providing the details of a pluggable database (PDB), then use the full service name instead of the alias. For example, pdb.example.com. If you are providing the details of a lone-pluggable database (Lone-PDB), then use the full service name. For example, pdb.example.com. If you are providing the details of a non-container database (Non-CDB), then use the SID.

SYS_PASSWORD

String

Yes

Enter the SYS user account's password.

SYSMAN_PASSWORD

String

Yes

Enter a password for creating a SYSMAN user account. This password is used to create the SYSMAN user, which is the primary owner of the Management Repository schema.

The SYSMAN account password must begin with a letter, and can only contain uppercase or lowercase letters, numbers and the following characters: $, # , _

Examples of invalid passwords: Welcome!, 123oracle, #Oracle

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

SYSMAN_CONFIRM_PASSWORD

String

Yes

Confirm the SYSMAN user account's password.

DEPLOYMENT_SIZE

String

Yes

Set one of the following values to indicate the number of targets you plan to monitor, the number of Management Agents you plan to have, and the number of concurrent user sessions you plan to have.

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

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

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

For example, "MEDIUM".

The prerequisite checks are run regardless of the selection you make, but the values to be set for the various parameters checked depend on the selection you make.

You can also modify the deployment size after the installation. For more information on deployment sizes, the prerequisite checks that are run, the database parameters that are set, and how you can modify the deployment size after installation, refer to What is a Deployment Size for Enterprise Manager Cloud Control in an Advanced Configuration?.

Note:

If the database you are connecting to is a database instance created with a preconfigured Management Repository using the database templates offered by Oracle, then make sure the deployment size you set here matches with the deployment size you selected on the Database Templates screen of Oracle Database Configuration Assistant (DBCA) while creating the database instance.

If you want to select a deployment size different from the deployment size you had selected while creating the database instance using DBCA, then do one of the following:
KEYSTORE_LOCATION

String

Yes

Enter the location of the keystore (location where the SSL key will get stored).
KEYSTORE_PASSWORD

String

Yes

Enter the password of the keystore.

MANAGEMENT_TABLESPACE_LOCATION

String

Yes

Enter the absolute path to the location where the data file (mgmt.dbf) for management tablespace can be stored. Ensure that the specified path leads up to the file name.

For example:

  • If the database is on a file system, then the path must look like "/u01/oracle/prod/oradata/mgmt.dbf".

  • If the database is on Automatic Storage Management (ASM), then the path must look like "+DATA/oemrsp01d/datafile/mgmt.dbf", where disk_group1 is a diskgroup created on ASM and prod is the Service ID (SID).

  • If the database is on a raw device, then the path must look like "</dev/raw1>/prod/oradata/mgmt.dbf", where /dev/raw1 is the raw device and prod is the SID.

Enterprise Manager Cloud Control requires this data file to store information about the monitored targets, their metrics, and so on. Essentially, everything else other than configuration data, software library data, and audit data.

CONFIGURATION_DATA_TABLESPACE_LOCATION

String

Yes

Enter the absolute path to the location where the data file (mgmt_ecm_depot1.dbf) for configuration data tablespace can be stored. Ensure that the specified path leads up to the file name.

For example, "/home/john/oradata/mgmt_ecm_depot1.dbf".

Enterprise Manager Cloud Control requires this data file to store configuration information collected from the monitored targets.

JVM_DIAGNOSTICS_TABLESPACE_LOCATION

String

Yes

Enter the absolute path to a location where the data file (mgmt_deepdive.dbf) for JVM Diagnostics data tablespace can be stored. Ensure that the specified path leads up to the file name.

For example, "/home/john/oradata/mgmt_deepdive.dbf".

Enterprise Manager Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).

EMPREREQ_AUTO_CORRECTION=false

Boolean

No

It specifies whether prereqs can be auto corrected.

AGENT_REGISTRATION_PASSWORD

String

Yes

Enter a password to secure the communication between the OMS and the Management Agents. Note that you have to provide the same registration password for securing your Management Agents.

AGENT_REGISTRATION_CONFIRM_PASSWORD

String

Yes

Confirm the agent registration password.

STATIC_PORTS_FILE

String

Yes

By default, ports described in What Ports Are Used for Installation? are honored. If you want to accept the default ports, then leave this field blank.

If you want to use custom ports, then enter the absolute path to the staticports.ini file that lists the custom ports to be used for the installation.

PLUGIN_SELECTION

String List

Yes

(A comma-separated list of plug-in names, where the plug-in names must be in double quotes)

By default, mandatory plug-ins such as Oracle Database Plug-in, Oracle Fusion Middleware Plug-in, and Oracle Exadata Plug-in, Oracle Cloud Framework Plug-in, and Oracle System Infrastructure Plug-in are automatically installed with the Enterprise Manager system.

In addition to the default ones, if you want to deploy any addition plug-in, then list those plug-in names in a comma-separated list. Ensure that the plug-in names are in double quotes.

If you want to deploy a deprecated plug-in that is supported only in the current release, but not in any of the future releases, then evaluate your selection and decide whether or not you want to proceed with the deployment of such plug-ins.

For example,

PLUGIN_SELECTION={"oracle.sysman.empa","oracle.sysman.vt"}

If you want to install some plug-ins that are not in the software kit (DVD, downloaded software), then do the following:

  1. Manually download the required plug-ins from Plug-in Update.

    Plug-ins produced by partners and customers are available for download from the Entreprise Manager Extensibility Exchange.

  2. Invoke the installer with the following option and pass the location where the additional plug-ins have been downloaded:

    ./em13500_<platform>.bin PLUGIN_LOCATION=<absolute_path_to_plugin_software_location>

b_upgrade

Boolean

No

For this case, set it to b_upgrade=false

EM_INSTALL_TYPE

String

No

For this case, set it to EM_INSTALL_TYPE=NOSEED

CONFIGURATION_TYPE

String

No

For this case, set it to ADVANCED

CONFIGURATION_TYPE=ADVANCED

Performing Postinstallation Tasks After Installing an Enterprise Manager System in Silent Mode

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