The scdscreate command creates a template for making an application highly available (HA) or scalable. Use the first form for network aware (client-server model) applications. Use the second form for non-network aware (clientless) applications. See SYNOPSIS.

The template can be created in two fundamentally different models:

Generic Data Service (GDS)

scdscreate creates a set of three driving scripts which work off of a single resource type SUNW.gds pre-installed on the cluster. These scripts will be named as start{RT_Name}, stop{RT_Name}, and remove{RT_Name} and will start, stop and remove an instance of that application respectively. In this model the implementation of the SUNW.gds resource type pre-installed on the cluster is immutable.

Generated Source Code

scdscreate creates a template for a Sun Cluster resource type, whose instantiations run under the control of the Resource Group Manager (RGM) to make the given application highly available and scalable.

Either model can create templates for network aware (client-server model) and non-network aware (client-less) applications.

scdscreate creates a directory of the form ${vendor_id}${resource_type_name} under working_directory. This directory contains the driving scripts, or the generated source, binary, and package files for the resource type. scdscreate also creates a configuration file, rtconfig, to store the user supplied configuration information for the resource type. scdscreate allows the creation of one resource type per directory; different resource types must be created in different directories.

The following options are supported:

-a

This argument specifies that the resource type being created is not network aware. scdscreate disables all the networking related code in the template created. Note that it is not possible to enable fault probing for a non-network aware application. However, the application is started under the Process Monitor Facility (PMF), which monitors the application and restarts it if it fails to remain alive. See pmfadm(1M).

-d working_directory

Specify this optional argument to create the template for the resource type in a directory other than the current directory. If you omit this argument, scdscreate creates the template in the current directory.

-g

Specify this optional argument to generate the Generic Data Service form of template to make an application HA or scalable.

-k

Specify this optional argument to generate source code in Korn Shell rather than C. See ksh(1).

-s

Specifies this optional argument to indicate that the resource type is scalable. It is possible to configure an instance (resource) of a scalable resource type into a failover resource group, and hence, turn off the scalability feature. If you omit this argument, scdscreate creates the template for a failover resource type.

-T resource_type_name

The resource type name, in conjunction with the vendor id, uniquely identifies the resource type being created.

-V vendor_id

The vendor id is typically the stock symbol, or some other identifier of the vendor creating the resource type. scdscreate prefixes the vendor id, followed by a dot (.) to the resource type name. This ensures the uniqueness of the resource type name in the event that multiple vendors use the same name.

0

Successful completion.

>0

An error occurred.

working_directory/rtconfig

Contains information from the previous session; facilitates the tool's quit and restart feature.

See attributes(5) for descriptions of the following attributes:

ksh(1), scdsbuilder(1HA), scdsconfig(1HA), pmfadm(1M), attributes(5)