- Take note of the location from which the IdentityMinder, SiteMinder, and SiteMinderAgent applications were deployed to the cluster.
The path appears in the WebLogic Admin Console under Deployments, application_name, Overview, Path.
- Back up all custom code.
The IdentityManager.ear found in step 1 is the one to back up, not the EAR from the staging area of any managed server.
- In the WebLogic Admin Console under Deployments, delete the IdentityMinder, SiteMinder and SiteMinderAgent applications.
- Shut down the weblogic server.
- On the admin server, delete the IdentityManager.ear, SiteMinder.ear, and SiteMinderAgent.ear folders from the location they were deployed from in r8.1 SP2.
- On each node, delete the IdentityManager, SiteMinder, and SiteMinderAgent folder from the staging area. They are in the following locations:
bea\weblogic92\common\nodemanager\servers\server_name\stage\IdentityMinder
bea\weblogic92\common\nodemanager\servers\server_name\stage\SiteMinder
bea\weblogic92\common\nodemanager\servers\server_name\stage\SiteMinderAgent
- Uninstall the Identity Manager Server.
This step leaves the Identity Manager environments and directories unchanged.
- If you are using a remote installation of SiteMinder and wish to continue to use it to protect your Identity Manager Environment, perform the following steps:
- Run the Identity Manager installer on that host to upgrade the Extensions for SiteMinder.
- Configure the Policy Store for CA Identity Manager.
Note: For more information about installing on a cluster, see the Installation Guide (Weblogic).
- Reinstall the Identity Manager Server, making sure you take the following actions:
- If you plan to continue to use SiteMinder, select Connect to Existing SiteMinder Policy Store on the Select Components screen.
- If you have different database stores for task persistence, workflow, audit, and reports, update the data sources to point to the separate stores.
- Configure all managed nodes using the Installation Guide procedure. However, in the last step of the Configure Managed Nodes procedure, replace the existing IM_SM_PATH definition line rather than adding a new line at the bottom of the file.
For example, in WL_HOME\weblogic92\common\bin\commEnv.cmd, the following line points to the old SiteMinder library:
IM_SM_PATH=%WL_HOME%\common\nodemanager\lib
Replace this line with the following line:
IM_SM_PATH=%WL_HOME%\common\nodemanager\servers\<server>\stage\IdentityMinder\IdentityMinder.ear\library
This complete path does not exist yet since you have not started the managed node since reinstalling Identity Manager.
- On the Admin Server, start WebLogic.
- In the Admin Console, start one managed node.
- Upgrade the workflow database.
- Export the Directories and Environments.
- Migrate the Task Persistence data.
- Recreate the Identity Manager Directories.
- Recreate the Identity Manager Environments.
Reapply all custom code, making sure you reapply all customizations to the cluster.
- Restart all managed nodes and verify the installation using the cluster section of the Installation Guide.