Installation Guides › Upgrade Guide › CA Identity Manager Upgrade › Main Upgrade Procedures › Upgrade the Identity Manager Server › Upgrade on a WebLogic 9.2 Cluster

Upgrade on a WebLogic 9.2 Cluster

Important! Use this procedure only if you were referred here by Select the Right Upgrade Procedure.

Upgrading the Identity Manager server on a WebLogic 9.2 cluster depends on the current installation.

• For an 8.1 SP2 Identity Manager server, the r8.1 SP2 Identity Manager Server on WebLogic 9.2 procedure applies.
• For an r12 or higher Identity Manager Server, see the steps that follow.

To upgrade the Identity Manager Server r12 or higher on a WebLogic 9.2 cluster

1. Perform the prerequisite steps.
2. Shut down all the managed nodes.
3. In the Weblogic Admin Console, under Deployments, delete castylesr5.1.1.ear.
4. Shut down the application server.
5. On the admin server, delete the castylesr5.1.1.ear folder from this location:

   bea\userprojects\domains\domain-name\applications
   

6. On each node, delete the Identity Manager EAR folder from the staging area:

   bea\weblogic92\common\nodemanager\servers\server_name\stage\
   

7. On each node, delete the Identity Manager EAR folder from the WebLogic cache:

   bea\weblogic92\common\nodemanager\servers\server_name\tmp\_WL_user\
   

8. Stop the SiteMinder services, if you are using SiteMinder.
9. Run the CA Identity Manager installer from the system where the previous CA Identity Manager installation was run.

   Note: For more information about installing on a cluster, see the Installation Guide (WebLogic).

10. Start WebLogic on the Admin Server.
11. Configure each managed node using the Configure Managed Nodes procedure in the Weblogic cluster section of the Installation Guide.
12. On each node, verify that all subdeployments point to the JMS servers that existed prior to the upgrade.
    1. Target GeneralMonitorCFdeployment subdeployment to each of the IM JMS servers. Associate GeneralMonitorCFdeployment with these resources:
       • GeneralMonitorCF
       • IMS Events
       • Run time status
       • Server Command Topic
       • General Monitor Messages
    2. If you have workflow, set wpConnectionFactory subdeployment to point to the Workflow JMS servers.

       wpConnectionFactory associates with the resources queue/wpServAutoActQueue, queue/wpUtilQueue, queue/wpEventQueue, and jms/wpConnectionFactory.

13. Optionally, migrate the task persistence data.
14. Restore all customizations to the cluster.
15. Update the new index.jsp.

    For more information, see the User Console Design Guide.

16. Start all the managed nodes from the Weblogic admin console.

    Starting the server first time after the upgrade generates workpoint errors. However, proceed with this step. Deploying the application on all nodes makes modifying the configuration easier.

17. If the nodes are not running on the default port, update the workpoint-client.properties file under identityMinder.ear/config on each node. Replace localhost with the hostnames of the system where the node is installed.