Skip Headers
Oracle® Identity Manager Installation Guide for Oracle Application Server
Release 9.0.3

Part Number B32459-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

7 Post-Install Configuration for Oracle Identity Manager Server and Oracle Application Server

After you have installed Oracle Identity Manager, you must complete some post-installation tasks before you can use the application. Additionally, there are several optional post-installation tasks you may choose to complete, depending on your deployment, before using the application. The following is a list of the sections in this chapter:

Required Post-Installation Tasks for Oracle Application Server

After you install the Oracle Identity Manager software on Oracle Application Server, you must perform the tasks in this section for Oracle Identity Manager to operate properly.

Increasing the Oracle Application Server Heap Size

After installing Oracle Identity Manager on Oracle Application Server, you must increase the Oracle Application Server heap size before using Oracle Identity Manager. Perform the following steps to increase the Oracle Application Server heap size:

  1. Open the <ORACLE_HOME>\opmn\conf\opmn.xml file in a text editor.

  2. Search for the following string:


    Change this string to the following:

  3. Save and close the <ORACLE_HOME>\opmn\conf\opmn.xml file.

  4. Restart the Oracle Application Server after increasing the heap size.

Optional Post-installation Tasks

After installing Oracle Identity Manager, you should considering performing the optional post-installation tasks documented in this section before using the application. Depending on your Oracle Identity Manager deployment, you may choose not to perform some of these tasks.

Changing Keystore Passwords

Oracle Identity Manager has two keystores: one for the Oracle Identity Manager server and one for the database. During installation, the passwords for both are set to xellerate. Oracle recommends changing the keystore passwords for all production installations. You can use the keytool to change the keystore password for either keystore.

To change the keystore password:

  1. Open a command prompt on the Oracle Identity Manager host computer.

  2. Navigate to the <XL_HOME>\xellerate\config directory.

  3. Run the keytool with the following options:

    <JAVA_HOME>\jre\bin\keytool -storepasswd -new <new_password> -storepass xellerate -keystore .xlkeystore -storetype JKS

    Table 7-1 lists the options used in the preceding example of keytool usage:

    Table 7-1 Command Options for keytool

    Option Description


    Location of the Java directory associated with the application server


    New password for the keystore

    -keystore <option>

    Keystore whose password you are changing (.xlkeystore for the Oracle Identity Manager server or .xldatabasekey for the database)

    -storetype <option>

    JKS for .xlkeystore and JCEKS for .xldatabasekey

  4. Launch a plain-text editor, then open the <XL_HOME>\xellerate\config\xlconfig.xml file.

  5. Edit the <xl-configuration>.<Security>.<XLPKIProvider>.<KeyStore> section to specify the keystore password.


    Change the <XLSymmetricProvider>.<KeyStore> section of the configuration file to update the password for the database keystore (.xldatabasekey).
    • Change the password tag to encrypted="false".

    • Enter the password (in the clear). For example, change the following block:

      <Password encrypted="true">xYr5V2FfkRYHxKXHeT9dDg==</Password>

      to the following:

      <Password encrypted="false">newpassword</Password>
  6. Restart your application server.

    When you stop and start the application server, a backup of the configuration file is created. The configuration file (with the new password) is read in, and the password is encrypted in the file.

  7. If all of the preceding steps have succeeded, you can delete the backup file.


    On UNIX or Linux, you may also want to clear the shell's command history by using the following command:

    history -c

Setting Log Levels

Oracle Identity Manager uses log4j for logging. Logging levels are configured in the logging properties file, <XL_HOME>/xellerate/config/ By default, Oracle Identity Manager is configured to output at the Warning level—except for DDM, which is configured to output at the Debug level by default. You can change the log level universally for all components or for an individual component.

Oracle Identity Manager components are listed in the <XL_HOME>\xellerate\config\ file in the XELLERATE section, for example:


To set Oracle Identity Manager log levels, edit the logging properties in the <XL_HOME>\xellerate\config\ file as follows:

  1. Open the <XL_HOME>\xellerate\config\ file in a text editor. This file contains a general setting for Oracle Identity Manager and specific settings for the components and modules that comprise Oracle Identity Manager.

    By default, Oracle Identity Manager is configured to output at the Warning level:


    This is the general value for Oracle Identity Manager. Individual components and modules are listed following the general value in the properties file. You can set individual components and modules to different log levels. The log level for a specific component overrides the general setting.

  2. Set the general value to the desired log level. The following is a list of the supported log levels, appearing in descending order of information logged (DEBUG logs the most information and FATAL logs the least information):

    • DEBUG

    • INFO

    • WARN

    • ERROR

    • FATAL

  3. Set other component log levels as desired. Individual components or modules can have different log levels. For example, the following values set the log level for the Account Management module to INFO, while the server is at DEBUG and the rest of Oracle Identity Manager is at the WARN level.


  4. Save your changes.

  5. Restart your application server so that the changes take effect.

Enabling Single Sign-On (SSO) for Oracle Identity Manager

The following procedure describes how to enable Single Sign-On for Oracle Identity Manager with ASCII character logins. To enable Single Sign-On with non-ASCII character logins, use the following procedure—but include the additional configuration setting described in step 4.

See Also:

Oracle Identity Manager Best Practices Guide for additional information about configuring Single Sign-On for Oracle Identity Manager with Oracle Access Manager.


Header names comprised only of alphabetic characters are certified. Oracle recommends not using special characters or numeric characters in header names.

To enable Single Sign-On for Oracle Identity Manager:

  1. Stop the application server gracefully.

  2. Launch a plain-text editor and open the following file:


  3. Locate the following Single Sign-On configuration (the following are the default settings without Single Sign-On):

  4. Edit the Single Sign-On configuration to be the following and replace <SSO_HEADER_NAME> with the appropriate header configured in your Single Sign-On system:


    To enable Single Sign-On with non-ASCII character logins you must include a decoding class name to decode the non-ASCII header value. Add the decoding class name and edit the Single Sign-On configuration as follows:


    Replace <SSO_HEADER_NAME> with the appropriate header configured in your Single Sign-On system

  5. Change your application server and web server configuration to enable Single Sign-On by referring to your application and web server vendor documentation.

  6. Restart the application server.