...
More detailed information on the individual steps can be found in the following sections.
1) Preparatory measures
1.1) Performing a database backup
As a first step, you should create a database backup that can be restored (rolled back) if the update fails. For information on how to do this, please refer to the user manual of your database management system.
1.2) Stopping the web application server
- Stop the web application server (e.g. Tomcat) in the usual way using either the command line or the Service Manager.
- Delete the contents of the “work” directory in the Tomcat installation.
1.3) Save old deployment
- In the subdirectory "\webapps" of the Web Application Server, you can find the deployment installed so far (usually with the name "\gtc").
- 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
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:
...
After the preparations are complete, you can update the database and then the deployment.
2) Update database
If SQL scripts are included with the delivery package, please carry out the following steps:
...
| Warning | ||
|---|---|---|
| ||
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. |
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.
...
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
- 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.
- 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.
- 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".
- If errors occur in the web application after the update, please also contact 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.
...
- In the testing and production environment the GTC is installed in version 19.00.01.
- Now you update the testing environment with version 19.00.03.
- A few weeks later you will receive a new delivery package and update the testing environment. This now has the version 19.00.07.
- The production environment still runs with version 19.00.01.
- You receive the permission from the business department to update the production system to version 19.00.07.
- In any case, you must first import the scripts of version 19.00.03 before you continue with the installation of version 19.00.07. 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.
...
- Activate Web Service to TransferClient
- Setting up the proxy between GTC and TransferClient (optional)
- Testing the connection to the TransferClient
- 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).
...
| Category | WebService |
| Name | eric |
| Host | <http://ipOderDns> |
| Port | <Port> |
| Parameter 1 | <"eric..."> |
6.2) Proxy between GTC and TransferClient
The proxy is maintained as a separate connection parameter on the administration page.
| Category | External system |
| Name | atcProxy |
| Host | <http://ipOderDns> |
| Port | <Port> |
| User | <UserName> |
| Password | <Password> |
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.
| Note |
|---|
With this test only the connection to the TC is tested. It can still happen that the TC itself cannot establish a connection to the tax administration. For this purpose, a proxy may have to be configured or ports may have to be released (see TC instructions). |
6.4) Proxy between TransferClient and tax authorities
The proxy is maintained as a separate connection parameter on the administration page.
...