Merging new and existing customized configuration files
To work with new features after you upgrade, you must merge the content of new configuration files with any existing, customized Identity Manager Service Center configuration files. If you do not merge the new and existing customized configuration files, you get errors when you work with the upgraded version of Identity Manager Service Center.
Before you begin
- See Location of Identity Manager Service Center customizable files and Customizing Identity Manager Service Center files (Software stack ) for the location of the Identity Manager Service Center customizable files and how to customize the files.
- If you did not previously customize the tertiary attribute in the
config/Access.Json, you can see that the tertiary attribute values are modified
from
"tertiary": [ "accessCategory", "entityProfile" ]to new default value"tertiary": [ "additionalInformation" ]. - If you did not previously customize the config/HeaderMenu.json, you can see
that the new attribute
menuIconItemis introduced. The tasks View Access, Request Access, and Edit and Delete Access are grouped under the Manage Access toolbar menu.
About this task
Virtual appliance Use
the following sections to work with the configuration files or the configuration properties from the
Identity Manager virtual appliance console:- To edit any custom files, see Managing custom files.
- To edit properties or other files, see Managing the server properties.
If you previously customized the configuration files that contain non-translatable configuration properties, complete the following steps.
Procedure
- Merge the content of the new configuration files into the existing customized
configuration files. For example, if you previously customized the file .../itim/custom/ui/config/Person.json, then merge it to the new.../itim/custom/ui/original/config/Person.json file.
- Replace the existing customized configuration files in the directory .../itim/custom/ui/config with the merged files.