OpenText Identity Governance contains two configuration utilities. You can use the two utilities to change the configuration or enable features after you have completed the installation. The utilities perform different tasks and you must use the proper utility for the proper task. The utilities are:
OpenText Identity Governance Configuration Update Utility (ConfigUpdate): You use this utility to modify Identity Reporting, OSP, and Auditing. These features are also part of other OpenText products and you use this utility on these common products across different products. Some properties require that you use the OpenText Identity Governance Configuration Update utility to update them. For more information, see Section 15.1.5, Using the OpenText Identity Governance Configuration Update Utility.
OpenText Identity Governance Configuration Utility (ConfigUtil): You use this utility to modify any of the OpenText Identity Governance settings you defined during the installation. For more information, see Section 15.1.4, Using the OpenText Identity Governance Configuration Utility.
OpenText Identity Governance contains multiple components, and you can install the components on the same server or different servers. OpenText Identity Governance uses databases and .properties files to store the configuration information. If you have OpenText Identity Governance and either Identity Reporting or OSP installed on the same server, the GLOBAL configuration databases and the ism-configuration.properties file might contain duplicate settings.
NOTE:For each property located in both the GLOBAL configuration database, and the ism.configuration.properties file, OpenText Identity Governance uses the property in the ism.configuration.properties file.
When updating the values associated with the duplicate settings, the different installation utilities place the information in different locations. If you are updating a duplicate setting using the OpenText Identity Governance Configuration Update utility, the value ends up in the ism-configuration.properties file. If you are updating a duplicate setting using the OpenText Identity Governance Configuration utility, the value ends up in the GLOBAL database.
Any component of OpenText Identity Governance, Identity Reporting, or OSP that retrieves the value of the duplicate property, retrieves the value from the ism-configuration.properties file rather than the value found in the GLOBAL database. This can cause issues in a clustered environment.
If you are running OpenText Identity Governance, Identity Reporting, and OSP in a clustered environment, ensure that you run the OpenText Identity Governance Configuration Update utility on each server in the cluster to get the information populated on each server.