Stopping and Starting the Remote Manager

Using the Form Version Control Utility 22-3 2. The utility checks the object status of the record in the USR table. The next step depends on the status of the record: ■ If the users record is in the Deleted state, then the utility moves on to the next users record. ■ If the users record is not in the Deleted state, then the utility checks the status of the account records in the connector-specific UD_ tables for that user. For each account record, the next step depends on the status of the account record: – If the account record is in the Revoked state, then the utility moves on to the next account record for that user. – If the account record is not in the Revoked state, then the utility performs the updates specified in the properties file. 3. For a particular account record, the utility first updates the version of the record and then updates the data as specified in the properties file.

22.4 Components of the FVC Utility

The following are components of the FVC Utility: ■ Properties file: You use a file with the .properties extension to provide details of the process form, child forms, and resource object on which you want to run the utility. The fvc.properties file is provided as a sample. If a new properties file is used, then the name of the file must be changed in fvcutil.sh or fvcutil.cmd. ■ xlFvcUtil.jar: This JAR file contains the utility classes required to run the FVC Utility. ■ fvcutil.sh and fvcutil.cmd: You use this script to run the utility.

22.5 Using the FVC Utility

The following sections describe the procedure to use the FVC Utility: ■ Preparing the Properties File ■ Addressing Prerequisites for Using the FVC Utility ■ Running the Utility

22.5.1 Preparing the Properties File

As mentioned earlier in this chapter, you use a properties file to define the data conversion actions that you want the FVC Utility to perform. Whether you must create or update the properties file depends on the upgrade scenario: Note: If an error is encountered, then an error message is displayed in the command window. After you fix the cause of the error and rerun the utility, records that have been updated before the error was encountered are not processed again. Note: When you install the Design Console, these files are copied into the OIM_DC_HOME directory. 22-4 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager ■ If you are upgrading from a predefined release to a predefined release of a connector, then look for a properties file in the connector deployment package. ■ If you are upgrading from a custom release or upgrading to a custom release, then you must add the required entries in the properties file. ■ If you are upgrading from a custom release to a predefined release of a connector, then see if the connector guide provides information about changes to the process form and child forms of the connector. You can use this information to determine the entries that you must add in the properties file. The following are sample entries for the properties file: ResourceObject;OID User FormName;UD_OID_USR FromVersion;8 ToVersion;9 Parent;UD_OID_USR_DEFTVAL;ABC Child;UD_OID_GRP_NORMALFIELD;XYZ;Update ParentChild;UD_OID_USR_FNAME;UD_OID_GRP_NORMALFIELD ChildChild;UD_OID_GRP_GROUP_NAME;UD_OID_GRP_NORMALFIELD ChildParent;UD_OID_GRP_NORMALFIELD;UD_OID_USR_LNAME ParentParent;UD_OID_USR_FNAME;UD_OID_USR_LOGIN; ParentParentLookupOrComboToCheckBox;UD_OID_USR_PREF_LANG;UD_OID_USR_CHKBOXTEST ChildParentLookupOrComboToCheckBox;UD_OID_GRP_GROUP_NAME;UD_OID_USR_CHKBOXTEST ChildDiffChild;UD_OID_GRP_NORMALFIELD;UD_OID_ROLE_DIFFFIELD Apply the following guidelines while adding or modifying entries in the properties file: ■ In the properties file, each line consists of the use case name, followed by old field name and the new field name. Each of these are separated by semicolon. For Example consider following entry in properties file: ParentChild;UD_OID_USR_FNAME;UD_OID_GRP_NORMALFIELD ParentChild: represents that the fields of the parent have been renamedmoved to be in the new child form UD_OID_USR_FNAME: represents the old field name in parent form UD_OID_GRP_NORMALFIELD: represents the new name of the field to be upgraded in the new form. ■ You must include the following lines in the properties file: – ResourceObject;RESOURCE_OBJECT_NAME Note: See the sample entries listed earlier to get a better understanding of the guidelines. Note: There can be spaces in the value as long as a space does not appear immediately after the semicolon. Note: The location and order of these 4 lines in the properties file does not matter.