Installation Guides › WebSphere Version › Installation on a WebSphere Cluster › WebSphere Cluster Setup › Create Profiles for the Cluster

Create Profiles for the Cluster

You set up a WebSphere 6.1 cluster in the WebSphere Administrator Console.

To create profiles for the cluster

1. Decide which systems you plan to use for the cluster.
   1. Select a system for the WebSphere Deployment Manager. For best performance, the system should not be used as a node for cluster members.
   2. Determine the cluster member nodes.
2. Install the WebSphere Deployment Manager using the IBM WebSphere documentation for the most recent instructions.

   During the installation, note the directory where you install the Deployment Manager.

   1. Install the IBM WebSphere Application Server Network Deployment V6.1 software on the Deployment Manager machine.

      When the installation completes, you are prompted to configure a profile, a WebSphere runtime environment.

   2. Run the Profile Creation Wizard to create the profile for the Deployment Manager machine. When you are prompted to select a profile type, select the Deployment Manager profile.
   3. Start the Deployment Manager using one of the following methods:
      • Run the StartManager.bat (Windows) or StartManager.sh (Solaris) from a command prompt.

        These scripts are located in the bin directory where WebSphere is installed.

      • If you registered the Deployment Manager as a Windows Service, use Windows Services to start the Deployment Manager.
3. Install the IBM WebSphere Application Server Network Deployment V6.1 software on each cluster member.
4. Use the Profile Creation Wizard to create a Custom profile for each node.

   A Custom profile allows you to configure a connection to the Deployment Manager.

5. Start each node as follows:
   1. Navigate to was_home\WebSphere\AppServer\bin on the system where the managed node is located.
   2. Execute the startNode.bat\.sh command.

   Note: CA Identity Manager does not support HTTP session persistence in a clustered environment.

6. Confirm that a single cell has all the nodes associated with it at this location:

   was_home/profiles/Deployment_Manager_Profile/config/cells/Cell_Name/Nodes/
   

   You should see all federated nodes displayed as folder names.

Creation of profiles may sometimes fail if the bootstrap ports (default: 2809) are not unique. You can check for an error message in the pctLog.txt file in the created profiles' logs folder. For example:

(Oct 10, 2007 6:45:55 PM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPWSProfileLaunchAction, err, INSTCONFFAILED: Cannot complete required configuration actions after the installation. The configuration failed. The installation is not successful. Refer to C:\Program Files\IBM\WebSphere\AppServer\logs\wasprofile\wasprofile_create_CustomIMFromNode.log for more details.

Inspecting the wasprofile_create_CustomIMFromNode.log shows this failure was due to Bootstrap ports that is not unique.