Identity Management Service › Connectors Guide › Connecting to Endpoints › IBM RACF v2 Connector › How to Migrate Data from the Plug-in Connector to the New Java Connector › Map Custom Attributes for Identity Management › Migrate Configuration and Data from Old Connector to New

Migrate Configuration and Data from Old Connector to New

The migration tool converts data from the old plugin connector to the new RACF v2 connector.

Note: You cannot migrate the endpoint using this tool. Before you can migrate the data, configure the endpoint in Identity Management.

RACFv2Migrate <options>

-h hostname

Specifies the computer that hosts IMPS.

-d domain

Identifies the Identity Management domain that contains the endpoints that you want to migrate. Default: im

-p port

Defines the port number of IMPS. Default: 20391.

-u username

Identifies the administrative user of the Identity Management domain.

-r S

Produces a report that lists the objects and inclusions that would have been migrated.

-r R

Migrates data and produces a report that lists the objects and associations that would have been migrated, plus any failures.

-m path

Specifies the file that contains mappings for custom attributes in RACF.

One of the pre-requisites of the migration tool is the administrator has to migrate the custom attributes to the new namespace manually before running the tool. The tool has no knowledge of the custom attributes added to the new namespace, hence the user is also responsible to create a mapping file and supply the location of the file when running the tool.

The mapping file should contain the from-custom-attribute=to-endpoint-attribute information, for example:

eTRACCustomAttribute001=eTRACAddressLine1
eTRACCustomAttribute002=eTRACAddressLine2

Note that the contents and format are the same as that used in schema_map.txt, and that file can be used as is as the mapping configuration file for migration.

-c path

Specifies the file that lists which endpoints have their data migrated. For more information, read Create Two Migration Mapping Files.

-l path

Specifies the logging configuration file. If this is omitted, the migration tool uses the default logging configuration specified in <JAVA_HOME>/lib/logging.properties. For more information, read Configure the Migration Log File.

Repair Migration Errors

After the migration has finished, check the outcome carefully. If the result of the migration is not correct, delete the new data and start again.

Follow these steps:

1. Delete the new endpoints specified in the endpoint mapping file.

   This step deletes all associated account objects in Identity Management without affecting data on the endpoint itself. This step also removes all associations between global users and accounts.

2. Delete the new account templates.

   This step removes all associations with the account templates.

You are now ready to migrate again.

Correlate the Data

If you migrated data from old endpoints, you first explored the data but you did not correlate the data. After the migration is complete, correlate the data.

To correlate the data, follow the instructions in the Identity Management Administration Guide. Search for these steps in Integrate the Managed Endpoint in Identity Management, in the Identity Management bookshelf.

For now, include the options for the correlation. The following steps list the actions to perform:

Follow these steps:

1. Create correlation rules.
2. Edit the explore and correlate definition.

   For now, select the correlation checkbox.

3. Explore and correlate the endpoint.

   For now, the data is both explored and correlated.

The endpoint is ready for use in Identity Management.