7 Post-Installation Configuration for Oracle Identity Manager and WebLogic

After you have installed Oracle Identity Manager, you must complete some post-installation tasks before you can use the application. Some of the post-installation tasks are optional, depending on your deployment, before using the applications.

This chapter discusses the following topics:

• Required Post-Installation Tasks for WebLogic

• Optional Post-installation Tasks

Required Post-Installation Tasks for WebLogic

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

Configuring WebLogic for Oracle Identity Manager

After you install Oracle Identity Manager, you must set the memory size, set up the authentication information for Oracle Identity Manager, then create and configure an XML registry.

Note: If you are configuring WebLogic for Oracle Identity manager in a clustered environment, start the following procedure on step 7.

To configure WebLogic for Oracle Identity Manager:

1. Use the WebLogic administration console to shut down the application server gracefully.

2. Navigate to <BEA_HOME>\user_projects\domains\<domain_name> (for example, C:\bea\user_projects\domains\mydomain).

3. Open the WebLogic start script file in a text editor. The start script is:

   • On Windows:

     startWebLogic.cmd

   • On Solaris:

     startWebLogic.sh

4. Edit the script to specify memory options:

   For Windows:

   Locate the line that starts with the following:

   %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS%
   
   

   Add the following line just before it:

   set MEM_ARGS=-Xmx1024m -XX:PermSize=128m
   
   

   For UNIX:

   Locate the line that starts with the following:

   ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}
   
   

   Add the following lines just before it:

   MEM_ARGS="-Xmx1024m -XX:PermSize=128m"
   export MEM_ARGS
   
   

5. Save and close the file.

6. Restart the WebLogic server by navigating to the following directory:

   <XL_HOME>\xellerate\bin\

   Run the following command on Windows:

   xlStartServer.bat

   Run the following command on UNIX:

   xlStartServer.sh

7. Log in to the WebLogic administration console.

8. In the left frame, select Security, select Realms, select myrealms, select Providers, then select Authentication.

9. Click Configure a new Xellerate Authenticator.

   1. Leave Name as the default.

   2. Set the Control Flag to Sufficient, then click Create.

10. In the left frame, click Authentication and select DefaultAuthenticator.

    1. Set the Control Flag to Sufficient, then click Apply.

11. In the left frame, click Services.

12. Right-click XML, then select Configure a new XMLRegistry from the short-cut menu.

13. Enter the registry information:

    1. Enter a unique name, for example, Oracle Identity Manager XML registry.

    2. Use default values for the other fields, then click Create.

14. Click the Target and Deploy tab.

    1. Click the server check box to select it (myserver is the default server name).

    2. Click Apply.

       
       

       Note: For clustered environments, be sure perform this step on all cluster members.

       
       

15. In the left-hand frame, click XML, then click your new XML registry entry to expand it.

16. Right-click Parser Select Entries, then select Configure a New XMLPareserSelectRegistryEntry from the short-cut menu.

17. Enter the configuration information:

    1. Make sure the Public ID field is blank.

    2. Make sure the System ID field is blank.

    3. In the Root Element Tag field, enter the word "database" without quotation marks.

    4. In the Document Builder Factory field, enter the following string:

       org.apache.crimson.jaxp.DocumentBuilderFactoryImpl

    5. Make sure the Parser Class Name field is blank.

    6. In the SAX Parser Factory field, enter the following string:

       org.apache.xerces.jaxp.SAXParserFactoryImpl

    7. Click Create.

18. Stop the WebLogic application server gracefully.

19. If you are using an Oracle database, copy the ojdbc14.jar file from <XL_HOME>\xellerate\ext\ to <BEA_HOME>\weblogic81\server\lib\.

    For clustered environments, copy the ojdbc14.jar file to <BEA_HOME>\weblogic81\server\lib\ on each of the XLMANAGED_SERVER_HOST nodes in the cluster.

20. Restart the WebLogic Server for the new configuration to become active.

Note: If you are using SQL Server as your database and the Oracle Identity Manager server log shows traces of exceptions related to MS JDBC classes, you must add three MS JDBC files to the beginning of CLASSPATH in the startWebLogic script located in the domain directory and restart the server. Add the following three files, located in the /weblogic81/server/lib/ directory, to the beginning of CLASSPATH in the startWebLogic script and restart the server: mssqlserver.jar msbase.jar msutil.jar In a clustered environment, add these three .jar files in the Class Path field in the Remote Start tab of all Managed Servers.

Configuring XA Connection Settings

After you install Oracle Identity Manager on WebLogic, you must set up an XA connection.

To set up an XA connection:

1. Log in to the WebLogic administrative console, and select Services.

2. Select JDBC on the Services page.

3. Select Connection Pools on the JDBC page.

4. Select xlXAConnectionPool on the Connection Pools page.

5. Select the Connections tab.

6. Select Show under Advanced Options.

7. Select Keep XA Connection Till Transaction Complete.

8. Click Apply to commit your changes.

9. Restart your WebLogic application server.

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
   <JAVA_HOME>	Location of the Java directory associated with the application server
   <new_password>	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.

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

   
   

   Note: 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, you could change the following block:

     <Security>
     <XLPKIProvider>
     <KeyStore>
              <Location>.xlkeystore</Location>
              <Password encrypted=ÓtrueÓ>xYr5V2FfkRYHxKXHeT9dDg==</Password>
              <Type>JKS</Type>
              <Provider>sun.security.provider.Sun</Provider>
     </KeyStore>
     
     

     To the following:

     <Security>
     <XLPKIProvider>
     <KeyStore>
           <Location>.xlkeystore</Location>
           <Password encrypted="false">newpassword
           </Password>
           <Type>JKS</Type>
           <Provider>sun.security.provider.Sun</Provider>
     </KeyStore>
     
     

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.

Setting Log Levels

Oracle Identity Manager uses log4j for logging. Logging levels are configured in the logging properties file, <XL_HOME>/xellerate/config/log.properties.

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

By default, Oracle Identity Manager is configured to output at the Warning level. 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\log.properties file in the XELLERATE section, for example:

log4j.logger.XELLERATE=WARN
log4j.logger.XELLERATE.DDM=DEBUG
log4j.logger.XELLERATE.ACCOUNTMANAGEMENT=DEBUG
log4j.logger.XELLERATE.SERVER=DEBUG
log4j.logger.XELLERATE.RESOURCEMANAGEMENT=DEBUG
log4j.logger.XELLERATE.REQUESTS=DEBUG
log4j.logger.XELLERATE.WORKFLOW=DEBUG
log4j.logger.XELLERATE.WEBAPP=DEBUG
log4j.logger.XELLERATE.SCHEDULER=DEBUG
log4j.logger.XELLERATE.SCHEDULER.Task=DEBUG
log4j.logger.XELLERATE.ADAPTERS=DEBUG
log4j.logger.XELLERATE.JAVACLIENT=DEBUG
log4j.logger.XELLERATE.POLICIES=DEBUG
log4j.logger.XELLERATE.RULES=DEBUG
log4j.logger.XELLERATE.DATABASE=DEBUG
log4j.logger.XELLERATE.APIS=DEBUG
log4j.logger.XELLERATE.OBJECTMANAGEMENT=DEBUG
log4j.logger.XELLERATE.JMS=DEBUG
log4j.logger.XELLERATE.REMOTEMANAGER=DEBUG
log4j.logger.XELLERATE.CACHEMANAGEMENT=DEBUG
log4j.logger.XELLERATE.ATTESTATION=DEBUG
log4j.logger.XELLERATE.AUDITOR=DEBUG

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

1. Open the <XL_HOME>\xellerate\config\log.properties 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:

   log4j.logger.XELLERATE=WARN

   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.

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.

   log4j.logger.XELLERATE=WARNlog4j.logger.XELLERATE.ACCOUNTMANAGEMENT=INFOlog4j.logger.XELLERATE.SERVER=DEBUG

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: OracleMetaLink Note 394670.1 for additional information about configuring Single Sign-On for Oracle Identity Manager with Oracle Access Manager. You can access the OracleMetaLink Web site at: https://metalink.oracle.com/

Note: 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:

   <XL_HOME>\xellerate\config\xlconfig.xml

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

   <web-client>
   <Authentication>Default</Authentication>
   <AuthHeader>REMOTE_USER</AuthHeader>
   </web-client>
   
   

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:

   <web-client>
   <Authentication>SSO</Authentication>
   <AuthHeader><SSO_HEADER_NAME></AuthHeader>
   </web-client>
   
   

   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:

   <web-client>
   <Authentication>SSO</Authentication>
   <AuthHeader><SSO_HEADER_NAME></AuthHeader>
   <AuthHeaderDecoder>com.thortech.xl.security.auth.CoreIDSSOAuthHeaderDecoder</AuthHeaderDecoder>
   </web-client>
   
   

   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.