Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

2) Update

...

If SQL scripts are included with the delivery package, please carry out the following steps:

...

    • 01_MSSQL_8.3.02_8.4.04.sql
    • 02_Insert_Reporting_MSSQL.sql
    • etc.
Warning
titleDatabase permissions

To import the database scripts use a user who has full permissions to the database schema. Otherwise, it may happen that database tables cannot be created or updated correctly or that the GTC cannot access the tables properly at runtime.

In any case, check the results in the log files to see if there are any anomalies. If you find any errors, please get in touch with the  Hotline GlobalTaxCenter.

...

deployment

Copy the new deployment into the subdirectory "\webapps", i.e. "<installation directory Tomcat>\webapps\gtc\". It may need to unzip the zip archive.

...

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


Warning
titleDatabase permissions

To execute the database scripts use a database user who has full permissions to the database schema. Otherwise, it may happen that database tables cannot be created or updated correctly or that the GTC cannot access the tables properly at runtime.

In any case, check the results in the log files to see if there are any anomalies. If you find any errors, please get in touch with the  Hotline GlobalTaxCenter.

If SQL scripts are included with the delivery package, please carry out the following steps:

  1. Start the DBMS of your database server and select the database schema that belongs to the GTC application.
  2. Execute the supplied SQL update scripts in order of the file names or versions on this schema. Use a user who has full permissions on the database.

    Example:
    • 01_MSSQL_8.3.02_8.4.04.sql
    • 02_Insert_Reporting_MSSQL.sql
    • etc.

4) Final steps

  1. Start the Web Application Server as usual from the command line or the Service Manager. Autorun jobs may now be executed when the server is started. These are part of the update and must be executed successfully. Do not cancel the server start, even if it takes longer than usual.
  2. After starting the WAS server, test the access to the GlobalTaxCenter or inform your responsible department to have the access tested if you do not have access data for the GTC yourself.
  3. Change (or an authorized representative) in the Masterdata area to the Administration dialogue and there to the Log tab and open the file "gtc_autorun.log". Check whether the autorun jobs have run successfully or whether error messages are displayed. In case of an error, please contact the Hotline GlobalTaxCenter and send the log files "gtc_autorun.log" and "gtc_system.log".
  4. If errors occur in the web application after the update, please also contact the Hotline GlobalTaxCenter and send the log files.

...