1OCF_HEARTBEAT_WAS(7) OCF resource agents OCF_HEARTBEAT_WAS(7)
2
3
4
6 ocf_heartbeat_WAS - Manages a WebSphere Application Server instance
7
9 WAS [start | stop | status | monitor | meta-data | validate-all]
10
12 Resource script for WAS. It manages a Websphere Application Server
13 (WAS) as an HA resource.
14
16 config
17 The WAS-configuration file.
18
19 (optional, string, default
20 "/usr/WebSphere/AppServer/config/server-cfg.xml")
21
22 port
23 The WAS-(snoop)-port-number.
24
25 (optional, integer, default 9080)
26
28 This resource agent supports the following actions (operations):
29
30 start
31 Starts the resource. Suggested minimum timeout: 300s.
32
33 stop
34 Stops the resource. Suggested minimum timeout: 300s.
35
36 status
37 Performs a status check. Suggested minimum timeout: 30s. Suggested
38 interval: 10s.
39
40 monitor
41 Performs a detailed status check. Suggested minimum timeout: 30s.
42 Suggested interval: 10s.
43
44 validate-all
45 Performs a validation of the resource configuration. Suggested
46 minimum timeout: 5s.
47
48 meta-data
49 Retrieves resource agent metadata (internal use only). Suggested
50 minimum timeout: 5s.
51
52 methods
53 Suggested minimum timeout: 5s.
54
56 The following is an example configuration for a WAS resource using the
57 crm(8) shell:
58
59 primitive p_WAS ocf:heartbeat:WAS \
60 op monitor depth="0" timeout="30s" interval="10s"
61
63 The following is an example configuration for a WAS resource using
64 pcs(8)
65
66 pcs resource create p_WAS ocf:heartbeat:WAS \
67 op monitor OCF_CHECK_LEVEL="0" timeout="30s" interval="10s"
68
70 http://clusterlabs.org/
71
73 ClusterLabs contributors (see the resource agent source for information
74 about individual authors)
75
76
77
78resource-agents UNKNOWN 04/06/2022 OCF_HEARTBEAT_WAS(7)