Sun Cluster 3.1 Data Services Developer's Guide

Command Line Interface to the SunPlex Agent Builder

The SunPlex Agent Builder has a command line interface that has equivalent functionality to the GUI interface. This interface consists of the commands scsdcreate(1HA) and scdsconfig(1HA). The following section performs the same function as the GUI-based procedure Creating a Service Using GDS in the Agent Builder but uses the non-GUI interface.

Creating A Service that Uses GDS Using the Command Line Equivalent Functionality of the SunPlex Agent Builder
  1. Create the service.

    For a failover service, use:

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

    For a scalable service, use:

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

    Note –

    The –d parameters are optional. If it is not specified, the working directory defaults to the current directory.

  2. Configure the service.

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

    Note –

    Only the start command is required. All other parameters are optional.

  3. Install the completed package on all nodes of the cluster.

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

  4. The following files will be installed during the pkgadd:


    Note –

    The man pages and script names will correspond to the Application Name you entered above preceded by the script name; for example, startapp.

    To view the man pages, you need to specify the path to the man page. For example, to view the startapp man pages, use:

    # man -M /opt/NETapp/man startapp
  5. On one node of the cluster, configure the resources and start the application.

    # /opt/NETapp/util/startapp -h <logichostname> -p <port and protocol list>

    The arguments to the start script will vary according to the type of resource: failover or scalable. Check the customized man page or run the start script without any argument to get a usage statement.

    # /opt/NETapp/util/startapp 
     The resource name of LogicalHostname or SharedAddress must be specified. 
     For failover services: 
     Usage: startapp -h <logical host name> 
              -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>]