Configuration for web and service applications
Configure Genero web applications and services using a subset of the elements provided for the Genero Application Server configuration.
- added to the Genero Application Server configuration file (as.xcf).
- provided in application-specific configuration files. Each application has its own configuration file, written in XML.
Elements in an application's configuration
The elements allowed, and how they are used, depend on whether the application is a web application or a web service (GWS). For a full list of valid elements and their place in the file hierarchy, see the appropriate topic:
Use application-specific configuration files
When you save changes to an application-specific configuration file, you do not need to restart the dispatcher. The dispatcher automatically detects the change, stops the existing proxy process, and starts a new proxy process with the updated configuration:
- For a web application, the dispatcher stops the existing uaproxy process and starts a new one.
- For a web service, the dispatcher stops the existing gwsproxy process and starts a new one.
You can archive application-specific configuration files separately from the GAS configuration file, and upgrades do not overwrite them. For these reasons, use application-specific configuration files rather than adding configuration to the GAS configuration file (as.xcf), which requires a dispatcher restart before changes take effect and risks being overwritten during an upgrade.