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

How to Migrate Data from the Plug-in Connector to the New Java Connector

This section applies to Identity Management only.

CA IAM Connector Server comes with a tool that helps you migrate account templates and their associations to objects of the new connector. If Identity Management already manages RACF endpoints using the plugin connector, you can use the existing RACF data with the new connector.

This tool migrates the following data:

• Account templates

  The migrated account templates have the same name as the old account templates.

• Associations between account templates and endpoints, roles, and accounts

You cannot use this tool to migrate endpoint objects. Before you can migrate other data, acquire and explore the endpoints with the new connector.

1. Before you migrate data, set up the connector without correlating, using the steps in How to Connect to RACF.
2. Create two migration mapping files.
3. Migrate the data
4. Repair migration errors
5. Correlate the data.

Create Two Migration Mapping Files

The migration tool works with two mapping files:

• (Required) A file that specifies which old endpoints are migrated to which new endpoints.

  The endpoint mapping file uses the following format:

  OldEndpointName=NewEndpointName
  

• (Optional) A file that specifies any custom attributes that you plan to manage.

  The custom attribute mapping file uses the following format:

  from-custom-attribute=to-endpoint-attribute
  

  The mapping file has the same format and contents as the schema_map.txt used in Provisioning Manager and Provisioning Server. You can use schema.txt as the mapping configuration file for the migration.

Follow these steps:

1. Set up any custom attributes in the new endpoint in Identity Management.
2. Prepare the endpoint mapping file. Only the old endpoints that are specified in this mapping file are migrated.

   When you run the mapping tool, use the –c option to specify the path to the mapping file.

3. Prepare the mapping file for any custom attributes, if necessary.

   When you run the mapping tool, use the –m option to specify the path to the mapping file.

Example: Endpoint mapping file

In the example below, the administrator chooses to keep the endpoint name the same:

MFTSS.org.com=MFTSS.org.com

Example: Custom attribute mapping file

CustomAttribute001=VSE-IES-Dflt-Usercat
CustomAttribute002=VSE-IES-Fld1

Run a Migration Report

Before you migrate your data, we recommend that you run a simulation first. This generates an HTML report that lists the following items:

• Objects and inclusions that are created
• Potential migration failures

You can then use the same migration tool to run the real migration.

Follow these steps:

1. Open a command prompt and navigate to this location:

   cs_home/bin/RACFv2Migrate

2. To run a simulated migration, use the racfv2migrate command with the -r S option. For example:

   RACFv2Migrate -h mycomputer -d im -p 20390 -u admin -c c:\endpointconfig.txt -m c:\schema_map.txt -r S 
   

3. To migrate the data, use the racfv2migrate command with the -r R option. For example:

   RACFv2Migrate -h server32 -d im -p 20389  -u etaadmin -n -r R -c tss_endpoints.properties -l logging.properties
   

   The tool migrates the data and saves a report in cs_home/jcs/resources/racfv2.

4. Verify the new account templates and associations.