Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The following section offers a short guide to updating the GlobalTaxCenter (GTC).

The delivery package for the GTC application generally comprises one deployment (directory with files, was file, or similar) and one directory in one or more database scripts.

Once the delivery package has been downloaded you can begin with the installation. Before you begin you should create a database backup (rollback), which can be recovered should the update fail. When these preparations have been completed you can update the database and the deployment. AMANA recommends that you start with the database and then update the deployment.

More detailed information about the individual steps is provided below.

1) Preparatory measures

1.1) Stop the web application server

  1. Stop the web application server (e.g. Tomcat) in the usual way using either the command line or the service manager.
  2. Delete the contents of the “work” directory in the Tomcat installation.

1.2) Making a backup of the old deployment

  1. The deployment currently installed (usually named "\gtc") is to be found in the "\webapps" subdirectory of the web application server.
  2. Rename this directory (e.g. "\gtc_alt") and then move it to a directory outside of the "\webapps" directory.

2) Update the database

If SQL scripts are attached to your package, please carry out the following steps:

  1. Start the SQL server management studio of your database server and select the database schema applicable for the GTC application.
  2. Execute the supplied SQL update scripts sequentially, either in order of file names or versions, in this schema. Apply a user with full permissions for the database. Example:
    • 01_MSSQL_8.3.02_8.4.04.sql
    • 02_Insert_Reporting_MSSQL.sql
    • etc.

Database permissions

To import the database scripts apply a user with full permissions for the database schema. Otherwise it may not be possible to correctly create or update tables, or the GTC may not be able to access the tables properly during runtime.

It is important to check for anomalies in the protocol results. If you find any errors, please get in touch with the  AMANA Hotline.

3) Update the deployment

Copy the new deployment into the "\webapps" subdirectory, i.e. "<Installationdirectory Tomcat>\webapps\gtc\". It may be necessary to unpack the zip archive.

As with the currently installed GTC version, the new deployment must be informed which type of database it should connect to. This is done by creating a reference to the correct database (MySql, Oracle, MS SQL) in the central "<gtc-root>WEB_INF\classes\repository.xml" file. The connection parameters must then be updated in the respective repository_<xyz>.xml.

A note on copying configuration files

Avoid simply copying the repository.xml files from the old GTC deployment into the new deployment. This can lead to errors because the content of the repository files can change slightly over time.

  1. Modifying the "<gtc-root>WEB_INF\classes\repository.xml" file:
    This is where you inform the GTC what kind of database to connect to. Search for the line: <!ENTITY datasource SYSTEM "repository_mysql.xml"> and if necessary replace the term "mysql" depending on your type of database. If you are using Oracle, type in “oracle”. For an MS SQL database write “mssql” (z.B. <!ENTITY datasource SYSTEM "repository_mssql.xml">).
  2. Copy the connection settings from the "repository_mysql.xml", "repository_oracle.xml" or "repository_mssql.xml" from the previous backup into the directory "<gtc-root>WEB-INF\classes\" and into the same-named file of the new 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.

4) Final steps

  1. Start the web application server in the usual way via the command line or service manager.
  2. Test your access to the GlobalTaxCenter (or) ask the department responsible at your company to test the access for you.
  3. If errors occur in the web application after the update, please contact the AMANA Hotline and send the “gtc_system.log” file from the subfolder “\log” of the Tomcat installation.
  • No labels