Installation guide

18 Identity Manager 4.0.1 Framework Installation Guide
 Appropriate Identity Manager architecture for the solution.
 Details for additional system connection requirements.
 Strategies for data validation and record matching.
 Directory design to support the Identity Manager infrastructure.
The following tasks should be completed during the requirements and design assessment:
 “Defining the Business Requirements” on page 18
 “Analyzing Your Business Processes” on page 19
 “Designing an Enterprise Data Model” on page 20
2.2.1 Defining the Business Requirements
In the discovery phase, you gathered your organization’s business processes and the business
requirements that define these business processes. Create a list of these business requirements and
then start mapping these processes in Designer by completing the following tasks:
 Create a list of the business requirements and determine which systems are affected by this
process. For example, a business requirement for terminating an employee might be that the
employee’s network and e-mail account access must be removed the same day the employee is
terminated. The e-mail system and the Identity Vault are affected by this termination process.
 Establish the process flows, process triggers, and data mapping relationships.
For example, if something is going to happen in a certain process, what other processes are
triggered?
 Map data flows between applications. Designer allows you to see this information. For more
information, see “Managing the Flow of Data” in the Designer 4.0.1 for Identity Manager 4.0.1
Administration Guide.
 Identify data transformations that need to take place from one format to another, such as 2/25/
2007 to 25 Feb 2007, and use Analyzer to change the data. For more information, see the Analyzer
4.0.1 for Identity Manager Administration Guide.
 Document the data dependencies that exist.
If a certain value is changed, it is important to know if there is a dependency on that value. If a
particular process is changed, it is important to know if there is a dependency on that process.
For example, selecting a “temporary” employee status value in a human resources system might
mean that the IT department needs to create a user object in eDirectory with restricted rights and
access to the network during certain hours.
 List the priorities.
Not every requirement, wish, or desire of every party can be immediately fulfilled. Priorities for
designing and deploying the provisioning system will help plan a road map.
It might be advantageous to divide the deployment into phases that enable implementation of a
portion of the deployment earlier and other portions of the deployment later, or use a phased
deployment that is based on groups of people within the organization.
 Define the prerequisites.
The prerequisites required for implementing a particular phase of the deployment should be
documented. This includes access to the connected systems that need to interface with Identity
Manager.
 Identify authoritative data sources.