Before you start installing Enterprise Manager Cloud Control, you must understand the fundamentals of Enterprise Manager installation, the various installation types you can use, the components that are installed by default, and so on. This section introduces you to the installation process, and covers the following:
You can install Enterprise Manager Cloud Control with either simple or advanced configuration. Table 4-3 describes the basic differences between the two installation types.
| Meant for demonstration or evaluation purposes, and small deployments, and when you do not want to worry about the granular control of the installer and want to install the Enterprise Manager system quickly, with less memory, and for monitoring fewer targets in their environment |
Meant for small, medium, and large deployments, and when you want to customize your installation with custom locations, directory names, and passwords. |
| Installs with minimal, default configuration settings and preferences that you need for a complete Enterprise Manager system. Does not offer too many options to customize your installation. |
Offers custom or advanced configuration options that you can select to suit your environment and customize your installation. |
| Configures with less memory to monitor up to 30 targets, with 2 Oracle Management Agents (Management Agent) and 2 concurrent user sessions for handling about 10 jobs per day. |
Offers an option to select the deployment size (small, medium, or large) of your choice, and depending on the deployment size you select, configures with the required memory.
The deployment size essentially indicates 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.
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 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 Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
|
| Sets lower values for database parameters. For information about the database initialization parameters to be set for various deployment sizes, refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
Sets higher values for database parameters. For information about the database parameters set for different deployment sizes, refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
| Allows you to use a database where the Management Repository is preconfigured using the database templates offered by Oracle. |
Allows you to use a database where the Management Repository is preconfigured using the database templates offered by Oracle. |
| Installs mandatory plug-ins such as Oracle Database plug-in, Oracle Fusion Middleware plug-in, Oracle My Oracle Support plug-in, Oracle Exadata plug-in, and Oracle Cloud Framework Plug-In. |
1) Installs mandatory plug-ins such as Oracle Database plug-in, Oracle Fusion Middleware plug-in, Oracle My Oracle Support plug-in, Oracle Exadata plug-in, and Oracle Cloud Framework Plug-In. 2) Installs any other plug-in you select in the installation wizard. |
| Creates a default user account weblogic for the WebLogic domain GCDomain. |
Allows you to change the name of the default user account weblogic for the WebLogic domain GCDomain. |
| Prompts for a common password for WebLogic Server administration, Node Manager, SYSMAN user account, and Management Agent registration. |
Prompts for separate, distinct passwords for WebLogic Server administration, Node Manager, SYSMAN user account, and Management Agent registration. |
| Creates a default OMS instance base directory (gc_inst) outside the Middleware home. |
Allows you to change the name of the default OMS instance base directory (gc_inst) to a name of your choice, and creates that directory outside the Middleware home. |
| Creates tablespaces for management, configuration data, and JVM diagnostics data in default locations. |
Allows you to change the locations of the tablespaces for management, configuration data, and JVM diagnostics data. |
| Installs with default ports. |
Allows you to customize the ports according to your environment. |
| Has only a few interview screens to fill in the Enterprise Manager Cloud Control Installation Wizard. |
Has many interview screens to fill in the Enterprise Manager Cloud Control Installation Wizard |
When you install OEM on a PC you need a
Net8 service name[1] that points to your database. You learned how to create one in the module about Net8. Oracle Enterprise Manager will have its own home directory. Underneath that will be a Net8 directory with a tnsnames.ora file just for Enterprise Manager. Be sure to place the service name entry for the
COIN database in that file. You may have other tnsnames.ora files on your PC, but Enterprise Manager will use the one underneath its home directory.
If you intend to use Enterprise Manager to start and stop your database, you will need to create a database password file, and you will need to grant yourself the SYSDBA privilege. You should have already done this in the previous module. If you have not performed these tasks yet, go back and do that now, because that will be necessary to complete this module.
One final note. You do not absolutely need to install Enterprise Manager for this course, or for this series of DBA courses. There are plenty of simulations in this course that show you how the various Enterprise Manager applications work. However, if you think that you will prefer Enterprise Manager to the command-based utilities, then you will probably want to install it.
Also, you should know that OEM does require Windows NT. Even if you are managing Unix databases, you always run OEM from a PC.