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 object 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 (SDDF) to monitor the Application Server. |
What happens to WebSphere Application Server
for z/OS if the web server goes down? |
WebSphere Application Server for z/OS requires
an IBM HTTP J2EE server web server in order to provide full function servlets.
So, if the web server goes down, applications that require a port of entry
(like servlets and SOAP) cannot run. |
What happens to other subsystems if Web
Server goes down? |
HTTP only provides information to other
subsystems, so they are unaffected if the web server goes down. |
Where to find more information |
z/OS HTTP Server Planning, Installing,
and Using |