Configuration
Starting with version 2.30, the configuration file has been simplified. Some configuration parameters are no longer needed due to the new architecture, and others are now handled transparently (such as the Web services pool and load).
--development
To start a GWC application in development mode, you must add the option --development to the gwcproxy entry in the appropriate xcf file.
<RESOURCE Id="res.gwcproxy.param" Source="INTERNAL">--development</RESOURCE><RESOURCE Id="res.gwcproxy" Source="INTERNAL">
"$(res.path.as)/bin/gwcproxy" $(res.gwcproxy.param)
</RESOURCE>Configuration file (xcf) inheritance
Prior to version 2.30, when an application was started with a RUN, the child application inherited the configuration of the parent unless the child application has its own configuration file. If the child application had its own configuration file (where the .xcf file shares the same name as the child application), then the child configuration took priority over the parent configuration, and was used for the child application.
Starting with version 2.30, this is no longer true. A 4gl application started with RUN or RUN WITHOUT WAITING will inherit the configuration of the parent application, and this cannot be changed. The configuration used to start the first application (the first FGLRUN) will be used for all child applications (child FGLRUNs).
While you might want to review your parent/child applications, this will likely not have an impact, as a customer survey determined that most had only provided a configuration file for the parent application and had not provided a configuration file for the child applications.
Resource of type FILE
Starting with version 2.30, resources of type FILE are no longer supported.
<RESOURCE Id="res.theme.default.gdc.template" Source="FILE">
$(res.path.tpl)/fglgdcdefault.html
</RESOURCE>ALIAS entry removed
Starting with version 2.30, the entry ALIAS has been removed. You can configure the
PICTURE element instead. For more information see the PICTURE topic in
the Genero Application User Guide v2.30
THREAD_POOL entry removed
Starting with version 2.30, the entry THREAD_POOL has been removed.
LOG output of type PATH de-supported
Starting with version 2.30, you cannot set a log output of type PATH.
REQUEST_QUEUE and REQUEST_RESULT for Web services are removed
Starting with version 2.30, Web Service REQUEST_QUEUE and REQUEST_RESULT have been removed.
Instead of these timeouts, the web server one is used. For example, the fastcgi idle timeout.
DVM_FREE removed
Starting with version 2.30, Web Service DVM_FREE has been removed.
It is no more needed as the Web Service pool management uses statistics of previous requests to decide whether to stop a DVM or not.
Hot Restart no longer necessary
There is no longer a need for a hot restart, as changes in an external XCF file are immediately taken into account at:
- Application startup for a web application
- GWS DVM startup for web services that could be at each new request
As a result, you should check the changes you have made to your XCF files and ensure they are correct before you save the file. For example, you could create a test.xcf file and validate that the test.xcf file is correct; then replace the production xcf file (assume the file is named prod.xcf for this discussion) by archiving prod.xcf and renaming test.xcf to prod.xcf.
Socket port selection
The following three entries of the INTERFACE_TO_DVM configuration are deprecated and will be removed in the next release.
The selection of a free socket port will be in charge of the operating system for performance issues.
License Consumption and Web Service Applications
Prior to this release, when it came to consuming licenses, you were able to go over the setting
of MAX_AVAILABLE, up to the limit specified for the application by the
MaxLicenseConsumption attribute. This is no longer the case.
MaxLicenseConsumption is no longer available as an application attribute and will
be ignored by the Genero Application Server. The maximum limit for licenses is given by
MAX_AVAILABLE. You will not be allowed to go over this limit.