1. Overview of Resource Management
Analyzing the Application for Suitability
Determining the Interface to Use
Setting Up the Development Environment for Writing a Data Service
Setting Resource and Resource Type Properties
Declaring Resource Type Properties
Declaring Resource Type Properties for a Zone Cluster
Declaring Extension Properties
Accessing Resource and Resource Group Property Information
How Methods Are Invoked in Zones
Starting and Stopping a Resource
Deciding Which Start and Stop Methods to Use
Using the Optional Init, Fini, and Boot Methods
Guidelines for Implementing a Fini Method
Implementing Monitors and Methods That Execute Exclusively in the Global Zone
Adding Message Logging to a Resource
Providing Administrative Support for a Resource
Implementing a Failover Resource
Implementing a Scalable Resource
Validation Checks for Scalable Services
Writing and Testing Data Services
Using TCP Keep-Alives to Protect the Server
Coordinating Dependencies Between Resources
3. Resource Management API Reference
6. Data Service Development Library
8. Sample DSDL Resource Type Implementation
9. Solaris Cluster Agent Builder
12. Cluster Reconfiguration Notification Protocol
B. Sample Data Service Code Listings
C. DSDL Sample Resource Type Code Listings
E. Requirements for Non-Cluster Aware Applications
F. Document Type Definitions for the CRNP
Before you begin to develop your data service, you must install the Solaris Cluster development package (SUNWscdev) to have access to the Solaris Cluster header and library files. Although this package is already installed on all cluster nodes, you typically develop your data service on a separate, non-cluster development machine, rather than on a cluster node. In this typical case, you must use the pkgadd command to install the SUNWscdev package on your development machine.
Note - On the development machine, ensure that you are using the Developer or Entire Distribution software group of the Solaris 10 OS.
When compiling and linking your code, you must set particular options to identify the header and library files.
Note - You cannot mix compatibility-mode compiled C++ code and standard-mode compiled C++ code in the Solaris Operating System and Solaris Cluster products. Consequently, if you intend to create a C++ based data service for use on Solaris Cluster, you must use the standard mode to compile that data service.
When you have finished development (on a non-cluster node), you can transfer the completed data service to a cluster for testing.
The procedures in this section describe how to complete the following tasks:
Install the Solaris Cluster development package (SUNWscdev) and set the correct compiler and linker options.
Transfer the data service to a cluster.
This procedure describes how to install the SUNWscdev package and set the compiler and linker options for data service development.
# cd cd-rom-directory
# pkgadd -d . SUNWscdev
Specify the -I option to identify the Solaris Cluster header files, the -L option to specify the compile-time library search path on the development system, and the -R option to specify the library search path to the runtime linker in the cluster.
# Makefile for sample data service ... -I /usr/cluster/include -L /usr/cluster/lib -R /usr/cluster/lib ...
When you have completed the data service on a development machine, you must transfer the data service to a cluster for testing. To reduce the chance of error during the transfer, combine the data service code and the RTR file into a package. Then, install the package on the Solaris hosts on which you want to run the service.
Note - Agent Builder creates this package automatically.