Some applications included in the Evaluator's Application Suite (EAS) rely on the existence of a License Database. A License Server controls access to the License Database.

For example, if you wish to use an Evaluation Specification from the central repository and customize it to adapt it to your specific needs, you need a license key (however, you do not need a license key for the demo Evaluation Specification, which allows you to try out EAS applications). As another example, you will need a "Content Authoring License" (CAL) if you wish to author Evaluation Specifications from scratch.

The License Server controls concurrent access to the License Database by multiple EAS applications and users. License Server setup differs depending on your environment. There are basically two senarios:

1. A Local License Server (LLS) runs on each user's system, and each user's computer hosts a private License Database.
   
2. A Network License Server (NLS) runs on a server system, which is accessible by all users that use EAS applications. The License Database resides on the server system.

The Local License Server is the preferred option when one of the following conditions apply:

1. You work in a single-user environment, meaning that you are the only user that uses EAS applications;
2. Multiple users work with EAS applications, but your organization's policy guidelines mandate that each user may only use those licenses that she/he actually needs.

The current EAS release provides support for the Local License Server. The NLS will be supported at a later date.

During installation on a Windows(TM) operating system, the installer will create a Windows service for you, which is automatically started when the operating system boots. Hence, in a Windows environment, no further action is required.

A startup item will be created on Mac OS X, and a start/stop script will be generated on UNIX-like system platforms.

If the License Server is not running, you will see a diagnostics window pop up when you use an EAS application, saying that the License Database cannot be accessed.