Migrating from Existing Resources

Connectors will eventually replace resource adapters. For this release, however, Identity Manager will continue to support all previous resource adapters. Although it is not strictly required to migrate to the connector equivalent when one is available, it is recommended.

When there is a new connector type available that can replace an existing resource adapter, a migration path is provided to enable customers to switch over to use the connector.

In general, the greater the number and the more complex your customized forms and workflows, the more complicated the conversion process. To prepare to migrate from an adapter-based resource to a connector-based one,

• Evaluate all existing forms and workflows that are related to the migrated resource for instances where searchFilter is set to a string.

• Replace each occurrence with connectorFilter. The value of the connectorFilter entry will be an instance of a filter, which is made by using the FilterBuilder class by an <invoke>.

Migrating to a Connector-Based Resource: General Steps

Do not perform this migration in a production environment. The migration does an in-place upgrade of the existing resource, changing it to use the connector instead of the previous resource adapter. All previous user account assignments to the resource will remain after the migration. While considerable effort is made in the migration to preserve backward-compatibility, it is recommended that the converted resource be tested before promoting to production.

1. Install the new connector (if not already installed)

2. Follow all the Identity Manager-specific installation steps documented for the connector, including importing any needed Exchange files.

3. Follow the migration procedure documented for the connector. Typically, this involves running a declared migration server task from Server Tasks > Run Tasks.