Support Files
Agent Builder places support files, such as pkginfo, postinstall, postremove, and preremove, in the install_directory/rt_name/etc directory. This directory also contains the resource type registration (RTR) file, which declares resource and resource type properties available for the target resource type and initializes property values at the time a resource is registered with a cluster (see Setting Resource and Resource Type Properties for more information). The RTR file is named as vendor_name.resource_type_name--for example, SUNW.ftp.
You can edit this file with a standard text editor and make changes without recompiling your source code. However, you must rebuild the package with the make pkg command.
Package Directory
The install_directory/rt_name/pkg directory contains a Solaris package. The name of the package is a concatenation of the vendor name and the application name, for example, SUNWftp. The Makefile in the install_directory/rt_name/src directory supports creation of a new package. For example, if you make changes to the source files and recompile the code, or make changes to the package utility scripts, use the make pkg command to create a new package.
When you remove a package from a cluster, the pkgrm command can fail if you attempt to run the command from more than one node simultaneously. You can solve this problem in one of two ways:
Run the removert_name script from one node of the cluster before running pkgrm from any node.
Run pkgrm from one node of the cluster, which takes care of all necessary clean up, then run pkgrm from the remaining nodes, simultaneously if necessary.
If pkgrm fails because you attempt to run it simultaneously from multiple nodes, run it again from one node then run it from the remaining nodes.
The rtconfig File
If you generate C or ksh source code, in the working directory, Agent Builder generates a configuration file rtconfig, which contains the information that you entered on the Create and Configure screens. If you launch Agent Builder from the working directory for an existing resource type (or load an existing resource type using the File menu Load Resource Type command), Agent Builder reads the rtconfig file and fills in the Create and Configure screens with the information that you provided for the existing resource type. This feature is useful if you want to clone an existing resource type (see Cloning an Existing Resource Type.
Navigating Agent Builder
Navigating Agent Builder is simple and intuitive. Agent Builder is a two-step wizard with a corresponding screen for each step (Create and Configure screens). You enter information in each screen by:
Typing information in a field.
Browsing your directory structure and selecting a file or directory.
Checking one of a set of mutually exclusive radio buttons--for example, Scalable or Failover.
Checking an on/off box. For example, checking Network Aware identifies the base application as network aware, while leaving this box blank identifies a non-network aware application.
The buttons at the bottom of each screen enable you to complete the task, move to the next or previous screen, or exit Agent Builder. Agent Builder highlights or grays out these buttons as appropriate.
For example, when you have filled in the fields and checked the desired options on the Create screen, click the Create button at the bottom of the screen. The Previous and Next buttons are grayed out because no previous screen exists and you cannot go to the next step before you complete this one.
Agent Builder displays progress messages in the output log area at the bottom of the screen. When Agent Builder finishes, it displays a success message, or a warning to look at the output log. The Next button is highlighted, or if this is the last screen, only the Cancel button is highlighted.
You can select Cancel at any time to exit Agent Builder.
Browse Button
Particular
Agent Builder fields enable you to type information or to click the Browse button to browse your directory structure
and select a file or directory. 
When you click Browse, a screen similar
to the following screen appears: 
Double click on a folder to open it. When you highlight a file, its name appears in the File name box. Click Select when you have located and highlighted the appropriate file.
Note - If you are browsing for a directory, highlight it and select the Open button. If there are no subdirectories, Agent Builder closes the browse window and places the name of the directory you highlighted in the appropriate field. If this directory has subdirectories, click the close button to close the browse window and return to the previous screen. Agent Builder places the name of the directory you highlighted in the appropriate field.
The icons in the upper right corner of the screen do the following:
|
This icon moves you up one level in the directory tree. |
|
This icon returns you to the home folder. |
|
This icon creates a new folder under the currently selected folder. |
|
This icon, for toggling between different views, is reserved for future use. |
Menus
Agent Builder provides File and Edit menus.
File Menu
The File men has two commands:
Load Resource Type -- Load an existing resource type. Agent Builder provides a browse screen from which you select the working directory for an existing resource type. If a resource type exists in the directory from which you launch Agent Builder, Agent Builder automatically loads the resource type. The Load Resource Type command allows you to launch Agent Builder from any directory and select an existing resource type to use as a template for creating a new resource type (see Cloning an Existing Resource Type).
Exit -- Exit Agent Builder. You can also exit by clicking Cancel on the Create or Configure screen.
Edit Menu
The Edit menu has commands to clear and save the output log:
Clear Output Log -- Clears the information from the output log. Each time you select Create or Configure, Agent Builder appends status messages to the output log. If you are engaged in an iterative process of making changes to your source code and regenerating output in Agent Builder and want to segregate the status messages, you can save and clear the log file before each use.
Save Log File -- Save the log output to a file. Agent Builder provides a browse screen that enables you to choose the directory and specify a filename.
Cluster Agent Module for Agent Builder
The Cluster Agent module for Agent Builder is a NetBeans™ module. The Cluster Agent module enables users of the Sun™ ONE Studio product to create resource types, or data services, for the Sun Cluster software through an integrated development environment. The Cluster Agent module provides a screen-based interface for describing the kind of resource type that you want to create.
Note - The Sun ONE Studio documentation contains information about how to set up, install, and use the Sun ONE Studio product.
Installing and Setting Up the Cluster Agent Module
The Cluster Agent module is installed when you install the Sun Cluster software. The Sun Cluster installation tool places the Cluster Agent module file scdsbuilder.jar in /usr/cluster/lib/scdsbuilder. To use the Cluster Agent module with the Sun ONE Studio software, you need to create a symbolic link to this file.
Note - The Sun Cluster and Sun ONE Studio products and Java™ 1.4 must be installed and available to the system on which you intend to run the Cluster Agent module.
Do you want to enable all users or only yourself to use the Cluster Agent module?
To enable all users, become superuser or assume an equivalent role and create the symbolic link in the global module directory:
# cd /opt/s1studio/ee/modules # ln -s /usr/cluster/lib/scdsbuilder/scdsbuilder.jar
Note - If you installed the Sun ONE Studio software in a directory other than /opt/s1studio/ee, substitute this directory path with the path that you used.
To enable only yourself, create the symbolic link in your modules subdirectory:
% cd ~your-home-dir/ffjuser40ee/modules % ln -s /usr/cluster/lib/scdsbuilder/scdsbuilder.jar
Stop and restart the Sun ONE Studio software.