EASA contains several tools for monitoring the usage of your EASA system. These tools will allow you to keep track of the following:

• All failed login attempts to your EASA system, including IP logging.

• The activity of Users on your EASA system with respect to EASAP submissions and runs.

• The length of EASAP run times and also the amounts these times are being lengthened due to waiting for available Compute Servers or application software licenses.

• The amount of disk space being used by the EASA system on the EASA Server.

• The status of the EASAP run queue.

This page provides feedback on the state of Compute Servers, Excel Servers and EASA Server Disk Space.

A comma separate list of email addresses may be supplied such that if a Compute Server or Excel Server goes inactive, or if the disk space goes below a preset amount, then these people are notified.

In order to use this capability, you must first set up the email capability within EASA via EASA→Configure→Email page.

The tests are done every 10 minutes. On the disk space check, an email will only be sent if the system goes from having 2*minimum disk space to below minimum disk space. This is to avoid too many emails being sent if the disk space usage is hovering around the minimum.

The information is also logged through Log4j via the category backend.EventNotification.

The log4j.properties file in the <EASAROOT>/webapps/easa/WEB-INF/classes folder within EASA may be modified to send the information to other locations.

You can monitor all failed attempts to log in to your EASA system due to bad passwords or unrecognized User IDs by selecting EASA→Administrator→System→Security Log. There are three types of failed attempts that will be recorded and displayed:

• Incorrect password entered

• Unrecognized user name

• Single or Multiple login attempts from another client computer

• Added or deleted users

• Added or deleted privileges (Author or Administrator)

• Change of a user's details (name, email or phone)

• Change of a user's password

For each instance of a failed login attempt, a row will be displayed in the table showing the time and date of the attempt, the User ID used during the attempt, and a message pointing towards one of the three issues listed above. The message for all failed login attempt issues will also display the IP address of the computer used in the attempt.

Tip: The data shown in the Security Log is stored in a text file called security.txt in the <SERVERDATA>/admin/logs folder. This file contains comma-separated data values and therefore is suitable for importing into spreadsheet tools, such as Microsoft Excel, for further analysis.

To see how often Users on your system are being denied access to EASA due to insufficient licenses being available, select Availability under the System menu while in Administrator mode. For each failed attempt, a row is placed in the table on the Availability page showing the time and date of the attempt and the user ID used in the attempt.

Tip: The data shown on the Availability page is stored in a text file called availability.txt in the <SERVERDATA>/admin/logs folder. This file contains comma-separated data values and therefore is suitable for importing into spreadsheet tools, such as Microsoft Excel, for further analysis.

To view statistics on the use of EASAPs on your system, select Activity under the System menu while in Administrator mode. The table shown on the Activity page contains a row for each month that your EASA system has been installed and active. Within each row, the following information is provided:

• User IDs that have submitted EASAP runs during the month

• EASAPs that have been submitted to run during the month

• The number of submissions and runs performed during the month

• The total EASAP run time accumulated during the month

By using the two search fields, one for Users and the other for Applications i.e. EASAPs, you can filter the EASAP usage information down to specific user IDs and/or specific EASAPs. Once filtered, the submissions, runs and run time information corresponds to just the Users and Applications currently displayed in the table. See the figure below for an example of the Activity page.

Note: A submission is recorded every time a user clicks on the 'Submit' EASAP button on an EASAP, while a run is recorded only if it runs to 'Completion'. Also, submissions of parametric and optimization studies may produce multiple runs per submission.

Tip: The data shown at EASA→Administrator→System→Activity is stored in two text files called submitted_runs.txt and runs.txt in the <SERVERDATA>/admin/logs folder. This file contains comma-separated data values and therefore is suitable for importing into spreadsheet tools, such as Microsoft Excel, for further analysis.

To view the efficiency with which your EASAPs run on your system select EASA→Administrator→System→Efficiency. A table listing all the EASAPs currently published in the Application Library will appear. In this table, the following statistics for each EASAP published on your EASA system will be shown:

• Average wait time for an available Compute Server in seconds for an EASAP run

• Average wait time for an available application software license in seconds for an EASAP run

• Average overall turnaround time in seconds for an EASAP run

When wait times for either compute servers or licenses become a large portion of the overall turnaround times, it may be worth considering making available to your EASA system more compute servers or licenses, whichever is needed.

Another common resource that requires monitoring is disk space usage on the EASA Server. You can find out how much disk space is being used on the EASA Server by selecting EASA→Administrator→System→Disk Space. A table will then appear with information about the disk space being used by each User of the system. A total for both Authoring and Users is provided above the table. Summing these two numbers will give you the total disk space being used by the EASA system beyond the initial 100 MB or so taken up during installation.

Users can reduce their disk usage by deleting their unwanted entries in EASA→Results library. Authors can reduce their disk space usage by deleting results from testing runs and deleting old, unneeded versions of EASAPs. Authors also have some control over how much disk space an EASAP run will use when finished.

Tip: Remind the Authors on your system to use CLEAR FILESPACE in their EASAPs to help keep the use of disk space to a reasonable level.

To view and manage the use of software and computer resources by users’ EASAP runs within your EASA system, select EASA→Administrator→System→Queue. A table listing all current EASAP runs present within the EASAP queue will appear showing a information each run and its status in the queue.

As an Administrator, you can perform two actions on EASAP runs shown at EASA→Administrator→System→Queue :

1. Stop an EASAP run by clicking on the Stop EASAP button () in the Stop column.
2. Change an EASAP run’s place in the queue by clicking on the Change Priority button () in the Priority column. Next, you either click on the Highest button to elevate the run to top of the queue or on Lowest button to drop the run to the bottom of the queue.