Adding the Trust Relation

21-6 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

21.4 Troubleshooting Remote Manager

Table 21–1 lists the troubleshooting steps that you can perform if you encounter problems with the remote manager: Table 21–1 Troubleshooting Remote Manager Problem Solution You encounter certificate trust issues. Ensure that the remote manager certificate is trusted on the Oracle Identity Manager side. Ensure that the remote manager certificate has not expired. Ensure that the remote manager port is correctly configured on the Oracle Identity Manager host. In other words, ensure that the port configured on the Oracle Identity Manager host must be the same port in the remote manager configuration. Ensure that the remote manager configuration, such as keystore location, alias, password, and key password, in the xlconfig.xml file and Oracle Identity Manager host configuration in the oim-config.xml file are correct. Ensure that the correct server certificate is trusted on the remote manager if client-auth is set. After ensuring all the conditions to resolve certificate trust issues, failure occurs while communicating between the remote manager and Oracle Identity Manager. Restart Oracle Identity Manager and remote manager by passing the following flag: -Djavax.net.debug={all|ssl} This flag, when turned on stores all the information related to the SSLTLS handshake in the logs. Here, all turns on all debugging, and ssl turns on SSL debugging. Note: Use this flag only for debugging purpose. When turned on, it dumps a huge amount of information in the logs. The remote manager connection fails. Ensure that there is no firewall between Oracle Identity Manager and remote manager that is blocking tcp traffic on the specific port. To do this, telnet from the Oracle Identity Manager host to the remote manager host on the remote manager port. Provisioning through the remote manager fails. Ensure that the adapter JAR files which are usually located in the OIM_HOMEJavaTasks directory or in the database are copied on the remote manager host in the JavaTasks directory. Ensure that the remote manager-based adapters have a Remote Task to invoke target APIs, as opposed to regular adapters, which can just use Java Task to do the same. Ensure that the remote manager-based connectors: - Define a remote manager IT resource. - Set the remote manager IT resource on the remote manager field on the regular IT resource, which contains the connectivity information of the target 22 Using the Form Version Control Utility 22-1 22 Using the Form Version Control Utility Process forms and child forms are used to hold account data of OIM Users. You can upgrade a form by adding, modifying, or removing fields on the form. For example, as part of an upgrade operation, you might add the Hire Date field and remove the Country of Origin field from a form. In addition, fields might be moved from the parent form to the child form. The Oracle Identity Manager Form Version Control FVC Utility facilitates the management of form data changes after a form upgrade operation. The FVC Utility is a command-line utility that works directly on the Oracle Identity Manager database. When you install the Oracle Identity Manager Design Console, the utility is present in the OIM_DC_HOME directory. You use a properties file to specify the form data updates that the utility must perform. The utility supports field mapping and data updates on a provisioning process form and its associated child forms. This chapter contains the following sections: ■ Use Cases Supported by the FVC Utility ■ Use Cases That Are Not Supported by the FVC Utility ■ Summary of the Form Version Control Process ■ Components of the FVC Utility ■ Using the FVC Utility ■ Troubleshooting

22.1 Use Cases Supported by the FVC Utility

In a single run, the FVC Utility can be used to manage form data updates corresponding to the following form changes: Note: The FVC Utility cannot perform the following functions: ■ Manage data updates on object forms ■ Move rows across forms In addition, you need not run the FVC Utility if there are no form-related changes from one release to the next release.