...

1. In the subdirectory "\webapps" of the Web Application Server, you can find the deployment installed so far (usually with the name "\gtc").
2. Rename this directory (e.g. "\gtc_old") and then move it to a directory outside the "\webapps" directory. Under no circumstances may the backuped deployment remain in the "\webapps" directory. This would lead to serious errors later on in the update process. 

1.4) Update SAPJCO(optional for systems with a SAP connection)

The GTC is working with a new SAPJCO version. Provided RFC connections are addressed with the GTC, you must perform the following steps when updating to GTC version 20.11.03 or newer:

1. Remove the "sapjco3Download the suitable connector for your system from this offical SAP-Site.
2. Delete any old sapjco{*}.jar " file from the deployment this directory: "<Tomcat-root>/webapps/<gtc-root>/WEB-INF/lib".The following steps must be performed only once:Remove the "sapjco3
3. Paste the new sapjco{*}.jar " file from the "in this directory:  "<Tomcat-root>/lib" directory, if necessary.
4. For licensing reasons, we are not allowed to offer these files for download or distribute them in the package. Download the files "sapjco3*.dll" or "libsapjco3.so" and "sapjco3{*}.jar" from the SAP support website.
5. Replace the dll or so file. (The Windows dll is usually placed in the system32 folder).
6. Place the downloaded "sapjco3{*}.jar" file in the "<Tomcat-root>/lib" directory. Do not rename the file. If an old sapjco{*}.jar exists in this folder replace it with the new one.
7. Delete the old sapjco{*}.dll from the system. It can be in different locations, but in most cases it is in the system32 folder from Windows.
8. Paste the new sapjco{*}.dll in this directory: "<Tomcat-root>/bin"

If you get any problems with this please contact our hotline.

After the preparations are complete, you can update the database and then the deployment.

...

If you know of any other modifications to the deployment (e.g. in the "web.xml" file), please copy these too by editing the respective file.

3) Update database

The database update can be done automatically or manually.

By default you'll get a delivery package without databasescripts and activated automatic datebase update feature.

Optionally you'll have the chance to update the database by manually executing scripts against the database. We can create and send the scripts to you if needed. Please see Section 3.2

3.1 Automatic update of the database

Please make sure to have a current database backup at hand, so it can be restored if needed.

Update of database doesn't need additional tasks. Upon start of application server (see section 5), the database is updated automatically by application.

Reminder: update of the database is done without further notification at startup, please check the log file "gtc_dbMigration.log" for messages. 

After successful update, the logfile should show:

2021-10-22 15:12:57 [INFO ] ###################### Migration successful ######################
2021-10-22 15:12:57 [INFO ] ScriptLocationPath: C:\Tomcat 9.0_GTC\webapps\ROOT\migration/sql
2021-10-22 15:12:57 [INFO ] ConfigLocationPath: C:\Tomcat 9.0_GTC\webapps\ROOT\migration/flywayConfig.properties
2021-10-22 15:12:57 [INFO ] CSVPlaceholderPath: C:\Tomcat 9.0_GTC\webapps\ROOT\migration/FlywayPlaceholders.csv
2021-10-22 15:12:58 [INFO ] ############################################
2021-10-22 15:12:58 [INFO ] Current version: 20211001100000000_DELETE FROM TFLAGCONFIGURATION
2021-10-22 15:12:58 [INFO ] Pending Scripts: No pending scripts
2021-10-22 15:12:58 [INFO ] ############################################

3.2 Manual update of the database

...