In a CA Data Protection enterprise environment, you may find more than one CMS (i.e. a production system and a test system). To reduce administration and enable you to configure CMS environments with similar configuration settings, Data Protection includes functionality that allows you to export one CMS “profile” and import it into another CMS.
A CMS “profile” is an xml file while consists of certain files in the CA Data Protection file system, plus the CMS installation properties located in the CA Data Protection WgnWellKnownString, WgnFile, Wgn3Role and Wgn3ResourceRole database tables. For example, a profile includes:
•User attributes: The name and index of all user attributes.
•Role privileges: The name of each role and the privileges assigned to that role.
•Audit settings: All audit settings.
•Audit templates: The names and contents of the audit templates.
•Severity thresholds: The low, medium and high severity threshold values for triggers.
•Policy Roles: The names and associated resources of all policy roles.
When importing a CMS profile into a CMS the import may fail with an error like the one below
Unable to save data to database: DBObject->INSERT exception Wgn3ResourceRole( 22,4010411 ) (State: 23000, DB Specific Error: 547): [CA DataMinder][SQLServer JDBC Driver][SQLServer]The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Wgn3ResourceRole_Resource". The conflict occurred in database "WGN_<DATABAS>", table "dbo.Wgn3Resource", column 'ResourceUID'.
By default when performing a CMS profile export from the command line, only the pre-defined policy classes are completely exported. Importing a profile from a CMS where custom policy classes existed will result in an error.
This is now included in cumulative FIX:SO01003 (incorporating Server_15.20_HF0162, Server_x64_15.20_HF0163, Client_15.20_HF0164, Client_x64_15.20_HF0165 and Server_Native_x64_15.20_HF0166).