Oracle^® Solaris Cluster Generic Data Service (GDS) Guide

How to Use the Command-Line Version of Agent Builder to Create a Service That Uses GDS

This section describes how to use the command-line interface to perform the same set of steps shown earlier in this chapter.

1. Become an administrator that provides solaris.cluster.modify authorization.
2. Create the service by performing one of the following steps.

   • Create a failover service.

     # scdscreate -g -V NET -T app -d /export/wdir

   • Create a scalable service.

     # scdscreate -g -s -V NET -T app -d /export/wdir

   ---

   Note -  The –d argument is optional. If you do not specify this argument, the current directory becomes the working directory.

   ---

3. Configure the service.

   # scdsconfig -s "/export/app/bin/start" \
   -e "/export/app/bin/configtest" \
   -t "/export/app/bin/stop" \
   -m "/export/app/bin/probe" -d /export/wdir

   You can specify property variables. Property variables are described in Using Property Variables in Oracle Solaris Cluster Data Services Developer’s Guide .

   ---

   Note -  Only the start command (scdsconfig -s) is required. All other options and arguments are optional.

   ---

4. On each node of the cluster, install the completed package.

   # cd /export/wdir/NETapp/pkg
   # pkgadd -d . NETapp

   ---

   Note -  This instruction applies to the SVR4 package that Agent Builder creates. If you need an IPS version of the package, use the pkgsend command to convert your SVR4 agent package to an IPS package, and use the pkg add command to install the IPS package. For more information, see the pkgsend (1) and pkg (1) man pages.

   ---

   The following files are installed by pkgadd:

   /opt/NETapp
   /opt/NETapp/README.app
   /opt/NETapp/man
   /opt/NETapp/man/man1m
   /opt/NETapp/man/man1m/removeapp.1m
   /opt/NETapp/man/man1m/startapp.1m
   /opt/NETapp/man/man1m/stopapp.1m
   /opt/NETapp/man/man1m/app_config.1m
   /opt/NETapp/util
   /opt/NETapp/util/removeapp
   /opt/NETapp/util/startapp
   /opt/NETapp/util/stopapp
   /opt/NETapp/util/app_config

   ---

   Note -  The man pages and script names correspond to the application name that you typed previously on the Create screen, preceded by the script name (for example, startapp).

   ---

5. On one node of the cluster, configure the resources and start the application.

   # /opt/NETapp/util/startapp -h logicalhostname -p port-and-protocol-list

   The arguments to the startapp script vary according to the type of resource: failover or scalable.

   ---

   Note -  To determine the command line that you need to type, check the customized man page or run the startapp script without any arguments to display a usage statement.

   To view the man pages, you need to specify the path to the man page. For example, to view the startapp(1M) man page, type:

   # man -M /opt/NETapp/man startapp

   To display a usage statement, type:

   # /opt/NETapp/util/startapp
   The resource name of LogicalHostname or SharedAddress must be specified.
   For failover services:
   Usage: startapp -h logicalhostname
   -p port-and-protocol-list
   [-n ipmpgroup/adapter-list]
   For scalable services:
   Usage: startapp -h shared-address-name
   -p port-and-protocol-list
   [-l load-balancing-policy]
   [-n ipmpgroup/adapter-list]
   [-w load-balancing-weights]

   ---