Installation guide

74 Chapter 4:Service Configuration and Administration
• Section 5.4, Setting Up a DB2 Service
• Section 6.1, Setting Up an NFS Service
• Section 6.2, Setting Up a High Availability Samba Service
• Section 7.1, Setting Up an Apache Service
4.1.1 Gathering Service Information
Before creating a service, gather all available information about the service resources and properties.
When adding a service to the cluster database, the cluadmin utility will prompt for this information.
In some cases, it is possible to specify multiple resources for a service (for example, multiple IP ad-
dresses and disk devices).
The service properties and resources that a user is able to specify are described in the following table.
Table 4–1 Service Property and Resource Information
Service
Property
or
Resource
Description
Service
name
Each service must have a unique name. A service name can consist of one to
63 characters and must consist of a combination of letters (either uppercase or
lowercase), integers, underscores, periods, and dashes. However, a service name
must begin with a letter or an underscore.
Preferred
member
Specify the cluster system, if any, on which the service will run unless failover has
occurred or unless the service is manually relocated.
Preferred
member
relocation
policy
When enabled, this policy will automatically relocate a service to its preferred
member when that system joins the cluster. If this policy is disabled, the service
will remain running on the non-preferred member. For example, if an administrator
enables this policy and the failed preferred member for the service reboots and joins
the cluster, the service will automatically restart on the preferred member.
Script
location
If applicable, specify the full path name for the script that will be used to start and
stop the service. See Section 4.1.2, Creating Service Scripts for more information.