The installation of YaST is only for Oracle Linux 6.0 or below. For Oracle Linux 7.0 operating system, no other installation is needed.
Note: These required installations are only applicable to hosts running Oracle Linux, Red Hat Linux, and SUSE Linux Operating Systems (x86 and x64 architectures only).
To administer a host through Enterprise Manager, you need to install scripts. To determine which scripts you need to install for your host, follow these steps:
Note:The credential user must have access to the Agent installation.
YaST and EM wrapper scripts must be installed for agents running on earlier versions like Oracle Linux 5, Oracle Linux 6, and SuSE Enterprise Linux 9 and 10. The scripts can be downloaded from http://oss.oracle.com/projects/yast
YAST is an operating system setup and configuration tool that comes as a standard tool as part of SUSE Linux distribution. The Linux administration feature uses YAST to run scripts. For Oracle Linux and RHEL4 (Red Hat), YAST rpm contains the Enterprise Manager scripts. Therefore installing YAST rpm from the following location will also install the Enterprise Manager scripts:
For SUSE, you need to download the Enterprise Manager scripts and additional remote access module from the following location:
Before you install YAST, you need to determine the following:
Determine the version of Linux on your machine. For example, the uname -a command lists the RHEL (RedHat), Oracle Linux, or SUSE versions, and the bits of the machine, for example 32-bit versus 64-bit. YAST is supported on RHEL4 and later and on Oracle Linux.
Verify that you have root privileges.
To install YAST, perform the following steps:
http://oss.oracle.com/projects/yast. The Project: Yast page appears.
For a demonstration of how to install YAST, see the YouTube video Oracle Enterprise Manager 12c: Install YAST located at
Credentials are needed to manage target instances.
To set up various credentials, select the Setup menu (located at the top-right of the UI page), then select Security. The following options are available:
Named Credentials are used for the Management Agent install. Named credentials explicitly grant you privileges on the host.
If a target has preferred credentials set, applications that log in to that target will automatically use the preferred credentials. Using preferred credentials simplifies access to managed targets.
Default credentials can be set for each target type. Default credentials are used for any targets that do not have preferred credentials explicitly set.
Privilege Delegation Setting enables you to configure the Management Agent to use Sudo or PowerBroker so you can run privileged scripts.
See the online help for additional information.
As you begin monitoring a host, you need to know what metrics you are allowed to monitor. You may also find that you need to set up monitoring credentials for target instances.
This section explains the required steps for these tasks.
The Monitoring Configuration page reports what monitoring you can do on the selected host.
To access the Monitoring Configuration page, perform the following steps:
In addition, the Monitoring status is provided. For example, Oracle has automatically enabled monitoring for this target's availability and performance, so no further monitoring configuration is necessary.
Monitoring Credentials allow you to monitor and access various target functionality. You can manage the already existing credentials for various target types using monitoring credentials.
To edit Monitoring Credentials, perform the following steps:
By default, a host has the following credential sets defined:
Host Credentials For Real-time Configuration Change Monitoring
Host SNMP Credentials
Host WBEM Credentials
Privileged Host Monitoring Credentials
You can add credential sets using the emcli create_credential_set verb with the -monitoring option.