By default, easyTravel uses an internal Derby Database on the Java side and an SQL Server Compact internal database on the .NET side. However you can change this to use other types of RDBMS, this page describes how you can configure this.
In the EasyTravel installation (dist) folder, search for this file:
These properties control the Database:
The above values are part of the standard EasyTravel installation.
They can be changed to use any database desired. The following sets of properties have been
tested against DB/2, SQLServer and Oracle DBMS:
also files launching jvm like weblauncher/weblauncher.sh should look like below:
Example code for the DB user creation:
There are at least two different JDBC drivers available for SQL Server, depending on which one you want to use the following settings apply:
SQL Server with JTDS-JDBC Driver
SQL Server with Microsoft JDBC Driver
easyTravel cannot ship the Microsoft JDBC driver because of license considerations. To make it work, you need to complete the following steps:
- Download the MS SQL JDBC drivers at: http://go.microsoft.com/fwlink/?LinkId=245496
- Unpack "mssql-jdbc-7.0.0.jre8.jar" to C:\Program Files\dynaTrace\easyTravel (x64)\lib
- Unpack "META-INF/MANIFEST.MF" from "com.dynatrace.easytravel.database.jar" in your main easyTravel directory
- Add "lib/mssql-jdbc-7.0.0.jre8.jar" to the end of the Class Path in MANIFEST.MF
- Overwrite the MANIFEST.MF in "com.dynatrace.easytravel.database.jar" with your changed file.
How to configure MySQL
Create a database and allow access from other machines:
Adjust config at /etc/mysql/my.cnf, in section [mysqld]:
character-set-server = utf8
collation-server = utf8_bin
- comment out
bind-address = 127.0.0.1
EasyTravel will try to automatically create the schema, which works for built-in Derby and the above mentioned DBMS.
This is done with the hibernate feature hibernate.hbm2ddl.auto set to update.
It also creates the database content on startup. Existing content will not be erased.
Currently two databases are supported:
- SQL Server Compact Edition (which is default)
- SQL Server
to switch to SQL Server you have to modify dotNetPaymentBackend/web.config.
at the bottom of the file you will find the element "connectionStrings". There remove the currently active connection-strings for "PaymentEntities" and "SQLConnection" and uncomment the other two, which are prepared for SQL Server.
Then fill out the place-holders with the corresponding values:
- **source** --> server
- **database** --> datebase-name
- **user** --> db-user
- **password** --> db-password
Make sure to modify both the SQLConnection and PaymentEntities.
Currently Schema has to be set to "dbo" which is the default value of SQL Server.
To create the tables on SQL Server with the correct constraints the following Script can be used: