12 Troubleshooting the Oracle Identity Manager Installation

This section describes the following problems that can occur during the Oracle Identity Manager installation:

• Oracle Identity Manager Installation Fails During Installation in a BEA WebLogic Server Cluster

• Task Scheduler Fails in a Clustered Installation

• Default Login Does Not Work

Note:

You can use the Diagnostic Dashboard tool for assistance when you troubleshoot the Oracle Identity Manager Installation. See Oracle Identity Manager Administrative and User Console Guide for detailed information.

Oracle Identity Manager Installation Fails During Installation in a BEA WebLogic Server Cluster

The Oracle Identity Manager installation will fail during installation in a BEA WebLogic Server cluster if incorrect values are defined for the target server and server port number. Do not define the Administrative Server as a target during the installation process; the setup script must create the JMS Server on a cluster member.

Workaround Example

The following is a sample procedure to clean up the BEA WebLogic Server services so that you can continue with the installation:

1. Open the WebLogic Server Administration Console to clean up the services that have been created for the cluster.

2. Select the JDBC tab and delete:

   • The connection pools

   • Both the data sources

3. Select the JMS tab and delete:

   • The xleConnectionFactory

   • Every xlJDBCStore

   • Every xlJMSServer

4. Open the OIM_HOME\Profile\weblogic.profile file, and then change the following:

   1. The BEA WebLogic Server target name from myserver to <cluster_member1>.

   2. The BEA WebLogic Server target port from 7001 to 7051.

5. Run the setup_weblogic.cmd script.

6. Review the log file to see that it runs successfully.

7. When the setup script runs successfully, restart BEA WebLogic Server.

You can either continue with your installation (restart the Oracle Identity Manager Installer at this point), or start the Oracle Identity Manager installation by removing all installed Oracle Identity Manager products as well as the WebLogic domain.

Task Scheduler Fails in a Clustered Installation

The Task Scheduler fails to work properly when the cluster members, which are computers that are part of the cluster, have different settings on their system clocks. Oracle recommends that the system clocks for all cluster members be synchronized within a second of each other.

Default Login Does Not Work

If the default login is not working for the Design Console or Administrative and User Console and you are using Microsoft SQL Server, then ensure that the Distributed Transaction Coordinator is running.

Note:

Microsoft SQL Server is not supported in Oracle Identity Manager release 9.1.0. See ÒCertified ComponentsÓ in Oracle Identity Manager Release Notes for information about certified components.