The ACF2 Driver supports Designer 4 Package features, which allows you to create a driver by selecting which packages to install. After you create and configure the driver, you need to deploy it to the Identity Vault and start it.
Driver packages can be updated at any time and are stored in the Package Catalog. Packages are initially imported into the Package Catalog when you create a project, import a project, or convert a project. It is important to verify you have the latest packages imported into the Package Catalog before you install the driver.
To verify you have the latest packages imported into the Package Catalog:
Open Designer.
In the toolbar, click
> .Click
if there are no package updates.or
Click OK to import the package updates.
In the Outline view, right-click the Package Catalog.
Click
.Select the ACF2 packages.
or
Click
to import all of the packages displayed, then click .NOTE:By default, only the base packages are displayed. Deselect
to display all packages.Click
to import the selected packages, then click in the successfully imported packages message.After the current packages are imported, continue to the next section, Installing the Driver Packages.
After you have imported the current driver packages into the Package Catalog, you can install the driver packages to create a new driver.
In Designer, open your project.
In the Modeler, right-click the driver set where you want to create the driver, then select
> .Select
from the list of base packages, then click .Select the optional features to install for the ACF2 driver. All options are selected by default. The options are:
NOTE:Publications referenced in the following option descriptions can be accessed at the Identity Manager 4.0.2 Documentation Web site.
Default Configuration: This package contains the default configuration information for the ACF2 driver. Always leave this option selected.
Entitlements: This package contains configuration information for synchronizing Logonid accounts and policies that enable account creation and auditing for the ACF2 driver. To enable account creation and auditing, verify that this option is selected. For more information, see the Identity Manager 4.0.2 Entitlements Guide.
Password Synchronization: This package contains the policies that enable the ACF2 driver to synchronize passwords. To synchronize passwords, verify that this option is selected. For more information, see the Identity Manager 4.0.2 Password Management Guide.
Data Collection: This package contains the policies that enable the driver to collect data for reports. If you are using the Identity Reporting Module, verify that this option is selected. For more information, see the Identity Reporting Module Guide.
Account Tracking: This package contains the policies that enable you to track accounts for reports. If you are using the Identity Reporting Module, verify that this option is selected. For more information, see the Identity Reporting Module Guide.
After selecting the optional packages, click
.(Conditional) If there are package dependencies for the packages you selected to install, you must install them to install the selected package. Click
to install the package dependencies listed.(Conditional) If more than one type of package dependency must be installed, you are presented with these packages separately. Continue to click
to install any additional package dependencies.(Conditional) The Common Settings page is only displayed if the Common Settings package is installed as a dependency. On the Install Common Settings page, fill in the following fields:
User Container: Select the Identity Vault container where ACF2 users will be added if they don’t already exist in the vault. This value becomes the default for all drivers in the driver set.
If you want a unique location for this driver, set the value for all drivers on this page. After the driver is created, change the value on the driver’s Global Configuration Values page.
Group Container: Since the ACF2 driver does not synchronize Group objects, this setting can be ignored.
Click
.On the Install ACF2 page, fill in the following field:
Driver Name: Specify a name for the driver that is unique within the driver set.
On the Install ACF2 Base page, fill in the following fields for the driver parameters:
Polling Interval: An interval, in seconds, that specifies how often the driver shim should check for publisher events.
Heartbeat Interval: An interval, in seconds, that specifies how often the publisher should send Heartbeat status messages from the driver shim.
Publisher Disabled: Specifies whether the publisher channel should be disabled.
Synchronize ACF2 Password Phrases: Specifies whether Identity Vault passwords should be synchronized with ACF2 Password Phrases.
Click
.On the Install ACF2 Base page, fill in the following fields to connect to the Remote Loader:
Connect to Remote Loader: By default, the driver is configured to connect using the Remote Loader. You must select
for this optionHost Name: Specify the port number where the Remote Loader is installed and is running for this driver. The default port number is 8090.
Port: Specify the Remote Loader’s password as defined on the Remote Loader. The Metadirectory server (or Remote Loader shim) requires this password to authenticate to the Remote Loader.
Remote Password: Specify the Remote Loader’s password as defined on the Remote Loader. The Metadirectory server (or Remote Loader shim) requires this password to authenticate to the Remote Loader.
Driver Password: Specify the driver object password that is defined in the Remote Loader service. The Remote Loader requires this password to authenticate to the Metadirectory server.
Click
.(Conditional) This page is displayed only if you selected to install the Account Tracking packages. On the Install ACF2 Account Tracking page, fill in the following field:
Realm: Specify the name of the realm, security domain, or namespace where the account name is unique.
Click
.(Conditional) This page is only displayed if you selected to install the Data Collection packages and the Account Tracking packages. On the Install ACF2 Account Tracking information page, fill in the following fields to define your ACF2 system.
Name: Specify a descriptive name for this ACF2 system. The name is displayed in reports.
Description: Specify a brief description for this ACF2 system. The description is displayed in reports.
Location: Specify the physical location for this ACF2 system. The location is displayed in reports.
Vendor: Leave Computer Associates as the vendor of ACF2. This information is displayed in reports.
Version: Specify the version of this ACF2 system. The version is displayed in reports.
Click
.(Conditional) This page is displayed only if you selected to install the Managed System Information packages. On the Install ACF2 Managed System Information page, fill in the following fields:
Classification: Select the classification of the ACF2 system. This information is displayed in the reports. Options include:
Mission-Critical
Vital
Not-Critical
Other
If you select
, you must specify a custom classification for the ACF2 system.Environment: Select the type of environment the ACF2 system provides. Options include:
Development
Test
Staging
Production
Other
If you select
, you must specify a custom classification for the ACF2 system.Click
.Review the summary of tasks that will be completed to create the driver, then click
.The driver is created. You can modify the configuration settings by continuing with the next section, Configuring the Driver. If you don’t need to configure the driver, skip ahead to Deploying the Driver.
There are many settings that can help you customize and optimize the driver. The settings are divided into categories such as Driver Configuration, Engine Control Values, and Global Configuration Values (GCVs). Although it is important for you to understand all of the settings, your first priority should be to review the Driver Parameters located on the Driver Configuration page and the Global Configuration Values. These settings must be configured properly for the driver to start and function correctly.
To access the Driver Properties page:
Open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.Modify the driver settings as necessary.
IMPORTANT:In addition to the driver settings, you should review the set of default policies and rules provided by the basic driver configuration. Although these policies and rules are suitable for synchronizing with Active Directory*, your synchronization requirements for the driver might differ from the default policies. If this is the case, you need to change them to carry out the policies you want. The default policies and rules are discussed in Section 1.2, Configuration Overview.
Continue with the next section, Deploying the Driver.
After a driver is created in Designer, it must be deployed into the Identity Vault:
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
> .If you are authenticated to the Identity Vault, skip to Step 5; otherwise, specify the following information:
Host: Specify the IP address or DNS name of the server hosting the Identity Vault.
Username: Specify the DN of the user object used to authenticate to the Identity Vault.
Password: Specify the user’s password.
Click
.Read through the deployment summary, then click
.Read the successful message, then click
.Click
to assign rights to the driver.The driver requires rights to objects within the Identity Vault. The Admin user object is most often used to supply these rights. However, you might want to create a DriversUser (for example) and assign security equivalence to that user. Whatever rights that the driver needs to have on the server, the DriversUser object must have the same security rights:
Click
, then browse to and select the object with the correct rights.Click
twice.Click
to exclude users that should not be synchronized.You should exclude any administrative User objects (for example, Admin and DriversUser) from synchronization:
Click
.When a driver is created, it is stopped by default. To make the driver work, you must start the driver and cause events to occur. Identity Manager is an event-driven system, so after the driver is started, it won’t do anything until an event occurs.
To start the driver:
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
> .Drivers are created with packages, and iManager does not support packages. In order to create or modify drivers, you must use Designer. See Section 3.7.1, Creating the Driver in Designer.