MySQL

In this section are the necessary steps for the installation of the LumisXP database on the MySQL Server:

Open the MySQL Query Browser, create a new database and execute the script db_mysql.sql.
In the file lumisdata/config/lumishibernate.cfg.xml change the database connection information.
 <property name="dialect">org.hibernate.dialect.MySQL5InnoDBDialect</property> <property name="connection.driver_class">com.mysql.cj.jdbc.Driver</property> <property name="connection.username">DB_USERNAME</property> <property name="connection.password">DB_PASSWORD</property> <property name="connection.url">jdbc:mysql://HOST_NAME/DATABASENAME?characterEncoding=UTF-8&useSSL=false&allowPublicKeyRetrieval=true&useConfigs=maxPerformance&prepStmtCacheSize=500&prepStmtCacheSqlLimit=2048</property> <property name="connection.isolation">2</property>

Another connection alternative with the database is the configuration of the datasource in the application server.
Run the file /setup/initializeportal.cmd for Windows®, or initializeportal.sh for Linux. This script executes a Java application that opens a connection to the database, using the information from the file lumisdata/config/lumishibernate.cfg.xml. This script also inserts the initial data necessary for the operation of LumisXP.

Notes

The MySQL Connector Java driver is not included in the LumisXP distribution, it can be found at the link below:

http://dev.mysql.com/downloads/connector/j/

There is a limitation when using MySQL that the date cannot be earlier than 01/01/1753. When this happens, an error message is returned indicating that the date is invalid.
The max_allowed_packet setting of MySQL that limits the maximum size of the packet received by the server must be configured with a value equal to or greater than 128M, very low values may cause issues in cluster scenarios. To work around this limitation, it is recommended to configure the server variable max_allowed_packet, as in the example below:
[mysqld] max_allowed_packet=128M

Where 128M is the maximum packet size. The server's default is 1M. The value should be adjusted according to the application's needs.
The configuration SQL Mode must contain STRICT_TRANS_TABLES. It is already part of the default value of this configuration starting from version 5.7.5 of MySQL.

Depending on the version of the JDBC driver and the operating system configurations, in some cases the driver may not be able to recognize the timezone of the system and may give an error like the message below when trying to initialize the connections with the database:

The server time zone value 'XXXX' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specific time zone value if you want to utilize time zone support.

In this case, it may be necessary to add to the value of connection.url the property serverTimezone to specify the timezone to be used by the driver. For more information about the properties of the MySQL JDBC connector, please refer to its manual.