Table of Contents
- Introduction

  | · Introduction · Server Administration · Different Versions · Concepts

- Installation
- Handling Challenger
- Virtual Servers
- Configuration Examples
- Modules
- Filesystems
- RXML Tags
- Graphics
- Proxy
- Databases
- Miscellaneous Modules
- Security Considerations
- Scripting
- Frontpage
- Upgrading
- Third Party Extensions
- Portability
- Reporting Bugs
- Appendix

Server Administration
The main task of the administrator is to provide the users with the services they need, while keeping the server functional and secure. A public web site is by definition reachable by any user on the internet, some of whom may harbor ill intent. Not only the web server itself but also all scripts and custom-made modules must be secure. With the most powerful Challenger modules, users can create pages with scripting and database accesses, pages that in themselves can be potential security hazards.

The administrator has to know about these security hazards and draw the line between functionality and security. The administrator can limit who gets to use which modules, in case not all users can be trusted with the security of the server.

The administrator also has to make sure the system is running smoothly. The main tools are the log files and event log. Most problems will be reported there.

The world of Challenger and the web are not static. New releases and third party software appears, and users demand more functionality. It is the administrator who has to determine if new software can be safely installed.

Besides knowing the Challenger server, the administrator needs to be familiar with Internet security and security issues related to the operating system the server is running on. It will not help that the Challenger server is made secure if the underlying operative system is not.