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

Language:

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

Assume the root role or a role that provides solaris.cluster.modify RBAC authorization.
Create the service by performing one of the following steps.
- Create a failover service.
```
# scdscreate -G -V vendor -T app appname \
[-d working directory] \
[-c] [-p]
```
- Create a scalable service.
```
# scdscreate -G -s -V vendor -T app appname \
[-d working directory] \
[-c] [-p]
```
- The –d argument is optional. If you do not specify this argument, the current directory becomes the working directory.
- The –c argument is optional. If set, a subclassed GDSv2 resource type is created.
- The –p argument is optional. If set, a proxy GDSv2 resource type is created.
Note - If the –c argument is selected and the –p argument is not selected, then a subclassed ORCL.gds resource type is created. If the –c and –p arguments are selected, then a subclassed ORCL.gds_proxy resource type is created.
Configure the service.
- For a non-proxy service, type:
```
# scdsconfig -s "path to your start command" \
[-d working directory] \
[-e "path to your validate command"] \
[-t "path to your stop command"] \
[-m "path to your probe command"] \
[-l "interpose logical hostname"] \
-p
```
- For a proxy service, type:
```
# scdsconfig -s "path to your prenet_start command" \
[-d working directory] \
[-e "path to your validate command"] \
[-t "path to your postnet_stop command"] \
[-l "interpose logical hostname"]
```
- The –s argument is required. You should specify the path to your start or prenet_start command.
- The –d argument is optional. If you do not specify this argument, the current directory becomes the working directory.
- The –e argument is optional. If you specify this argument, you should specify the path to your validate command.
- The –t argument is optional. If you specify this argument, you should specify the path to your stop or postnet_stop command.
- The –m argument is optional. If you specify this argument, you should specify the path to your probe command.
- The –l argument is optional. If you specify this argument, you should specify the interpose logical host name.
- The –p argument is optional. Selecting this argument ensures that PMF_managed=FALSE is set. See Chapter 2, Creating a Data Service with GDSv2 for more information on the PMF_managed command.
On each node of the cluster, install the completed package.
```
# cd working directory/pkg
# pkgadd -d . vendorappname
```
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.
On one node of the cluster, configure the resources and start the application.
```
# cd /opt/vendorappname/util/startapp [arguments] logicalhostname -p port-and-protocol-list
```
Note - The arguments to the startapp script vary according to the type of resource you created and configured. 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/vendorappname/man startapp
```