...
| Excerpt |
|---|
|
Configuration of the "Tomcat 9"MemoryAfter installation, run the application "->Startmenu->Tomcat->"configure tomcat" and perform the following steps: Tab "General": Set the start of the service to automatic. Tab "Java": Enter "512" in the field "Initial Memory Pool". Tab "Java": In the field "Maximum Memory Pool" enter approximately half of the available physical memory. For example, 2048 for 4096 MB RAM. For 32-bit systems, please bear in mind the limitation of the working memory to approx. 3.5 GB. The memory settings made here affect the performance and runability of the application. They may need to be adjusted over time as usage increases.
HTTPSMake the necessary connector settings in the „D:\Server\Tomcat\lib\server.xml" configuration file to ensure communication via https. A reference to a valid key store for identifying the module Tax Transfer Hub to other applications must be maintained. Connection to the databaseDatabase driverCopy the database driver that matches your database server into the "\lib" directory in the Tomcat installation directory. Microsoft SQL Server - https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server
ConfigurationConfigure the database connection as a JNDI connection in Tomcat: |
...
| Excerpt |
|---|
|
Windows authentication(Optional for Microsoft SQL Server) From the JDBC driver package, the appropriate “*.dll”-file must also be copied from the folder “auth” into the directory “System32” of the system.
Example path: .\sqljdbc_8.2.2.0_deu\sqljdbc_8.2\deu\auth\x64\mssql-jdbc_auth-8.2.2.x64.dll The Windows user must be entered in Tomcat The user needs permissions on the server of the Tomcat to run the Tomcat service as well as write permissions in the Tomcat folder for logs. The user needs permissions on the database server. The user needs the above-mentioned permissions on the database schema.  Image Removed Image Added
The connections in the context.xml must correspond to this example:
|
...
| Excerpt |
|---|
| name | self-signed_Certificates |
|---|
|
Use of Self-Signed CertificatesIf you have integrated a self-signed TLS/SSL certificate in Tomcat, it can happen that HTTP requests from the Tax Data Hub this module to other modules cannot be carried out. In this case, enter the following parameter in the "Java Options" field in Tomcat. This explicitly allows the use of self-signed certificates in the application. This configuration is generally not recommended for productive systems. |
-Dtaxdatahub.api.allowSelfSignedCertificat=true
| Excerpt |
|---|
|
StartStart the Tomcat application server on which you have installed the
|
...
service module, either under System Services or with the "Configure Tomcat" application. Wait until the server has started.
|
...
Open a supported browser and enter the following in the address bar (note the port selected when installing the Tomcat): "http://:/taxdatahub".
...
Whether the service module has been configured correctly and is accessible from other modules can be checked via the module view of the portal. To do this, log in to the portal with administration rights and click on Modules in the Administration tab. The service module appears in the list and is indicated by a green traffic light. If the traffic light is yellow, check the connection properties to see whether the corresponding paths have been maintained correctly and check whether the https connection has been maintained correctly.
|
| Excerpt |
|---|
The software can now be handed over to the departments for use or professional testing. Finally, a few comments: We would like to recommend that you make a regular backup of the database, as this contains the data of the application. The deployment does not have to be backed up constantly. Here it is sufficient to have the status ready when a version is delivered.
|