Installation Guides › Upgrade Guide › CA Identity Manager Upgrade › Run the Upgrade Wizard › Upgrade the Identity Manager Server › Upgrade the Identity Manager Server with the Upgrade Wizard › Upgrade an Identity Manager Server on a WebSphere Cluster › If you upgraded WebSphere from 6.1.0.15 › Upgrading from CA Identity Manager r8.1 SP2 after Upgrade from WebSphere 6.1.0.15

Upgrading from CA Identity Manager r8.1 SP2 after Upgrade from WebSphere 6.1.0.15

Use this procedure if you upgraded your application server from WebSphere 6.1.0.15 and you are upgrading from CA Identity Manager r8.1. SP2.

To upgrade from CA Identity Manager r8.1 SP2

1. Perform the prerequisite steps.
2. Install the minimum supported version of WebSphere and the minimum supported JDK version.

   Note: See the CA Identity Manager support matrix on CA Support for the latest supported versions.

3. Remove all cluster members from the cluster except one cluster member.

   The remaining cluster member is referred to as the primary cluster member.

4. Shut down the remaining cluster member.
5. Stop the SiteMinder services.
6. If JAAS – J2C authentication aliases are used with Task Persistence data sources (JNDI name jdbc/idm) or Workflow data sources (JNDI name jdbc/WPDS), be sure to remove the association from those data sources, as follows:
   1. In the Administrative Console, go to Resources, JDBC, Data Sources.
   2. Open the data source.
   3. Locate the 'Component-managed authentication alias' section.
   4. Make note of the alias currently used and replace it with none.
   5. Repeat Steps a through d for the other data sources.
7. On the system where the Deployment Manager is installed, run the CA Identity Manager installer and launch the Upgrade Wizard.
8. Start the Deployment Manager.
9. If you performed Step 6, restore the JAAS – J2C authentication alias information previously used for Task Persistence data sources (JNDI name jdbc/idm) and Workflow data sources (JNDI name jdbc/WPDS), as follows:
   1. In the Administrative Console, go to Resources, JDBC, Data Sources.
   2. Open the data source.
   3. Locate the 'Component-managed authentication alias' section.
   4. Restore the alias information you noted in Step 6.
   5. Repeat Steps a through d for the other data sources.
10. Add back the cluster members, as follows:
    1. In the Administrative Console for the Deployment Manager, go to Servers, Clusters.
    2. Add a cluster member, selecting one of the nodes for which you created a profile.
    3. Repeat this procedure for each cluster member you need to add to the cluster.
11. Configure the message engines for each added cluster member that you added back to the cluster, as follows:

    Note: You do not need to configure the message engine for the primary cluster member.

    1. From the Deployment Manager, navigate to Websphere_home/profiles/deployment_manager_profile/bin.
    2. Execute wsadmin as follows:

       For Windows:

       wsadmin -f ims6SetupClusterMember.jacl node server cluster jndiname
       

       For Unix/Solaris:

       ./wsadmin -f ims6SetupClusterMember.jacl node server cluster jndiname
       

       Note: If you want to use the existing messaging store, use the same JNDI name that you used in the previous installation. If you are creating a messaging store, enter the new jndiname for that store.

    3. Verify that the script completes with a "Save the Configuration" message and no errors.
    4. Repeat Steps b and c for each added cluster member.
12. Verify the message store information, as follows:
    1. In the Administrative Console, go to Service Integration, IMSBus.
    2. For each message engine, verify the following message store information:
       • The data source JNDI name is a JNDI name of an existing data source
       • The schema name is an existing schema name in the database associated with this data source.

         The default IBMWSSIB may not work, for example, 'dbo' for MS SQL.

    3. Verify that the Core Group policy exists for each messaging engine, and that each cluster member has a messaging engine targeted to it through the policy's preferred server.

       Note: For more information about creating core group policies, see the Installation Guide.

13. Configure the messaging engine stores for each cluster member, as follows:
    1. In the Administrative Console, go to Service Integration, Buses, IMSBus, Messaging engines, select the messaging engine name, and click message store.
    2. Change the schema name for the messaging engine store to the database schema name.
    3. If you are using existing messaging stores, run the following commands on the database for each messaging store you reuse:
       • truncate table SIB000
       • truncate table SIB001
       • truncate table SIB002
       • truncate table SIBXACTS
       • truncate table SIBKEYS
       • truncate table SIBOWNER
       • truncate table SIBOWNERO
       • truncate table SIBCLASSMAP
       • truncate table SIBLISTING
14. Update the WebSphere Path definition for each cluster member, for example, if you have clusterMember1 and clusterMember2, update as follows:
    1. In the Administrative Console, go to Application servers, clusterMember1, Server Infrastructure, Java and process definition, Process Definition, Environment Entries.
    2. Add the full path to the IdentityMinder.ear/library directory. For example, on Windows, the path may be: C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv02\installedApps\wasserverCell01\IdentityMinder.ear/ library
    3. Repeat Steps a and b for clusterMember2.
15. Restore any customizations to the cluster.
16. Perform post-upgrade configurations.