Identity Management Service › Connectors Guide › Connecting to Endpoints › CA Top Secret Connector › How to Migrate Data from the Plug-in Connector to the New Java Connector › Import the CA LDAP Server Certificate into the CA IAM Connector Server Keystore › tssv2migrate—Migrate Data from Old Plug-in Connector to New Connector

tssv2migrate—Migrate Data from Old Plug-in Connector to New Connector

The migration tool converts data from the old plug-in connector to the new CA Top Secret v2 connector.

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

TSSv2Migrate <options>

-c path

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

-d domain

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

-h hostname

Specifies the computer that hosts Provisioning Server.

-l path

Specifies the logging configuration file. If you omit this option, the migration tool uses the default available logging configuration from the following path: java_home/lib/logging.properties.

For more information, read Configure the Migration Log File.

-m path

Specifies the file that contains mappings for custom attributes in CA Top Secret. For more information, read Create Two Migration Mapping Files.

-n

Disable TLS communication. Default: TLS is enabled.

-p port

Defines the port number of the Provisioning Server. Default for no TLS: 20389. Default for TLS: 20390.

-r S

Produces a report that lists the objects and associations 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.

-u username

Identifies the administrative user of the Identity Management domain.

Repair Migration Errors

After the migration has finished, verify 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 that are specified in the endpoint mapping file.

   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.

   Removes all associations with the account templates.

You are 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.