Required for all installations
An OpenText Identity Manager Server installation comprises of the following components.
The OpenText Identity Manager Server executes tasks within OpenText Identity Manager. It comprises of Identity Vault, Identity Manager Engine, and OpenText Identity Manager drivers.
To support the OpenText Identity Manager Server operations, the installation program installs a supported version of Oracle Java Runtime Environment (JRE). To install the OpenText Identity Manager Server components, use the OpenText Identity Manager Engine installation option of the installation program.
When you install OpenText Identity Manager Engine, the installation process creates and configures a connection to Identity Vault. OpenText Identity Manager uses Identity Vault as the default repository of all identity data. Identity data includes current state of managed identities, including user account and organizational data.
The OpenText Identity Manager engine processes all data changes that occur in the Identity Vault or a connected application. The server on which the OpenText Identity Manager engine runs is referred to as the OpenText Identity Manager server.
The OpenText Identity Manager Server handles provisioning of users, and manages connected system accounts and groups through drivers. A driver is the software interface to a connected system.
OpenText Identity Manager Drivers run as part of the OpenText Identity Manager Server architecture. A driver acts as a gateway to a native endpoint type system technology. For example, computers running Active Directory Services can be managed only if the Active Directory driver is installed either on the OpenText Identity Manager server or the target application server with which the OpenText Identity Manager server can communicate. Drivers manage the objects that reside on the connected systems. Managed objects include accounts, groups, and optionally, endpoint-type specific objects.
A driver translates OpenText Identity Manager Engine actions into changes on the connected system, such as “Create a new email account on a Microsoft Exchange connected system.” Every driver that is configured in OpenText Identity Manager has an associated event cache file (TAO file). Events are cached in the cache file before a driver processes them. By default, the cache files are placed in Identity Vault’s DIB (Data Information Base) directory.
OpenText Identity Manager provides several in-built drivers (Java, native, .NET) to manage connections with different types of connected systems. OpenText Identity Manager also provides the ability to develop a custom driver to enable data synchronization to a variety of other systems such as a home-grown application or a repository that has no technology interface and cannot leverage out-of-box drivers.
Drivers can be installed locally on the OpenText Identity Manager Server or with a Remote Loader. A Remote Loader loads drivers and communicates with the OpenText Identity Manager engine on behalf of drivers installed on remote servers. If the application runs on the same server as the OpenText Identity Manager engine, you can install the driver on that server. However, if the application does not run on the same server as the OpenText Identity Manager engine, you must install the driver on the application’s server. To help with the workload or configuration of your environment, you can install Remote Loader on a server separate from the servers that have Tomcat and the OpenText Identity Manager server. For more information about Remote Loader, see Determining When to Use the Remote Loader in the OpenText™ Identity Manager CE 24.4 (v4.10) Driver Administration Guide.
Use the Identity Manager Remote Loader Server installation option to install the Remote Loader service and the driver instances in the Remote Loader.
Identity Manager Fanout Agent is an installation component used by Java Database Connectivity (JDBC) Fanout driver to create multiple JDBC Fanout driver instances. The Fanout driver provisions users, groups, and password to multiple databases with minimal effort. This eliminates the need for the OpenText Identity Manager administrator to configure multiple JDBC drivers using the same policies to provision multiple databases of the same type. You can centrally manage user accounts and have them automatically created, configured, maintained, and removed when appropriate. For more information, see the OpenText Identity Manager Driver for JDBC Fanout Implementation Guide.
To install Fanout Agent, use the Identity Manager Fanout Agent installation option of the installation program.
OpenText Identity Console is a replacement for iManager.
OpenText Identity Console is a Web-based administration console that provides virtual, secure and customized access to network administration utilities from anywhere over the Internet and Web browser. It makes the decentralization of the administrative tasks much easier.
With OpenText Identity Console, you can perform similar tasks as performed with Designer and also monitor the health of your system. We recommend that you use OpenText Identity Console for administrative tasks. Use Designer for configuration tasks that require changes to packages, modeling, and testing prior to deployment.
For more information, see OpenText™ Identity Console CE 24.4 (v1.9) Administration Guide.