Connection Timeout to Provisioning Server During Startup After Migration

Products

• CA Identity Manager

Issue/Introduction

This article addresses startup failures in CA Identity Manager (IDM) following an upgrade or migration, specifically when the application server fails to connect to the Provisioning Server due to incorrect port or server configurations remaining from the previous environment.

When starting the Application Server after an IDM migration, the system fails to initialize, citing a javax.naming.CommunicationException with a connection timeout error. The logs indicate the system is attempting to connect to a non-standard port (e.g., 20490) associated with the legacy Provisioning Server instead of the new environment.

Environment

• Product: CA Identity Manager
• Release: 14.4

Cause

Post-migration, the IDM object store database (IM_DIR_CONNECTION table) may retain references to the old Provisioning Server's host and port. These settings override the new configuration.

Resolution

To resolve this issue, update the connection configuration within the Identity Manager object store database:

1. Stop the Identity Manager Application Server.
2. Query the IDM object store database to view the current configuration: SELECT * FROM IM_DIR_CONNECTION;
3. Identify the row corresponding to the Provisioning Server connection.
4. Update the record to reflect the correct hostname and port of the new Provisioning Server.
   • Example: Update the PORT and HOST values to match the new infrastructure (e.g., port 20390).
5. Restart the Identity Manager Application Server to apply the changes.

Additional Information

Modifying database tables directly should be done with caution. Always back up the database before making manual updates.