Customizing Identity Manager Service Center files (Software stack )
As a site administrator, you might want to customize Identity Manager Service Center to meet your specific business needs. Customization involves either copying and modifying files that are provided by IBM® or creating your own custom files to use in place of the IBM files. You must ensure that your new and modified custom files are placed in the correct location. Otherwise, the files cannot be found and used by Identity Manager Service Center.
Before you begin
Customizing the Identity Manager Service Center user interface requires access to files and
folders under the WebSphere® Application Server
configuration folder of your IBM Verify Identity Governance runtime
environment.
See Location of Identity Manager Service Center customizable files for the exact location of the files and folders to which you need access. To obtain access to the necessary files and folders, contact your system administrator.
About this task
The Identity Manager Service Center can be customized in many ways. To customize a particular aspect of the Identity Manager Service Center such as the login page, or the home page, see the appropriate customization instructions. Most customization tasks involve changing or providing replacements for one or more of the customizable files that are provided by IBM. This procedure describes how to create a custom file and where to place the custom file so that it can be used by the IBM Verify Identity Governance server.
Note: In single-server WebSphere Application Server environments, IBM Verify Identity Governance uses the custom file immediately after it is copied
to its correct location in the .../itim/custom/ui folder. In managed-cluster
environments, the custom file is used as soon as the configuration is synchronized to the
application servers in the cluster. For significant customization, create and test the customized
files when there are no active users of the Identity Manager Service Center.Many of the customizable files contain text that is translated into multiple languages for globalization. For customizable globalization files, a default file exists that is not locale-specific, such as common.properties. There are also locale-specific files for each supported language such as common_fr.properties for French and common_ar.properties for Arabic. The instructions in the following sections describe how to customize the default version of a globalization file only. If you choose to customize globalization files, follow the same instructions to customize the locale-specific versions of the files. You must customize the files for each language that you intend to support in your environment.
Procedure