Filter and Import the RoleDefinition and Environment
Filter and Import the RoleDefinition and Environment
144
The Environment Migration tool allows you to filter and update items in the Roles and Tasks (Role Definitions) and Environment Settings based on the selections and mappings in the Migration Xpress user interface.
You must manually import the filtered and updated Role Definitions and Environment Settings XML files into the target system using Identity Manager Management Console.
Follow these steps:
- Update the <Migration_Xpress_download_directory>/conf/environment.properties file with an appropriate value for each of the properties as explained below:PropertyTypeDescriptionRolesAndTasksInputFileRequiredPath of the Roles and Tasks (Role Definitions) XML input file. On submitting the source environment details in the Migration Xpress user interface, the input file is generated and stored at <Migration_Xpress_download_directory>/data/RoleDefinitions-cache-SOURCE.xml.The items in the input file are filtered and updated based on the mappings that you have selected in the Migration Xpress user interface.Example:RolesAndTasksInputFile=data/RoleDefinitions-cache-SOURCE.xmlRolesAndTasksOutputFileRequiredPath of the Roles and Tasks (Role Definitions) XML output file. The tool creates the folder structure and places the filtered and updated items from RolesAndTasksInputFile into this output file.Example:RolesAndTasksOutputFile=data/RoleDefinitions-Filtered.xmlEnvironmentSettingsInputFileRequiredPath of the Environment Settings XML input file. On submitting the source environment details in the Migration Xpress user interface, the input file is generated and stored at <Migration_Xpress_download_directory>/data/EnvironmentSettings-cache-SOURCE.xml.The items in the input file are filtered and updated based on the mappings that you have selected in the Migration Xpress web user interface.Example:EnvironmentSettingsInputFile=data/EnvironmentSettings-cache-SOURCE.xmlEnvironmentSettingsOutputFileRequiredPath of the Environment Settings XML output file. The tool creates the folder structure and places the filtered and updated items from EnvironmentSettingsInputFile into this output file.Example:EnvironmentSettingsOutputFile=data/EnvironmentSettings-Output.xmlSelectedItemsInputFileRequired forFILTERorFULLmodesRepresents the <Migration_Xpress_download_directory>/conf/environment.selection.map file. The tool filters the following two files based on the items inenvironment.selection.mapfile.
- RolesAndTasksInputFile
- EnvironmentSettingsInputFile
Example:SelectedItemsInputFile=conf/environment.selection.mapUserAttributesMappingInputFileRequired forUPDATEorFULLmodesRepresents the <Migration_Xpress_download_directory>/conf/environment.userAttrMapping.map file. The tool filters and/or updates the following two files based on the items inenvironment.userAttrMapping.mapfile.- RolesAndTasksInputFile
- EnvironmentSettingsInputFile
Example:UserAttributesMappingInputFile=conf/environment.userAttrMapping.mapGroupAttributesMappingInputFileRequired forUPDATEorFULLmodesRepresents the <Migration_Xpress_download_directory>/conf/environment.groupAttrMapping.map file. The tool filters and/or updates the following two files based on the items in environment.groupAttrMapping.map file.- RolesAndTasksInputFile
- EnvironmentSettingsInputFile
Example:GroupAttributesMappingInputFile=conf/environment.groupAttrMapping.mapOrganizationAttributesMappingInputFileRequired forUPDATEorFULLmodesRepresents the <Migration_Xpress_download_directory>/conf/environment.orgAttrMapping.map file. The tool filters and/or updates the following two files based on the items in environment.orgAttrMapping.map file.- RolesAndTasksInputFile
- EnvironmentSettingsInputFile
Example:OrganizationAttributesMappingInputFile=conf/environment.orgAttrMapping.map - Run the environment migration tool. There are two ways to run the tool.
- Method 1:<Migration_Xpress_download_directory>/lib/java -cp migration-xpress-<version>.jar -Dloader.main=com.ca.tools.environment.migration.StartConsole org.springframework.boot.loader.PropertiesLauncher -p environment.properties -mode <filter|update|full>
- Method 2:Windows: <Migration_Xpress_download_directory>bin\mx_environment.cmd -p environment.properties -m <FILTER|UPDATE|FULL> Linux: <Migration_Xpress_download_directory>./bin/mx_environment.sh -p environment.properties -m <FILTER|UPDATE|FULL>Options:-p <file>Represents the environment properties File.Path:<Migration_Xpress_download_directory>/conf/environment.properties-m <action>-mode <action>Filter:Filter Roles and Tasks (Role Definition) and Environment Setting XML files based on the items selected by a user.Update:Update attributes (user, group, and organization) based on the Attribute Mapping files.Full:
- Filter Roles and Tasks (Role Definition) and Environment Setting XML files based on the items selected by a user.
- Update attributes (user, group, and organization) based on the Attribute Mapping files.
- Import the filtered role definition to the target system.
- In the Identity Manager Management Console, navigate toEnvironments, <environment>, Role and Task Settings.
- ClickImport.
- Import the filtered environment settings XML to the target system.
- In the Identity Manager Management Console, navigate toEnvironments, <environment>,Advanced Settings.
- ClickImport.
- [Applicable only when migrating a standalone deployment to Virtual Appliance] If you are migrating a standalone deployment to Virtual Appliance, change the provisioning directory name to the target provisioning directory name in the<Migration_Xpress_download_directory>/data/Envsettings-filtered.xmlfile.
The Provisioning Roles in the imported RoleDefinition file and Provisioning Directory should be same. To this end, import the provisioning roles only after the Provisioning Directory has been migrated. It is recommended that export of the source Provisioning Directory and RoleDefinition should be done as close as possible to avoid mismatches.