Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Services Developer's Guide Oracle Solaris Cluster 4.0 |
1. Overview of Resource Management
3. Resource Management API Reference
6. Data Service Development Library
8. Sample DSDL Resource Type Implementation
9. Oracle Solaris Cluster Agent Builder
Advantages and Disadvantages of Using the GDS
Ways to Create a Service That Uses the GDS
GDS and Oracle Solaris Cluster Administration Commands
Selecting the Method to Use to Create a GDS-Based Service
Monitor_retry_interval Property
Network_resources_used Property
Using Agent Builder to Create a Service That Uses the GDS
Creating and Configuring GDS-Based Scripts
Using Oracle Solaris Cluster Administration Commands to Create a Service That Uses the GDS
Command-Line Interface for Agent Builder
How to Use the Command-Line Version of Agent Builder to Create a Service That Uses GDS
12. Cluster Reconfiguration Notification Protocol
A. Sample Data Service Code Listings
B. DSDL Sample Resource Type Code Listings
C. Requirements for Non-Cluster-Aware Applications
D. Document Type Definitions for the CRNP
You can use Agent Builder to create the service that uses the GDS. Agent Builder is described in more detail in Chapter 9, Oracle Solaris Cluster Agent Builder.
# /usr/cluster/bin/scdsbuilder
Note - The combination of vendor name and application name is used as the name of the package for the scripts.
You can use the Browse drop-down menu to select the directory rather than typing the path.
You do not need to select Network Aware because that setting is the default when you create the GDS.
Note - You cannot use the following characters in the RT Version field: space, tab, slash (/), backslash (\), asterisk (*), question mark (?), comma (,), semicolon (;), left square bracket ([), or right square bracket (]).
Agent Builder creates the scripts. The results are displayed in the Output Log area.
Note that the Create button is grayed out. You can now configure the scripts.
The Configure screen appears.
After creating the scripts, you need to configure the new service.
You can specify property variables. Property variables are described in Using Property Variables.
You can specify property variables. Property variables are described in Using Property Variables.
You can specify property variables. Property variables are described in Using Property Variables.
You can specify property variables. Property variables are described in Using Property Variables.
Agent Builder configures the scripts.
Note - Agent Builder concatenates the vendor name and the application name to create the package name.
A package for scripts is created and placed in the following directory:
working-dir/vendor-name-application/pkg
For example, /export/wdir/NETapp/pkg.
# 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).
# /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]
Agent Builder generates three scripts and a configuration file based on input that you provide when you create the package. The configuration file specifies the names of the resource group and the resource type.
The scripts are as follows:
Start script. Configures the resources and starts the application that is under RGM control.
Stop script. Stops the application and takes down resources and resource groups.
Remove script. Removes the resources and resource groups that are created by the start script.
These scripts have the same interface and behavior as the utility scripts that are generated by Agent Builder for non-GDS-based data services. The scripts are put in an Oracle Solaris package that you can reuse across multiple clusters.
You can customize the configuration file to provide your own names for resource groups or other arguments that are normally given as arguments to the scrgadm and scswitch commands. If you do not customize the scripts, Agent Builder provides default values for these arguments.