Page Comparison

...

1.6) Switch Tomcat to Java 17

If you already had a GTC version 22.09.00 or newer installed, you can skip this step.

The document Upgrade from Java8 to Java17 describes how Java 17 is installed and made known to the Tomcat 9.

...

1.7) Store database driver in Tomcat

If you already had a GTC version 22.09.00 or newer installed, you can skip this step.

For licensing reasons, AMANA is not allowed to deliver the JDBC drivers for MySQL, Microsoft SQL Server and Oracle in the GTC deployment.

...

If you get any problems with this please contact our hotline.

1.9)

...

Central in Tomcat (JNDI)

Update Kerberos SSO configuration (optional)

If single sign-on with Kerberos has been implemented in your installation, you must implement adjustments.

With Java 17, weak Kerberos authentication is no longer officially supported. In this chapter we provide detailed information on the configuration.

Kerberos-SSO when using Java 17

1.10) Configuration of the database connection in the GTC

Central in Tomcat (JNDI)

If you are already using the JNDI configuration, you can skip this step.

The previous standard deployment of the GTC provided that the database connection was customised for each GTC delivery in the repository file matching the database. This process is now simplified to the extent that the standard deployment is configured with the JNDI datasource "gtcdatasource". For this purpose, the customer must expand the context.xml file in the Tomcat/conf directory once per Tomcat by defining the JNDI datasource there within the context tag. Using the JNDI configuration has the advantage that the database connection no longer has to be adapted within the GTC deployment.

<Resource auth="Container" driverClassName="com.mysql.cj.jdbc.Driver"oracle.jdbc.driver.OracleDriver"
        maxTotal="20" maxIdle="10" maxWaitMillis="-1" name="jdbc/gtcdatasource" username="root" password="test" 
        type="javax.sql.DataSource" url="jdbc:mysqloracle://localhosthostname:3306/gtc" 
/>

When using the Microsoft SQL server, information on the encryption (encrypt) and the trustworthiness (trustServerCertificate) of the server certificate must be provided:

<Resource	auth="Container" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"     
            maxTotal="20" maxIdle="10" maxWaitMillis="-1" name="jdbc/gtcdatasource" username="root" password="test" 
			type="javax.sql.DataSource"  			url="jdbc:sqlserver://hostname:1433;DatabaseName=...;encrypt=...;trustServerCertificate=..." 
			username="..." password="..." ...
/>

In the case of the Microsoft SQL server, AMANA also recommends an installation with Integrated Security, in which no username and password details need to be stored in the context.xml. Instead, the account under which the Tomcat service is run is used for the database connection.

...