Sun Cluster Software

Sun Cluster software is installed to satisfy local dependencies. Some components in a solution might use Sun Cluster software to satisfy quality of service requirements. On these computers, the Sun Cluster software must be installed, configured, and verified before the components that run in the cluster are installed. Typically, Sun Cluster software is installed when solution-level dependences dictate the installation of the components that run in the cluster.

Sun Cluster software itself has no dependencies on other components so it can be installed and configured at any time during the installation and configuration of a distributed solution.

Basic Installation Procedures for Sun Cluster Software

The basic steps for installing and configuring Sun Cluster software are the following:

1. Before attempting to install Sun Cluster software, make sure that the shared external storage has been attached and configured. This is typically done as part of implementing the network connectivity specifications. For more information, see Developing a Network Connectivity Specification.

2. Use the Java ES installer to install Sun Cluster core software on all computers systems specified in your deployment architecture. Do not install the components that run in the cluster at this time.

3. Configure the computers, including running the Sun Cluster configuration utility.

4. Run the Java ES installer a second time and install the components that run in the cluster. These are typically Messaging Server and/orCalendar Server. Install these components only on the first computer in the cluster.

5. Run the Directory Preparation Tool, and configure the component instances, including configuring them for single sign-on.

6. Verify the component instances.

7. Run the Java ES installer a third time. Install the Sun Cluster Agent for Messaging Server and/or Sun Cluster Agent for Calendar Server.

8. Use the agents to configure component resources, add the resources to the resource group, and enable the resources.

9. Test the failover capability of the resources.

Choosing Configuration Values for Sun Cluster

For each Sun Cluster node in your solution, you must input values that configure the instance to interoperate with the other computers in the cluster. For information on choosing configuration values, see Chapter 2, Installing and Configuring Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS.

Adding Installation Instructions for Sun Cluster to Your Plan

For detailed information on installing Sun Cluster software that, see Sun Cluster Software Example in Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

To add installation and configuration instructions for Sun Cluster software, do the following:

1. Before attempting to install Sun Cluster, software make sure that the shared external storage has been attached and configured. This is typically done as part of implementing the network connectivity specifications. For more information, see Developing a Network Connectivity Specification.

2. Use the Java ES installer to install Sun Cluster Core on all computers systems specified in your deployment architecture. Do not install the components that run in the cluster at this time.

3. Prepare the computers for Sun Cluster configuration. This includes adding file systems to the shared storage, setting up mount points, and mounting these file systems.

4. Run the Sun Cluster configuration utility on the first computer to establish the cluster. Supply configuration values suitable for the expected load. After configuration, reboot the computer.

5. Complete the configuration of Network Timing Protocol on all computers in the cluster.

   1. When you configure Messaging Server you must specify the Directory Server instance where information about Messaging Server users is stored.

   2. When you configure Messaging Server you supply the name of the LDAP directory branch that will represent the email domain managed by the Messaging Server instance. The Messaging Server configuration wizard adds this branch to the tree.

6. Add a quorum device to the cluster.

7. Set up cluster disks and mirroring.

8. Create new cluster file systems and mount the corresponding global directories.

9. Create a cluster resource group and associate it with a virtual host name and IP address.

10. Test failover of the cluster resource group.

11. Run the Java ES installer a second time and install the components that run in the cluster. These are typically Messaging Server and/orCalendar Server. Install these components only on the first computer in the cluster.

12. Run the Directory Preparation Tool, as described in Messaging Server.

13. If Messaging Server is installed in the cluster, run the Messaging Server configuration wizards, as described in Messaging Server.

14. If Messaging Server is installed in the cluster, configure Messaging Server for single sign-on.

15. If Messaging Server is installed in the cluster, start the Messaging Server instance.

16. Verify the Messaging Server instance.

17. If Calendar Server is installed in the cluster, run the Calendar Server configuration wizard, as described in Calendar Server.

18. If Calendar Server is installed in the cluster, create a calendar server administration user, user group and directory on the other computers in the cluster. (The configuration wizard did this on the first computer in the cluster.)

19. If Calendar Server is installed in the cluster, configure the Calendar Server instance for single sign-on.

20. If Calendar Server is installed in the cluster, start the Calendar Server instance.

21. Verify the Calendar Server instance.

22. Run the Java ES installer a third time. Select the Sun Cluster Agent for Messaging Server and/or Sun Cluster Agent for Calendar Server.

23. Use the Messaging Server agent to configure a Messaging Server resource, add it to the resource group, and enable it.

24. Test the failover capability of the Messaging Server resource.

25. Use the Calendar Server agent to configure a Calendar Server resource, add it to the resource group, and enable it.

26. Test the failover capability of the Calendar Server resource.