Web server (servlet) automation and recovery scenarios

This table provides scenarios for web server (or servlet) automation and recovery.

Table 1. Web server (or servlet) scenarios. . Displays web server (or servlet) scenarios for automation and recovery.
Task	WebServer automation and recovery scenarios
Startup	Web servers have a relationship with WebSphere® Application Server for z/OS® only in the sense that a client application program that is written to use WebSphere Application Server for z/OS facilities may be written as a servlet. Any implications for ordering of startup will be introduced by the applications. You probably want to have the WebSphere Application Server for z/OS servers up and ready before starting the client application that the web server is hosting.
Shutdown	There are no dependencies from the product code. Similar to most applications, you may want to quiesce the clients prior to taking down the target WebSphere Application Server for z/OS servers. Shut down the web server to stop the port of entry.
Handling in-flight or indoubt transactions if there is a failure	Since a web server is stateless, there are no in-flight or indoubt transactions.
How to determine if a web server is running	Use the z/OS display commands and viewer tools such as SDSF or the administrative console, to monitor the web server.
What happens to WebSphere Application Server for z/OS if the web server goes down?	WebSphere Application Server for z/OS can be enhanced when combined with an IBM HTTP Web Server for more robust load balancing and failover.
What happens to other subsystems if a Web Server goes down?	There is no effect on other subsystems.
Where to find more information	z/OS HTTP Server Planning, Installing, and Using or the documentation for your particular web server.