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

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

Creating a Project Plan 23
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
The development of this model begins by answering questions such as the following:
Š
What types of objects (users, groups, etc.) are being moved?
Š
Which events are of interest?
Š
Which attributes need to be synchronized?
Š
What data is stored throughout your business for the various types of objects being managed?
Š
Is the synchronization one-way or two-way?
Š
Which system is the authoritative source for which attributes?
It is also important to consider the interrelationships of different values between systems.
For example, an employee status field in PeopleSoft might have three set values: employee,
contractor, and intern. However, the Active Directory system might have only two values:
permanent and temporary. In this situation, the relationship between the “contractor” status in
PeopleSoft and the “permanent” and “temporary” values in Active Directory needs to be
determined.
The focus of this work should be to understand each directory system, how they relate to each other,
and what objects and attributes need to be synchronized across the systems. After the design is
complete, the next step is to create a proof of concept. Proceed to
Section 2.3, “Proof of Concept,”
on page 23 .
2.3 Proof of Concept
The outcome of this activity is to have a sample implementation in a lab environment that reflects
your company’s business policy and data flow. It is based on the design of the data model developed
during the requirement analysis and design and is a final step before the production pilot.
NOTE: This step is often beneficial in gaining management support and funding for a final
implementation effort.
Chapter 3, “Technical Guidelines,” on page 27 contains information that can help you validate your
proof of concept. It contains technical guidelines to help make your Identity Manager deployment
successful.
As you create the proof of concept, you need to also create a plan to validate the data that you have
in your systems. This step helps you make sure that conflicts don’t occur between systems. Proceed
to
Section 2.4, “Data Validation and Preparation,” on page 23 to make sure these conflicts do not
occur.
2.4 Data Validation and Preparation
The data in production systems can be of varying quality and consistency and therefore might
introduce inconsistencies when synchronizing systems. This phase presents an obvious point of
separation between the resources implementation team and the business units or groups who “own”
or manage the data in the systems to be integrated. At times, the associated risk and cost factors
might not belong in a provisioning project.