Veritas Cluster Server Bundled Agents Reference Guide
Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec Veritas⢠Cluster Server Bundled Agents Reference Guide - Symantec
114 Services and applications agents GenericService agent Table 6-4 GenericService agent optional attributes (continued) Optional Attributes Domain Description The domain to which the user specified in the UserAccount attribute belongs. If the domain name is not specified, the agent assumes that the user belongs to the local machine. This attribute is ignored if the UserAccount attribute is not specified or if the domain name is specified in the UserAccount attribute itself. Note: This attribute can take localized values. Type and Dimension: string-scalar Password The password of the user, in whose context, the service would be started. If the UserAccount attribute is empty or contains a built-in service account, this attribute is ignored. Type and Dimension: string-scalar service_arg An array of arguments passed to the service. Type and Dimension: string-vector UserAccount A valid user account in whose context the service will be monitored. Username can be of the form username@domain.com or domain.com\username. If you do not specify a value for this attribute, then the user account of the service in the SCM is ignored. To monitor service under built-in accounts, you must provide explicit values. For example: UserAccount=‘LocalSystem’, ‘Local Service’, or ‘Network Service’. Domain=‘NT Authority’. The ‘NT Authority’ domain is not applicable for the ‘LocalSystem’ account. Note: This attribute can take localized values. Type and Dimension: string-scalar
Services and applications agents ServiceMonitor agent 115 Table 6-4 GenericService agent optional attributes (continued) Optional Attributes UseVirtualName Description Set this value to enable the service specified by the ServiceName attribute to inherit the Virtual Server context of Lanman resource specified in LanmanResName attribute. If this attribute is set, the LanmanResName becomes a mandatory attribute. Note: It is recommended that you do not set this attribute for system services. If you configure system services using the GenericService agent, then this attribute is not supported. Type and Dimension: boolean-scalar LanmanResName The name of the Lanman resource on which the GenericService resource depends. Note: It is recommended that you do not set this attribute for system services. If you configure system services using the GenericService agent, then this attribute is not supported. Type and Dimension: string-scalar Sample configuration GenericService Telephony_Service ( ServiceName = "Telephony Service" DelayAfterOnline = 10 DelayAfterOffline = 10 UserAccount = Administrator Password = bphNepE Domain = VCS-DOMAIN service_arg = { 3 } ) ServiceMonitor agent The ServiceMonitor agent monitors a service or starts a user-defined script and interprets the exit code of the script. A service is an application type supported by Windows that conforms to the interface rules of the SCM. The agent can be configured to monitor a service using the Service Control Manager (SCM) or through a user-defined script. When configured to monitor using the SCM, the agent queries the SCM database for the status of the service. When configured to monitor using a script or an executable, the agent executes the script on each system in the cluster, once every
- Page 63 and 64: Network agents Lanman agent 63 Tabl
- Page 65 and 66: Network agents Lanman agent 65 Tabl
- Page 67 and 68: Network agents Lanman agent 67 Tabl
- Page 69 and 70: Network agents Lanman agent 69 Tabl
- Page 71 and 72: Network agents Lanman agent 71 LANM
- Page 73 and 74: Chapter 4 FileShare agents This cha
- Page 75 and 76: FileShare agents FileShare agent 75
- Page 77 and 78: FileShare agents FileShare agent 77
- Page 79 and 80: FileShare agents FileShare agent 79
- Page 81 and 82: FileShare agents FileShare agent 81
- Page 83 and 84: FileShare agents CompositeFileShare
- Page 85 and 86: FileShare agents CompositeFileShare
- Page 87 and 88: FileShare agents CompositeFileShare
- Page 89 and 90: FileShare agents CompositeFileShare
- Page 91 and 92: FileShare agents CompositeFileShare
- Page 93 and 94: Chapter 5 PrintShare agents This ch
- Page 95 and 96: PrintShare agents PrintSpool agent
- Page 97 and 98: PrintShare agents PrintShare agent
- Page 99 and 100: PrintShare agents PrintShare agent
- Page 101 and 102: PrintShare agents PrintShare agent
- Page 103 and 104: Chapter 6 Services and applications
- Page 105 and 106: Services and applications agents In
- Page 107 and 108: Services and applications agents In
- Page 109 and 110: Services and applications agents In
- Page 111 and 112: Services and applications agents Ge
- Page 113: Services and applications agents Ge
- Page 117 and 118: Services and applications agents Se
- Page 119 and 120: Services and applications agents Pr
- Page 121 and 122: Services and applications agents Pr
- Page 123 and 124: Services and applications agents Pr
- Page 125 and 126: Services and applications agents MS
- Page 127 and 128: Services and applications agents MS
- Page 129 and 130: Chapter 7 VCS infrastructure and su
- Page 131 and 132: VCS infrastructure and support agen
- Page 133 and 134: VCS infrastructure and support agen
- Page 135 and 136: VCS infrastructure and support agen
- Page 137 and 138: VCS infrastructure and support agen
- Page 139 and 140: VCS infrastructure and support agen
- Page 141 and 142: VCS infrastructure and support agen
- Page 143 and 144: VCS infrastructure and support agen
- Page 145 and 146: VCS infrastructure and support agen
- Page 147 and 148: VCS infrastructure and support agen
- Page 149 and 150: VCS infrastructure and support agen
- Page 151 and 152: VCS infrastructure and support agen
- Page 153 and 154: VCS infrastructure and support agen
- Page 155 and 156: VCS infrastructure and support agen
- Page 157 and 158: VCS infrastructure and support agen
- Page 159 and 160: VCS infrastructure and support agen
- Page 161 and 162: Chapter 8 VCS hardware replication
- Page 163 and 164: VCS hardware replication agent for
Services and applications agents<br />
ServiceMonitor agent<br />
115<br />
Table 6-4<br />
GenericService agent optional attributes (continued)<br />
Optional Attributes<br />
UseVirtualName<br />
Description<br />
Set this value to enable the service specified by the ServiceName<br />
attribute to inherit the Virtual <strong>Server</strong> context of Lanman resource<br />
specified in LanmanResName attribute. If this attribute is set,<br />
the LanmanResName becomes a mandatory attribute.<br />
Note: It is recommended that you do not set this attribute for<br />
system services. If you configure system services using the<br />
GenericService agent, then this attribute is not supported.<br />
Type and Dimension: boolean-scalar<br />
LanmanResName<br />
The name of the Lanman resource on which the GenericService<br />
resource depends.<br />
Note: It is recommended that you do not set this attribute for<br />
system services. If you configure system services using the<br />
GenericService agent, then this attribute is not supported.<br />
Type and Dimension: string-scalar<br />
Sample configuration<br />
GenericService Telephony_Service (<br />
ServiceName = "Telephony Service"<br />
DelayAfterOnline = 10<br />
DelayAfterOffline = 10<br />
UserAccount = Administrator<br />
Password = bphNepE<br />
Domain = VCS-DOMAIN<br />
service_arg = { 3 }<br />
)<br />
ServiceMonitor agent<br />
The ServiceMonitor agent monitors a service or starts a user-defined script and<br />
interprets the exit code of the script. A service is an application type supported<br />
by Windows that conforms to the interface rules of the SCM. The agent can be<br />
configured to monitor a service using the Service Control Manager (SCM) or<br />
through a user-defined script.<br />
When configured to monitor using the SCM, the agent queries the SCM database<br />
for the status of the service. When configured to monitor using a script or an<br />
executable, the agent executes the script on each system in the cluster, once every