Preparing the Properties File

Using the Form Version Control Utility 22-7 record to the selected state if the field value is True case sensitive. For all other values, the utility sets the check box to the deselected state. Sample line: ChildParentLookupOrComboToCheckBox;UD_OID_GRP_GROUP_NAME;U D_OID_USR_CHKBOXTEST – ChildDiffChild;OLD_FIELD_NAME;NEW_FIELD_NAME The utility moves data from the OLD_FIELD_NAME field on the source child form to the NEW_FIELD_NAME field on the target child form. Sample line: ChildDiffChild;UD_OID_GRP_NORMALFIELD;UD_OID_ROLE_DIFFFIEL D

22.5.2 Addressing Prerequisites for Using the FVC Utility

Before you run the utility:

1. Set the Java home directory path in the FVC Utility script as follows:

a. Depending on the operating system and application server that you are using,

open one of the following files in a text editor: fvcutil.sh fvcutil.cmd

b. Search for set JAVA_HOME.

c. Set the Java home directory path as shown in the following example:

set JAVA_HOME=C:\Java\

d. Save and close the file.

2. Verify that the version of the process parent form on which you want to run the

utility is the Active version. To check if the version of a form is the Active version:

a. Log in to the Design Console

b. Expand the Development Tools folder, and then double-click Form Designer.

c. Search for and open the form.

d. Active Version field of the form displays the active version of the form.

3. The utility cannot update a form field if the field is associated with error-handling

adapters. If any field is associated with error-handling adapters, then dissociate the adapters as follows: Note: This update is carried out only if the source child form contains a single row. A scenario in which the source child form contains more than one row is not supported. Note: After you run the utility, you can again set up the association between the field and its error-handling adapters. The procedure is described later in this chapter. 22-8 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager a. Log in to the Design Console

b. Expand the Process Management folder, and then double-click Process

Definition . c. Search for and open the process definition of the connector. d. Make a note of the name of the task that updates the field. e. Double-click the task. For example, if the userID field has an error-handling adapter, then double-click the updateUserID task. f. On the Integration tab of the Editing Task dialog box, make a note of the adapter variable names and their descriptions.

g. Click Remove.

h. To confirm that you want to remove the event-handler adapter, click OK in

the message that is displayed.

i. Click Save.

22.5.3 Running the Utility

Run the following script: For Unix: sh fvcutil.sh For Windows: fvcutil.bat This will prompt you to enter the following details:

1. Enter Oracle Identity Manager admin username: Enter Oracle Identity Manager

administrator username.

2. Enter Oracle Identity Manager admin password: Provide Oracle Identity Manager

administrator password.

3. Enter logger level: Enter the logger level. It can be DEBUG, WARN, INFO, or

ERROR.

4. Enter logger location: Provide the location and name of the log file that you want

the utility to create at the end of each run. For example, Path nameFVC.log.

22.6 Troubleshooting

Table 22–1 lists the error messages that you might encounter in the log file and the corresponding actions that you can take to fix the issues: Note: You must execute the FVC utility every time the form version is changed. Using the Form Version Control Utility 22-9 Table 22–1 Error Messages and Solutions Error Message Solution Could not find objects with name=OBJECT_NAME Check the name of the resource object provided in the properties file. Ensure that it is spelled correctly. Could not find form with name=FORM_NAME Check the name of the form provided in the properties file. Ensure that it is spelled correctly. Could not find active version of the form. A newly created form might not have been committed and set to the Active state. Ensure that the form is in the Active state. ToVersion value and active version of the form do not match. Ensure that the ToVersion value is the same as the version of the form that is currently active. Either ToVersion or FromVersion values are not valid versions. Ensure that the ToVersion and FromVersion values are correct. FIELD_NAME field does not exist in the Oracle Identity Manager database. Ensure that the name of the field is spelled correctly. 22-10 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 23 Using the Archival Utilities 23-1 23 Using the Archival Utilities This chapter describes how to use the various archival utilities in the following sections: ■ Using the Reconciliation Archival Utility ■ Using the Task Archival Utility ■ Using the Requests Archival Utility ■ Using the Audit Archival and Purge Utility

23.1 Using the Reconciliation Archival Utility

This section describes how to use the Reconciliation Archival utility. It contains the following topics: ■ Understanding the Reconciliation Archival Utility ■ Prerequisite for Running the Reconciliation Archival Utility ■ Archival Criteria ■ Running the Reconciliation Archival Utility ■ Log File Generated by the Reconciliation Archival Utility

23.1.1 Understanding the Reconciliation Archival Utility

Oracle Identity Manager stores reconciliation data from target systems in Oracle Identity Manager tables called active reconciliation tables: During the reconciliation process, Reconciliation Manager reconciles data in the active reconciliation tables with the Oracle Identity Manager core tables. Because Reconciliation Manager does not remove reconciled data from the active reconciliation tables, they might eventually grow very large, resulting in decreased performance during the reconciliation process. You can use the Reconciliation Archival utility to archive data that has been reconciled with Oracle Identity Manager. The Reconciliation Archival utility stores archived data in the archive reconciliation tables , which have the same structure as the active reconciliation tables. Table 23–1 lists the active reconciliation tables with the corresponding archive reconciliation tables in which data from the active reconciliation tables are archived.