When you open a Knowledge Base with GeneXus 18 Upgrade 7 or a higher version using a previous GeneXus version, the system will automatically import the new version of GAM (4.1.x).
A Build performed from the IDE will automatically execute a metadata migration, immediately after that.
This version won't run a Reorganization.
While in the Development Environment the update is performed automatically and transparently, the Database update in the Production Environment requires, the developer to execute it.
- Migrate metadata using GAM Deploy Tool (GDT) through the command line.
.NET Framework: In the directory <KB>\<NetFramework_env>\web\bin the exe is distributed.
agamdeploytool.exe -upgradegam -admin_name gamadmin -admin_pass gamadmin123
JAVA: In the directory <TOMCAT_DIR>\webapp\<App_Name>\WEB-INF\classes\<path_to_package> the class is distributed.
java -cp "../../../lib/*" genexus.security.api.agamdeploytool -upgradegam -admin_name gamadmin -admin_pass gamadmin123
.NET: In the directory <KB>\<NET_env>\web\bin the library is distributed.
dotnet agamdeploytool.dll -upgradegam -admin_name gamadmin -admin_pass gamadmin123
- If the GDT runs successfully, then the closing lines must be:
Connecting to GAM database ...
Data migration from 4.0.9 to 4.1.0
>>> Success
From GeneXus 18 Upgrade 9 onwards, the GAM version will be represented as follows: <major>.<minor>.<number>.
<major> and <minor> are used for data structure versioning; <number> is used for metadata versioning.
This migration will be the last one that will change its <minor> value to migrate only the GAM metadata. From 4.1.0 onwards, metadata migration will impact on the third digit (4.1.x), and when the <major> or <minor> value is changed (x.x.0) it will imply a Database Reorganization.
For more information, see the following SAC.
The GAM Database is fully backward compatible. This means that you may continue using KBs with a GeneXus version prior to GeneXus 18 pointing at a new Database.