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, user initiated profile editing, and related approvals

• Field configuration on pages

• Menu selections that are available to users

To configure the various aspects of the Administrative and User Console, you edit certain files. These files and how to edit them are described in the various sections of this Guide. For example, to learn how to customize the general page layout, see Chapter 2, "Customizing General Page Layout" .

See Also:

Oracle Identity Manager Globalization Guide for information on how to globalize Oracle Identity Manager Administrative and User Console

Accessing Administrative and User Console Customization Files

During installation, Oracle Identity Manager is deployed to your application server as an Enterprise ARchive (EAR). This archive file contains some of the files for customizing your Administrative and User Console, for example Xellerate.css, xlWebAdmin.properties, and xlDefaultAdmin.properties. The name of the EAR file varies depending on your application server, as follows:

• JBoss or OC4J—XellerateFull.ear

• WebSphere—Xellerate.ear

• WebLogic—WLXellerateFull.ear

To access the files for customizing your client, you 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:

   Oracle recommends that you back up 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.