GAS installation and application data directories

GAS is installed in different directories in a Linux®/UNIX™ platform to a Windows® one. To help you manage your GAS installation, there are descriptions of its files and directories, and recommendations for its use.

The two main directories of the GAS are:

GAS Installation directory

The installation directory contains the installation files. It is defined by the FGLASDIR environment variable and set by the resource $(res.path.as) in the GAS configuration file. The directories and files of the GAS installation directory are described in Table 1.
Table 1. FGLASDIR directories and files
Directory GAS installation directory
$FGLASDIR
Sub-directories Files or Details Description
/ Contains script for setting environment variables:

On Linux/UNIX: envas

On Windows: envas.bat

Root directory
/bin *.exe GAS dispatchers and VMProxy executables.
/Docker *.exe, Dockerfile Contains scripts for working with Docker containers.
/etc as.xcf Gas configuration files.
/tpl
Sub-directories Files or details Description
/shortcut *.gdc Shortcuts for applications that can be run by the Genero Desktop Client using /da/r URLs. See Running desktop applications
No additional information
/web demos.html, etc. Root directory for direct communication to the application server. The demos.html file provides access to Demos applications.

GAS application data directory

The application data directory, or appdata, is where the application data files managed by the GAS are located. The appdata directory is set by the resource $(res.appdata.path) in the GAS configuration file. The directories and files of the appdata directory are described in Table 2
Table 2. appdata directories and Files
Directory GAS application data directory
appdata
On Windows: C:\ProgramData\FourJs\gas\gas_version

On Linux/UNIX: $FGLASDIR/appdata

Sub-directories Files or Details Description
/app *.xcf Default application group; the default location for your application configuration files.
/deployment Contains a directory for each application. Applications deployed with Genero Archive.
/gbc_deployment Contains a directory for each GBC. Genero Browser Clients deployed on the GAS.
/log vm, proxy, and dispatcher logs.
Important: Users need write permissions for this directory. Users who installed the GAS have write permissions. If users that start the GAS (for example Apache®) are not in that group, then you need to grant them write permission.
A directory is created for each dispatcher, for example, httpdispatch (for the standalone GAS).
The logs for a given day are stored in a directory named for that date.
Note: DVM logs are redirected to files when DAILYFILE is set for the log output type.
/monitoring Stores data for Web services you are monitoring. Directories are created as sessions for Web services with configured alerts start. The session id becomes the directory's name.
/public
Note: Public images should not be placed in the /public root directory as the fglrun does not look for images to be served via the GAS there. Searches start in its sub-directory paths.
Sub-directories Files Description
/common Image files and resources Stores common images used by applications. It is the default PUBLIC_IMAGEPATH directory.
/deployment Image files and resources A directory is created for each application.
A public resource path for all applications.
/session Persistent session table information.
Important: Users need write permissions for this directory. Users who installed the GAS have write permissions. If users that start the GAS (for example Apache®) are not in that group, then you need to grant them write permission.
A directory is created for each dispatcher.
/tmp
Important: Users need write permissions for this directory. Users who installed the GAS have write permissions. If users that start the GAS (for example Apache®) are not in that group, then you need to grant them write permission.
Sub-directories Files Description
/dispatcher_name Transferred files Default file transfer directory.A directory is created for each dispatcher.
/gasadmin Stores gasadmin actions. Example actions include exploring the configuration (xcf) files.
No additional information.
/services *.xcf Default services group; the default directory for your Web services configuration files.

Prerequisites for application data directory

GAS requires that all appdata files are located on the same file system. This requirement is based on the following:
  • The appdata directory and all the search paths for VM server image files defined by the FGLIMAGEPATH environment variable must be located on the same file system. For more information, see the Genero Business Development Language User Guide.
  • The DVM uses hard links to avoid file copies. As hard links are direct pointers to data on the disk, they can not span file systems.
Note: It is not recommended to change the location of appdata.
If you need to customize the application directory location due to, for example, disk space constraints, it is recommended that you move the entire directory hierarchy starting from the root directory at appdata and ensure that all appdata files are relocated on the same file system.
Note: If you have two partitions, partition A and B, they are considered two distinct file systems even if stored on the same physical device.
To implement a location change for appdata, there are two recommended options:
  • You can reset the resource $(res.appdata.path) in the GAS configuration file with an absolute path reference to the new location. The example shows appdata located in the path of the GAS installation resource, $(res.path.as):
    <RESOURCE Id="res.appdata.path" Source="INTERNAL">$(res.path.as)/appdata</RESOURCE>
  • Or alternatively, at the command line you can override the GAS configuration file $(res.appdata.path) resource with dispatcher option -E.