Novell IDENTITY MANAGER 3.6.1, Руководство по установке

Страница: 30 / 104

30 Identity Manager 3.6.1 Installation Guide
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
There are many variables that affect the performance of the server. The standard recommendation is
that you have no more than ten drivers running on a Metadirectory server. However, if you are
synchronizing millions of objects with each driver, you might not be able to run ten drivers on a
server. On the other hand, if you are synchronizing 100 objects per driver, you can probably run
more than ten drivers on one server.
Setting up the Identity Manager solution in a lab environment gives you the opportunity to test how
the servers will perform. You can use the health monitoring tools in iManager to obtain a baseline
and then be able to make the best decisions for your environment. For more information about the
health monitoring tools, see “
Monitoring Driver Health ” in the Identity Manager 3.6.1 Common
Driver Administration Guide .
For considerations for each driver, see the Identity Manager Drivers documentation Web site (http://
www.novell.com/documentation/idm36drivers/index.html) . Driver-specific information is provided
in each driver guide.
3.3 eDirectory Guidelines
eDirectory is the Identity Vault that stores the objects that are synchronized through the Identity
Manager solution. The follow sections contain guidelines that help you plan your deployment of
eDirectory.
Š
Section 3.3.1, “Identity Manager Objects in eDirectory,” on page 30
Š
Section 3.3.2, “Replicating the Objects that Identity Manager Needs on the Server,” on page 31
Š
Section 3.3.3, “Using Scope Filtering to Manage Users on Different Servers,” on page 32
3.3.1 Identity Manager Objects in eDirectory
The following list indicates the major Identity Manager objects that are stored in eDirectory and
how they relate to each other. No objects are created during the installation of Identity Manager. The
Identity Manager objects are created during the configuration of the Identity Manager solution.
Š
Driver Set: A driver set is a container that holds Identity Manager drivers and library objects.
Only one driver set can be active on a server at a time. However, more than one server might be
associated to one driver set. Also, a driver can be associated with more than one server at a
time. However, the driver should only be running on one server at a time. The driver should be
in a disabled state on the other servers. Any server that is associated with a driver set must have
the Metadirectory engine installed on it.
Š
Library: The Library object is a repository of commonly used policies that can be referenced
from multiple locations. The library is stored in the driver set. You can place a policy in the
library that every driver in the driver set can reference.
Š
Driver: A driver provides the connection between an application and the Identity Vault. The
driver is the connector that enables data synchronization and sharing between systems. The
driver is stored in the driver set.
Š
Job: The purpose of a job is to complete a task that occurs many times. For example, a job can
configure a system to disable an account on a specific day, or to initiate a workflow to request
an extension of a person’s access to a corporate resource. The job is stored in the driver set.