The following table summarizes the tasks for installing and configuring Sun Cluster HA for Sun Java System Application Server EE (HADB) and provides cross-references to detailed instructions for performing these tasks. Perform the tasks in the order that they are listed in the table.
Table 1–1 Tasks for Installing and Configuring Sun Cluster HA for Sun Java System Application Server EE (HADB)
Task |
For Instructions |
---|---|
Plan the installation and configuration of Sun Cluster HA for Sun Java System Application Server EE (HADB) | |
Install and configure the Sun Java System Application Server EE (HADB) software |
Installing and Configuring the Sun Java System Application Server EE (HADB) Software |
Create a Sun Java System Application Server EE (HADB) management domain |
Creating a Sun Java System Application Server EE (HADB) Management Domain |
Install the Sun Cluster HA for Sun Java System Application Server EE (HADB) package |
Installing the Sun Cluster HA for Sun Java System Application Server EE (HADB) Package |
Register and configure Sun Cluster HA for Sun Java System Application Server EE (HADB) as a data service mastered on multiple nodes at one time |
Registering and Configuring the Sun Cluster HA for Sun Java System Application Server EE (HADB) |
Verify the installation and configuration of Sun Cluster HA for Sun Java System Application Server EE (HADB) | |
Tune the fault monitor for Sun Cluster HA for Sun Java System Application Server EE (HADB) |
Tuning the Fault Monitor for Sun Cluster HA for Sun Java System Application Server EE (HADB) |
If you run multiple data services in your Sun Cluster configuration, you can set up the data services in any order, with the following exception. If Sun Cluster HA for Sun Java System Application Server EE (HADB) depends on the Sun Cluster HA for DNS, you must set up DNS first. For details, see Sun Cluster Data Service for DNS Guide for Solaris OS. DNS software is included in the Solaris software. If the cluster is to obtain the DNS service from another server, configure the cluster to be a DNS client first.