Paths to files and directories of your GAS installation are set by resources in the GAS
configuration file,as.xcf. Knowing the absolute path of resources, helps you when
working with GAS.
See the
GAS configuration file.
Note: Resources are like variables that
identify or name the resource. For example
res.path.as identifies the GAS
installation directory while the value of this resource will contain the absolute path to your GAS
installation
directory.
<RESOURCE Id="res.path.as" Source="INTERNAL">C:\4js\gas\2.50.34</RESOURCE>
When, for example, you deploy applications you do not need to know where the real
resources are actually located in the production environments because you can map to real
resources with a reference using this syntax, $(RESOURCE Id). Therefore
$(res.path.as) references the GAS installation directory in all hosts where
GAS is installed.
Typical resources and relative path locations
The following are some
typical resources and relative path locations to some of the more common installation and
application data files which you will need to run or reference:
$(res.path.as)/etc/as.xcf
$(res.path.as)/bin/httpdispatch.exe
$(res.fgldir)/fglrun.exe
$(res.appdata.path)/app
$(res.appdata.path)/deployment
Note: Installation
directories may also be identified by environment variables which are set at installation time by
script files, see
Table 1.
-
To find the absolute path of resources, you will need to first locate your
as.xcf file where these predefined resources are set.
The as.xcf file is an XML file which contains the default configuration
for the GAS. You must search your disk for it in directories where the file is likely to be
located.
-
In a text editor or with Genero Studio, open the as.xcf file and locate
the source of your $(res.path.as) resource. You should find its source path amongst
the RESOURCE list elements for your platform (e.g. WNT or UNX).
The source path for $(res.path.as) is platform dependent.
- On Linux®/UNIX™, it
is also represented by the environment variable FGLASDIR.
- On Windows™ by the environment variable FGLASDIR.
Knowing the source of this resource, you will be able to locate the binary file of, for
example the Dispatcher: httpdispatch, the standalone dispatcher used by the
GAS.
-
In the as.xcf file, locate and note the source of your
$(res.appdata.path) resource.
- On Linux/UNIX it
is also represented by FGLASDIR/appdata
- On Windows, for example,
C:/ProgramData/<vendor>/gas/<gas_version>.