Installation Guide › WebSphere Version › Installation on a WebSphere Cluster › How to Install CA IdentityMinder on a WebSphere Cluster › Run the Installation from the Deployment Manager

Run the Installation from the Deployment Manager

Once you have created the WebSphere cluster, you can install CA IdentityMinder on it. To install the CA IdentityMinder on all cluster members, you use this procedure and the procedures that follow it.

Note: At previous releases of CA IdentityMinder, creating a message store and message engine was a manual process. At this release, you create an empty message store database and supply that database name when you run the CA IdentityMinder installer. WebSphere then populates the message store table, creates the message engine, and deploys the CA IdentityMinder application ear and binaries to each node in the cluster.

Follow these steps:

1. Perform these steps if you are using Microsoft SQL server:
   1. Open SQL Management Studio.
   2. Locate the user who owns the message store database.
   3. Set that user's default schema to dbo.  
2. Log into the system with the Deployment Manager.
   • On Windows, log in as the Windows Administrator.
   • On UNIX, log in as root.
3. Stop the first cluster member, the only cluster member that you have configured so far.
4. Start the Node Agent for that cluster member.
5. Stop the WebSphere Deployment Manager.
6. On the system that hosts the Deployment Manager, run the CA IdentityMinder installation.
   • Windows: From your installation media, run the following program:

     ca-im-release-win32.exe
     

   • UNIX: From your installation media, run the installation program. For example, for Solaris:

     ca-im-release-sol.bin
     

   release represents the current release of CA IdentityMinder.

   Important! Be sure that you have the collected the information needed by the installer, such as user names, host names, and ports.

7. Complete the Select Components section by including the CA IdentityMinder Server and any other components that you need on this system.

   Note: If you see options to upgrade the workflow database and migrate task persistence data, enable those options. They appear in some scenarios when your previous installation was CA Identity Manager r12.

8. When you enter any password or shared secret in the installation, be sure to provide a password that you can recall when needed.

   

9. Complete the other sections based on your requirements for the installation.

   The WebSphere section includes these fields:

   WebSphere Install Folder

   The folder or directory where WebSphere is installed. You find this location in the Windows or UNIX file system.

   Server Name

   The first cluster member in the WebSphere cluster. You find this name in the WebSphere console.

   Profile Name

   The deployment manager profile. You find this name in the Windows or UNIX file system at the path:

   was_home/profiles/Deployment_Manager_Profile

   Cell Name

   The deployment manager's cell which can be found in the WebSphere console.

   Note: Cell names are case sensitive in all operating systems. Be sure to use the correct case.

   Node Name

   A node that contains the Server Name you supplied on this screen. You find this name in the WebSphere console.

   Note: Node names are case sensitive in all operating systems. Be sure to use the correct case.

   Cluster Name

   The name of the cluster. You find this name in the WebSphere console.

   Access URL and port

   The URL and port number of the Web Server used for load balancing.

   

10. Complete the Message Store section. The installer creates a JDBC data source as the Message Engine message store based on the following information you provide:
    • Hostname
    • Port
    • Database name

      Enter the message store database.

    • Username

      Enter the user who owns the message store database.

    • Password
    • Schema name

      For Microsoft SQL Server, enter dbo.

      For Oracle, enter the user who owns the message store database.

If any issues occur during installation, inspect the installation logs.

Important! Do not start the cluster yet, as it will not function. Complete the remaining procedures, which conclude with the steps to start the cluster.