Sun Cluster 3.0 5/02 Supplement

Configuring the Driving Scripts

After creating the driving scripts, you need to use the SunPlex Agent Builder to configure the new service.

  1. Click the Next button and the configuration panel appears.

  2. Either enter the location of the Start command or use the browse button to locate the Start command.

  3. (Optional) Enter the Stop command or use the browse button to locate the Stop command.

  4. (Optional) Enter the Probe command or use the browse button to locate the Probe command.

  5. (Optional) Specify the timeout values for the Start, Stop, and Probe commands.

  6. Click Configure to start the configuration of the driving scripts.

    A package for driving scripts will be created and placed in:


    working-dir/<vendor_name><application>/pkg

    For example, /export/wdir/NETapp/pkg.


    only -

    The package name consists of a concatenation of the Vendor Name and Application Name.


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


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

  8. The following files will be installed during the 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


    only -

    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
    

  9. 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 <nafogroup/adapter list>] 
     For scalable services: 
     Usage: startapp 
              -h <shared address name> 
              -p <port and protocol list> 
              [ -l <load balancing policy>] 
              [-n <nafogroup/adapter list>] 
               [-w <load balancing weights>]