JGAS configuration file

The JGAS configuration file, as.xcf, provides default configurations for embedded applications.

As the JGAS is packaged in the FGLGWS product, the default configuration file is located in the FGLDIR/web_utilities/jgas/WebContent/WEB-INF/ directory.

When the JGAS is embedded in a war file for application deployment, it is located in its WEB-INF directory.

Configuration elements

The JGAS configuration file as.xcf is an XML file. The main elements are similar to the standard GAS as.xcf file:
  • Its root element is CONFIGURATION.
  • RESOURCES is basically the same as RESOURCE_LIST in the standard GAS, except there is only one RESOURCES element allowed. There are also no platform specific resources for Windows® and UNIX®.
  • INTERFACE is the same as standard GAS element INTERFACE_TO_CONNECTOR.

The JGAS configuration does not provide an abstract application definition. Instead two templates, one for APPLICATION (for JGAS) and one for SERVICE (for JGAS) provides default settings. Only one APPLICATION and SERVICE template is allowed in the JGAS configuration file.

Configuration elements not in JGAS

The following configuration elements do not exist in JGAS:
  • MONITOR
  • GROUP. The application group concept is not supported. There is no requirement, therefore, to reference a group in application or service configuration.
  • PROMPT (for AUTO_LOGOUT (for JGAS)). Re-login after auto logout is not supported.
  • FILE_TRANSFER and its child element TIMEOUT
  • Component configuration elements are not supported in the JGAS. Where in the standard GAS there is a using attribute in, for example the APPLICATION element, which can reference a component element, this is not used in JGAS.
Note: An implementation of the MONITOR and re-login (after auto logout) features are under development for JGAS and will be delivered in a later release.

Log elements

The LOG (for JGAS) element allows you to configure logging for both console and log file.

These elements can be enabled or disabled independently. If the CONSOLE log is enabled all DVM output is displayed to the standard output. If the DAILYFILE is enabled, the DVM log is redirected to a log file. Logging filters can be applied for both the console and log file with the CATEGORIES (under LOG for JGAS)element.

Schema validation

The JGAS configuration does not reference an XML Schema Definition (XSD) file to validate the configuration as in standard GAS. Therefore the xmlns:xsi and xsi:noNamespaceSchemaLocation attributes are not used in the APPLICATION element. This simplifies the configuration and allows for flexibility in, for example, the ordering of elements. Validation takes place internally. For compatibility with existing application xcf files, if schema attributes are defined, they are just ignored.

Element order

Configuration elements are well-formed and defined hierarchically as in the standard GAS. This means that child elements must appear within the parent node. As schema validation in JGAS is flexible, the order child elements appear within a parent node is not important. For example if PATH appears after AUTO_LOGOUT, it is not an issue with JGAS.