Application configuration file

An application configuration file defines an application environment and provides the JGAS with the information needed to run an application.

Configuration file

Tip: Application configuration files defined for standard GAS are compatible with JGAS.

Typically, the name of the configuration file matches the name of the application and has an xcf suffix. For example, if the application name was "app1", create a configuration file named app1.xcf.

The configuration starts with the APPLICATION (for an application) element. Within this element, you can define local resources, set the execution environment, the timeout, and the output settings.

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.

Inheritance mechanism

The JGAS configuration has no inheritance mechanism as in standard GAS. Therefore the Parent attribute is not used in the APPLICATION element. For compatibility with existing xcf files, if a Parent attribute is defined, it is just ignored. Template application and service configurations provide defaults that applications can use. See Application and service templates.

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.

Example 1 - A simple application configuration file

The simplest application configuration file specifies a path to the compiled application files.

<APPLICATION>
  <EXECUTION>
    <PATH>$(res.deployment.path)/app</PATH>
    <MODULE>helloapp.42m</MODULE>
    <AUTO_LOGOUT>
      <TIMEOUT>20</TIMEOUT>
    </AUTO_LOGOUT>
  </EXECUTION>
</APPLICATION>

Note: The MODULE element specifies the name of the .42m module to run. If the module name is the same as the configuration file name, the MODULE element is not necessary.