By default Semarchy x runtime is using an internal HSQL database as the log database.
This makes it extremely easy to launch the runtime out-of-the box because you do not need to install additional software on your machine.
However for specific reasons, you can choose to use another database.
Below article provides best practices for selecting and maintaining a log database in Semarchy xDI. You will find some ideas that should make it easier for you to choose the right log database for your runtime.
Need
Customers often seek guidance on how to choose and manage a log database for their Semarchy xDI runtime environment.
Summarized Solution
Select a robust database with JDBC support, ensure proper maintenance, and use appropriate runtime parameters for optimal performance.
Detailed Solution
- Choose a database that has an official JDBC driver
As a Java application, Semarchy xDI connects to databases via JDBC drivers. Ensure the chosen database has a compatible JDBC driver installed in the runtime directory.
- Choose a robust database
The log database stores details of all sessions executed by the runtime. In production environments, this can be a significant amount of data. Consider using major recognized database technologies such as Microsoft SQL Server, MySQL, Postgres, or Oracle.
- Choose a database for which your company has a good technical know-how
If your organization primarily uses MSSQL databases and has a dedicated team of DBAs, it may be best to use MSSQL for your log database. Proper maintenance and supervision are crucial to prevent issues in production environments.
- Monitor your database and keep it well maintained
Regular maintenance is essential for any database. Schedule purges to limit the number of sessions retained in the log database, such as keeping only the last month's sessions.
- Use runtime parameters adapted to the chosen RDBMS technology
Once you have selected a database technology, ensure you configure the appropriate parameters in your runtime's configuration file. Some databases, like Microsoft SQL Server, may require specific parameters to avoid issues such as deadlocks.
- One environment, one log database
It is recommended that each environment has its own log database. Avoid using the same log schema across multiple environments to simplify operations related to purging and updating runtimes.
Notes
- Always validate your database choices and configurations against the specific version of Semarchy xDI you are using.
- Consider the scalability and performance requirements of your applications when selecting a log database.