The scdsconfig command configures the resource type template previously created by scdscreate(1HA). There are two forms of this command. Use the first form for network aware (client-server model) applications. Use the second form for non-network aware (clientless) applications. See SYNOPSIS.

scdsconfig configures application specific commands to start, stop and probe the application. You can also use scdsconfig to set timeout values for the start, stop and probe commands. scdsconfig supports both network aware (client-server model) and non-network aware (client-less) applications. You can run scdsconfig from the same directory where scdscreate was run; alternatively, you can specify that directory using the -d option. scdsconfig configures the resource type template by plugging the user specified parameters at appropriate places in the generated code. If C was the type of generated source code, it compiles the code. scdsconfig puts everything into an installable Solaris package. It creates the package in the pkg subdirectory under the ${vendor_id}${resource_type_name} directory created by scdscreate.

The following options are supported:

-d working_directory

If scdsconfig is not run from the same directory where scdscreate was run, then this option is required to specify the directory where the resource type template was originally created.

-m probe_command

This optional parameter specifies a command to periodically check the health of the application. It must be a complete command line that can be passed directly to a shell to probe the application. The probe_command returns with an exit status of 0 if the application is OK. An exit status of greater than 0 indicates a failure of the application to perform correctly. In this event, the resources of this resource type will either be restarted on the same node or the resource group containing the resource will be failed over to another healthy node depending on the failure history of the application in the past.

-n probe_timeout

This optional parameter specifies the timeout, in seconds, for the probe command. The timeout must take into account system overloads to prevent false failures. The default value is 30 seconds.

-s start_command

The start command starts the application. It must be a complete command line that can be passed directly to a shell to start the application. You can include command line arguments to specify hostnames, port numbers, or other configuration data necessary to start the application. To create a resource type with multiple independent process trees, you specify a text file containing the list of commands, one per line, to start the different process trees.

-t stop_command

This optional parameter specifies the stop command for the application. It must be a complete command line that can be passed directly to a shell to stop the application. If you omit this option then the generated code stops the application via signals. The stop command is allotted 80% of the timeout value to stop the application. If it fails to stop it within this period a SIGKILL is allotted 15% of the timeout value to stop the application. If that also fails to stop the application, the stop method returns with an error.

-u start_method_timeout

This optional parameter specifies the timeout, in seconds, for the start command. The timeout must take into account system overloads to prevent false failures. The default value is 300 seconds.

-v stop_method_timeout

This optional parameter specifies the timeout, in seconds, for the stop command. The timeout must take into account system overloads to prevent false failures. The default value is 300 seconds.

The following exit values are returned:

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:

scdsbuilder(1HA), scdscreate(1HA), attributes(5)