JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Services Developer's Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information

Preface

1.  Overview of Resource Management

2.  Developing a Data Service

Analyzing the Application for Suitability

Determining the Interface to Use

Setting Up the Development Environment for Writing a Data Service

How to Set Up the Development Environment

Transferring a Data Service to a Cluster

Setting Standard Properties

Cluster Properties

Resource Type Properties

Resource Properties

Resource Group Properties

Resource Property Attributes

Node List Properties

Setting Resource and Resource Type Properties

Declaring Resource Type Properties

Declaring Resource Properties

Declaring Extension Properties

Implementing Callback Methods

Accessing Resource and Resource Group Property Information

Idempotence of Methods

How Methods Are Invoked in Zones

Generic Data Service

Controlling an Application

Starting and Stopping a Resource

Using Start and Stop Methods

Deciding Which Start and Stop Methods to Use

Using the Optional Init, Fini, and Boot Methods

Using the Init Method

Using the Fini Method

Guidelines for Implementing a Fini Method

Using the Boot Method

Monitoring a Resource

Implementing Monitors and Methods That Execute Exclusively in the Global Zone

Adding Message Logging to a Resource

Providing Process Management

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

Testing HA Data Services

Coordinating Dependencies Between Resources

Legal RGM Names

RGM Legal Names

Rules for Names Except Resource Type Names

Format of Resource Type Names

RGM Values

3.  Resource Management API Reference

4.  Modifying a Resource Type

5.  Sample Data Service

6.  Data Service Development Library

7.  Designing Resource Types

8.  Sample DSDL Resource Type Implementation

9.  Oracle Solaris Cluster Agent Builder

10.  Generic Data Service

11.  DSDL API Functions

12.  Cluster Reconfiguration Notification Protocol

13.  Security for Data Services

A.  Sample Data Service Code Listings

B.  DSDL Sample Resource Type Code Listings

C.  Requirements for Non-Cluster-Aware Applications

D.  Document Type Definitions for the CRNP

E.  CrnpClient.java Application

Index

Legal RGM Names

This section lists the requirements for legal characters for Resource Group Manager (RGM) names and values.

This section covers the following topics:

RGM Legal Names

RGM names fall into the following categories:

Rules for Names Except Resource Type Names

Except for resource type names, all names must comply with these rules:

Format of Resource Type Names

The format of the complete name of a resource type depends on the resource type, as follows:

A period separates vendor-id and base-rt-name. A colon separates base-rt-name and rt-version.

The variable elements in this format are as follows:

vendor-id

Specifies the vendor ID prefix, which is the value of the Vendor_id resource type property in the RTR file. If you are developing a resource type, choose a vendor ID prefix that uniquely identifies the vendor, such as your company's stock ticker symbol.

base-rt-name

Specifies the base resource type name, which is the value of the Resource_type resource type property in the RTR file.

rt-version

Specifies the version suffix, which is the value of the RT_version resource type property in the RTR file. The version suffix is only part of the complete resource type name if the RTR file contains the #$upgrade directive.


Note - If only one version of a base resource type name is registered, you do not have to use the complete name in administrative commands. You can omit the vendor ID prefix, the version number suffix, or both.


For more information, see Resource Type Properties.

Example 2-1 Complete Name of a Resource Type With the #$upgrade Directive

This example shows the complete name of a resource type for which properties in the RTR file are set, as follows:

The complete name of the resource type that is defined by this RTR file is as follows:

ORCL.sample:2.0

Example 2-2 Complete Name of a Resource Type Without the #$upgrade Directive

This example shows the complete name of a resource type for which properties in the RTR file are set, as follows:

The complete name of the resource type that is defined by this RTR file is as follows:

ORCL.abc

RGM Values

RGM values fall into two categories: property values and description values. Both categories share the same rules: