12 Troubleshooting Your Oracle Identity Manager Installation

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

• Oracle Identity Manager Installation Fails with a WebLogic Clustered Environment

• Task Scheduler fails in a Clustered Environment

• Default Login Not Working

Tip: You can use the Diagnostic Dashboard tool to assist when you troubleshoot your Oracle Identity Manager Installation. Refer to the Oracle Identity Manager Administrative and User Console for detailed information.

Oracle Identity Manager Installation Fails with a WebLogic Clustered Environment

The Oracle Identity Manager installation may fail within a WebLogic clustered environment when the wrong values are defined for the target server and server port number. You should not define the Admin Server as a target during the installation process, since the setup script needs to create the JMS Server on a cluster member.

Work Around Example

Use the following steps as an example to clean up the WebLogic services so that you can continue with the installation:

1. Open the WebLogic administration console to clean up the services that have been created for your cluster.

2. Select the JDBC tab and delete:

   1. The connection pools

   2. Both data sources

3. Select the JMS tab and delete:

   1. The xleConnectionFactory

   2. Every xlJDBCStore

   3. Every xlJMSServer

4. Open the <XL_HOME>\Profile\weblogic.profile file, then change the following:

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

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

5. Run the script setup_weblogic.cmd.

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

7. Once the setup script runs successfully, you must restart the 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 over by removing all installed Oracle Identity Manager products as well as the WebLogic domain.

Task Scheduler fails in a Clustered Environment

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

Default Login Not Working

If the default login is not working for the Design Console or Administrative and User Console and you are using an SQL Server, make sure that the Distributed Transaction Coordinator is running (it should have been set as a default).