PK
Pz@oa, mimetypeapplication/epub+zipPK Pz@ iTunesMetadata.plistj
This chapter describes what property files and the command locations within them you need to validate before installing a standalone Oracle Management Agent (Management Agent). In particular, this chapter covers the following:
Every time you install a Management Agent, the property files mentioned in the platformInfo.properties
file are loaded with default locations to commands that are required for successfully running certain Application Programming Interfaces (APIs). For example, the ping
executable. This section describes such property files. In particular, this section covers the following:
Table B-1 describes the property files loaded from the platformInfo.properties
file.
Table B-1 Property Files Loaded from platformInfo.properties File
Loading Order | Property File Name | Type | Description |
---|---|---|---|
1 |
Generic |
Contains arguments that need to be passed every time the commands listed in this file are run. | |
2 |
Generic |
Contains paths for all the commands that need to be run, regardless of the operating system. | |
3 |
|
Operating System-Specific |
Contains commands that need to be run for a particular operating system. For example, On Microsoft Windows, the path to the Cygwin binaries is hardcoded in the |
4 |
Generic |
Contains variables that are used to specify the command paths. You must uncomment the variables that you want to use and specify appropriate values. |
Keep in mind the following points:
The property files mentioned in the platformInfo.properties
file are loaded one-by-one in ascending order. This means that command locations you specify in the last file that is loaded will override the values you specified for the same key in the previously loaded property file.
For example, spaths.properties
is loaded before ssPaths.properties
. So if the default location for the ping executable in sPaths.properties
file is usr/bin/ping
, and if location for the same executable in the ssPaths.properties
file is usr/sbin/ping
, then the value in the latter file takes precedence over the former file.
If you want to include other command variables, then you can do one of the following:
Specify the additional command variables in sPaths.properties
, ssPaths_<platform>.properties
, or userPaths.properties
.
Create a new property file with additional command variables. Then, mention the name of this new property file in platforminfo.properties
.
Table B-2 describes the other property files that are loaded.
Table B-2 Other Property Files Loaded
Property File Name | Type | Description |
---|---|---|
Generic |
Contains properties that help you control the activity and performance of the application. For example, these:
| |
Generic |
If there are error messages displayed in the error stream that you know can be ignored in the setup, then you can update these messages in the Generally, if the error stream contains data when you run any command, then it is assumed that the command failed. However, the data in the error stream may not always correspond to the error. So, to ignore such error messages, you must add the messages (including the banner) to the For example, when you run Administrator. It usually boils down to these two things:#1) Respect the privacy of others.#2) Think before you type.Password: This essentially is just a warning and does not constitute the failure of the executed command. |
Note: The data format for these files mandates only one property per line. You must specify the property values in the format:variable=value . |
The default command locations specified in the property files can vary between hosts and operating systems. Therefore, it is important to verify the command locations before you install a Management Agent.
To validate the command locations, follow these steps:
Access the platformInfo.properties
file from the following location of the OMS home, and make note of the property files you need to validate for your platform:
$<OMS_HOME>/oui/prov/resources
Access each of the property files you noted in Step (1), and verify that the command locations mentioned for the following variables map to valid locations on the OMS host:
SSH_PATH
SCP_PATH
SH_PATH
PING_PATH
Access each of the property files you noted in Step (1), and verify that the command locations mentioned for the following variables also map to valid locations on the destination host:
SCP_PATH
SH_PATH
SSH_PATH
CHMOD_PATH
MKDIR_PATH
RM_PATH
This part describes how you can install Enterprise Manager Cloud Control. In particular, this part contains the following chapters:
This chapter provides an overview of Oracle Enterprise Manager Cloud Control (Enterprise Manager Cloud Control) and helps you understand its architecture and the various core components that are integrated within the product.
This chapter contains the following sections:
Enterprise Manager Cloud Control is system management software that delivers centralized monitoring, administration, and life cycle management functionality for the complete IT infrastructure, including systems running Oracle and non-Oracle technologies.
Your environment may comprise multiple Oracle Databases, Oracle WebLogic Servers, Web applications deployed on these servers, hosts running these targets, and so on. You can, of course, use the individual product consoles to monitor the status of each of these targets, but it becomes cumbersome to shuttle between multiple console windows and track the performance of each of these targets using so many windows.
Enterprise Manager Cloud Control offers a solution that allows you to monitor and manage the complete Oracle IT infrastructure from a single console. In addition, it provides support for business-driven IT management and business-centric top-down application management to manage your business services, user experience, and infrastructure. It also offers support for monitoring certain non-Oracle products, for example, IBM WebSphere Application Server, Microsoft SQL Server, Juniper Networks NetScreen Firewall, and so on.
With a broad set of end-to-end monitoring, administration, configuration management, provisioning, and security capabilities, Enterprise Manager Cloud Control reduces the cost and complexity of managing computing environments. Robust service-level management functionality within Enterprise Manager Cloud Control dramatically improves service levels through rich transaction and end-user performance monitoring and deep diagnostics for multi-tier Internet applications.
For more information about Enterprise Manager Cloud Control, access the following URL:
http://www.oracle.com/us/products/enterprise-manager/index.html
Enterprise Manager Cloud Control includes the following components:
Oracle Management Agent
Oracle Management Service
Oracle Management Repository
Oracle Management Plug-Ins
Enterprise Manager Cloud Control Console
Figure 1-2 shows a sample Enterprise Manager Cloud Control architecture and illustrates how these core components fit into the architecture.
Note: In Figure 1-2, the load balancer and the multiple OMSes are depicted only to indicate how a sample Enterprise Manager Cloud Control architecture would look in a large organization. They are not a prerequisite or a requirement for an Enterprise Manager system installation. If you do not have a load balancer, then the Management Agents communicate directly with the OMSes. |
The following sections describe the core components of Enterprise Manager Cloud Control.
Oracle Management Agent (Management Agent)
The Management Agent is an integral software component that enables you to convert an unmanaged host to a managed host in the Enterprise Manager system. The Management Agent works in conjunction with the plug-ins to monitor the targets running on that managed host.
Oracle Management Service (OMS)
The OMS is a Web-based application that orchestrates with the Management Agents and the Oracle Management Plug-Ins to discover targets, monitor and manage them, and store the collected information in a repository for future reference and analysis. The OMS also renders the user interface for Enterprise Manager Cloud Control. The OMS is deployed to the Oracle Middleware Home (middleware home), which is the parent directory that has the Oracle WebLogic Server home, the OMS home, the Management Agent home, the plug-in home, the Java Development Kit (JDK), the OMS instance base directory, the Oracle WT directory, the Oracle Common directory, and other relevant configuration files and directories. While deploying the OMS, the Enterprise Manager Cloud Control Installation Wizard installs Oracle WebLogic Server if it does not already exist in your environment. As a result, a WebLogic Server admin console is also installed.
Oracle Management Repository (Management Repository)
The Management Repository is a storage location where all the information collected by the Management Agent gets stored. It consists of objects such as database jobs, packages, procedures, views, and tablespaces.
The OMS uploads the monitoring data it receives from the Management Agents to the Management Repository. The Management Repository then organizes the data so that it can be retrieved by the OMS and displayed in the Enterprise Manager Cloud Control console. Since data is stored in the Management Repository, it can be shared between any number of administrators accessing the Enterprise Manager Cloud Control.
At the time of installation, the Enterprise Manager Cloud Control Installation Wizard configures the Management Repository in your existing, certified database. The wizard, however, does not install a new database.
Oracle Management Plug-Ins (Plug-Ins)
Plug-Ins are pluggable entities that offer special management capabilities customized to suit specific target types. Unlike the earlier releases of Enterprise Manager, in Enterprise Manager Cloud Control, the plug-ins work in conjunction with the OMS and the Management Agent to monitor every target in your environment. Therefore, they are deployed to the OMS as well as the Management Agent. In the earlier releases, plug-ins enabled you to monitor only third-party targets, but in Enterprise Manager Cloud Control, plug-ins enable you to monitor all types of targets in your environment.
Plug-ins have independent release cycles, so every time you have a new version of an Oracle product released, you will have a new version of the plug-in released to support monitoring of that new product version in Enterprise Manager Cloud Control. This simplifies things because you no longer have to wait to upgrade your Enterprise Manager system to support a new product version; instead you can upgrade your plug-ins to monitor the new product version.
Table 1-1 lists the mandatory plug-ins that are installed by default with a new Enterprise Manager system. In addition to these mandatory plug-ins, you can optionally install other plug-ins available in the software kit (DVD, downloaded software bundle, and so on). The installer offers a screen where you can select the optional plug-ins and install them.
Table 1-1 Mandatory Plug-Ins Installed with Enterprise Manager Cloud Control
Name | Description |
---|---|
Oracle Database |
Enables you to monitor and manage Oracle Database and related targets such as Oracle Real Application Clusters (Oracle RAC), Oracle Automatic Storage Management (Oracle ASM), and so on. |
Oracle Fusion Middleware |
Enables you to monitor and manage Oracle Fusion Middleware products such as Oracle WebLogic Domain, Oracle WebLogic AdminServer, Oracle WebLogic Server, Oracle SOA Suite, Oracle Web Tier, and so on. |
Oracle My Oracle Support |
Enables you to log in to My Oracle Support from within the Cloud Control console, search the knowledge library for notes and documents, raise service requests, and create patch plans and templates for patching monitored targets. |
Oracle Exadata |
Enables you to monitor and manage Oracle Exadata targets. |
Enterprise Manager Cloud Control Console
The Enterprise Manager Cloud Control console is the user interface you see after you install Enterprise Manager Cloud Control. With the help of the console, you can monitor and administer your entire computing environment from one location on the network. All the systems and services including enterprise application systems, databases, hosts, middleware application servers, listeners, and so on, are easily managed from one central location.
This chapter describes how you can install Oracle Management Agent (Management Agent). In particular, this chapter covers the following:
Oracle Management Agent (Management Agent) is one of the core components of Enterprise Manager Cloud Control that enables you to convert an unmanaged host to a managed host in the Enterprise Manager system. The Management Agent works in conjunction with the plug-ins to monitor the targets running on that managed host.
Therefore, at any point in time, if you want to monitor a target running on a host, ensure that you first convert that unmanaged host to a managed host by installing a Management Agent, and then manually discover the targets running on it to start monitoring them.
To install a Management Agent, use the Add Host Targets Wizard that is accessible from within the Enterprise Manager Cloud Control console. Oracle recommends you to this wizard particularly for mass-deployment of Management Agents.
The Add Host Targets Wizard is an application that offers GUI-rich, interactive screens. The wizard enables you to do the following on multiple hosts across platforms with options to run preinstall and postinstall scripts:
Install a Management Agent (called Shared Agent) using an existing, centrally shared Management Agent (called Master Agent)
Note: This chapter only describes how you can deploy a fresh Management Agent using the Add Host Targets Wizard. For information on cloning an existing instance and deploying a Management Agent using a shared instance, refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
To monitor a target, you need to add the target to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.
For information about discovering targets in Enterprise Manager Cloud Control, refer to the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Once the installation is complete, you will see the following default contents in the agent base directory:
<agent_base_directory> |_____core |_____12.1.0.1.0 |_____plugins |_____agent_inst |_____sbin |_____plugins.txt |_____plugins.txt.status |_____agentimage.properties
Note: If you want to move your Management Agents from one Enterprise Manager Cloud Control to another, then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new Enterprise Manager Cloud Control. This is typically done when you want to move from an Enterprise Manager Cloud Control in a test environment to an Enterprise Manager Cloud Control in a production environment. |
Before you begin installing an Oracle Management Agent, keep these points in mind:
The Add Host Targets Wizard converts an unmanaged host to a managed host in the Enterprise Manager system by installing an Oracle Management Agent 12c.
Oracle recommends you to use the Add Host Targets Wizard to mass-deploy Management Agents in your environment.
Oracle Management Agent 12c communicates only with Oracle Management Service 12c and not with any earlier release of Enterprise Manager.
If you have multiple hosts, sharing a common mounted drive, then install the Management Agents in two different phases:
In the Add Host Targets Wizard, select the deployment type Fresh Agent Install, and install a Management Agent on the host where the drive is shared. Alternatively, you can select the deployment type Clone Existing Agent, and clone the Management Agent to the host where the drive is shared.
For more information, refer to the chapter on cloning a Management Agent in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
In the Add Host Targets Wizard, select the deployment type Add Host to Shared Agent, and install a Management Agent on all other hosts that access the shared, mounted drive. (Here, you will select the Management Agent you installed in the previous step as the master agent or shared agent.)
For more information, refer to the chapter on installing a Shared Agent in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
If you have an Oracle RAC Cluster with multiple nodes, then you must install a Management Agent on each of the nodes separately. In other words, in the Add Host Targets Wizard, you must add each node explicitly as a destination host.
The Add Host Targets Wizard uses SSH to establish connectivity between Oracle Management Service (OMS) and the remote hosts where you want to install the Management Agents.
Only SSH1 (SSH version 1) and SSH2 (SSH version 2) protocols offered by OpenSSH are supported for deploying a Management Agent.
SSH public key Authentication and password based authentication are supported. So you can use an existing SSH public key authentication without exposing your passwords. You can provide a dummy password in the wizard and bypass the validation.
To set up the SSH keys, follow these steps:
Navigate to the following location in the OMS home:
$<OMS_HOME>/oui/prov/resources/scripts
For example,
/home/software/em/middleware/oms/oui/prov/resources/scripts
Run the following script, and pass the OMS user name you used for installing the OMS and the fully qualified name of the target hosts.
sshUserSetup.sh -setup -user <user_name> -hosts <target_hosts>
Access the Add Host Targets Wizard, and provide the dummy password and install the Management Agent.
The wizard ignores the dummy password, and honors the keys present in the following location on the OMS host to perform the installation. Here, $HOME refers to the home directory of the OMS install user.
$HOME/.ssh/id_rsa
$HOME/.ssh/identity
The Add Host Targets Wizard supports Named Credentials that enable you to use a set of credentials registered with a particular name specifically for this operation, by your administrator. This ensures an additional layer of security for your passwords because as an operator, you can only select the named credential, which is saved and stored by an administrator, and not know the actual user name and password associated with it.
In case the named credential you select does not have the root privileges to perform the installation, then you can set the named credential to run as another user (locked user account). In this case, the wizard logs in to the hosts using the named credential you select, but performs the installation using the locked user account you set.
For example, you can create a named credential titled User_A, and set it to run as User_X that has the root privileges. In this case, the wizard logs in to the hosts as User_A, but installs as User_X.
By default, the Add Host Targets Wizard configures only the following types of plug-ins:
All discovery plug-ins that were configured with the OMS from where the Management Agent software is being deployed.
Oracle Home discovery plug-in
Oracle Home monitoring plug-in
You must have read privileges on the Oracle WebLogic Server's alert log directories for the Support Workbench (Incident) metrics to work properly. You must also ensure that the Management Agent that is monitoring this Oracle WebLogic Server target is running on the same host as the Oracle WebLogic Server.
You must not install two Management Agents on the same host. This disrupts the communication with the OMS.
If you have common mount point in your organization, then ensure that it is generic and ensure that you install the Management Agent in this generic mount points. This guideline helps when you upgrade your Management Agents to higher releases in the future within the same mount point, and not acquire new mount points each time.
For example, have a mount point such as /oracle/product/agent
and install the Management Agent in there so that it appears as /oracle/product/agent/agent12c.
Do not install the Management Agent directly in the mount point because it breaks the upgrade path and causes problems with cleanup operations.
Table 8-1 lists the prerequisites you must meet before installing the Management Agent.
Table 8-1 Prerequisites for Installing Oracle Management Agent
Requirement | Description |
---|---|
Hardware Requirements |
Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 2. |
Software Requirements |
(For Microsoft Windows) Ensure that you have installed Cygwin on the destination host as described in Chapter 5. |
Operating System Requirements |
Ensure that you install the Management Agent only on certified operating systems as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support. To access this matrix, follow these steps:
|
Package Requirements |
Ensure that you install all the operating system-specific packages as described in Chapter 3. |
User and Operating System Group Requirement |
Ensure that you create the required operating system groups and users as described in Chapter 4. |
Destination Host Requirements |
Ensure that the destination hosts are accessible from the host where the OMS is running. If the destination host and the host on which OMS is running belong to different network domains, then ensure that you update the For example, if the fully-qualified host name is
|
Destination Host Credential Requirements |
Ensure that all the destination hosts running on the same operating system have the same set of credentials. For example, all the destination hosts running on Linux operating system must have the same set of credentials. The wizard installs the Management Agent using the same user account. If you have hosts running on the same operating system but with different credentials, then have two different deployment sessions. |
(Only for UNIX)
| |
If a firewall configured in your environment does not allow any ping traffic, then ensure that you do the following:
| |
Ensure that the SSH daemon is running on the default port (that is, 22) on all the destination hosts. To verify the port, run the following command:
If the port is a non-default port, that is, any port other than 22, then update the
| |
On the destination host, ensure the following:
| |
Ensure that the software of the Management Agent you want to install is available in Oracle Software Library (Software Library).
| |
Validate the path to all command locations as described in Appendix B. | |
If you are installing from an ipv6 OMS to a non-ipv6 host, then follow these step:
| |
Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. By default, the temporary directory location set to the environment variable | |
| |
Ensure that you (in fact, all users accessing the agent base directory) have read and execute permission on all the directories that lead up to the agent base directory. For example, if the agent base directory is | |
| |
Installing User Requirements |
|
Agent User Account Permissions and Rights (For Microsoft Windows) |
(For Microsoft Windows) If you are installing the Management Agent on a Microsoft Windows-based operating system, then ensure that the agent user account has permissions and rights to perform the following:
To verify whether the agent user has these rights, follow these steps:
|
Permissions for cmd.exe (For Microsoft Windows) |
(For Microsoft Windows) If you are installing the Management Agent on a Microsoft Windows-based operating system, then ensure that you grant the For more information on this restriction and to understand how you can grant these permissions, access the following URL to Microsoft Web site: |
Ensure that the preinstallation and postinstallation scripts that you want to run alon~ug with the installation are available either on the OMS host, destination hosts, or on a shared location accessible to the destination hosts. | |
|
To install a fresh Management Agent, follow these steps:
In Cloud Control, do one of the following:
From the Setup menu, select Add Target, and then, click Auto Discovery Results. On the Auto Discovery Results page, select a host you want to monitor in Enterprise Manager Cloud Control, and click Promote.
From the Setup menu, select Add Target, and then, click Add Targets Manually. On the Add Targets Manually page, select Add Host Targets and click Add Host.
On the Host and Platform page, do the following:
Accept the default name assigned for this session or enter a unique name of your choice. The custom name you enter can be any intuitive name, and need not necessarily be in the same format as the default name. For example, add_host_operation_1
.
A unique deployment activity name enables you to save the installation details specified in this deployment session and reuse them in the future without having to enter all the details all over again in the new session.
Click Add to enter the fully qualified name and select the platform of the host on which you want to install the Management Agent.
Note:
|
Alternatively, you can click either Load from File to add host names stored in a file, or Add Discovered Hosts to add host names from a list of hosts discovered by Enterprise Manager. For information on how the host name entries must appear in the host file, see Format of Host List File.
Note: When you click Add Discovered Hosts and add hosts from a list of discovered hosts, the host's platform is automatically detected and displayed. The platform name is detected using a combination of factors, including hints received from automated discovery and the platform of the OMS host. This default platform name is a suggestion, so Oracle strongly recommends you to verify the platform details before proceeding to the next step. |
If you are correcting the platform names, and if all the hosts run on the same platform, then set the platform for the first host in the table and from the Platform list, select Same for All Hosts. This will ensure that the platform name you selected for the first host is also set for the rest of the hosts in the table.
Note:
|
Click Next.
On the Installation Details page, do the following:
In the Deployment Type section, select Fresh Agent Install.
Note: If you have multiple hosts sharing a common mounted drive, then install the Management Agents in two different phases:
|
From the table, select the first row that indicates the hosts grouped by their common platform name.
In the Installation Details section, provide the installation details common to the hosts selected in Step 3 (b). For Installation Base Directory, enter the absolute path to the agent base directory where you want the software binaries, security files, and inventory files of Management Agent to be copied.
For example, /u01/app/Oracle/
.
Note: The Installation Base Directory is essentially the agent base directory. Ensure that the directory you provide is empty. If a previously run deployment session had failed for some reason, then you might see an ADATMP_<timestamp> subdirectory in the agent base directory. In this case, either delete the subdirectory and start a new deployment session, or retry the failed session from the Add Host Status page. |
For Instance Directory, accept the default instance directory location or enter the absolute path to a directory of your choice where all Management Agent-related configuration files can be stored.
For example, /u01/app/Oracle/agent_inst
If you are entering a custom location, then ensure that the directory has write permission. Oracle recommends you to maintain the instance directory inside the agent base directory.
From Named Credential list, select an appropriate profile whose credentials can be used for setting up the SSH connectivity between the OMS and the remote hosts, and for installing a Management Agent on each of the remote hosts.
Note:
|
For Privileged Delegation Setting, validate the Privilege Delegation setting to be used for running the root scripts. By default, it is set to the Privilege Delegation setting configured in Enterprise Manager Cloud Control.
If you leave this field blank, the root scripts will not be run by the wizard; you will have to run them manually after the installation. For information about running them manually, see After You Install.
This setting will also be used for performing the installation as the user set in the Run As attribute of the selected Named Credential if you had set the user while creating that Named Credential.
Note: In the Privilege Delegation setting, the%RUNAS% is honored as the root user for running the root scripts and as the user set in the Run As attribute of the Named Credential for performing the installation. |
For Port, accept the default port (3872) that is assigned for the Management Agent to communicate, or enter a port of your choice.
The custom port you enter must not be busy. If you are not sure, you can leave this field blank. Enterprise Manager Cloud Control automatically assigns the first available free port within the range of 1830 - 1849.
(Optional) In the Optional Details section, enter the absolute path to an accessible location where the preinstallation and postinstallation scripts you want to run are available. Note that only shell scripts are supported, and only one preinstallation or one postinstallation script can be specified.
If you want to run the script as root
, then select Run as Root. If the script is on the host where OMS is running and is not on the host where you want to install the Management Agent, then select Script on OMS. In this case, the script will be copied from the OMS host to the destination hosts, and then run on the destination hosts.
(Optional) For Additional Parameters, enter a whitespace-separate list of additional parameters that you want to pass during the installation. For a complete list of supported additional parameters, see Table 8-2.
For example, if you want to provide the inventory pointer location file, then enter -invPtrLoc
followed by the absolute path to the file location. However, note that this parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms.
Repeat Step 3 (b) to Step 3 (i) for every other row you have in the table.
Click Next.
On the Review page, review the details you have provided for the installation and do one of the following:
If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.
If you want to cancel the deployment session for some reason, click Cancel. You are automatically taken to the Add Targets Manually page.
If you are satisfied with the details, then click Deploy Agent to install the Management Agent. You are automatically taken to the Add Host Status page that enables you to monitor the progress of the deployment session.
If you want to cancel a running deployment session, then on the Add Host Starge page, click Cancel. Note that once you cancel the session, you cannot track or resume the session in any way. However, the currently launched commands on the remote hosts will continue to run until they are completed.
Note:
|
In the Add Host Targets Wizard, you can click Load from File to add the hosts listed in a file. However, ensure that the file you select has one of the following formats:
Only the host name.
For Example,
host1.example.com
host2.example.com
The host name followed by the platform name.
For Example,
host1.example.com linux
host2.example.com aix
The supported platform names are linux_x64, linux, solaris, hpunix, hpi, linux_zseries64, aix, linux_ppc64, windows_x64, solaris_x64, win32.
Table 8-2 lists the additional parameters supported for installing a new Management Agent.
Table 8-2 Supported Additional Parameters
Parameter | Description |
---|---|
INVENTORY_LOCATION |
Enter the absolute path to the Central Inventory (oraInventory). For example, Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms. |
-invPtrLoc |
Enter the absolute path to the inventory file that has the location of the Central Inventory (oraInventory). For example, Note: This parameter is supported only on UNIX platforms, and not on Microsoft Windows platforms. |
s_agentServiceName |
(Only for Microsoft Windows) Enter a custom name for the Management Agent service. Every Management Agent appears as a service in Microsoft Windows, and every Management Agent has a default service name. If you want to assign a custom name to identify it, then use this parameter. For example, |
EM_STAGE_DIR |
Enter the absolute path to a custom location that can be created as a temporary Provisioning Advisor Framework (PAF) staging directory. By default, every time you install a Management Agent, a 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 ( If you want to override this location with a custom location, you can pass this option and enter a custom location. For example,
|
After you install the Management Agent, follow these steps:
Verify the installation on the Add Host Status page. Review the progress made on each of the phases of the deployment operation — Initialization, Remote Prerequisite Check, and Agent Deployment.
Note: In the Add Host Targets Wizard, after you click Deploy Agent to install one or more Management Agents, you are automatically taken to the Add Host Status page.If you want to view the details or track the progress of all the deployment sessions, then from the Setup menu, select Add Target, and then, click Add Targets Manually. On the Add Targets Manually page, select Add Host Targets and click Add Host Results. |
If a particular phase fails or ends up with a warning, then review the details provided for each phase in the Agent Deployment Details section, and do one of the following:
Ignore the warning or failure, and continue with the session if you prefer.
You can choose to proceed with the deployment of Management Agents only on those remote hosts that have successfully cleared the checks, and you can ignore the ones that have Warning or Failed status. To do so, click Continue and select Continue, Ignoring Failed Hosts.
You can choose to proceed with the deployment of Management Agents on all the hosts, including the ones that have Warning or Failed status. To do, click Continue and select Continue, All Hosts.
Fix the problem by reviewing the error description carefully, understanding its cause, and taking action as recommended by Oracle.
You can choose to retry the deployment of Management Agents with the same installation details. To do so, click Retry and select Retry Using Same Inputs.
You can retry the deployment of Management Agents with modified installation details. To do so, click Retry and select Update Inputs and Retry.
Note: If you want to cancel a running deployment session, then click Cancel. Note that once you cancel the session, you cannot track or resume the session in any way. However, the currently launched commands on the remote hosts will continue to run until they are completed. |
If required, manually verify the installation:
Navigate to the Management Agent home and run the following command to see a message that confirms that the Management Agent is up and running:
$<AGENT_HOME>/bin/emctl status agent
Note: If the status of the Management Agent is down for some reason, then manually start the Management Agent:
|
Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully:
$<AGENT_HOME>/bin/emctl upload agent
Verify if all the plug-ins were installed successfully. To do so, access the following log file from the Management Agent home, and search for the sentence WARN:Plugin configuration has failed.
$<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log
For example,
$<MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log
If you find the sentence, resolve the issue by running the AgentPluginDeploy.pl
script from the Management Agent home.
$<MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/perl/bin/perl <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0 -agentDir <AGENT_BASE_DIR> -pluginIdsInfoFile <AGENT_BASE_DIR>/plugins.txt -action configure -emStateDir <AGENT_INSTANCE_HOME>
For example,
/u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/perl/bin/perl /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/ -agentDir /u01/app/Oracle/Middleware/agent -pluginIdsInfoFile /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/sysman/install/plugins.txt -action configure -emStateDir /u01/app/Oracle/Middleware/agent/agent_inst
(Only for UNIX Operating Systems) If you had ignored the prerequisite check warning about not having root privileges, SUDO/PBRUN binaries, or SUDO/PBRUN privileges, then manually run the following scripts as a root user from each of the hosts where the installation was done. If you do not have SUDO/PBRUN privileges, then request your Administrator who has the privileges to run these scripts.
If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh
script from the inventory location specified in the oraInst.loc
file that is available in the Management Agent home.
For example, if the inventory location specified in the oraInst.loc
file is $HOME/oraInventory
, then run the following command:
$HOME/oraInventory/oraInstRoot.sh
Note: If you are not a root user, then use SUDO/PBRUN to change to a root user. For example, run the following command:
|
Run the root.sh
script from the Management Agent home:
$<AGENT_HOME>/root.sh
Note: If you are not a root user, then use SUDO/PBRUN to change to a root user. For example, run the following command:
|
By default, the host and the Management Agent get automatically added to the Enterprise Manager Cloud Control console for monitoring. None of the targets running on that host get automatically discovered and monitored.
To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.
For information about discovering targets in Enterprise Manager Cloud Control, refer to the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Note: If you want to move your Management Agents from one Enterprise Manager Cloud Control to another, then you must first deinstall those Management Agents and plug-ins, and then redeploy those Management Agents and plug-ins using the new Enterprise Manager Cloud Control. This is typically done when you want to move from an Enterprise Manager Cloud Control in a test environment to an Enterprise Manager Cloud Control in a production environment. |
This chapter describes how you can install Application Dependency and Performance (ADP) in the Enterprise Manager Cloud Control environment.
In particular, this chapter covers the following:
Application Dependency and Performance (ADP) is one of the critical functionalities in Enterprise Manager Cloud Control that allows you to analyze Java EE, SOA, Portal, OSB, and ADF applications. It captures the complex relationships among various application building blocks in its application schema model - the core of the Oracle intelligent platform.
Therefore, to manage applications effectively, gain an understanding of the complex relationships among the business functions, associated interconnected components, and the underlying runtime environments, you must deploy Application Dependency and Performance (ADP) Manager application, and monitor them by installing the corresponding ADP agents.
To install ADP, use the Middleware Diagnostics page that is accessible from within Enterprise Manager Cloud Control console. To access the page, from Setup menu, select Middleware Diagnostics.
The Middleware Diagnostics Page is a GUI based screen that enables you to deploy ADP Manager, and monitor the health of the ADP Manager application in a reliable and an efficient manner.
Using Middleware Diagnostics Page, you can achieve the following:
Deploy Application Dependency and Performance Manager.
Monitor the availability of all the ADP Managers.
Access information about the ADP Managers like host to which the managers are deployed, the current status, the port on which they running, version, and so on.
Before you begin installing Application Dependency and Performance, keep these points in mind.
For ADP Manager:
The Weblogic Server on which you want to deploy the ADP Manager application must be up and running.
ADP Manager can be deployed only on managed servers that are part of Enterprise Manager Cloud Control domain.
Oracle recommends that you do not deploy other applications to the managed server on which the ADP Manager is deployed.
For ADP Agent:
To deploy ADP Agent, the WebLogic Server hosting the ADP Manager should be up and running.
Ensure that at least one ADP Manager up and running in Active state to deploy an ADP Agent.
Ensure that you meet the following prerequisites:
For information about ADP Manager hardware requirements, refer to "CPU, RAM, Heap Size, and Hard Disk Space Requirements for OMS"
The default ADP Manager ports are: ADP Manager Port: 51099, Java Provider Port: 55003, and Remote Service Controller Port: 55000
Before deploying ADP Agent, ensure that you meet the following prerequisites:
This section contains the following topics:
To deploy ADP Manager on the same host as OMS, automatically creating a managed server, you must log in to Enterprise Manager Cloud Control with Super Administrator privilieges (SYSMAN
), and perform the following steps:
In Cloud Control, from Setup menu, select Middleware Diagnostics.
On the Middleware Diagnostics page, click Deploy ADP Manager.
The ADP Manager deployment page appears.
On the Deploy ADP Manager page, select Create a managed server, and enter the following details:
Select an OMS Server from the Host list. The list comprises of all the servers discovered in Enterprise Manager WebLogic domain.
For example, host1.example.com (EMGC_OMS1),
host2.example.com (EMGC_OMS2)
, and so on.
Enter a unique Managed Server Name.
For example, EMGC_ADPMANAGER1, EMGC_ADPMANAGER2,
and so on.
The Port numbers for Listen Port, SSL Listen Port, ADP Manager Registry Port, ADP Manager Java Provider Port, and ADP Manager Controller Port are populated with the default values 4200, 4201, 51099, 55003, and 55000 respectively. You can change these values if required.
Note: ADP Manager registry port enables communication between ADP Manager and ADP Agent.
Depending on the host selected in the previous step, you are prompted for the credentials, as follows:
If you select the same host as the Administration Server (EMGC_OMS1
), then you must provide the Oracle WebLogic Administration Server Host Credentials and Oracle WebLogic Domain Credentials.
If you select a different host (EMGC_OMS2
) from the Administration Server, then in addition to Oracle WebLogic Administration Server Host Credentials and Oracle WebLogic Domain Credentials, you must also provide Oracle WebLogic Managed Server Host Credentials
Where,
Oracle WebLogic Administration Server Host Credentials are credentials for the host where the WebLogic Administration Server is running.
Oracle WebLogic Domain Credentials are credentials of the Weblogic domain in the Enterprise Manager Cloud Control.
Oracle WebLogic Managed Server Host Credentials are the credentials of the host machine where the Managed Server is running.
For more information about credentials, see Selecting Credentials.
Click Deploy to submit the job.
The ADP Deployment Status page appears with a link to the job status. Click the link to see the status of the job that you submitted.
To deploy ADP Agents to a WebLogic Server, perform the following steps:
In Cloud Control, from the Targets menu, select Middleware.
The Middleware page displays a list of all the Middleware targets discovered and managed in Cloud Control. Click target name to select the desired target.
On the Middleware page, click Oracle WebLogic Domain. Ensure that the selected domain is not an Enterprise Manager Cloud Control domain (EMGC_DOMAIN
).
Note: ADP Agent cannot be deployed on a managed server (WebLogic Server) present in the Enterprise Manager domain. |
All the managed server present in the domain appear on the domain home page.
From the WebLogic Domain menu, select Diagnostics, and then click Setup Diagnostics Agents to deploy agents to the selected managed servers.
On the Deploy Diagnostics Agents page, choose the Oracle WebLogic Server (managed server) to which you want to deploy the ADP agents.
Ensure that you retain the selection of only those Diagnostic Agent(s) that you want to deploy to each of the managed server, deselect the others.
By default, the following servers appear deselected:
The Administration server is not selected by default.
All the managed servers that are not up and running appear deselected by default.
If the Deployed Version and the Version to Deploy are the same, and the status of already deployed ADP agent is up and running.
Note: In Addition to the managed server selected, the ADP Agent is deployed to the Administration Server of the selected domain. |
In the Diagnostics Agent Configuration section, enter the ADP Configuration Properties for the selected agents:
Select the desired ADP Manager from the ADP Manager list.
The ADP agents selected for deployment will report to the selected ADP Manager.
If you select the Update Remote Start configuration option, then some configuration scripts run in the background to facilitate the monitoring process. Select this option if you use node manager to stop or start the WebLogic Servers to which ADP agent is being deployed.
For more information about the NodeManager, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
If the version of the WebLogic Server is greater than 9.2.X, and if the Management Agent is used to discover the monitored WebLogic domain which is not JRF enabled, then an Additional Configuration section appears.
In the WebLogic Home field, enter the absolute path to the WebLogic home of the monitored domain.
If the WebLogic Middleware Home field appears, then enter the absolute path to the WebLogic Middleware Home of the monitored domain.
In the Credentials section, provide Oracle WebLogic Administration Server Host Credentials , Oracle WebLogic Domain Credentials, Oracle Enterprise Manager WebLogic Administration Server Host Credentials, and Oracle Enterprise Manager WebLogic Domain Credentials.
Where,
Oracle WebLogic Administration Server Host Credentials are credentials for the host where the WebLogic Administration Server is running.
Oracle WebLogic Domain Credentials are credentials of the monitored Weblogic domain in the Enterprise Manager Cloud Control.
Oracle Enterprise Manager WebLogic Administration Server Host Credentials are required to access the host where the WebLogic administration server for the Cloud Control domain is running.
Oracle Enterprise Manager WebLogic Domain Credentials are required to access the Enterprise Manager Cloud Control domain.
For more information about selecting credentials, see Selecting Credentials.
Click Deploy to submit the job. A Diagnostics Agent Deployment status page appears:
The status page appears with a link to the job status. Click the link to see the status of the job that you submitted.
Note: Restart the administration server and the managed servers to which the ADP Agents have been deployed. These servers should be restarted only after the deployment has completed successfully. |
This section contains the following details:
Once you have deployed ADP Manager, you can perform the following sanity checks to verify if the ADP manager has been installed accurately on the managed server:
In Cloud Control, from Setup menu, click Middleware Diagnostics. On the Middleware Diagnostics page, the newly deployed JVMD Manager must appear and its status must be up and running.
In Cloud Control, from the Targets menu, select Middleware, from Middleware Features, click Application Dependency and Performance. On the ADP home page, in the Registration tab, the managed server on which the ADP Manager is deployed must appear. Select the manager name and click Test Connect to ensure that the manger is up and running.
Once you have deployed ADP Agent, you can perform the following steps to verify if the ADP Agent is installed on the targeted manager servers accurately:
In Cloud Control, from Targets menu, select Middleware.
On the Middleware page, from Middleware Features, click Application Dependency and Performance.
On the Monitoring tab, expand the folder corresponding to the ADP Manager associated with the deployed agents.
Select the Status node in the navigation tree, and click the node, do not expand it. Verify the Agent Information table for the servers that you deployed to.
Note: If you have not restarted the monitored servers, then the EJB Deployed status should be true, and the Agent Installed status should be false.Once you restart the monitored servers, the Agent Status for those servers should be REPORTING. |
The script content on this page is for navigation purposes only and does not alter the content in any way.
This chapter describes the hardware requirements you must meet before installing Oracle Management Service (OMS), a standalone Oracle Management Agent (Management Agent), and Oracle Management Repository (Management Repository). In particular, this chapter covers the following:
CPU, RAM, Heap Size, and Hard Disk Space Requirements for OMS
CPU, RAM, and Hard Disk Space Requirements for Standalone Management Agent
CPU, RAM, and Hard Disk Space Requirements for Management Repository
Table 2-1 describes the CPU, physical memory (RAM), heap size, and hard disk space requirements for installing an OMS (including a Management Agent that comes with it).
Table 2-1 CPU, RAM, Heap Size, and Hard Disk Space Requirements Per OMS
Small | Medium | Large | |
---|---|---|---|
(1 OMS, <=1000 targets, <100 agents) |
(2 OMSes for <=10,000 targets and <1000 agents) |
(> 2 OMSes, >=10,000 targets, >=1000 agents) | |
CPU Cores/Host |
2 |
4 |
8 |
RAM |
4 GB |
6 GB |
8 GB |
RAM with ADPFoot 1 , JVMDFoot 2 |
6GB |
10 GB |
14 GB |
Oracle WebLogic Server JVM Heap Size |
512 MB |
1 GB |
2 GB |
Hard Disk Space |
7 GB |
7 GB |
7 GB |
Hard Disk Space with ADP, JVMD |
10 GB |
12 GB |
14 GB |
Footnote 1 ADP Manager is Application Dependency and Performance
Footnote 2 JVMD is JVM Diagnostics
Note: While installing an additional OMS (by cloning an existing one), if you have installed BI publisher on the source host, then ensure that you have 7 GB of additional hard disk space on the destination host, so a total of 14 GB. |
For a standalone Oracle Management Agent, ensure that you have 2 CPU cores per host, 512 BM of RAM, and 1 GB of hard disk space.
Table 2-2 describes the RAM and the hard disk space requirements for configuring a Management Repository:
Table 2-2 RAM and Hard Disk Space Requirements for Management Repository
Small | Medium | Large | |
---|---|---|---|
(1 OMS, <=1000 targets, <100 agents) |
(2 OMSes for <=10,000 targets and <1000 agents) |
(> 2 OMSes, >=10,000 targets, >=1000 agents) | |
CPU Cores/HostFoot 1 |
2 |
4 |
8 |
RAM |
4 GB |
6 GB |
8 GB |
Hard Disk Space |
50 GB |
200 GB |
400 GB |
Footnote 1 For high availability, Oracle Real Application Cluster (Oracle RAC) database must be setup.
This chapter explains how you can install Cygwin and start the SSH daemon on Microsoft Windows hosts. In particular, this chapter covers the following:
Note: This chapter is applicable only for the following cases:
|
When you use the Add Host Targets Wizard to install Oracle Management Agent (Management Agent) on a destination host that is running on Microsoft Windows, as a prerequisite, you are expected to have Cygwin installed and the SSH Daemon started on that destination host.
Similarly, when you use the Add Host Targets Wizard to install from an OMS host that is running on Microsoft Windows, as a prerequisite, you are expected to have Cygwin installed on that source host.
The Add Host Targets Wizard is an application built into the Enterprise Manager Cloud Control console. It offers GUI-rich, interactive screens to enable you to install Management Agents on unmanaged hosts and convert them to managed hosts so that they can be monitored and managed in Enterprise Manager Cloud Control.
Cygwin is essentially a utility that offers a Linux-like environment on a Microsoft Windows operating system. Technically, it is a DLL (cygwin1.dll) that acts as a Linux API layer providing substantial Linux API functionality. Once you install Cygwin, you can configure the SSH Daemon on it.
The SSH Daemon enables the Add Host Targets Wizard to establish an SSH connectivity (Secure Shell) between the destination host and the host running Oracle Management Service (OMS). Using this connectivity, the wizard transfers the software binaries to the destination host over SSH protocol, and installs and configures the Management Agent.
Caution: Ensure that your password-enabled SSH connection is set up between the host and OMS, and not between destination hosts. |
In Enterprise Manager Cloud Control, the Add Host Targets Wizard automatically sets up and drops the SSH connectivity. Therefore, all you need to do is, manually install Cygwin on the destination host and start the SSH Daemon on it.
To install Cygwin, follow these steps:
Before starting with the SSHD setup, ensure you are not using OpenSSH and MKSNT when using the Add Host Targets Wizard. The Add Host Targets Wizard uses the complete Cygwin suite (full collection of the software tools packaged in Cygwin).
To get the complete collection of Cygwin, do the following:
Ensure OpenSSH\bin
and mksnt
are not in your PATH environment variable. If they are, remove them by doing the following:
Right-click on My Computer and go to Properties.
In the System Properties window, click Advanced.
In this tab, click Environment Variables.
Here, search for the PATH system variable, select it, and if the OpenSSH\bin
and mksnt
are present in the PATH, click Edit.
In the Edit System Variable dialog box, delete these two values from the PATH, and click OK.
Stop the SSH Daemon if it is running from OpenSSH
:
Right-click on My Computer, and select Manage.
In the Computer Management window, in the left pane, expand Services and Applications, and select Services.
In the right pane, right-click the SSH daemon service and click Stop.
Note: Ensure you rename the installation directories ofOpenSSH and mksnt. |
Visit the following Web site, and install the Cygwin software in the C:\cygwin
directory:
Note: If you install Cygwin in a different directory on the destination host, then do the following:(a) Ensure that you update the (b) If the OMS as well as the target is on Microsoft Windows, ensure that Cygwin is installed in the same location on the OMS host. |
While installing Cygwin, ensure that you select the following packages in the Select Packages screen:
From the Archive category, select unzip
and zip
.
From the Net category, select openssh
.
After you install Cygwin, navigate to the C:\cygwin
directory, open the cygwin.bat
file using the Notepad utility, and edit it to add the following line:
set CYGWIN=binmode tty ntsec
Open the Cygwin Bash Shell and verify whether cygrunsrv
is installed:
bash cygrunsrv -h
Note: If you are prompted to provide a Cygwin value, enterbinmode tty ntsec . If this returns an error message stating service does not exist, you are on the right track, and can proceed to the next step. |
Open a new command prompt and run the following:
-bash -ssh-host-config
Note: Enter no when prompted to create sshd user account (message reads sshd user account needs to be created).Enter yes for all other prompts. When prompted to answer the question Which value should the environment variable CYGWIN have when sshd starts?, Oracle recommends that you set the value to at least ntsec as shown in the following example. This will enable you to change the user context without having to specify the password. As an answer to the previously mentioned question, specify a value that is similar to the following and press Enter: CYGWIN="binmode tty ntsec" |
Now, open the /etc/passwd
file, and remove only those entries of the user that you will use to connect to the OMS machine.
For example,
If the user that you are employing to connect to the OMS machine is a local user, execute the following:
/bin/mkpasswd -l –u <USER> >> /etc/passwd
If the user you are employing to connect to the OMS machine is a domain user, execute the following:
/bin/mkpaswd.exe -d -u <USER> >> /etc/passwd /bin/mkgroup.exe -d >> /etc/group mkdir -p /home/<USER> (for example, mkdir -p /home/pjohn) chown <USER> /home/<USER> (for example, chown pjohn /home/pjohn)
If the user you are employing to connect to the OMS machine is a domain user, do the following:
Right-click on My Computer, and select Manage.
In the Computer Management dialog box that appears, go to Services and Applications, and select CYGWIN sshd.
Right-click CYGWIN sshd and select Properties.
In the Properties dialog box, go to the Log On tab.
Here, specify the domain/user name and password. Click Apply.
Change the permission of /etc/ssh_host_rsa_key
. It is recommended that you do not allow private key files to be accessible by others.
Now, go to the CYGWIN command prompt, and execute the following:
chmod 644 /etc/ssh* chown <USERNAME> /var/empty chmod 755 /var/empty chmod 644 /var/log/sshd.log
Note: If/var/log/sshd.log does not exist, you do not have to execute the following command:
chmod 644 /var/log/sshd.log |
Start the SSH daemon by executing:
/usr/sbin/sshd
Alternatively, from the same BASH prompt, you can also execute:
cygrunsrv -S sshd
Note: Usecygrunsrv -E sshd to stop the SSH daemon. |
You can now test your cygwin
setup.
To do this, go to a different machine (that has the ssh
client running), and execute the following command:
ssh -l <USERNAME> <localhost> 'date' OR ssh -l <USERNAME> <this node> 'date'
For example,
ssh -l pjohn example.com 'date'
This command will prompt you to specify the password. When you specify the correct password, the command should return the accurate date.
To verify if the timezone environment variable (TZ
) is accessible by the SSH server on the remote hosts, execute the following command from the OMS host:
ssh -l <user_name> -n <remote_node> 'echo $TZ'
If this command does not return the TZ
environment variable value, you must set the TZ
variable and ensure this is accessible by the SSH server. You can set the TZ
environment variable on remote hosts in the following sections:
If the shell being used is BASH, add the following line to the .bashrc
file in the home directory of the user (being used) for ssh
access:
export TZ=<your machine's timezone>
If you are using a CSH shell, then add the following line to the .cshrc
file in that directory:
setenv TZ <your machine's timezone>
Depending on the shell that is present on the host, set the TZ variable by running the following command. In the following command, PST8PDT
is only an example.
For a CSH Shell, specify: setenv TZ PST8PDT
Restart the SSH daemon by executing:
sudo /etc/init.d/sshd restart
Now, execute the following command from the OMS home to verify if the SSH server can access the TZ variable.
ssh -l <user_name> -n <node_name> 'echo $TZ'
The timezone variable must be set in the rc
file of the shell that the host is using.
For example, if the host is using a BASH shell, go to the user's home directory ($HOME
) and add the following to the ~/.bashrc
file to set the TZ variable:
TZ=PST8PDT; export TZ
If the host is using a CSH shell, go to $HOME
and add the following to the ~/.cshrc
file:
setenv TZ PST8PDT
Now, execute the following command from the OMS home to verify if the SSH server can access the TZ variable.
ssh -l <user_name> -n <node_name> 'echo $TZ'
This chapter describes how you can install a new Enterprise Manager system while utilizing an existing, certified Oracle Database to store Oracle Management Repository (Management Repository). In particular, this chapter covers the following:
You can install Enterprise Manager Cloud Control with either simple or advanced configuration.
As part of a new Enterprise Manager system, the installation wizard does the following:
Installs the following components in the middleware home you enter in the installation wizard:
Oracle Management Service 12c Release 1 (12.1.0.1)
Oracle Management Agent 12c Release 1 (12.1.0.1)
Oracle JRF 11g Release (11.1.1.4.0), which includes oracle_common
directory
Oracle Web Tier 11g Release (11.1.1.4.0), which includes Oracle_WT
directory
Oracle Database Management Plug-In
Oracle Fusion Middleware Management Plug-In
Oracle My Oracle Support Management Plug-In
Oracle Exadata Management Plug-In
Note:
|
Creates an Oracle WebLogic domain called GCDomain
. For this WebLogic Domain, a default user account, weblogic
, is used as the administrative user. You can choose to change this, if you want, in the installer.
Creates a Node Manager user account called nodemanager
. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.
Configures an Oracle Management Service Instance Base location (gc_inst
) in the Oracle Middleware Home (middleware home), for storing all configuration details related to Oracle Management Service 12c. You can choose to change this, if you want, in the installer.
For example, if the middleware home is /u01/app/Oracle/Middleware/
, then the instance base location is /u01/app/Oracle/Middleware/gc_inst
. You can choose to change this, if you want, in the installer. However, you can change it for only advanced installation and not for simple installation.
Configures Oracle Management Repository in the existing, certified Oracle Database.
Runs the following configuration assistants to configure the installed or upgraded components:
Plugins Prerequisites Check
Repository Configuration Assistant
MDS Schema Configuration Assistant
OMS Configuration Assistant
Plugins Deployment and Configuration Assistant
Start Oracle Management Service Configuration Assistant
Plugins Inventory Migration Configuration Assistant
Oracle Configuration Manager Repeater Configuration Assistant
Oracle Configuration Manager for OMS Configuration Assistant
Agent Configuration Assistant
By default, the following are the contents of the middleware home for this type of installation:
<middleware_home> |_____wlserver_10.3 |_____jdk16 |_____oms |_____plugins |_____oracle.sysman.db.oms.plugin_12.1.0.1.0 |_____oracle.sysman.emas.oms.plugin_12.1.0.1.0 |_____oracle.sysman.mos.oms.plugin_12.1.0.1.0 |_____agent |_____plugins |_____oracle.sysman.db.agent.plugin_12.1.0.1.0 |_____oracle.sysman.db.discovery.plugin_12.1.0.1.0 |_____oracle.sysman.emas.agent.plugin_12.1.0.1.0 |_____oracle.sysman.emas.discovery.plugin_12.1.0.1.0 |_____core |_____12.1.0.1.0 |_____agent_inst |_____sbin |_____agentimage.properties |_____gc_inst |_____Oracle_WT |_____oracle_common |_____utils |_____logs |_____modules |_____user_project |_____ocm.rsp |_____registry.dat |_____domain-registry.xml |_____registry.xml
Before you begin, keep these points in mind:
You must ensure that you have the latest Enterprise Manager Cloud Control software:
Ensure that you have the Enterprise Manager Cloud Control software released in February 2012 - Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) (With Bundle Patch 1). You can download it from the following URL:
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
If you had downloaded and installed the Enterprise Manager Cloud Control software released in October 2011, then apply the following patches, which are part of the Bundle Patch 1 released in February 2012, on the OMS and the Management Agent. In this case, you do not have to download the one released in February 2012.
On OMS, apply the patch 13242773.
On Management Agent, apply the patches 13242776, 13491785, 13550565, and 13550561.
To apply these patches, you can either read the My Oracle Support note 1395505.1 or the ReadMes packaged with the patches.
If you had downloaded the Enterprise Manager Cloud Control software released in October 2011, but not installed it yet, then discard that software and download the one released in February 2012 - Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) (With Bundle Patch 1. You can download it from the following URL:
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
(Only for Microsoft Windows) Ensure that there are no white spaces in the name of the directory where you download the Enterprise Manager Cloud Control software. For example, do not download the software to a directory titled Program Files
because there is a white space between the two words of the directory name.
You can install Enterprise Manager Cloud Control using the installation wizard only on a single host, that is, locally on the server where the wizard is invoked. You cannot install on multiple or remote hosts.
Enterprise Manager Cloud Control can communicate only with Oracle Management Agent 12c and not with any earlier release of the Management Agent.
While installing on hosts that have multiple host names (for example, virtual hosts), you can pass the fully qualified host name using the ORACLE_HOSTNAME
argument. Ensure that the host name you enter does not have underscores.
For example:
./runInstaller ORACLE_HOSTNAME=example.com
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.
You must set the DISPLAY
environment variable.
In bash terminal, run the following command:
export DISPLAY=<hostname>:<vnc port>.0
For example, export DISPLAY=example.com:1.0
In other terminals, run the following command:
setenv DISPLAY <hostname>:1.0
For example, setenv DISPLAY example.com:1.0
The Enterprise Manager Cloud Control Installation Wizard installs Java Development Kit (JDK) 1.6 v24 and Oracle WebLogic Server 11g Release 1 (10.3.5) only if they do not exist in your environment.
If Oracle WebLogic Server 11g Release 1 (10.3.5) does not exist and if you want to manually install it, then ensure that you install it using JDK 1.6 v24+ (64-bit version for 64-bit platforms and 32-bit version for 32-bit platforms).
Download JDK 1.6 v24+ for your platform from the platform vendor's Web site. For example, download SUN JDK 1.6 v24+ for Linux platforms from Oracle Web site. Similarly, download the JDK for other platforms from other vendors' trusted Web sites.
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.5) on Linux 64-bit platforms, first install the 64-bit JDK for that platform, and then download and use the wls1035_generic.jar
file to install Oracle WebLogic Server.
For example,
<JDK home>/bin/java -d64 -jar <absolute_path _to_wls1035_generic.jar>
If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.5) on Linux 32-bit platforms, then download and use either the wls1035_linux32.bin
file or the wls1035_generic.jar
file.
For example,
<JDK home>/bin/java -jar <absolute_path _to_wls1035_generic.jar>
You must download the Oracle WebLogic Server software from Oracle Web site, and follow the instructions outlined in the Oracle® Fusion Middleware Installation Guide for Oracle WebLogic Server to install it. 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.
You must not install Enterprise Manager Cloud Control in a middleware home that is on an NFS-mounted drive. Installing Enterprise Manager on an NFS-mounted drive causes the Oracle HTTP Server to restart frequently, which in turn makes the OMS inaccessible.
If you are forced to install on such a shared drive, then perform an advanced installation as described in Installing with Advanced Configuration so that you can enter a non-NFS-mounted location for the OMS instance base directory (gc_inst
). In simple installation, you have no control over the OMS instance base directory location, as the default location is set by the installation wizard.
You must ensure that the Oracle WebLogic Server 11g Release 1 (10.3.5) 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.
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 must upgrade all existing EMCLI clients of the earlier release to 12c Release 1 so that they can work with Enterprise Manager Cloud Control. This means, you must discard the old one and set up a new one.
For information about setting up a new EMCLI client, see the Enterprise Manager Command Line Interface Download page within the Cloud Control console. To access that page, in Cloud Control, from the Setup menu, select My Preferences, and then, click Command Line Interface.
In addition to the mandatory plug-ins listed above, you can optionally install other plug-ins available in the software kit (DVD, downloaded software). The installer offers a screen where you can select the optional plug-ins and install them. However, if you want to install some plug-ins that are not available in the software kit (DVD, downloaded software), then refer to Advanced Installer Options.
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.
Table 6-1 lists the prerequisites you must meet before installing Enterprise Manager Cloud Control.
Table 6-1 Prerequisites for Installing Enterprise Manager Cloud Control
Requirement | Description |
---|---|
Hardware Requirements |
Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 2. |
Operating System Requirements |
Ensure that you install Enterprise Manager Cloud Control only on certified operating systems as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support. To access this matrix, follow these steps:
Note: If you use Oracle Solaris 10, then ensure that you have update 9 or higher installed. To verify whether it is installed, run the following command:
You should see the output similar to the following. Here,
|
Package Requirements |
Ensure that you install all the operating system-specific packages as described in Chapter 3. |
Operating System Groups and Users Requirements |
Ensure that you create the required operating system groups and users as described in Chapter 4. |
Unique Host Name and Static IP Address Requirements |
Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network. Note: You must use only a static IP address. If you use a dynamic IP address, the installation will fail. |
Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. By default, the temporary directory location set to the environment variable | |
Ensure that you allocate 100 MB of space for the central inventory directory. Also ensure that the central inventory directory is not on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1. | |
Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file. For example:
| |
File Descriptor Requirements |
Ensure that you set the file descriptor to a minimum of 4096. To verify the current value set to the file descriptors, run the following command:
If the current value is not 4096 or greater, then as a root user, update the
|
Ensure that the existing database is a certified database as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support. To access this matrix, follow these steps:
Important:
| |
Ensure that the host name specified in the The following is the recommended format of the
For example,
According to RFC 952, the following are the assumptions: A name (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of domain style names. No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. Also, if DNS server is configured in your environment, then you should be able to use DNS to resolve the name of the host on which you want to install the OMS. For example, all these commands must return the same output:
| |
Ensure that you meet the following requirements:
| |
| |
Ensure that the Central Inventory ( | |
Proximity Requirements |
Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond. |
Ensure that the ports you assign (within the given range) to the following components are free and available:
To verify if a port is free, run the following command:
| |
Internet Connection Requirements |
Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support. |
This section describes the following:
To install Enterprise Manager Cloud Control with simple configuration, 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. This helps you set up your Management Repository beforehand without starting 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 Appendix A. |
Invoke the Enterprise Manager Cloud Control Installation Wizard
Invoke the installation wizard as a user who belongs to the oinstall
group you created following the instructions in Chapter 4.
<Software_Location>/runInstaller
In this command, <Software_Location>
is either the DVD location or the location where you have downloaded the software kit.
Enter My Oracle Support Details
(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).
If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support.
Click Next.
Install Software Updates
On the Software Updates screen, select one of the following sources from where the software updates can be installed while the installation of the Enterprise Manager system is in progress. If you do not want to apply them now, then select Skip.
(Recommended) Select Search for Updates, and then, select Local Directory if you have already manually downloaded the software updates to an accessible local or remote location. Enter the location where the updates are available, and click Search for Updates. To search the computer and select the location, click Browse. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.
If the updates have been downloaded to the default location, then select or enter the full path to the scratch path location. For example, if the scratch path location is /scratch/OracleHomes
and if the software updates are available in /scratch/OracleHomes/Updates
, then enter /scratch/OracleHomes/Updates
.
If the software updates have been downloaded to a custom location, then select or enter the full path to the custom location. For example, if the custom location is /home/john
and if the software updates are available in /home/john/Updates
, then enter /home/john/Updates
.
Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.
Enter the My Oracle Support account user name and password, and click Search for Updates. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch
Note: If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches. To do so, log in to Enterprise Manager Cloud Control, and from the Setup menu, select My Oracle Support, and then, click Set Credentials. On the My Oracle Support Preferred Credentials page, enter the credentials and click Apply. |
Click Next.
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears. For details, see step (6). Otherwise, the Check Prerequisites screen appears. For details, see step (8).
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:
<system drive>\Program Files\Oracle\Inventory
Enter Oracle Inventory Details
On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.
Enter the full path to a directory where the inventory files and directories can be placed.
Note:
|
Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.
Click Next.
Check Prerequisites
On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.
The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.
The status of the prerequisite check can be either Warning, Failed, or Succeeded.
If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.
Although Oracle recommends you to investigate and correct the problems, if you are compelled to proceed without resolving them, then select Ignore to ignore the warnings and failures.
However, all package requirements must be met or fixed before proceeding any further. Otherwise, the installation might fail.
Click Next.
Select Installation Type
On the Install Types screen, do the following:
Select Create a New Enterprise Manager System, and then, select Simple.
Validate or enter the middleware home where you want to install the OMS and other core components.
Note:
|
Click Next.
Enter Configuration Details
On the Configuration Details screen, do the following:
Enter an administrator password, which can be used as a common password for configuring the Enterprise Manager Cloud Control.
Note: Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. |
The administrator password is used as a common password for SYSMAN user account, WebLogic user account, node manager user account, and also for authenticating new Oracle Management Agents that join the Enterprise Manager system.
Enter the fully qualified name of the host where the existing database resides, the database's listener port and its service name or system ID (SID), and the SYS user account's password.
Note: Oracle Real Application Cluster (Oracle RAC) nodes are referred to by their virtual IP (vip) names. Theservice_name parameter is used instead of the system identifier (SID) in connect_data mode, and failover is turned on. For more information, refer to Oracle Database Net Services Administrator's Guide. |
The installer uses this information to connect to the existing, certified Oracle Database for creating the SYSMAN schema. SYSMAN schema holds most of the relational data used in managing Enterprise Manager Cloud Control.
Note: If any repository-related prerequisite check fails, see Appendix A to manually run the prerequisite check. |
Click Next.
Note:
|
Review and Install
On the Review screen, review the details you provided for the selected installation type.
If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.
After you verify the details, if you are satisfied, click Install to begin the installation process.
On the Install Progress screen, view the overall progress (in percentage) of the installation and the status of each of the configuration assistants. Configuration assistants are run for configuring the installed components of Enterprise Manager Cloud Control.
Note:
|
Once the software binaries are copied and configured, you are prompted to run the allroot.sh
script, and the oraInstRoot.sh
script if this is the first Oracle product installation on the host. Open another window, log in as root
, and manually run the scripts.
If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script.
On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.
For more information about this installation, refer to the following file in the OMS home:
$<OMS_HOME>/install/setupinfo.txt
Note: If the installation fails for some reason, review the log files available in the following locations of the OMS home:
|
To install Enterprise Manager Cloud Control with advanced configuration, 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. This helps you set up your Management Repository beforehand without starting 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 Appendix A. |
Invoke the Enterprise Manager Cloud Control Installation Wizard
Invoke the installation wizard as a user who belongs to the oinstall
group you created following the instructions in Chapter 4.
<Software_Location>/runInstaller
In this command, <Software_Location>
is either the DVD location or the location where you have downloaded the software kit.
Note: For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options. To make yourself aware of some installation-related known issues, see Limitations. |
Enter My Oracle Support Details
(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).
If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support.
Click Next.
Install Software Updates
On the Software Updates screen, select one of the following sources from where the software updates can be installed while the installation of the Enterprise Manager system is in progress. If you do not want to apply them now, then select Skip.
(Recommended) Select Search for Updates, and then, select Local Directory if you have already manually downloaded the software updates to an accessible local or remote location.
Enter the location where the updates are available, and click Search for Updates. To search the computer and select the location, click Browse. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.
If the updates have been downloaded to the default location, then select or enter the full path to the scratch path location. For example, if the scratch path location is /scratch/OracleHomes
and if the software updates are available in /scratch/OracleHomes/Updates
, then enter /scratch/OracleHomes/Updates
.
If the software updates have been downloaded to a custom location, then select or enter the full path to the custom location. For example, if the custom location is /home/john
and if the software updates are available in /home/john/Updates
, then enter /home/john/Updates
.
Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.
Enter the My Oracle Support account user name and password, and click Search for Updates. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch
Note: If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches. To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, click Set MOS Credentials and register the credentials. |
Click Next.
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears. For details, see step (6). Otherwise, the Check Prerequisites screen appears. For details, see step (8).
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:
<system drive>\Program Files\Oracle\Inventory
Enter Oracle Inventory Details
On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.
Enter the full path to a directory where the inventory files and directories can be placed.
Note:
|
Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.
Click Next.
Check Prerequisites
On the Prere quisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.
The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.
The status of the prerequisite check can be either Warning, Failed, or Succeeded.
If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.
Note: You can choose to ignore the checks with Warning status by clicking Ignore. However, all package requirements must be met or fixed before proceeding any further. |
Click Next.
Select Installation Type
On the Install Types screen, do the following:
Select Create a New Enterprise Manager System, and then, select Advanced.
Validate or enter the middleware home where you want to install the OMS and other core components.
Note:
|
Click Next.
Select Plug-Ins
On the Select Plug-Ins screen, select the optional plug-ins you want to install from the software kit (DVD, downloaded software) while installing the Enterprise Manager system. The screen lists the mandatory plug-ins as well as the optional plug-ins. The grayed rows indicate the mandatory plug-ins that will be installed.
Note: During installation, if you want to install a plug-in that is not available in the software kit, then refer to Advanced Installer Options for the point that describes how you can install additional plug-ins. |
Click Next.
Enter WebLogic Server Configuration Details
On the WebLogic Server Configuration Details screen, enter the credentials for the WebLogic Server user account and the Node Manager user account, and validate the path to the Oracle Management Service instance base location.
Note: Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. |
By default, the WebLogic Domain name is GCDomain
, and the Node Manager name is nodemanager
. These are non-editable fields. The installer uses this information for creating Oracle WebLogic Domain and other associated components such as the admin server, the managed server, and the node manager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.
Click Next.
Enter Database Connection Details
On the Database Connection Details screen, enter the fully qualified name of the host where your existing, certified Oracle Database resides, its listener port and its service name or system ID (SID), and the SYS user account's password.
Note: Oracle Real Application Cluster (Oracle RAC) nodes are referred to by their virtual IP (vip) names. Theservice_name parameter is used instead of the system identifier (SID) in connect_data mode, and failover is turned on. For more information, refer to Oracle Database Net Services Administrator's Guide. |
The installer uses this information to connect to the existing, certified Oracle Database for creating the SYSMAN schema. SYSMAN schema holds most of the relational data used in managing Enterprise Manager Cloud Control.
Note: If any repository-related prerequisite check fails, see Appendix A to manually run the prerequisite check. |
Click Next.
Note:
|
Enter Repository Configuration Details
On the Repository Configuration Details screen, do the following:
For SYSMAN Password, enter a password for creating the SYSMAN user account. The SYSMAN user account is used for creating the SYSMAN schema, which holds most of the relational data used in managing Enterprise Manager Cloud Control. SYSMAN is also the super administrator for Enterprise Manager Cloud Control.
Note: Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. |
For Registration Password, enter a password for registering the new Management Agents that join the Enterprise Manager system.
Note: Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value. |
For Management Tablespace, enter the full path to the location where the data file for management tablespace (mgmt.dbf
) can be stored. The installer uses this information for storing data about the monitored targets, their metrics, and so on. Ensure that the specified path leads up to the file name.
For example, /u01/oracle/prod/oradata/mgmt.dbf
For Configuration Data Tablespace, enter the full path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1.dbf
) can be stored. This is required for storing configuration information collected from the monitored targets. Ensure that the specified path leads up to the file name.
For example, /u01/oracle/prod/oradata/mgmt_ecm_depot1.dbf
For JVM Diagnostics Data Tablespace, enter the full path to a location where the data file for JVM Diagnostics data tablespace (mgmt_ad4j.dbf
) can be stored. Ensure that the specified path leads up to the file name. Enterprise Manager Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).
For example, /u01/oracle/prod/oradata/mgmt_ad4j.dbf
Note: If you are configuring the Management Repository on a database that uses Oracle Automatic Storage Management (Oracle ASM) for storage, then when you enter the data file location, only the disk group is used for creating the tablespaces. For example, if you specify+DATA/a.dbf , then only +DATA is used for creating the tablespaces on Oracle ASM, and the exact location of the data file on the disk group is decided by Oracle Managed Files. |
Click Next.
Customize Ports
On the Port Configuration Details screen, customize the ports to be used for various components.
Note: If all the ports on this screen appear as -1, then it indicates that the installer is unable to bind the ports on the host. To resolve this issue, exit the installer, verify the host name and the IP configuration of this host (ensure that the IP address of the host is not being used by another host), restart the installer, and try again. |
You can enter a free custom port that is either within or outside the port range recommended by Oracle.
To verify if a port is free, run the following command:
On Unix:
netstat -anp | grep <port no>
On Microsoft Windows:
netstat -an|findstr <port_no>
However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini
file and if you want to use those ports, then click Import staticports.ini File and select the file.
Note: If thestaticports.ini file is passed during installation, then by default, the ports defined in the staticports.ini file are displayed. Otherwise, the first available port from the recommended range is displayed. |
Click Next.
Review and Install
On the Review screen, review the details you provided for the selected installation type.
If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.
After you verify the details, if you are satisfied, click Install to begin the installation process.
On the Install Progress screen, view the overall progress (in percentage) of the installation and the status of each of the Configuration Assistants. Configuration Assistants are run for configuring the installed components of Enterprise Manager Cloud Control.
Note:
|
Once the software binaries are copied and configured, you are prompted to run the allroot.sh
script, and the oraInstRoot.sh
script if this is the first Oracle product installation on the host. Open another window, log in as root
, and manually run the scripts.
If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script. You will directly reach the Finish screen as described in Step (25).
On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.
For more information about this installation, refer to the following file available in the OMS home:
$<OMS_HOME>/install/setupinfo.txt
Note: If the installation fails for some reason, review the log files available in the following locations of the OMS home:
|
The following are some additional, advanced options you can pass while invoking the installer:
By default, GCDomain
is the default name used for creating the WebLogic Domain. To override this and use a custom WebLogic Domain name, invoke the installer with the WLS_DOMAIN_NAME
option, and enter a unique custom name.
For example, if you want to use the custom name EMDomain
, then run the following command:
./runInstaller WLS_DOMAIN_NAME=EMDomain
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
During installation, if you want to install some plug-ins that are not in the software kit (DVD, downloaded software), then follow these steps:
Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location:
http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html
Invoke the installer with the following option, and pass the location where the plug-ins you want to install are available:
./runInstaller -pluginLocation <absolute_path_to_plugin_software_location>
This displays a list of plug-ins available in the software kit (DVD, downloaded software) as well as the plug-ins available in this custom location. You can choose the ones you want to install.
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
To understand the limitations involved with this advanced option, see Limitations.
While installing on hosts having multiple IP addresses, the host name is derived from the ORACLE_HOSTNAME
variable that is passed while invoking the installer. Ensure that the host name you enter does not have underscores.
For example:
./runInstaller ORACLE_HOSTNAME=example.com
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 6-2 lists the different combinations of these advanced options, and describes the workaround to be followed for each combination:
Table 6-2 Advanced Options and Workarounds
Advanced Option | Workaround |
---|---|
|
|
|
|
|
|
After you install, do the following:
(Only for UNIX Operating Systems) If you did not run the allroot.sh
script when the installer prompted you to do so, then run them manually now:
If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh
script from the inventory location specified in the oraInst.loc
file that is available in the Management Agent home.
For example, if the inventory location specified in the oraInst.loc
file is $HOME/oraInventory
, then run the following command:
$HOME/oraInventory/oraInstRoot.sh
Note: If you are not a root user, then use SUDO to change to a root user. For example, run the following command:
|
Run the allroot.sh
script from the OMS home:
$<OMS_HOME>/allroot.sh
Note: If you are not a root user, then use SUDO to change to a root user. For example, run the following command:
|
Navigate to the OMS home and run the following command to see a message that confirms that OMS is up and running.
$<OMS_HOME>/bin/emctl status oms
For example,
/u01/middleware/oms/bin/emctl status oms
Navigate to the Management Agent home and run the following command to see a message that confirms that the Management Agent is up and running.
$<AGENT_HOME>/bin/emctl status agent
Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully.
$<AGENT_HOME>/bin/emctl upload agent
Note: By default, you can access Enterprise Manager Cloud Control only using the HTTPS protocol. If you want to use the HTTP protocol, then unlock it by running the following command from the OMS home:
|
Verify if all the plug-ins were installed successfully. To do so, access the following log file from the Management Agent home, and search for the sentence WARN:Plugin configuration has failed.
$<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log
For example,
$<MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log
If you find the sentence, resolve the issue by running the AgentPluginDeploy.pl
script from the Management Agent home.
$<MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/perl/bin/perl <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0 -agentDir <AGENT_BASE_DIR> -pluginIdsInfoFile <AGENT_BASE_DIR>/plugins.txt -action configure -emStateDir <AGENT_INSTANCE_HOME>
For example,
/u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/perl/bin/perl /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/ -agentDir /u01/app/Oracle/Middleware/agent -pluginIdsInfoFile /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/sysman/install/plugins.txt -action configure -emStateDir /u01/app/Oracle/Middleware/agent/agent_inst
(Optional) If- the repository prerequisites had failed, and if you had manually run the EM Prerequisite Kit and taken corrective actions to meet the repository requirements, then run the utility again to reset the repository settings to what it had originally:
/install/requisites/bin/emprereqkit -executionType install -prerequisiteXMLLoc <prereq_xml_location> -connectString <connect_string> -dbUser SYS -dbPassword <db_password> -reposUser sysman -reposPassword <repo_user_password> -dbRole sysdba -runPrerequisites -runPostCorrectiveActions -useHistory
Note: If you had run the installation wizard and let the installation wizard take corrective actions to correct the repository settings, and if you had exited the wizard without completing the installation process, then remember that the repository settings might not reset to their original values because you abruptly ended the installation. In this case, before invoking the installation wizard again, run this command to manually reset the values. |
By default, the following targets get automatically discovered and monitored in the Enterprise Manager Cloud Control console:
Oracle WebLogic Domain (for example, GCDomain
)
Oracle WebLogic AdminServer
Oracle WebLogic Server
Oracle Web Tier
Application deployments, one for the Enterprise Manager Cloud Control console and one for the platform background services.
Oracle Management Service
Oracle Management Repository
Oracle Management Agent
The host on which you installed Enterprise Manager Cloud Control
However, the other targets running on that host and other hosts do not get automatically discovered and monitored. To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.
For information about discovering targets in Enterprise Manager Cloud Control, refer to the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Configure your proxy server as described in .
(Optional) If you want to modify the connection descriptor for the Management Repository, then shut down the OMS, run the following command, and then restart the OMS.
emctl config oms -store_repos_details (-repos_host <host> -repos_port <port> -repos_sid <sid> | -repos_conndesc <connect descriptor>) -repos_user <username> [-repos_pwd <pwd>] [-no_check_db]
Note: On Linux, you need to double escape the connect descriptor using single and double quotes. However, on Microsoft Windows, you need not.For example, on Linux:
For example, on Microsoft Windows:
|
(Optional) If you want to change the SYSMAN and SYSMAN_MDS passwords, then shut down the OMS, run the following command, and then restart the OMS.
emctl config oms -change_repos_pwd