Foreword

We like to welcome you as a client of the GlobalTaxCenter.

The following is a quick installation guide for the GlobalTaxCenter assuming a default installation on a Tomcat application server.

If your installation requirements differ from the assumptions made here, we will be happy to consult you on how to facilitate the integration of the GlobalTaxCenter in your company.

Preconditions

Data base

A database on one of the following database servers

• Microsoft SQL Server 2012 or later
  
  
• (Oracle 12c)

Application server

• Apache Tomcat 7 or 8

• Oracle Java JDK at least 1.8
• JDBC driver for one of the following databases:
  • Oracle 9i, 10g, 11 (http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/)
  • Microsoft SQL Server 2008(R2) (http://msdn.microsoft.com/data/jdbc)

The following folder structure should appear in your delivery after unpacking:

• database scripts
  • <"Mysql|MSSql|Oracle-create.sqlScript">
  • < if necessary additional scripts with numbering >

• deployment
  • gtc
    • Jsp
    • META_INF
    • WEB_INF
    • Static
    • <and further folders>

Tomcat installation

In the following we assume an installation on a Windows operating system.

An installation on a Unix-like system only differs in the paths and the installation procedure described under 1) and 2).

1. Install the JDK and create the system variable "JAVA_HOME" which points to the installation directory.
2. Install Apache Tomcat into a folder of your choice. In the following the folder "C:\Server\Tomcat" is assumed.

In detail:

• We recommend to install the start menu entries to simplify the configuraton.
• The ports used by Tomcat can be customized to your needs.

Configuration after installation

1. Unpack the delivery and extract the file "JAAS.config" in the folder "WEB_INF\classes\" and copy it into the installation directory of Tomcat (C:\Server\tomcat).
2. After installation execute the application "→ start menu → tomcat → "configure tomcat".
3. Perform the following steps:

                Tab "General": Set starting-option of the service to automatic

                Tab "Java": In the window "Java options" add the line

                "-Djava.security.auth.login.config=<path and filename of JAAS.config>" (which you copied in Step 1)

                Insert the lines in the same window:

                      -XX:PermSize=256m

                      - XX:MaxPermSize=512m

              Enter "128" in the Initial Memory Pool window.

              In the Maximum Memory Pool window, enter about half of the available RAM. Please consider the following 32 bit systems the limitation of the working memory to approx. 3.5 GB.

             The memory settings affects the influence of the performance and the running capability of the application.

             These may have to be adjusted over time as the use of the product increases.

Database

1. The steps for setting up the database are kept general at this point in order to satisfy the different configurations of the database systems.
2. Create a new database/database scheme on the database server.
3. Create a database user with permission to "INSERT", "UPDATE", "DELETE", "ALTER" on this database.
4. Make sure that the database can be accessed from the application server with this user. If you use the SQL Server with windows authentication, the Tomcat service must execute under a domain account and this domain account must be configured as a user in the database.
   Download the sqljdbc_auth.dll of the Microsoft JDBC driver sqljdbc_6.2 from the internet and copy it to the bin directory of Tomcat.
5. Execute the scripts included in your shipment to create the database on it.
6. Make sure that the user who imports the DB scripts has all rights on the GlobalTaxCenter database.

Application setup

The following steps set up the GlobalTaxCenter web application on the Tomcat application server.

1. Copy the folder "gtc" from your delivery into the "webapps" directory in the Tomcat installation directory. Of course, you can edit it to another location to configure it and copy it to "webapps" after completion.
2. Now configure the following files below this folder:

• WEB_INF\classes\repository.xml:

          search the line <!ENTITY datasource SYSTEM "repository_mysql.xml" and replace "mysql" according to your database with "oracle", "mssql" or "mssql_integratedSecurity" if necessary.

• WEB_INF\classes\repository_<dbms>.xml:

          here <dbms> stands for the database system selected above. In this file you adjust the IP/ host name of the database server, the database name and the user/ password according to the parameters selected under "Database"

• WEB_INF\classes\repository_mssql_integratedSecurity.xml:

         In this file, you adjust the IP/ host name of the database server and the database name.

System start und activation

1. Now start the Tomcat application server either under System Services or with the "Configure tomcat" application.
2. Start a browser and enter in the address bar (note the port selected in "Install Tomcat"): http://<IP adress or hostname of the application server>:8080/gtc
3. It should now load a login page, where you can log in - user: superuser ; password: test.
4. Now a website should ask you for activation. Copy the contents of the upper text window into an e-mail and send it to your contact person from our company. Alternatively, you can click the "Request activation" button, which automatically creates an e-mail.
5. We will send you the activation in the form of  a text file. Please copy its content into the text window below and confirm by clicking on "Activate".
6. If an error should occur with one of the previous points, please check the parameters entered under setup of the application and contact us.

Concluding remark

After the GlobalTaxCenter has been activated, the installation is sucessfully completed.

The software can now be handed over to the specialist departments for productive or specialist tests.

Finally, a few remarks:

1. We recommend that you back up the database regularly, as this contains the application data.
2. The deployment does not have to be backed up all the time. In this case, it is sufficient to keep the status ready when a version is delivered.
3. You should document the configuration you have carried out so that adjustments can be made in the event of system updates or a recovery. In particular, you should note any adjustments that are made that differ from those in this document.