Create a configuration file for the Web runtime the same way that you would for the standard ACUCOBOL-GT runtime. Instructions can be found in the ACUCOBOL-GT User's Guide > Compiler and Runtime > Runtime Configuration.
Once you have a configuration file, you can access it via AcuServer, using the standard @ServerName:/pathname syntax, or you can bundle it into a library file along with the COBOL object files and resources. For information on using AcuServer to access your configuration files, see Setting up Accounts. For information on creating library files, see Packaging your Application and Resources.
Note that if you choose the library file method, you must also specify the name of the configuration file as an option when you invoke the Web runtime. (This is described in Invoking your COBOL Application with the Web Runtime.)
The Web runtime loads the configuration file by performing the equivalent of a SET CONFIGURATION statement for each line of the configuration file. Note that there are a few configuration variables that cannot be modified this way. They are MAX_FILES, MAX_LOCKS and LOCKS_PER_FILE. When you are using the ACUCOBOL-GT Web Runtime, these variables are initialized to the following values:
MAX_FILES 255
MAX_LOCKS 512
LOCKS_PER_FILE 256
Note that FILE_PREFIX is initially set to the list of directories specified in the "acuauth.txt" security file. This authorization file specifies the directories to which your COBOL programs have access on the user's machine. The path given in "acuauth.txt" is limited to 4096 characters, like the FILE_PREFIX variable. The path given in this file must be enclosed in quotation marks. If you define an alternate FILE_PREFIX in the configuration file that you embed with your object library, that value overrides the "acuauth.txt" setting.