This article provides some scenarios for automation and recovery of WebSphere Application Server for z/OS.
Task | WebSphere Application Server for z/OS (daemon) automation and recovery scenarios |
---|---|
Startup | See the instructions in the Where to perform WebSphere Application Server operations topic. |
Shutdown | See the instructions in the Where to perform WebSphere Application Server operations topic. |
Handling inflight or indoubt transactions if there is a failure | The daemon is a location agent. If the daemon fails during the course of a transaction, locate requests to the daemon can fail. These request failures might be surfaced by the client ORB. If the client is a WebSphere Application Server for z/OS client running in a sysplex, the locate request can be routed to another available daemon in the sysplex, if present. |
How to determine if the daemon is running | Use the MVS display command. |
What happens to WebSphere Application Server for z/OS if the daemon goes down? | If the daemon goes down, all WebSphere Application Server for z/OS servers started on the same system also are terminated. |
What happens to other subsystems if the daemon goes down? | Other subsystems continue to work fine. As a general rule, if the servers on multiple systems are defined in cluster and there is another one in the sysplex, if the daemon goes down , clients are not affected. |