A resource type specifies common properties and callback methods that apply to all of the resources of the given type. You must register a resource type before you create a resource of that type. For details about resource types, see Planning for Oracle Solaris Cluster Data Services.
An administrator can register a resource type for a zone cluster by specifying a resource type registration (RTR) file that resides inside the zone cluster. In other words, the file must be under the zone root path. The RTR file inside the zone cluster cannot have the Global_zone property set to TRUE. The RTR file inside the zone cluster cannot be of type RTR_LOGICAL_HOSTNAME or RTR_SHARED_ADDRESS.
The administrator can also register a resource type for a zone cluster from the location /usr/cluster/lib/rgm/rtreg. The administrator in the zone cluster cannot modify any RTR files in this directory. This enables registering system resource types for a zone cluster, even when the RTR file has one of the properties that cannot be set directly from the zone cluster. This process provides a secure way of delivering system resource types.
Before You Begin
Ensure that you have the name for the resource type that you plan to register. The resource type name is an abbreviation for the data service name.
# clresourcetype register resource-type
Specifies name of the resource type to add.
# clresourcetype show
The following example registers the SUNW.oracle_server:8 resource type, which represents the HA Oracle Server application in an Oracle Solaris Cluster configuration.
# clresourcetype register SUNW.oracle_server:8 # clresourcetype show SUNW.oracle_server:8 Resource Type: SUNW.oracle_server:8 RT_description: Resource type for Oracle Server RT_version: 8 API_version: 2 RT_basedir: /opt/SUNWscor/oracle_server Single_instance: False Proxy: False Init_nodes: All potential masters Installed_nodes: <All> Failover: True Pkglist: <NULL> RT_system: False Global_zone: False
After registering resource types, you can create resource groups and add resources to the resource group. For details, see Creating a Resource Group.
The following man pages: