Installation guide

Technical Guidelines 25
3.1.2 Designer Guidelines
Designer is a thick client that is installed on a workstation. Designer is used to design, test, document,
and then deploy your Identity Manager solution. Using Designer throughout the planning phase
helps you capture information in one place. It also helps you see issues you might not be aware of as
you look at all of the components of the solution together.
There are no major considerations for using Designer, unless you have multiple people working on
the same project. Designer allows for version control of the project. For more information, see
“Version Control” in the Designer 4.0.1 for Identity Manager 4.0.1 Administration Guide.
3.1.3 iManager Guidelines
iManager is a Web application that is the administration tool for Identity Manager. When you install
Identity Manager, the installation expects that you already have an iManager server installed in your
eDirectory tree.
If you have more than 10 administrators constantly working in iManager at one time, you should
have a server that hosts only iManager. Figure 3-2 represents this configuration of your Identity
Manager solution. If you have only one administrator, you can run iManager on your Metadirectory
server without complications.
3.1.4 Role Mapping Administrator Guidelines
The Role Mapping Administrator is a Web application that discovers authorizations and permissions
that can be granted within your major IT systems. It allows business analysts, not just IT
administrators, to define and maintain which authorizations are associated with which business
roles.
There are no major considerations for using the Role Mapping Administrator. You can run the Role
Mapping Administrator on a separate server as show in Figure 3-2 or you can run it on the
Metadirectory server. For more information, see the Identity Manager Role Mapping Administrator 4.0.1
Installation and Configuration Guide.
3.2 Metadirectory Server Guidelines
You can have one or more Metadirectory servers in your Identity Manager solution, depending on
the server workload. The Metadirectory server requires that eDirectory be installed as shown in
Figure 3-3. You can add a Remote Loader server, not represented in the figure, to help with the
workload or configuration of your environment.
Drivers must run on the same server as the connected application. For example, to configure the
Active Directory driver, the server in Figure 3-3 must be a member server or a domain controller. If
you do not want to install eDirectory and Identity Manager on a member server or domain controller,
then you can install the Remote Loader on a member server or a domain controller. The Remote
Loader sends all of the events from Active Directory to the Metadirectory server. The Remote Loader
receives any information from the Metadirectory server and passes that to the connected application.
The Remote Loader provides added flexibility for your Identity Manager solution. For more
information, see the Identity Manager 4.0.1 Remote Loader Guide.