1 Overview

The Oracle Identity Manager Customization Guide explains how to customize the following aspects of your Oracle Identity Manager Administrative and User Console:

• General Page Layout

• Descriptive Text, Labels, and Error Messages

• Colors, Fonts, and Alignment

• Logos

• Self registration and user initiated profile editing (and related approvals)

• Field configuration on pages

• Menu selections that are available for users

The files to be edited and the procedures to be used when editing those files are described within each section dedicated to the particular aspect of your Administrative and User Console. For example, for procedures related to customizing the General Page Layout, refer to the Customizing General Page Layout section.

Accessing Administrative and User Console Customization Files

Oracle Identity Manager is deployed to your application server as an Enterprise ARchive (EAR) file called Xellerate.ear. This file is created and deployed to the application server during installation. The name of this file may vary depending on the application server used for deployment. For example, if you use JBoss, this file is called XellerateFull.ear, while in WebSphere it is a folder called Xellerate.ear, and in WebLogic it is a folder named WLXellerateFull.ear. This archive file contains some of the files for customizing your Administrative and User Console (such as, Xellerate.css and xlWebAdmin.properties). To access the files for customizing your client, you have to unpack a Web Archive (WAR) file, make your desired edits, repack the WAR file, and run a script that regenerates the EAR file, and deploys it to your application server.To customize the Administrative and User Console, ensure that your application server is running and then perform the following tasks:

1. Uncompress the entire xlWebApp.war file from the <XL_HOME>/xellerate/webapp directory into any directory.

2. Modify the files required (files to be customized

   
   

   Note: It is recommended that you create backups of any files before modifying them.

   
   

3. Create a new archive file called xlWebApp.war using the jar utility.

4. Copy (and overwrite) the xlWebApp.war file in <XL_HOME>/xellerate/webapp.

5. Run the patch_<appserver> script from the <XL_HOME>/xellerate/setup directory, where <appserver> is the name of your application server, for example, if you are using WebLogic, this file is called patch_weblogic.

6. Restart your application server (JBoss, WebSphere, or WebLogic).