|
Apache Manager Table of Contents
|
| bet | 4/4 | | Sana | 21.03.2020 | | Hajmi | 0,89 Mb. | | #8307 |
The interface is simple (see figure to the left). The “Objects” frame gives a view of the Apache configuration objects that are currently stored in the directory and gives the user the ability to navigate the hierarchy. The object hierarchy begins with a server group, generally called “Apache Group.” The top group contains other groups that define an organization that will make sense for the administrator. Apache groups may be organized according to platform, deployment, or some other configuration model.
[Figure-3, Objects Frame]
Each object in the directory holds a common set of directives that may be inherited by lower level objects in the tree. The “Apache Group” object or the highest object in the tree contains the set of directives that are common across all instances of the Apache web server regardless of the platform that it is running on. Objects that appear at lower levels in the tree, define directives that are specific to particular configurations. The lower the object sits in the tree, the more specific or unique the directives are to a particular Apache web server configuration. The complete configuration for a particular web server is a combination of the directives contained by the server object along with the directives contained by each object within its hierarchical path.
Directive Frame
T he “Directives” frame is the central view which displays the configuration contents held by the currently selected object. This frame gives the administrator the ability to manage the directives that are contained in the object, add child-objects or alter the attribute values of the object itself. Additionally, for server objects, the “Directives” frame allows the administrator to view the server’s configuration file as it would be created by the configuration daemon. In the configuration file view, all directives are linked back to the object where they were defined. This makes it easy to navigate to an object that holds a specific directive without having to know where the directive came from. [Figure-4, Directives Frame]
The Apache Manager interface also allows the administrator to restart each Apache web server that is administered through this interface. If the configuration file for a specific server has been changed manually, this will be communicated back to the directory by the configuration daemon and displayed in the web interface. It gives the administrator the option of importing the changes or rejecting them in order to maintain synchronization between the physical server and the directory. It displays the current status of each Apache server indicating whether the server is currently running or not. Whenever a change is made in the directory, a flag within the Apache server object can be set that directs the configuration daemon to rebuild the physical configuration file for a particular Apache server and restart it. Through the web interface, the administrator has a view of all of their servers within a web farm and the ability to manage those servers.
Apache Manager is a platform independent administration solution that allows an administrator to manage multiple Apache web server configurations from a single web interface. By taking advantage of the directory, it provides the necessary tools to consolidate common configuration directives into a hierarchy of objects, stored in a single location so that all Apache servers may be easily managed from the Internet. Apache Manager is an excellent solution for administrators that are responsible for managing multiple Apache web servers. Apache Manager is not only capable of managing a large number of Apache web servers; it will also manage different versions of Apache running on different platforms. The only real requirement is that the platform supports a JVM and the ability to connect to a directory service through the LDAP protocol. Apache Manager removes the complexity and overhead common to managing multiple Apache web servers.
|
| |
