...

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

...

The delivery package for the GTC application usually consists of a deployment (directory with files, war file, etc.) and a directory with one or more database scripts.Image Removed

Once the delivery package has been downloaded, you can begin with the installation. Please follow the order given below (first database and then deployment) when updating. A different order can lead to incorrect system behaviour after the update.

...

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. 

...

3) Update deployment

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

...

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 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 the Hotline GlobalTaxCenter and send the log files.

5) Transfer to other instances

If you are working with different instances (development, test, integration, production, ...) please be careful that you are doing the same steps in each instance.

For example:

1. Your In the testing and your production environment are working with GTC the GTC is installed in version 19.00.01.
2. Then Now you update the testing environment , first with version 19.00.03 and some weeks later with .
3. A few weeks later you will receive a new delivery package and update the testing environment. This now has the version 19.00.07.
4. The production environment is still working runs with version 19.00.01.Now you
5. want You receive the permission from the business department to update the production environment. Be careful that you update it first with system to version 19.00.07.
6. In any case, you must first import the scripts of version 19.00.03 and then with before you continue with the installation of version 19.00.07. So you can be sure, that no database updates are missing.This is the only way to prevent an inconsistency in the database.

6) TransferClient installation and integration into the GTC

If the GTC (Tax Return module) is also used for electronic transfers to the german tax authorities, the TransferClient version must also be updated at regular intervals. In this case, the GTC update provides a second installation package for the TC. This package has to be installed according to the instructions. During the installation the Web Service URL should be noted, because it has to be stored/updated in the administration area of the GTC.

To configure the TC connection in the GTC, the following steps must be performed. For the configuration, editing authorisations for the area Master Data / Administration are necessary.

1. Activate Web Service to TransferClient
2. Setting up the proxy between GTC and TransferClient (optional)
3. Testing the connection to the TransferClient
4. Setting up the proxy between TransferClient and tax authorities (optional)

6.1) Activate Web Service to TransferClient

The following configuration must be carried out so that the Elster transmission is available as a web service. On the administration page, the connection to the TC is added. (The TC must be started as a web service).
A new connection of the category "WebService" is set up. The name must be "eric" (case sensitive). 

"Host" and "Port" must be entered according to the TC installation. If the Web Service URL of the TC does not end in "eric", the last part of the URL (e.g. eric29) in the connection must be entered in the field Parameter 1.

6.2) Proxy between GTC and TransferClient

The proxy is maintained as a separate connection parameter on the administration page.

6.3) Connection test to the TransferClient

Now the connection to the TC can be tested by clicking on the gear symbol (in the front of the line). A message is then displayed whether the test was successful or not.

6.4) Proxy between TransferClient and tax authorities

The proxy is maintained as a separate connection parameter on the administration page.