JGAS 5.00 upgrade guide

These topics describe product changes you must be aware of when upgrading to version 5.00.

Important:

This incremental upgrade guide covers only topics related to the Genero Application Server for Java (JGAS) version specified in the page title. Check prior upgrade guides if you migrate from an earlier version, and complete the migration tasks for all versions between your existing version and the target version, in order. Make sure to also read about the new features for this version.

Corresponding new features page: JGAS 5.00 new features.

Previous upgrade guide: JGAS 4.01 upgrade guide,

This release does not require you to complete specific instructions or be aware of changes when upgrading from the previous version.

Changes to JGAS delivery

Starting with version 5.00, the JGAS is no longer embedded in the FGLGWS package. Its installation path is no longer in the $FGLDIR/web_utilities/jgas directory.

The JGAS is now provided in a separate standalone archive (zip).

Where before you did not need to install the JGAS, you now need to download the JGAS package from the Download page of the Four Js Web site and install it to a local directory of your choice. For installation details, go to Install Genero Application Server for Java.

Standalone JGAS and Jetty no longer embedded

Starting with version 5.00, the embedded Jetty web server and the standalone JGAS is removed from the JGAS installation. Where before you could execute applications deployed in a war file with the standalone JGAS, you now need a Java Enterprise Edition (J2EE) container such as Apache Tomcat® (version 10 or greater), Jetty, or Glassfish, to access your applications and services via a browser.
Important:

If using Apache Tomcat, the JGAS is compatible with Apache Tomcat version 10 or greater.

For details of the contents of the installation package, go to JGAS package content.

Changes to fglgar

Starting with version 5.00, there are changes to the fglgar command features for creating Java Web Archive (war) files and running applications.
  • When creating a war file, you must now use the --web-content option of the fglgar war command to specify the path to the Java Web Content directory of your JGAS installation. The --web-content option is now mandatory. For examples, see Build war file and run the application
  • Where before you could execute applications deployed in a war file with the standalone JGAS using the fglgar run command, this feature is no longer available and therefore the fglgar run has been removed.
For more information on using fglgar commands, refer to the fglgar page in the Genero Business Development Language User Guide. For details of other changes, such as creating war files for testing and deployment, review the JGAS Quick Start topics.

Java version 17 required

Starting with version 5.00, you need a Java Development Kit (JDK) to use the JGAS. Make sure that your JDK version is version 17 or greater.

Single sign-on (SSO) now has its own manual

Single Sign-on topics are no longer included in the Genero Application Server for Java User Guide. SSO is now documented in the Single Sign-On User Guide.

Changes in earlier versions

Make sure to check the upgrade notes of earlier versions, to not miss changes introduced in maintenance releases. For more details, see JGAS 4.01 upgrade guide.