MySql Database Configuration for ThinMan External Database:
Read how to configure MySql Database as ThinMan External Database for more information
Below it is explained the necessary setup needed when you choose a ThinMan operation mode requiring an external database.
¶ Setting ThinMan Primary and Secondary Database parameters
The database parameters must be configured whenever you chose to install ThinMan with an external database. These parameters are configured on the "ThinMan Server Configuration" GUI.
The setup will depend on the chosen operation mode.
¶ Setting ThinMan Primary Server Database parameters
On Primary Server there are two distinct menu paths to start the ThinManServer Configuration GUI:
- From inside the ThinMan Console, menu "Tools" → "ThinMan Server" → "ThinMan Server Settings".
- From Windows menu, "Start" → "Praim - ThinMan" → "ThinMan Server Settings".
The ThinMan Server Configuration window opens.
Select DataBase tab from the ThinMan Server Configuration GUI.
Select from the Database Models list the entry MySQL Database and insert values for:
- Host: is the hostname or IP Address where MySQL Instance is installed (in case the host is the same where the ThinMan resides, use "localhost");
- Schema/Name: name of the MySQL database schema dedicate to ThinMan;
- Username: Database user name granted access to schema containing ThinMan data;
- Password: ThinMan schema user's password;
Replace the values between <> with the ones you prefer.
At the end of configuration click "OK" and accept the service restarting request.
If there are problems connecting to the database read MySQL Database Connection Problem from external host.
¶ Setting ThinMan Secondary Server Database parameters
Because the ThinMan Secondary Server does not have a Console, the only menu path available to start the ThinManServer Configuration GUI is:
- From Windows menu, "Start" → "Praim - ThinMan" → "ThinMan Server Settings".
¶ ThinMan HALF redundant configuration (ThinMan Primary and Secondary Server with Single Database)
Select "DataBase" Tab from the ThinMan Server Configuration GUI.
In case of HALF redundant configuration, you have to configure the ThinMan Secondary Server Database external parameters pointing to the same MySQL instanced pointed from the ThinMan Primary Server.
Select from the "Database Models" list the entry "MySQL Database" and insert values for:
- Host: is the hostname or IP Address where the unique MySQL Database Instance is installed ,the same reconfigured on the PrimaryThinMan Server;
- Schema/Name: name of the MySQL database schema dedicate to ThinMan;
- Username: Database user name granted access to schema containing ThinMan data;
- Password: ThinMan schema user's password;
Replace the values between <> with ones you prefer.
At the end of configuration click "OK" and accept the service restarting request.
REPLICATION MODE ENABLE CHECKBOX
The "Replication Mode Enable" checkbox is present only in Secondary Server configuration GUI, not in Primary Server one.For the HALF redundant configuration the "Replication Mode Enable" checkbox must be unchecked. For more details on different ThinMan Operation mode see ThinMan Operation Modes.
If there are problems connecting to the database read MySQL Database Connection Problem from external host.
¶ ThinMan FULL redundant configuration (ThinMan Primary and Secondary Server with Double Database)
If you are setting parameters in the Secondary Server and in case you are using MySQL Replication in a Dual Database Mode you have to enable the "Replication Mode Enable" option.
Select "DataBase" Tab from the ThinMan Server Configuration GUI.
In case of FULL redundant configuration, you have to configure the Secondary ThinMan Server Database external parameters pointing to the its own Slave MySQL Database
Select from the "Database Models" list the entry "MySQL Database" and insert values for:
- Host: is the hostname or IP Address where the Slave MySQL Database Instance is installed, mandatory different from the one configured on the PrimaryThinMan Server;
- Schema/Name: name of the Slave MySQL database schema dedicate to ThinMan;
- Username: Database user name granted access to schema containing ThinMan data;
- Password: ThinMan schema user's password;
Replace the values between <> with ones you prefer.
At the end of configuration click "OK" and accept the service restarting request.
NOTE ONLY FOR THINMAN FULL REDUNDANT CONFIGURATION
The "Replication Mode Enable" checkbox is present only in Secondary Server configuration GUI, not in Primary Server one. The "Replication Mode Enable" checkbox must be checked in ThinMan FULL redundant configuration (Primary and Secondary Server with Dual Database under MySQL Replication). For more details on different ThinMan Operation mode see ThinMan Operation Modes
¶ Setting Primary and Secondary Database parameters manually (only for expert users)
In case of problems with the GUI configuration you can modify manually all the parameters above.
This operation needs to modify some configuration files of the ThinMan environment, it is only intended for expert users.
¶ Primary Server
Modify with a text editor (e.g. Notepad) the file "<ThinMan_installation_directory>/Server/webapps/condor/WEB-INF/dataSource.properties" changing parameters value in this way:
jdbc.url=jdbc:mysql://<ip_hostname_masterDB_server>/<schema_name>
jdbc.username=<masterDB_username>
jdbc.password=<password>
jdbc.embedded=false
jdbc.driver=com.mysql.jdbc.Driver
hibernate.dialect=org.hibernate.dialect.MySQLDialect
¶ Secondary Server
Modify with a text editor (e.g. Notepad) the file "<ThinMan_installation_directory>/Server/webapps/condor/WEB-INF/dataSource.properties" changing parameters value in this way::
jdbc.url=jdbc:mysql://<ip_hostname_slaveDB_server>/<schema_name>
jdbc.username=<slaveDB_username>
jdbc.password=<password>
jdbc.embedded=false
jdbc.driver=com.mysql.jdbc.Driver
hibernate.dialect=org.hibernate.dialect.MySQLDialect
In case you are using MySQL Replication in a Dual Database Mode you have to modify the file "<ThinMan_installation_directory>/Server/conf/condor.properties" changing the following parameter:
condor.mode=secondary-slave
Note
This last parameter has to be modified only if we are using Primary and Secondary Server with Dual Database in MySQL Replication, not in other modes. For a detailed description see ThinMan Operation Modes.