The following is a brief overview of how you should proceed when updating the Tax Services.

The delivery package for the Tax Services application usually consists of a deployment (directory with war file).

After the delivery package has been downloaded, you can start the installation.

Preparation actions

Perform database backup

As a first step, you should create a database backup that can be restored (rolled back) if the update should fail. For information on how to do this, please refer to the user manual of your database management system.

Stop the Web Application Server

1. Stop the Web Application Server (e.g. Tomcat) as usual via the command line or the Services Manager.

2. Delete the contents of the "work" directory of the Tomcat installation.

Back up old Deployment

1. In the "\webapps" subdirectory of the Web Application Server you will find the previously installed deployment (usually with the name "taxtransferhub").

2. Rename this directory or the "war" file (e.g. to "taxtransferhub_alt") and then move it to a directory outside the "\webapps" directory. The saved deployment must never remain in the "\webapps" directory. This would lead to serious errors in the later course of the update.

After the preparations have been completed, you can update the deployment.

Update the deployment

Copy the new deployment into the subdirectory "\webapps", i.e. "<installation directory Tomcat>\webapps\taxservices". If necessary, unpack the zip archive.

Similar to the previously installed Tax Services version, the new deployment must be made aware of the type of database it is to connect to.

1. If a JNDI connection is used, no adjustment is necessary.

2. When specifying the database connection directly:

   1. Edit the file "\WEB_INF\classes\META-INF\persistence.xml".

   2. Delete the line with the XML tag "" completely.

   3. Comment out the "" XML block.

   4. Comment in the block for your DBMS and comment out the other blocks.

   5. Adjust the IP/host name of the database server, the database name and user/password according to the parameters selected under the item "Database".

Final steps

1. Start the Web Application Server as usual via the command line or the Services Manager. The database migration is now started when the server is started. Do not cancel the server start, even if it takes longer than usual to start.

2. After starting the Web Application Server, test access to the Tax Services or inform your responsible department to have access tested if you do not have access data for the Tax Services yourself.

3. If errors occur in the web application after the update, please also contact the GlobalTaxCenter hotline and send the log files along.