16.3. Managing Web Applications Contexts
JBoss ON manages the full lifecycle of web application contexts within the
mod_cluster
load-balancing cluster.
Web application contexts can be stopped or disabled. Stopping or disabling a webapp context removes it from load-balancing balancing so that the Apache server cannot forward requests to the webapp, but it leaves the application running and available directly from the JBoss server address. (Stop allows the webapp context to drain before removing it from the load-balancing, so this essentially shuts down the webapp gracefully. It can take several minutes or even hours for the webapp context to stop. Disabling a webapp context immediately removes it from load balancing.)
JBoss ON has operations that allow JBoss administrators to manage the state of their web contexts within the
mod_cluster
domain.
![Running Web Application Context Operations](https://access.redhat.com/webassets/avalon/d/Red_Hat_JBoss_Operations_Network-3.1-How_to_Manage_JBoss_Servers-en-US/images/fdc684f4eb2c6e85040b8dc6f8df3f7a/mod_cluster_context_operation.png)
Figure 16.5. Running Web Application Context Operations
Web context resource operations only apply to the specific selected context.