Monitoring the Hosting Platform - Expert Consolidation in Oracle Database 12c - page 293

Both tests should succeed. If not, you need to troubleshoot any issues as there is little point in continuing
from this stage. You will notice that there are a couple of jobs Enterprise Manager creates for you that are pending
execution. The task of these jobs is to check for the latest information from My Oracle Support. To view these jobs you
navigate to Enterprise ➤ Job ➤ Activity. The Enterprise Menu is right beneath the Oracle logo on the top-left corner of
the screen. You need to perform an “Advanced Search” for “Target Type” Targetless to view the jobs.

Create a Software Library
The software library is a directory structure used by all the OMSs to store patches and other components. It has to be
set up in a way to allow every OMS to access it. Many components within Enterprise Manager will need a software
library configured, which is why it has to be set up. Navigate to Setup ➤ Provision and Patching ➤ Software Library.
When you first get there you will see no entry in the lists. For the software library to become functional, you need to
define at least one “Upload File Location”. This location should only be local to the OMS if you do not plan to extend
the Enterprise Manager infrastructure to more than just a single Management Service. Since that is rarely the case, you
should mount an NFS share to the same location on each OMS in the configuration before creating the first entity.
In the “Software Library: Administration” screen, ensure that you selected the “Upload File Locations” tab and “OMS
Shared Filesystem”. A click on the plus sign will bring up a pop-up menu allowing you to specify a name and location for
your new file system. Provide the settings and click on “OK” to continue. A job will be started in the background to finish
the creation of the software library. Oracle will initialize the library and after a little while makes it available to users.

Creating and Managing Enterprise Manager Accounts
Users in Cloud Control are referred to as administrators. The authentication and authorization system provides a
wealth of different methods to let users access the Enterprise Manager console. Users can be authenticated outside
of Enterprise Manager as well from a variety of other sources, including Microsoft's Active Directory. Covering all
of these authentication methods is not possible in this chapter, which is why the default so-called repository-based
authentication will be used as one way to identify users. With repository-based authentication every user provisioned
in the Enterprise Manager system will be created as a named user in the repository database. The advantage of this
approach is that every user password can be maintained with password profiles as any other database account. On the
downside EM administrators need to remember yet another username and password combination.

■ if you have a requirement for authenticating large numbers of users the integration of an existing lDap-based
service should be considered more seriously.

Note

In Enterprise Manager you can create two types of users: administrators and super administrators. Be careful
granting the super-administrator role to anyone because real damage can be done with it! The difference between
these two classes of users is their scope: the super administrator can create and manage any other administrator and
his objects in Cloud Control whereas the administrator is limited to his own objects and therefore more restricted.
As is the rule with the root account on UNIX systems, you should limit the use of the super administrator accounts to
global setup operations and configuration. You should definitely not use it on a routine basis. Also bear in mind that
for auditing purposes it is essential that you use named users rather than generic accounts: another good reason to
keep the SYSMAN password very safe.
The privilege system in Enterprise Manager 12c is very flexible, and is a real revelation after the rather strict
model in previous generations of the software. Generally speaking the system differentiates between:

• Grants on specific managed targets

• Grants applicable to all targets

• Grants on the Enterprise Manager system itself, so-called resource privileges