PK
j?oa, mimetypeapplication/epub+zipPK j? iTunesMetadata.plist
Illustration firewall_agent.gif shows a diagram of the Management Agent and the Management Service. A line representing the firewall appears between the Management Agent and the Management Service.
Two additional lines represent data being uploaded to the Management Service and the Management Service contacting the Management Agent, respectively. Text in the diagram explains how you need to:
Configure the Management Agent to use a proxy server for uploads to the Management Service
Open the Management Agent port (usually 1830) in the firewall so the Management Service can communicate with the Management Agent.
The illustration shows a screen capture of a typical Enterprise Manager chart. A callout in the lower right corner of the illustration identifies the icon you can click to display a textual representation of the data in the chart. This icon appears next to all charts when textual descriptions are enabled.
PK5N PK j? OEBPS/img_text/ports_new.htmQfirewall port requirements
PK"U, PK j? OEBPS/img_text/firewall_oms.htmrIllustration firewall_oms.gif shows a diagram of the Management Agent and the Oracle Management Service. A line representing the firewall appears between them. The diagram includes text that explains how you must:
Configure the Management Service to use a proxy server for connections to the Management Agent
Open the upload URL port in the firewall so that data can be uploaded from the Management Agent to the Management Service.
This chapter describes how you can install Oracle Management Agent (Management Agent) in silent mode. In particular, this section covers the following:
Installing a Management Agent in silent mode is only an alternative to installing it using the Add Host Target Wizard. While the Add Host Target Wizard requires you to use its GUI-rich interview screens for providing all the installation details, the silent mode requires you to use a response file for providing the installation details and a deployment script (agentDeploy.sh
) for silently installing the Management Agent using the information supplied in the response file.
The response file and the deployment script are available as part of the Management Agent software. Instead of creating a response file, you can also choose to pass the values as separate arguments while invoking the deployment script.
Installing in silent mode is best suited when you want to install an additional Management Agent on a destination host, from the destination host itself, and without using the Add Host Target Wizard in the Enterprise Manager Cloud Control console.
Once the installation is complete, you will see the following default contents in the installation base directory:
<installation_base_directory> |_____core |_____12.1.0.1.0 |_____plugins |_____plugins.txt |_____plugins.txt.status |_____agent_inst |_____sbin |_____agentimage.properties
Before you begin installing a Management Agent, keep these points in mind:
Before installing the Management Agent, you must procure the Management Agent software from the OMS host and transfer it to the destination host for installation. The Management Agent software you procure contains the core binaries required for installation, the response file to be edited and passed, and the agentDeploy.sh
script.
By default, the OMS host contains the Management Agent software for the platform on which the OMS is running. For example, if the OMS host is Linux x86, then the Management Agent software available by default is only for Linux x86.
If you want to install the Management Agent on a platform that is different from the one on which the OMS is running, then download the software for the desired platform using the Self Update console.
For information on Self Update and how you can use it to download the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
You can run the agentDeploy.sh
script only from the destination host.
You can install only on one host at a time using the agentDeploy.sh
script, therefore use this approach when you want to install only on a few hosts.
You can provide the installation details either in a response file or as values for individual arguments that can be passed while invoking the agentDeploy.sh
script. However, Oracle recommends that you create a response file and capture the information there.
You can install even if the OMS is unreachable. In this case, you must pass the special option -forceConfigure
while invoking the agentDeploy.sh
script. For more information, see Table 5-3.
Typically, you will use this option only when you are installing the Management Agent before installing the OMS, and you know for sure that you will install the OMS later on the host and port mentioned in the response file.
However, do not pass the option -forceConfigure
when installing the Management Agent using software-only method as described in Chapter 9.
You cannot run any preinstallation or postinstallation scripts as part of the installation process. Of course, you can run manually them after the installation ends.
By default, the agentDeploy.sh
script 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 not install two Management Agents on the same host. This disrupts the communication with the OMS.
Before installing the Management Agent, ensure that you meet the following prerequisites.
Table 5-1 Prerequisites for Installing Oracle Management Agent in Silent Mode
Requirement | Description |
---|---|
Hardware Requirements |
Ensure that you meet the hard disk space and physical memory requirements. For more information, see the chapter on hardware requirements in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
Software Requirements |
(For Microsoft Windows) Ensure that you have installed Cygwin on the destination host. For more information, see the chapter on installing Cygwin in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
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:
| |
Ensure that you install all the operating system-specific packages. For more information, see the chapter on package requirements in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. | |
Ensure that the destination host where you want to install the Management Agent has the appropriate users and operating system groups created. For more information, see the chapter on creating operating system groups and users in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. | |
Ensure that the
| |
(Only for UNIX) Ensure that you have SUDO privileges to invoke | |
(For Microsoft Windows) On the destination host, ensure that the cygwin software location appears before other software locations in the | |
Path Validation Requirements |
Validate the path to all command locations. For more information, see the appendix on validating command locations in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. |
Port Requirements |
Ensure that the default ports described in What Default Ports Are Used? are free. |
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 | |
Installation Base Directory Requirements |
Ensure that the installation base directory is empty. Ensure that the installing user owns the installation base directory. Ensure that the installer user or the root user owns all the parent directories. Ensure that the root user owns the root directory. For example, if the installation base directory is |
Agent Instance Home Requirements |
Ensure that the agent instance home location you specify in the response file is empty. |
| |
Installing User Requirements |
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group. Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory. For example, if the inventory owner is abc and the user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory. |
| |
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:
|
(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: |
To install a Management Agent in silent mode, follow these steps:
On the OMS host, from the OMS home, log in to the EMCLI client. EMCLI Client is available by default with every OMS installation, so you need not install the client separately.
$<OMS_HOME>/bin/emcli login -username=sysman -password=<password>
For example,
$<OMS_HOME>/bin/emcli login -username=sysman -password=2benot2be
Note: The user name must always besysman . Do not enter any other user name. |
$<OMS_HOME>/bin/emcli sync
Identify the platforms for which the Management Agent software is available on the OMS host:
$<OMS_HOME>/bin/emcli get_supported_platforms
This command lists all the platforms for which the Management Agent software is available on the OMS host. Example 5-1 shows a sample output of the command.
Example 5-1 Output Showing Software Availability for Different Platforms
--------------------------------------------------- Version = 12.1.0.1.0 Platform Name = Linux x86 --------------------------------------------------- Version = 12.1.0.1.0 Platform Name = Oracle Solaris on x86-64 (64-bit) --------------------------------------------------- Version = 12.1.0.1.0 Platform Name = HP-UX PA-RISC (64-bit) ---------------------------------------------------
If the output lists the platform on which you want to install the Management Agent, then proceed to the next step. Otherwise, download the software for the required platform using the Self Update console.
For information on Self Update and how you can use it to download the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Download the Management Agent software from Oracle Software Library to a temporary directory on the OMS host:
$<OMS_HOME>/bin/emcli get_agentimage -destination=<download_directory> -platform="<platform>" -version=<version>
For example,
./emcli get_agentimage -destination=/tmp -platform="Linux x86" -version=12.1.0.1.0
Note: In the command, note the following:
|
The command downloads the core Management Agent software to the destination directory you entered. For example, for Linux x86, you will see the file 12.1.0.1.0_AgentCore_46.zip
. For information on the contents of this core software, see Understanding the Contents of the Downloaded Management Agent Software.
Transfer the downloaded ZIP file to a temporary directory (/tmp
) on the destination host where you want to install the Management Agent. You can use any FTP software to transfer the file. For example, FileZilla.
On the destination host, extract the contents of the ZIP file using the unzip utility:
unzip /tmp/<software_zip_file> -d <software_extract_location>
For example,
unzip /tmp/12.1.0.1.0_AgentCore_46.zip -d /tmp/agtImg
Edit the response file agent.rsp
as described in Table 5-2.
<software_extract_location>/agent.rsp
Invoke the deployment script and pass the response file:
<software_extract_location>/agentDeploy.sh AGENT_BASE_DIR=<absolute_path_to_agentbasedir> RESPONSE_FILE=<absolute_path_to_responsefile>
Note:
|
Run the root scripts when you are prompted. For more information, see After You Install.
Table 5-2 describes the various parameters you must include in the response file.
Table 5-2 Creating a Response File for Installing Oracle Management Agent in Silent Mode
Parameter | Description |
---|---|
OMS_HOST |
Enter the OMS host name. For example, |
EM_UPLOAD_PORT |
Enter the upload port (HTTP or HTTPS) for communicating with the OMS. For example, |
AGENT_REGISTRATION_PASSWORD |
Enter a password for registering new Management Agents that join the Enterprise Manager system. By default, the communication between the OMS and the Management Agents is secured, and any new Management Agents that join the Enterprise Manager system must be authenticated before they become part of the system. The password you enter here will be used for authenticating those new Management Agents. For example, |
AGENT_INSTANCE_HOME |
Enter a directory location on the destination host where all Management Agent-related configuration files can be stored. For this parameter, you can do one of the following:
|
AGENT_PORT |
Enter a free port on which the Management Agent process should be started. The same port is used for both HTTP and HTTPS. For example, If you do not enter any value, then either 3872 or any free port between 1830 and 1849 is honored. |
b_startAgent |
Enter For example, |
ORACLE_HOSTNAME |
Enter the fully qualified domain name of the host where you want to install the agent. For example, |
s_agentHomeName |
Enter the name of the Oracle home you want to see created for the Management Agent. For example, |
s_agentServiceName |
Enter the customized Management Agent service name. If you leave this field blank, then it gets defaulted to Oracle+<oracle_home_name>+Agent. |
Table 5-3 lists the options supported by the agentDeploy.sh
script.
Table 5-3 Understanding the Options Supported by agentDeploy.sh Script
Options | Description |
---|---|
-prereqOnly |
Runs only the prerequisite checks. Does NOT actually install the Management Agent. This option is useful when you want to verify whether your environment meets all the prerequisites for a successful Management Agent installation. |
-ignorePrereqs |
Skips running the prerequisite checks. Use this when you have already used the |
-invPtrLoc |
Considers the Oracle Inventory directory for storing inventory details. Enter the absolute path to the Important: If you enter a value for this option, do NOT use the |
INVENTORY_LOCATION |
Considers the Oracle Inventory directory for storing inventory details. Enter the absolute path to the Important:
|
-help |
Displays command line help and describes the usage of the deployment script. |
-debug |
Logs more debug messages useful for debugging and resolving errors. |
-ignoreUnzip |
Skips extracting the software binaries of the Management Agent software. Use this when you do not want to copy the binaries again, but only want to configure the available binaries. |
-softwareOnly |
Installs only the software binaries, and does NOT configure the installation. Use this when you want to perform a software-only installation of the Management Agent. For more information, see Chapter 9. Note: This option does not apply if you are cloning using a ZIP file. |
-configOnly |
Configures the software binaries, and does not install any software binaries. Use this when you have performed a software-only installation using the Note: This option does not apply if you are cloning using a ZIP file. |
-forceConfigure |
Forcefully configures the Management Agent even when the OMS is unreachable. Use this option only when you are installing the Management Agent before installing the OMS, and when you know for sure that you will install the OMS later on the same host and port mentioned for the parameters If you pass this option, then do not pass -configOnly, -softwareOnly, and -prereqOnly. Note: When you pass this option, the Management Agent is configured to use HTTP (non-secure) communication. To establish a secure HTTPS communication between the Management Agent and the OMS, you must manually secure the Management Agent after the OMS is available. |
Table 5-4 describes the contents of the core Management Agent software you download before installing the Management Agent.
Table 5-4 Contents of the Downloaded Management Agent Software
Files | Description |
---|---|
12.1.0.1.0_PluginsOneoffs_<platform id>.zip |
Plug-in ZIP file containing all the discovering plug-ins, which were installed with the OMS, Oracle Home discovery plug-in, and Oracle Home monitoring plug-in. |
agentcoreimage.zip |
Archived ZIP file containing the core agent bits and agent set-uid binaries. |
agentDeploy.sh |
Shell script used for deploying the Management Agent. |
unzip |
Utility used for unarchiving the ZIP files. |
Agentimage.properties |
Properties file used for getting the version, platform ID, and so on. |
agent.rsp |
Response file to be edited and passed for installing the Management Agent. |
After you install the Management Agent, follow these steps:
(Only for UNIX Operating Systems) When prompted, manually run the following scripts as a root user. If you do not have SUDO 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 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 to change to a root user. For example, run the following command:
|
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:
$<INSTANCE_HOME>/bin/emctl status agent
Note: If the status of the Management Agent is down for some reason, then manually start the Management Agent by running the following command from its Oracle home:
|
Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully:
$<INSTANCE_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
If you find the sentence, resolve the issue by running the AgentPluginDeploy.pl
script from the Management Agent home. In this command, all <AGENT_HOME>
references refer to the Management Agent home.
$<AGENT_HOME>/perl/bin/perl <AGENT_HOME>/bin/AgentPluginDeploy.pl -oracleHome <AGENT_HOME> -agentDir <AGENT_BASE_DIR> -pluginIdsInfoFile <AGENT_BASE_DIR>/plugins.txt -action configure -emStateDir <AGENT_INSTANCE_HOME>
For example,
/home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0/perl/bin/perl /home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome /home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0 -agentDir /home/john/programs/oracle/EMGC_Main_20SH/agent -pluginIdsInfoFile /home/john/programs/oracle/EMGC_Main_20SH/agent/core/12.1.0.1.0/sysman/install/plugins.txt -action configure -emStateDir /home/john/programs/oracle/EMGC_Main_20SH/agent/agent_inst
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.
This chapter introduces you to Enterprise Manager advanced configuration and provides basic information about your Enterprise Manager installation. It describes the directory structure and how to make Enterprise Manager accessible to all your users.
After you review this chapter, you can move on to the other advanced configuration tasks described in this manual.
Specifically, this chapter includes the following topics:
Enterprise Manager is designed to install easily with a set of standard configuration settings so you can get up and running with the software quickly.
However, Oracle realizes that hardware and software management requirements vary dramatically among business enterprises. As a result, Enterprise Manager can be reconfigured after installation so you can:
Implement Enterprise Manager security and firewall features.
Enable End-User Performance Monitoring for your Web applications.
Reconfigure Enterprise Manager components when you need to modify the topology of your network environment.
Maintain and troubleshoot the Enterprise Manager components as your business grows.
Before you perform maintenance and advanced configuration tasks, you must be familiar with the directories and files that are copied to disk when you install Enterprise Manager. Understanding where specific files are located can help you if you need to troubleshoot installation or configuration problems.
When installing Enterprise Manager, if you select a location that does not contain WebLogic Server, then JDK will be installed in the jdk16
directory before installation of WebLogic Server.
Use the following sections to become familiar with the directories that are created on your disk when you install Enterprise Manager:
Understanding the Enterprise Manager Directories Installed with Management Service
Understanding the Enterprise Manager Directories Installed with Management Agent
Identifying the Agent Instance Home When Using the emctl Command
When you install Oracle Enterprise Manager Cloud Control 12c, you install the Oracle Management Service. With the Oracle Management Service, you install the following Oracle home directories:
Oracle Management Service home directory
Middleware WebTier home directory
Middleware Common home directory
Oracle Management Service Instance home directory
Oracle Management Agent home directory
Oracle Management Service Plugins home
Oracle Management Agent Plugins home
The Oracle Management Service is a J2EE application that is installed and deployed using the Oracle WebLogic Server.
The installation procedure installs the Enterprise Manager components within the Cloud Control Home, including the Oracle Management Service. For more details about the OMS directories, see About the Oracle Management Service Home Directory.
Information about the directories that are specific to the Fusion Middleware installation can be found in the Fusion Middleware documentation.
In addition to the Oracle Management Service home directory, the installation procedure installs the Oracle Management Agent that is used to gather management data and perform administration tasks for the targets on the Oracle Management Service host.
The Oracle Management Agent is installed in a separate Oracle home directory which is at the same level as the Fusion Middleware home directory. For more details, see Understanding the Enterprise Manager Directories Installed with Management Agent.
Figure 10-1 shows some of the important directories you should be familiar with in a typical Cloud Control installation. You can use this information as you begin to maintain, troubleshoot, and configure the Oracle Management Service installation.
Table 10-1 describes the directories installed with Enterprise Manager.
Table 10-1 Directories Installed with Enterprise Manager
Directory | Description |
---|---|
wlserver_10.3, logs, utils, modules |
These directories contain Fusion Middleware files. |
jdk16 |
This directory contains JDK configuration files. |
oms |
This directory contains OMS configuration files. For more information, see Understanding the Enterprise Manager Directories Installed with Management Service. |
plugins |
This directory contains metadata plug-ins configuration files installed on the OMS. |
agent |
This directory contains agent configuration files. For more details, see Understanding the Enterprise Manager Directories Installed with Management Agent. |
gc_inst |
The OMS instance home directory. For more details, see Understanding the Enterprise Manager Directories Installed with Management Service. |
oracle_WT |
This directory contains Oracle WebTier configuration files. |
oracle_common |
This directory contains common files used by OMS, Oracle WebTier, and WebLogic Server directories. |
Table 10-2 describes in detail the Oracle Management Service directories installed with Oracle Management Service. In the table, ORACLE_HOME
refers to the Oracle Management Service home directory in which the Oracle Management Service is installed and deployed.
Table 10-2 Important Directories in the Management Service Oracle Home
Directory | Description |
---|---|
The | |
|
This directory contains configuration files for OMS home. The default |
The | |
|
This directory contains log files for the Oracle Management Service. |
|
The |
|
This directory contains schema log files. The repository log files are under |
The Oracle Management Agent is installed automatically when you install Oracle Management Service. This local instance of the Oracle Management Agent gathers management information about the targets on the Oracle Management Service host. You can then manage those targets, such as the host itself, from the Cloud Control Console.
You can install additional Oracle Management Agents using different installation methods. This enables you to install the Oracle Management Agent on the hosts throughout your enterprise. The Oracle Management Agent can then gather management data about the targets on each host so those targets can be managed from the Cloud Control Console.
Specifically, the Oracle Management Agent files are installed into the same directory structure shown in the agent
directory when you install the Oracle Management Service (Figure 10-1).
The agent directory structure, when you install a standalone agent or install the OMS is the same. The AGENT_BASE_DIR
is the directory where agent is installed and contains the following main directories:
AGENT_HOME
AGENT_INSTANCE_HOME
SBIN_HOME
PLUGIN_HOME
The directory that contains the files required to run the Oracle Management Agent is referred to as the AGENT_INSTANCE_HOME
directory. For example, to start or stop an Oracle Management Agent, you use the emctl
command located in the bin
directory of the AGENT_INSTANCE_HOME
. Similarly, to configure files for the Oracle Management Agent, you modify the configuration files in the sysman/config
directory of the AGENT_INSTANCE_HOME
. See Figure 10-2 for the agent directory structure.
Table 10-3 describes some of the important agent directories.
Table 10-3 Important Directories in the Oracle Management Home
When you install Cloud Control, the resulting directory structure can often include multiple subdirectories with the same name. For example, you can have a bin
directory within the agent_instance_home directory. Use the emctl
command within the agent_instance_home/bin
directory to control the Oracle Management Agent.
In addition, you can have a bin
directory within the Oracle Management Service Oracle home. Use the emctl
command in this directory to control the Oracle Management Service.
To quickly identify the Agent Instance home that is controlled by the files in a particular bin
directory, use the following command:
$PROMPT> emctl getemhome
This command displays the path to the current Agent Instance home that will be affected by commands executed by this instance of the emctl
command.
As part of the effort to make Oracle products, services, and supporting documentation accessible and usable to the disabled community, Enterprise Manager offers several features that make management data available to users of assistive technology. Enterprise Manager provides the following accessibility features:
Support for Screen Reader
Support for High Contrast
Support for Large Fonts
To enable Screen Reader support, you must modify the following configuration settings:
Enable Accessibility Mode in My Preferences.
Set uix-config.xml flag.
Set web.xml flag.
To enable screen reader mode, do the following:
On the Cloud Control home page, from the Setup menu, select My Preferences and then select Accessibility.
In the Accessibility Preference page, select I use a screen reader. Click Apply.
ADF accessibility mode is a session based setting which takes place immediately and does not require you to restart the Enterprise Manager Management Service.
For ADF pages, you will see an Accessibility Preferences dialog after logging into Cloud Control for the first time. The settings in this dialog are the same as those in the Accessibility Preference page mentioned above.
To enable screen reader mode for UIX pages, do the following:
Locate the uix-config.xml
configuration file.
To locate the uix-config.xml
file in a Cloud Control installation, change directory to the following location in the Oracle Management Service home:
./oms11g/sysman/archives/emgc/deployments/EMGC_DOMAIN/emgc.ear/em.war/WEB-INF/uix-config.xml
Open the uix-config.xml
file using a text editor and set the following entry:
<!-- An alternate configuration that disables accessibility features --> <default-configuration> <accessibility-mode>screenReader</accessibility-mode> </default-configuration>
Save and close the file.
Restart the Oracle Management Service.
Note: UIX accessibility mode is a product-wide setting. You will have to restart the Enterprise Manager Management Service for this setting to take effect. |
To configure web.xml file, follow these steps:
Locate the web.xml
configuration file.
To locate the web.xml
file in a Cloud Control installation, change directory to the following location in the Oracle Management Service home:
./oms11g/sysman/archives/emgc/deployments/EMGC_DOMAIN/emgc.ear/em.war/WEB-INF/web.xml
Open the web.xml
file with your favorite text editor and locate the following six lines of the file:
<!-- Uncomment this to enable textual chart descriptions <context-param> <param-name>enableChartDescription</param-name> <param-value>true</param-value> </context-param> -->
Remove comments from this section by deleting the first line and the last line of this section so that the section consists of only these 4 lines:
<context-param> <param-name>enableChartDescription</param-name> <param-value>true</param-value> </context-param>
Save and exit the file.
Restart the Oracle Management Service.
Throughout Enterprise Manager, charts are used to display performance data. For most users, these charts provide a valuable graphical view of the data that can reveal trends and help identify minimum and maximum values for performance metrics.
However, charts do not convey information in a manner that can be read by a screen reader. To remedy this problem, you can configure Enterprise Manager to provide a complete textual representation of each performance chart. By default, support for the textual representation of charts is disabled. When textual description for charts is enabled, Enterprise Manager displays a small icon for each chart that can be used as a drill-down link to the textual representation.
To verify whether Screen Reader support has been enabled for ADF pages, follow these steps:
On the Cloud Control home page, click Help and then select About Enterprise Manager.
In the About Enterprise Manager dialog box, ensure that Accessibility Preference - Screen Reader Support is set to Enabled.
If Accessibility Preference - Screen Reader Support is set to Disabled, follow the steps listed in Enabling Enterprise Manager Accessibility Features.
To verify whether Screen Reader support has been enabled for UIX pages, follow these steps:
On the Cloud Control home page, from the Enterprise menu, select Reports and then select Information Publisher Reports.
In the Information Publisher Reports page, click Hardware Summary. The Hardware Summary page is displayed. If accessibility setting has been enabled, you will see the icon shown in Figure 10-3: