scdscreate -V vendor-id -T resource-type-name -a [-s] [-n RT-version] [-d working-directory] [-k | -g]
The scdscreate command creates a template for making an application highly available (HA) or scalable. This command enables you to create C-, Generic Data Service (GDS)-, or Korn shell-based templates for both network aware (client-server model) and non-network aware (clientless) applications.
You can create the template in one of two fundamentally different ways:
scdscreate creates a set of three driving scripts that work from a single resource type SUNW.gds, which is preinstalled on the cluster. These scripts are named startRT-Name, stopRT-Name, and removeRT-Name and starts, stops, and removes an instance of that application. In this model, the implementation of the SUNW.gds resource type that is preinstalled on the cluster is immutable.
scdscreate creates a template for an Oracle Solaris 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, in which you can store configuration information for the resource type. scdscreate allows you to create only one resource type per directory. You must create different resource types in different directories.
The following options are supported:
This parameter specifies that the resource type that is being created is not network aware. scdscreate disables all the networking related code in the template that is created.
This optional parameter specifies the version of the generated resource's type. If you omit this parameter, and you're creating a C- or Korn shell-based application, the text string 1.0 is used by default. If you omit this parameter, and you're creating a GDS-based application, the RT_version string of the GDS is used by default. The RT-version distinguishes between multiple registered versions, or upgrades, of the same base resource type.
You cannot include the following characters in RT-version: blank, tab, slash (/), backslash (\), asterisk (*), question mark (?), comma (,), semicolon (;), left square bracket ([), or right square bracket (]).
Creates 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.
This optional parameter generates the GDS-based form of the template to make an application highly available or scalable.
This optional parameter generates source code in Korn shell command syntax rather than in C. See ksh (1) .
This optional parameter indicates that the resource type is scalable. You can 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.
The resource type name and resource type version, in conjunction with the vendor ID, uniquely identifies the resource type that is being created.
The vendor ID is typically the stock symbol, or some other identifier of the vendor that is creating the resource type. scdscreate affixes the vendor ID, followed by a period (.) to the beginning of the resource type name. This syntax ensures that the resource type name remains unique if more than one vendor uses the same resource type name.
The command completed successfully.
An error occurred.
Contains information from the previous session and facilitates the quit and restart feature of scdscreate.
See attributes (5) for descriptions of the following attributes: