PK
oAoa, mimetypeapplication/epub+zipPK oA iTunesMetadata.plistj
This chapter describes how you can install JVM Diagnostics (JVMD) in the Enterprise Manager Cloud Control environment.
In particular, this chapter covers the following:
JVM Diagnostics (JVMD) is one of the critical functionalities in Enterprise Manager Cloud Control that enables administrators to diagnose performance problems in Java applications in the production environment. By eliminating the need to reproduce problems, it reduces the time required to resolve these problems thus improving application availability and performance.
Therefore, to manage applications effectively and identify the root cause of performance problems in the production environment without having to reproduce them in the test or development environment, you must deploy JVMD Manager. The JVMD Manager runs as an Enterprise JavaBeans (EJB) Technology on a WebLogic Server.
The JVMD Agent is deployed on the targeted JVM (the one running a production WebLogic Server). It collects real-time data and transmits it to the JVM Diagnostics Manager. This data is stored in the Management Repository, and the collected information is displayed on Enterprise Manager Cloud Control console for monitoring purposes. The communication between the JVMD Manager and the JVMD Agent can be a secure (SSL) or non-secure connection.
To install JVMD, use the Application Performance Management page that is accessible from within Enterprise Manager Cloud Control console. To access the portal, from Setup menu, and then select Application Performance Management.
The Application Performance Management Page is a GUI based screen that enables you to deploy and upgrade the JVMD Manager and Agents, and monitor the health of the JVMD Manager application in a reliable and an efficient manner.
Using Application Performance Management Page, you can achieve the following:
Deploy JVM Diagnostics Manager.
Monitor the availability of all the JVMD Managers.
Access information about the JVMD Managers like the hosts to which the managers are deployed, the current status, the port on which they running, version, and so on.
Before you begin installing JVM Diagnostics, keep these points in mind.
For JVMD Manager:
The Weblogic Server on which you want to deploy the JVMD Manager, must be up and running.
JVMD 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 JVMD Manager is deployed.
For JVMD Agents:
To deploy JVMD Agent, the WebLogic Server hosting the JVMD Manager should be up and running.
Ensure that at least one JVMD Manager is up and running in Active state, to deploy a JVMD Agent.
Ensure that you meet the following prerequisites:
For more information about JVMD Manager hardware requirements, refer to "CPU, RAM, Heap Size, and Hard Disk Space Requirements for OMS"
The JDK version required to deploy JVMD Agent is JDK 1.5 or higher
Supported Operating Systems for JVMD Agents are:
Linux x86
Linux x86-64
Windows x86
Windows x86-64
Solaris x86
Solaris x86-64
Solaris SPARC
Solaris SPARC (64 bit)
AIX PowerPC (32 bit)
AIX PowerPC (64 bit)
JRVE
HP IA-64(32 bit)
HP IA-64(64 bit)
HP PA-RISC(32 bit)
This section contains the following topics:
To deploy JVMD Manager on the same host as OMS; automatically creating a managed server, you must log in with SYSMAN
account (a default Super Administrators account that is installed with Enterprise Manager), and perform the following steps:
In Cloud Control, from Setup menu, select Application Performance Management.
For more information about the Application Performance Management page, see Figure 10-1.
On the Application Performance Management page, from the Add menu, select JVM Diagnostics Engine.
On the Deploy JVM Diagnostics page, select Create a managed server, and enter the following details:
Select an OMS Server from the Host list. The list is comprised of all the servers present in the Enterprise Manager WebLogic domain.
For example, host1.example.com (EMGC_OMS1),
host2.example.com (EMGC_OMS2)
, and so on.
Enter a unique name for the managed server in the Managed Server Name field.
For example, EMGC_JVMDMANAGER1
, EMGC_JVMDMANAGER2,
and so on.
The Port numbers for Managed Server Listen Port and Managed Server SSL Listen Port are populated with the default values 3800 and 3801 respectively. You can change these values by entering custom value if required.
Specify the Oracle Management Server Host Credentials and Oracle WebLogic Domain Credentials:
Where,
Oracle Management Server Host Credentials are the credentials for the host machine where the OMS server selected is running. For example, the OMS selected is EMGC_OMS1
(host1.example.com)
.
Oracle WebLogic Domain Credentials are credentials of the Weblogic domain in the Enterprise Manager Cloud Control.
For more information about credentials, see Selecting Credentials.
Click Deploy to submit the job.
The JVMD Manager 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 JVMD 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 related targets discovered, and being managed in Cloud Control. Click target name to select the desired target.
From the Middleware page, click Oracle WebLogic Domain. JVMD Agents can be deployed on Enterprise Manager WebLogic domain or other WebLogic Domains too.
All the managed server present in the domain appear in 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 as shown in Figure 10-3, choose the Oracle WebLogic Server (managed servers) to which you want to deploy the JVMD agents.
Ensure that you retain the selection of only those Diagnostic Agent(s) that you want to deploy to each of the Managed Servers, 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 the already deployed JVMD agent is up and running.
In the Diagnostics Agent Configuration section, enter the JVMD Configuration Properties for the selected agents.
Select the desired JVMD manager from the JVMD Manager list.
The JVMD agents selected for deployment will report to this JVMD Manager.
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 , and Oracle 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.
For more information, see Selecting Credentials.
Click Deploy to submit the job. A Diagnostics Agent Deployment status page as follows 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.
The section contains the following:
Once you have deployed JVMD manager, you can perform the following sanity checks to verify if the JVMD manager has been installed accurately on the managed server. To monitor the health of the JVM Diagnostics Manager, perform the following steps:
In Cloud Control, from Setup menu, select Application Performance Management.
On the Application Performance Management page, all the deployed Managed Servers are listed. Attributes like Host, Port, SSL Port, Version, Status, Availability, and Server available on the Application Performance Management page helps monitor the status and the availability of the JVMD Manager.
Once you have deployed JVMD Agent, you can perform the following sanity checks to verify if the JVMD Agent is installed on the targeted managed servers accurately:
In Cloud Control, from the Targets menu, select Middleware. On the Middleware home page, select the domain where the JVMD agent was deployed. On the left hand pane, from Target Navigation section, click Java Virtual Machine Pools to expand the menu, the JVMD targets appear.
Each of the targets corresponds to one of the managed servers chosen for JVMD agent deployment. All these mentioned targets should be up and running.
Log into the WebLogic Administration console of the domain where the JVMD agent was deployed. The targeted managed servers should have a new application with the name javadiagnosticagent_<managed_server_name>
, and this application should up and running.
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:
Note: For information on the releases Enterprise Manager Cloud Control has had so far, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
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
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 OMS instances 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 OMS instances. |
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 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.
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 default plug-ins that are installed with a new Enterprise Manager system. In addition to these 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 Default 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.
Cloud Control Basic Installation Guide
12c Release 2 (12.1.0.2)
E22624-13
September 2012
Oracle Enterprise Manager Cloud Control Basic Installation Guide, 12c Release 2 (12.1.0.2)
E22624-13
Copyright ?? 2012,??Oracle and/or its affiliates. All rights reserved.
Primary Author: ??Aravind Jayaraaman
Contributing Author: ??Namrata Bhakthavatsalam, Pradeep Gopal
Contributor: ??Anu Vale, Smitha Vishwanathan, Abhishek Suresh Kumar, Srilatha Uravakonda, Pushkar Jha, Prakash Jaganathan, Mohammed Nazim, Rajesh Parasuraman, Maria Teresa Gil Lucientes, Shilpa Thergaonkar, Palem Naga Maheshwara Reddy, Devanand Patil, Kunamalla Thirumaleshwar, Rajiv Kuriakose, Ashish Goel, Atif Jamil, Karthik Somasundaram, Abhishek Vaidya, Smitha Nath, Erik Demember, Bala Kuchibhotla, Raghavendra Nadidare, Amitabh Khare, Suman Kumar Pramanik, Sanjay Ediga, Akanksha Sheoran, Patrick Combs, Nicole Haba, Glen Hawkins, James Kao, Bhavin Desai, Jeff Barber, David Eschliman, Akshai Duggal, Andrew Gregory, Lachlan Williams, Meghan Ede, Frank Montgomery Jr, Courtney Llamas, David Eschliman, Laiju Raghuvaran, Asham Vohra, Mayumi Hayasaka, Qiang Chen
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
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:
Note: For information on the releases Enterprise Manager Cloud Control has had so far, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
This section covers the following:
You can install Enterprise Manager Cloud Control with either simple or advanced configuration. Table 6-1 describes the basic differences between the two installation types.
Table 6-1 Differences Between Simple and Advanced Installation
Simple Installation | Advanced Installation |
---|---|
Meant for demo or evaluation purposes, and small deployments, and when you do not want to worry about the granular control of the installer and want to install the Enterprise Manager system quickly, with less memory, and for monitoring fewer targets in their environment |
Meant for small, medium, and large deployments, and when you want to customize your installation with custom locations, directory names, and passwords. |
Installs with minimal, default configuration settings and preferences that you need for a complete Enterprise Manager system. Does not offer too many options to customize your installation. |
Offers custom or advanced configuration options that you can select to suit your environment and customize your installation. |
Configures with less memory to monitor up to 30 targets, with 2 Oracle Management Agents (Management Agent) and 2 concurrent user sessions for handling about 10 jobs per day. |
Offers an option to select the deployment size (small, medium, or large) of your choice, and depending on the deployment size you select, configures with the required memory. The deployment size essentially indicates the number of targets you plan to monitor, the number Management Agents you plan to have, and the number of concurrent user sessions you plan have. The prerequisite checks are run regardless of the selection you make, but the values to be set for the various parameters checked depend on the selection you make For more information on deployment sizes, the prerequisite checks that are run, the database parameters that are set, and how you can modify the deployment size after installation, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
Sets fewer database parameters. For information about the database parameters that are set, refer to Setting Database Initialization Parameters |
Sets more database parameters. For information about the database parameters set for different deployment sizes, refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide. |
Allows you to use a database where the Management Repository is preconfigured using the database templates offered by Oracle. |
Allows you to use a database where the Management Repository is preconfigured using the database templates offered by Oracle. |
Installs four mandatory plug-ins such as Oracle Database plug-in, Oracle Fusion Middleware plug-in, Oracle My Oracle Support plug-in, and Oracle Exadata plug-in. |
Installs four mandatory plug-ins such as Oracle Database plug-in, Oracle Fusion Middleware plug-in, Oracle My Oracle Support plug-in, and Oracle Exadata plug-in, and any other plug-in you select. |
Creates a default user account weblogic for the WebLogic domain GCDomain. |
Allows you to change the name of the default user account weblogic for the WebLogic domain GCDomain. |
Prompts for a common password for WebLogic Server administration, Node Manager, SYSMAN user account, and Management Agent registration. |
Prompts for separate, distinct passwords for WebLogic Server administration, Node Manager, SYSMAN user account, and Management Agent registration. |
Creates a default OMS instance base directory |
Allows you to change the name of the default OMS instance base directory |
Creates tablespaces for management, configuration data, and JVM diagnostics data in default locations. |
Allows you to change the locations of the tablespaces for management, configuration data, and JVM diagnostics data. |
Installs with default ports. |
Allows you to customize the ports according to your environment. |
Has only a few interview screens to fill in the Enterprise Manager Cloud Control Installation Wizard. |
Has many interview screens to fill in the Enterprise Manager Cloud Control Installation Wizard |
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 2 (12.1.0.2)
Oracle JRF 11g Release (11.1.1.6.0), which includes oracle_common
directory
Oracle Web Tier 11g Release (11.1.1.6.0), which includes Oracle_WT
directory
Oracle Database Plug-In
Oracle Fusion Middleware Plug-In
Oracle My Oracle Support Plug-In
Oracle Exadata Plug-In
Note:
|
Installs Oracle Management Agent 12c Release 2 (12.1.0.2) in the agent base directory you specify (outside the Middleware home).
For example, if the middleware home is /u01/app/Oracle/Middleware/,
then you can specify the agent base directory as /u01/app/Oracle/agent12c.
Creates an Oracle WebLogic domain called GCDomain
. For this WebLogic Domain, a default user account, weblogic
, is used as the administrative user. In advanced installation, you can choose to change this if you want.
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. In advanced installation, you can choose to change this if you want.
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. If the database instance is created using the database template offered by Oracle, then this step is skipped.
Note: The existing, certified Oracle Database must be one of the certified databases listed in the Enterprise Manager certification matrix available on My Oracle Support, or a database instance created with a preconfigured Oracle Management Repository (Management Repository) using the database templates offered by Oracle.To access the Enterprise Manager certification matrix, follow the steps outlined in Appendix E. For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Appendix D. The database can be on a local or remote host, and if it is on a remote host, it must be monitored by Oracle Management Agent. However, Oracle Real Application Clusters (Oracle RAC) databases must only be on a shared disk. |
Runs the following configuration assistants to configure the installed or upgraded components:
Plugins Prerequisites Check Configuration Assistant
Repository Configuration Assistant
Note: If you use a database instance that was created with a preconfigured Management Repository using the database templates offered by Oracle, then Repository Out-of-Box Configuration Assistant is run instead of Repository Configuration Assistant. |
MDS Schema Configuration Assistant
OMS Configuration Assistant
Plugins Deployment and Configuration Assistant
Start Oracle Management Service Configuration Assistant
Oracle Configuration Manager for OMS Configuration Assistant
Agent Configuration Assistant
This section describes the following:
Overview of the Directory Structure for Enterprise Manager Installation
Overview of the Directory Structure for Management Agent Installation
By default, the following are the contents of the Middleware home for this type of installation:
<middleware_home> |_____wlserver_10.3 |_____jdk16 |_____oms |_____plugins |_____gc_inst |_____Oracle_WT |_____oracle_common |_____utils |_____logs |_____modules |_____user_projects |_____ocm.rsp |_____registry.dat |_____domain-registry.xml |_____registry.xml
By default, the following are the contents of the agent base directory for this type of installation:
<agent_base_directory> |_____core |_____12.1.0.2.0 |_____plugins |_____agent_inst |_____sbin |_____plugins.txt |_____plugins.txt.status |_____agentimage.properties
Before you begin, keep these points in mind:
You must ensure that you have the latest Enterprise Manager Cloud Control software.
To download the latest software, access the following URL:
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
For information about downloading the latest software, refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
Ensure that there are no white spaces in the name of the directory where you download and run the Enterprise Manager Cloud Control software from. For example, do not download and run the software from a directory titled EM Software
because there is a white space between the two words of the directory name.
You can install Enterprise Manager Cloud Control 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.
Oracle Management Service 12c Release 2 (12.1.0.2) can communicate only with Oracle Management Agent 12c Release 2 (12.1.0.2) and Oracle Management Agent 12c Release 1 (12.1.0.1), and not with any earlier release of the Management Agent.
And Oracle Management Service 12c Release 1 (12.1.0.1) can communicate only with Oracle Management Agent 12c Release 1 (12.1.0.1), and not with any earlier release or higher release of the Management Agent.
Do not install on a symlink. If you do, then you will not be able to clone this OMS later.
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 the following Oracle Web site URL:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
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 procure the Oracle WebLogic Server 11g Release 1 (10.3.5) software and install it following the instructions outlined in the Oracle?? Fusion Middleware Installation Guide for Oracle WebLogic Server. Ensure that it is a default installation. 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.
If you are installing Enterprise Manager Cloud Control in a Middleware home that is on an NFS-mounted drive, then ensure that you maintain the lock file in a local file system and not in that NFS-mounted location. To do so, after you install, modify the lock file location in the httpd.conf
file to map to a location on a local file system. For instructions, refer to After You Install.
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.
You can optionally use the database templates offered by Oracle to create a database instance with a preconfigured Management Repository. To do so, refer to Appendix D. You can use such a database instance for simple as well as advanced installation.
However, note that the database templates are essentially designed for simple installation, although they can be used for advanced installation. Therefore, while performing an advanced installation (possibly with small, medium, or large deployment size selection), when you provide the details of such a database, you will be prompted that the database parameters need to be modified to suit the deployment size you selected. You can confirm the message to proceed further. The installation wizard will automatically set the database parameters to the required values.
If you want to optionally follow the configuration guidelines for deploying the Management Repository so that your management data is secure, reliable, and always available, refer to the Oracle Enterprise Manager Cloud Control Administrator's Guide.
In addition to the mandatory plug-ins, 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.
Oracle offers bug fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for bug fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:
http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf
When determining supportability and certification combinations for an Enterprise Manager Cloud Control installation, you must consider Enterprise Manager Cloud Control's framework components as well as the targets monitored by Enterprise Manager Cloud Control. Oracle recommends keeping your Cloud Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license.
You can find the OMS and Management Agent entries in the /etc/oragchomelist
file for all UNIX platforms except HPUNIX, HPia64, Solaris Sparc.
On HPUNIX, HPia64, Solaris Sparc platforms, the entries are present in /var/opt/oracle/oragchomelist
.
As a prerequisite, you must have an existing Oracle Database to configure the Management Repository. This database can also have the Automatic Memory Management (AMM) feature enabled.
Table 6-2 lists the prerequisites you must meet before installing Enterprise Manager Cloud Control.
Table 6-2 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 the Enterprise Manager certification matrix, follow the steps outlined in Appendix E. For information about platforms receiving future support, refer to My Oracle Support note 793512.1. 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 |