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:
Introduction to Installing Enterprise Manager in Silent Mode
Before You Begin Installing Enterprise Manager in Silent Mode
Prerequisites for Installing Enterprise Manager in Silent Mode
Performing Postinstallation Tasks After Installing an Enterprise Manager System in Silent Mode
Note:
All general purpose file systems, including OCFS2 and ACFS, are acceptable for storing Enterprise Manager Cloud Control 12c software binaries and OMS instance home files (configuration files ingc_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 12c on servers of SPARC series: T1000, T2000, T5xx0, and T3-*. For more information, see My Oracle Support note 1590556.1.
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, keep these points in mind:
You must ensure that you have the latest Enterprise Manager Cloud Control software.
To download the latest software, access the following URL:
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
For information about downloading the latest software, refer to Section 1.2.2.
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.
You can install Enterprise Manager Cloud Control only on a single host—locally on the server where you invoke the installation wizard with a response file. You cannot install on remote hosts.
To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.
Oracle Management Service 12c can communicate only with the following versions of Oracle Management Agent 12c:
Table 3-1 Compatibility Between OMS and Management Agents Across 12c Releases
|
Oracle Management Agent 12c Release 1 (12.1.0.1) + Bundle Patch 1 (Refers to agents and their plug-ins patched or upgraded to, or installed with Bundle Patch 1) |
Oracle Management Agent 12c Release 2 (12.1.0.2) |
Oracle Management Agent 12c Release 3 (12.1.0.3) |
Oracle Management Agent 12c Release 4 (12.1.0.4) |
Oracle Management Agent 12c Release 5 (12.1.0.5) |
|
|
Oracle Management Service 12c Release 1 (12.1.0.1) + Bundle Patch 1 |
Yes (includes Management Agents with and without Bundle Patch 1) |
No |
No |
No |
No |
|
Oracle Management Service 12c Release 2 (12.1.0.2) |
Yes (includes Management Agents with and without Bundle Patch 1) |
Yes |
No |
No |
No |
|
Oracle Management Service 12c Release 3 (12.1.0.3) |
Yes (Only Management Agents released in January 2012 [with Bundle Patch 1]) |
Yes |
Yes |
No |
No |
|
Oracle Management Service 12c Release 4 (12.1.0.4) |
No |
Yes |
Yes |
Yes |
No |
|
Oracle Management Service 12c Release 5 (12.1.0.5) |
No |
Yes |
Yes |
Yes |
Yes |
You must not set the ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the Oracle directories do NOT appear in the PATH.
The Enterprise Manager Cloud Control Installation Wizard installs Java Development Kit (JDK) 1.6.0.43.0 and Oracle WebLogic Server 11g Release 1 (10.3.6), but only if you do not specify the use of existing installations. Oracle strongly recommends using the 12c installation process to install the JDK and Oracle WebLogic Server for use with Enterprise Manager 12c.
If Oracle WebLogic Server 11g Release 1 (10.3.6) does not exist and if you choose to manually install it, then ensure that you install it using JDK 1.6.0.43.0 (64-bit version for 64-bit platforms and 32-bit version for 32-bit platforms).
Download JDK 1.6.0.43.0 for your platform from the platform vendor's Web site.
For example, download SUN JDK 1.6.0.43.0 for Linux platforms from the following Oracle Web site URL:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
If you already have JDK, then verify its version by navigating to the <JDK_Location>/bin directory and running the following command:
"./java -fullversion"
To verify whether it is a 32-bit or a 64-bit JDK, run the following command:
"file *"
If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.6) on Linux 64-bit platforms, first install the 64-bit JDK for your platform, and then download and use the wls1036_generic.jar file to install Oracle WebLogic Server.
For example,
<JDK home>/bin/java -d64 -jar <absolute_path _to_wls1036_generic.jar>
If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.6) on Linux 32-bit platforms, then download and use either the wls1036_linux32.bin file or the wls1036_generic.jar file.
For example,
<JDK home>/bin/java -jar <absolute_path _to_wls1036_generic.jar>
You must follow the instructions outlined in the Oracle® Fusion Middleware Installation Guide for Oracle WebLogic Server to install Oracle WebLogic Server. The guide is available in the Fusion Middleware documentation library available at:
http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html
You must ensure that the Oracle WebLogic Server installation is a typical installation, and even if you choose to perform a custom installation, ensure that components chosen for custom installation are the same as the ones associated with a typical installation.
You must ensure that the user installing the WebLogic Server is the same as the one installing Enterprise Manager Cloud Control.
After installing Oracle WebLogic Server, make sure you apply the patches 14482558, 13349651, 16080294, and 16888501 on it. Without these patches, the additional OMS installation will fail.
For instructions to apply these patches, see the following URL:
http://docs.oracle.com/cd/E14759_01/doc.32/e14143/intro.htm#CHDCAJFC
You must ensure that the Oracle WebLogic Server 11g Release 1 (10.3.6) installed by the Enterprise Manager Cloud Control Installation Wizard or by you is dedicated for Enterprise Manager Cloud Control. You must not have any other Oracle Fusion Middleware product installed in that Middleware home.
Enterprise Manager Cloud Control cannot coexist with any Oracle Fusion Middleware product in the same Middleware home because the ORACLE_COMMON property is used by both the products.
Do not install on a symlink. Installing in such a location may impact life cycle operations such as patching and scaling out.
You can optionally use the database templates offered by Oracle to create a database instance with a preconfigured Management Repository. To do so, refer to Oracle Enterprise Manager Cloud Control Basic Installation Guide. You can use such a database instance for simple as well as advanced installation.
However, note that the database templates are essentially designed for simple installation, although they can be used for advanced installation. Therefore, while performing an advanced installation (possibly with small, medium, or large deployment size selection), when you provide the details of such a database, you will be prompted that the database parameters need to be modified to suit the deployment size you selected. You can confirm the message to proceed further. The installation wizard will automatically set the database parameters to the required values.
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. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Section 3.5.
Enterprise Manager is not affected when you enable or disable features such as XML DB on the Oracle Database in which you plan to configure the Management Repository. Therefore, you can enable or disable any feature in the database because Enterprise Manager does not rely on them
If you want to optionally follow the configuration guidelines for deploying the Management Repository so that your management data is secure, reliable, and always available, refer to the Oracle Enterprise Manager Cloud Control Administrator's Guide.
By default, the software updates cannot be applied during installation because the INSTALL_UPDATES_SELECTION variable in the response file is set to "skip". However, if you want to apply them during installation, then you can modify this variable as described in Table 3-3.
Oracle offers bug fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for bug fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:
http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf
When determining supportability and certification combinations for an Enterprise Manager Cloud Control installation, you must consider Enterprise Manager Cloud Control's framework components as well as the targets monitored by Enterprise Manager Cloud Control. Oracle recommends keeping your Cloud Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license.
You can find the OMS and Management Agent entries in the /etc/oragchomelist file for all UNIX platforms except HPUNIX, HPia64, Solaris Sparc.
On HPUNIX, HPia64, Solaris Sparc platforms, the entries are present in /var/opt/oracle/oragchomelist.
As a prerequisite, you must have an existing Oracle Database to configure the Management Repository. This database can also have the Automatic Memory Management (AMM) feature enabled.
If you are installing in, or will be converting in the future to, a high-availability or a disaster-recovery configuration, then review and become familiar with the contents in Chapter 16, Chapter 17, Chapter 18 before continuing with this installation.
Once you have reviewed the information in the aforementioned chapters, follow the best practices referenced in Chapter 17, specifically the information in Section 17.3.1 in order to best prepare your installation for high availability or disaster recovery.
The locale-specific data is stored in the <OMS_Oracle_Home>/nls/data directory. Oracle strongly recommends that you either set the environment variable ORA_NLS10 to <OMS_Oracle_Home>/nls/data or do not set at all.
If you install the OMS and the Oracle Database, which houses the Management Repository, on the same host, then when you reboot the host, the OMS and the Management Agent installed with it will not automatically start up. You will have to manually start them.
Enforcing option is supported for Security-Enhanced Linux (SELinux).
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.
This section covers the following:
Advanced Installer Options Supported for Installing an Enterprise Manager System in Silent Mode
Editing the new_install.rsp Response File for Installing an 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
Copy the following response file to an accessible location on your local host:
<Software_Location>/response/new_install.rsp
In this command, <Software_Location> is either the DVD location or the location where you have downloaded the software kit.
Edit the response file and enter appropriate values for the variables described in Table 3-3.
Invoke the installer. (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:
./runInstaller -silent -responseFile <absolute_path>/new_install.rsp [-invPtrLoc <absolute_path_to_oraInst.loc>]
Otherwise, run the following command:
./runInstaller -silent -responseFile <absolute_path>/new_install.rsp
Note:
To invoke the installation wizard on UNIX platforms, run runInstaller. To invoke on Microsoft Windows platforms, run setup.exe.
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.
When you invoke runInstaller or setup.exe, if the Enterprise Manager Cloud Control Installation Wizard does not appear, then it is possible that you do not have read and write access to /stage, which a subdirectory in the Disk1 directory of the Enterprise Manager software.
There is a classpath variable that the installation wizard computes for OPatch as ../stage/Components/, and when the TEMP variable is set to /tmp, the installation wizard tries to look for the opatch JAR file in the /tmp/../stage directory, which is equivalent to /stage. However, if you do not have read and write permission on /stage, then the installation wizard can hang. Under such circumstances, verify if you have read and write access to the /stage directory. If you do not have, then set the TEMP variable to a location where the install user has access to, and then relaunch the installation wizard.
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 Section 3.4.2.
Note:
If a prerequisite check fails reporting a missing package, then make sure you install the required package, and retry the installation. The installer validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide. To understand the logic the installer uses to verify these packages, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.
If any repository-related prerequisite check fails, then run the check manually. For instructions, see the appendix on EM Prerequisite Kit in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.
If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Resolve the issue and retry the configuration assistant. For more information, see Appendix J.
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 EM_STAGE_DIR option, and enter a unique custom location.
For example,
./runInstaller EM_STAGE_DIR=/home/john/software/oracle/pafdir -silent -responseFile <absolute_path>/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 b_startAgent 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:
./runInstaller START_OMS=true b_startAgent=false -silent -responseFile <absolute_path>/new_install.rsp
To understand the limitations involved with this advanced option, see Section 3.4.3.
When you use START_OMS and b_startAgent 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-2 lists the different combinations of these advanced options, and describes the workaround to be followed for each combination:
Table 3-2 Advanced Options and Workarounds
| Advanced Option | Workaround |
|---|---|
|
|
|
|
|
Start the Management Agent:
|
|
|
|
Table 3-3 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-3 Editing Response File for Installing Enterprise Manager System
| 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, 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, Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms. |
|
SECURITY_UPDATES_VIA_MYORACLESUPPORT |
Boolean |
No |
|
|
DECLINE_SECURITY_UPDATES |
Boolean |
No |
|
|
INSTALL_UPDATES_SELECTION |
String |
Yes |
By default, this variable is set to
|
|
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 |
|
PROXY_PWD |
String |
Yes |
Enter the password that can be used to access the proxy server. Note: Applies only if you have set the |
|
PROXY_HOST |
String |
Yes |
Enter the name of the proxy host. Note: Applies only if you have set the |
|
PROXY_PORT |
String |
Yes |
Enter the port used by the proxy server. Note: Applies only if you have set the |
|
ORACLE_MIDDLEWARE_HOME_LOCATION |
String |
Yes |
Enter the location where you want the installer to install Oracle WebLogic Server 11g Release 1 (10.3.6) and Java Development Kit 1.6.0.43.0. For example, Ensure that the middleware location has write permission. If you have already installed them manually, then enter the location where you have installed them. Also, make sure you have applied the patches 14482558, 13349651, 16080294, and 16888501 on the Oracle WebLogic Server. Without these patches, the additional OMS installation will fail. For instruction to apply these patches, see the following URL:
For more information about Oracle Middleware home, see Section 2.3.2. 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 |
|
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 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, 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 |
|
WLS_ADMIN_SERVER_USERNAME |
String |
Yes |
By default, |
|
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, 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, For more information about this location, see Section 2.3.3. 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 Section 3.5. |
|
CONFIGURE_ORACLE_SOFTWARE_LIBRARY |
Boolean |
No |
If you want to configure the Software Library at the time of installation, set this parameter to 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. However, Oracle recommends that you configure it at the time of installation so that it is automatically configured by the installer, thus saving your time and effort. |
|
SOFTWARE_LIBRARY_LOCATION |
String |
Yes |
If you have set |
|
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, 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:
If your Oracle RAC database 11.2 or higher is configured with Single Client Access Name (SCAN) listener, then you can enter a connection string using the SCAN listener. Note: If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter for the |
|
LISTENER_PORT |
String |
Yes |
Enter the listener port to connect to the existing database. For example, " |
|
SERVICENAME_OR_SID |
String |
Yes |
Enter the service name or the system ID (SID) of the existing database. For example, |
|
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. Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. If you connect to a database instance that was created using the database template offered by Oracle, then note that the password assigned to the user accounts SYSMAN_MDS, SYSMAN_APM, and SYSMAN_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the SYSMAN password you enter 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.
For example, 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 Section 2.1.6. 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 Step 2 of 12: 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:
|
|
MANAGEMENT_TABLESPACE_LOCATION |
String |
Yes |
Enter the absolute path to the location where the data file ( For example:
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 ( For example, 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 ( For example, Enterprise Manager Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP). |
|
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 Section 2.1.10 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 |
|
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 Management Plug-In, Oracle Fusion Middleware Management Plug-In, Oracle My Oracle Support Management Plug-In, and Oracle Exadata Management Plug-In get automatically installed with the Enterprise Manager system. However, if you want to install any of the other optional plug-ins that are available in the software kit (DVD or downloaded software), then enter the plug-in IDs for this variable. For example,
If you want to install any plug-in that is not available in the software kit, then do the following:
|
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.