In opening a Knowledge Base from GeneXus 17 Upgrade 8 or higher, if you use an older version of GeneXus, it will automatically import the new version of GAM (4.0.6).
A Build performed from the IDE will automatically execute a reorganization of the Database, and a metadata migration, immediately after that.
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.
The steps for performing the update in the Production environment are:
- Reorganize the Database. To this end, the SQL script content is distributed in the GeneXus installation in the following path: <GX_installation_path>\Library\GAM\Platforms\<environment>\ReorganizationScript405To406.txt
Note: The execution of the reorganization process must be incremental. When migrating from a version prior to 4.0.5, you must execute each reorganization in order, starting by the one that follows your version.
- To complete the upgrade, migrate the metadata using the 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.5 to 4.0.6
The GAM Database is fully backward compatible. This means that you may continue using KBs with a GeneXus version prior to v17u8 pointing at a new Database.