OCF_HEARTBEAT_WAS(7)

💅 ocf_heartbeat_WAS — your fave WebSphere wrangler (section 7 of the manual, bestie)

okay so this is ocf_heartbeat_WAS(7) — the whole entire manual page, and I promise it's gonna be painless. grab a boba, we're doing cluster stuff. 🧋✨

---

✨ NAME ✨

ocf_heartbeat_WAS — it manages a WebSphere Application Server instance. that's it, that's the vibe. 👑

---

🦋 SYNOPSIS 🦋

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

like, pick one of those and go, bestie. 🫶

---

🌸 DESCRIPTION 🌸

so this is the resource script for WAS. it manages a Websphere Application Server (WAS) as an HA resource. literally its whole job. main character energy, no cap. 💅

---

🎀 SUPPORTED PARAMETERS 🎀

these are the knobs you can turn, and ngl there are only two, so you can absolutely memorize them:

• config — the WAS-configuration file. that's the whole thing. it's optional, it's a string, and the default is "/usr/WebSphere/AppServer/config/server-cfg.xml" (yes the quotes and the full path, copy it exactly bestie 🍓).
• port — the WAS-(snoop)-port-number. optional, integer, default 9080. it's giving "tiny parameter list, huge responsibility". 🔥

---

💫 SUPPORTED ACTIONS 💫

okay so this resource agent supports the following actions (operations). timeouts are suggestions — the cluster's minimum patience, basically:

• start — starts the resource. suggested minimum timeout: 300s. a whole five minutes of patience, slay. ⏳
• stop — stops the resource. suggested minimum timeout: 300s. same energy. 🛑
• status — performs a status check. suggested minimum timeout: 30s. suggested interval: 10s. it's checking in on you every ten seconds, that's love fr fr. 🥺
• monitor — performs a detailed status check. suggested minimum timeout: 30s. suggested interval: 10s. the detailed one, bestie, it's thorough. 👀
• validate-all — performs a validation of the resource configuration. suggested minimum timeout: 5s. quick little vibe check on your config. ✅
• meta-data — retrieves resource agent metadata (internal use only). suggested minimum timeout: 5s. don't touch, that's the resource agent's own business. 🙈
• methods — suggested minimum timeout: 5s. that's it, that's the whole description. iconic minimalist behavior. ⭐

---

🌈 EXAMPLE CRM SHELL 🌈

here's an example configuration for a WAS resource using the crm(8) shell. copy-paste responsibly:

primitive p_WAS ocf:heartbeat:WAS \
  op monitor depth="0" timeout="30s" interval="10s"

look at that. gorgeous. no notes. 💖

---

🧚 EXAMPLE PCS 🧚

and here's the same kind of situation but for a WAS resource using pcs(8):

pcs resource create p_WAS ocf:heartbeat:WAS \
  op monitor OCF_CHECK_LEVEL="0" timeout="30s" interval="10s"

note the OCF_CHECK_LEVEL="0" instead of depth="0" — different tool, different syntax, same dream. 🦋

---

👑 SEE ALSO 👑

• http://clusterlabs.org/ — go look, it's the source of all this lore. iykyk. 🔗

---

💜 AUTHOR 💜

ClusterLabs contributors (see the resource agent source for information about individual authors). we stan a collective. 🫶

heads up bestie: meta-data is marked internal use only, so unless you know exactly why you're poking it, maybe let the cluster handle that one. 💀

---

and that's the whole page!! this legendary little doc shipped as resource-agents UNKNOWN, dated 10/01/2026, and you just read the entirety of OCF_HEARTBEAT_WAS(7). go forth and manage that WebSphere, bestie — you're gonna ate. 💅✨🎀