GAS 3.10 new features

A summary of new features and changes in functionality introduced with Genero Application Server (GAS) 3.10.

Important: This page covers only those new features introduced with the Genero Application Server version specified in the page title. Check prior new features pages if you migrate from an earlier version. Make sure to also read the upgrade guide corresponding to this Genero version.

Corresponding upgrade guide: GAS 3.10 upgrade guide.

Previous new features guide: GAS 3.00 new features.

Table 1. General
Overview Reference
The Genero Web Client for JavaScript (GWC-JS) is renamed to Genero Browser Client (GBC). All documentation is updated to use the new name. No additional reference.
GBC is no longer embedded in the Genero Application Server (GAS). It is now delivered as its own module in the Genero Enterprise bundle. It is also documented in a separate manual. See Genero Browser Client User Guide.
Table 2. Docker and the GAS
Overview Reference
The GAS provides support for creating a Docker image to run the GAS in a Docker container.
Note: In ${FGLASDIR}/docker, follow the instructions in the Readme.md to build and run a docker container.
 See Run Genero Application Server in Docker container.
Table 3. Single Sign-On (SSO) and delegation
Overview Reference
There is a new method for managing environment variables defined in delegation parameters and passed in HTTP headers to the REST service. Environment variable names are converted to uppercase before being set in the DVM environment. See DELEGATE and From the REST service to the proxy
The PROMPT element provides a feature that allows a user to re-log in to an application after an auto logout event.
Note:

Delegation Web services for SSO OpenID Connect and SAML are provided in the FGLGWS package. These support the PROMPT (for auto logout) feature.

See Re-login prompt and Authorize re-log in with OpenID Connect SSO and Authorize re-log in with SAML SSO
Table 4. Web Services and the GAS
Overview Reference
In your Web services configuration files (xcf) a reference to a parent configuration in the APPLICATION element's Parent attribute is required. This reference must contain the prefix "ws.". See APPLICATION (for a service) and Configure applications for Web service
Authentication and access service security cookie updated with SameSite="Strict". See SameSite attribute is now recommended when setting HTTP cookies
Table 5. Engine and Architecture
Overview Reference
The Genero Application Server for Java (JGAS) is an implementation of the Genero Application Server (GAS) that is written in Java. It can be used for the development, testing, and deployment of applications to a Java Enterprise Edition (Java EE) server. It is also documented in a separate manual. See Genero Application Server for Java User Guide
The j2eedispatch dispatcher is being replaced by the JGAS. The j2eedispatch supporting topics have been removed. Please see the Java Servlet Installation and Web Server Configuration topics in the Genero Application Server 3.00 User Guide.
A new element called REPORT_REMOTE_URL_PREFIX added to INTERFACE_TO_CONNECTOR allows you to configure the URL of the Genero Report Engine server. See REPORT_REMOTE_URL_PREFIX, Configuring Genero Report Engine on GAS
The desupported proxies gdcproxy and html5proxy are no longer provided in the package. They are replaced by the universal proxy, uaproxy (ua), which is used for all applications. The supporting topics have been removed. Please see the Tools and Commands topics in the Genero Application Server 3.00 User Guide.
In an enhancement for GAS 3.10.16, dispatchers create a pid file. You can set the httpdispatch and fastcgidispatch dispatchers to write their process-ids to a file on disk with the --pid-file option of the command. See
The options of the GAS tool named gasadmin have been reorganized into commands; session, config, gar, gbc, reset-log.
  • The gbc command adds functions for working with GBC clients.
  • The reset-log provides options to reconfigure logs for a proxy session; such as change the output type, or output path.
 See gasadmin tool.
The --session-cleanup option of the gasadmin tool has been enhanced to clean temporary files/directories created, that may not have been removed at the end of a session. See gasadmin tool.
The --monitor option of the gasadmin tool allows you to retrieve information to monitor a session. See gasadmin tool.
Specifying a GBC front-end customization has been simplified. The GBC element may contain the name of a file that specifies the customization directory. The GBC can also be specified in a URI query string parameter to override the application configuration. See GBC and URI Examples
The GWC_JS_LOOKUP_PATH element is renamed to GBC_LOOKUP_PATH. Both names continue to be supported. See GBC_LOOKUP_PATH
The GWC-JS element is renamed to GBC. GWC-JS is deprecated. Both elements continue to be supported. See GBC
The environment variable FGL_VMPROXY_START_URL is set to the URL used to start the application, which is available for use by the Genero BDL application. See How to get the URL of the application
Starting at 3.10.19
One license consumed per browser:

All applications started from the same browser count as one for licensing purposes, and therefore only one license is used.

 See Genero front-ends and license counting
Table 6. Deployment
Overview Reference
The fglgar tool has new features for packaging and deploying Web applications. It is no longer provided in the GAS package. It is now delivered in the FGLGWS package. See the fglgar topic in Genero Business Development Language User Guide.
The res.gbc.deployment resource points to $(res.appdata.path)/gbc_deployment. It contains the deployed GBC clients and is part of the default GBC_LOOKUP_PATH. See GAS installation and application data directories and the gasadmin gbc command options in gasadmin tool.
A deployment portal is provided to deploy GBC and Genero Archives via an HTML web page. It is accessible at URL http://host:port/ws/r/services/DeploymentService/html. See the Genero deployment portal topic in Genero Application Server User Guide 3.10.
The GBC can be reset to the initial installed version delivered in the FGLGWS package with the gasadmin gbc command and the --reset option. A reset can also be carried out via the deployment portal. See:
A GBC client deployed on the GAS can be renamed with the gasadmin gbc command and the --rename option. You can also use the deployment portal interface to rename the GBC. See:
  • gasadmin tool
  • See the Genero deployment portal topic in Genero Application Server User Guide 3.10.
Table 7. Miscellaneous
Overview Reference
The desupported fglxslp migration tool is no longer provided in the package. All supporting topics have been removed.
Note:

The new features listed in this topic are available in the latest version of the GAS. Contact your support channel for more details.