Summary

In this chapter, we covered the admin agent, which allows the use of a single Administrative console to be used to administer multiple application servers. When a server is registered (federated) to the admin agent, we can start and stop servers without losing access to the Admin console. The admin agent allows us to also configure other aspects of WebSphere Application Server in a centralized fashion.

We also covered a simple example of how to use IHS as a web server in front of the WebSphere Application Server, thus allowing HTTP requests to applications mapped to the web server on port 80, as opposed to going to the web container. We learned that IBM HTTP Server can use the WebSphere plugin, which is the mechanism by which IHS can route requests to the application server. By creating a web server definition, we were able to propagate (copy) a file called plugin-cfg.xml, which contains the URI paths (context root and URLs) of all the applications that have web modules mapped to...