1OCF_HEARTBEAT_WAS(7)          OCF resource agents         OCF_HEARTBEAT_WAS(7)
2
3
4

NAME

6       ocf_heartbeat_WAS - Manages a WebSphere Application Server instance
7

SYNOPSIS

9       WAS [start | stop | status | monitor | meta-data | validate-all]
10

DESCRIPTION

12       Resource script for WAS. It manages a Websphere Application Server
13       (WAS) as an HA resource.
14

SUPPORTED PARAMETERS

16       config
17           The WAS-configuration file.  (optional, string, default
18           /usr/WebSphere/AppServer/config/server-cfg.xml)
19
20       port
21           The WAS-(snoop)-port-number.  (optional, integer, default 9080)
22

SUPPORTED ACTIONS

24       This resource agent supports the following actions (operations):
25
26       start
27           Starts the resource. Suggested minimum timeout: 300.
28
29       stop
30           Stops the resource. Suggested minimum timeout: 300.
31
32       status
33           Performs a status check. Suggested minimum timeout: 30. Suggested
34           interval: 10.
35
36       monitor
37           Performs a detailed status check. Suggested minimum timeout: 30.
38           Suggested interval: 10.
39
40       validate-all
41           Performs a validation of the resource configuration. Suggested
42           minimum timeout: 5.
43
44       meta-data
45           Retrieves resource agent metadata (internal use only). Suggested
46           minimum timeout: 5.
47
48       methods
49           Suggested minimum timeout: 5.
50

EXAMPLE

52       The following is an example configuration for a WAS resource using the
53       crm(8) shell:
54
55           primitive p_WAS ocf:heartbeat:WAS \
56             op monitor depth="0" timeout="30" interval="10"
57

SEE ALSO

59       http://www.linux-ha.org/wiki/WAS_(resource_agent)
60

AUTHOR

62       Linux-HA contributors (see the resource agent source for information
63       about individual authors)
64
65
66
67resource-agents 3.9.2             07/08/2011              OCF_HEARTBEAT_WAS(7)