ServerStart.aro resides in the same directory as the SteelArrow server binary. This script is called each time the server is started. Within this script SteelArrow code can be placed that is to be executed when the server is started. Examples of use may include sending a mail message to the administrator notifying them of the server starting. Another example would be to load this file with TIMEDOPER operations. By doing this scripts can be executed at predetermined times (ie. sending reports on a nightly basis).
(View sample)

Functions.aro resides in the same directory as the SteelArrow server binary. This file may contain several functions that will be made available to all users. This aids in the security configuration of SteelArrow since these functions could potentially allow functionality that would otherwise not be available to system users. As an example, an administrator can create functions to offer limitted access to the FILE tag. See the FUNCTION tag for an overview of creating and calling functions.
(View sample)

PageStats.aro resides in the same directory as the SteelArrow server binary. This file can be used to store site statistics in a database. In order for this script to have any effect on the system, it is necessary to have SteelArrow installed as a filter on the web server. As each page is requested from the server, PageStats.aro is called, and receives a CGI table containing all request information. As well, the CGI table will contain a variable CGI.SCRIPT_EXT which represents the extension of the requested file.
(View sample)

CatchError.aro resides in any directory at the current executing script level, or lower. This script is retrieved when an unhandled error occurs. Since the script can appear at the root of the file system, one CatchError.aro can be used for all web applications. The script receives all variables in the same context as when the error occurred, as well as an ERROR table describing the error condition.
(View sample)

Application.aro resides in any directory at the current executing script level, or lower. This script is retrieved everytime a SteelArrow script is requested. Essentially the application.aro script is pre-pended to the beginning of all requested scipts. Since the application.aro script could potentially reside at the root of the file system, one script can be used for all web applications or depending on setup, several application.aro scripts could handle numerous web applications each.
(View sample)