Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Approaching database support

Written By

Kanchan Bisht

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Approaching database support issues in the Liferay.

Environment

  • Liferay DXP 7.0

Resolution

  • There are two ways to set up database connections in the portal-ext.properties file.
    • If both JDBC properties and JNDI name are set then JNDI takes preference. If neither is set, then the default HSQL database will be used.
      1) JDBC properties: The portal.properties file contains configuration for all the supported databases. Customize those values in the portal-ext.properties file. In this case, the connection pool will be managed by Liferay. 
      jdbc.default.driverClassName=
      jdbc.default.url=
      jdbc.default.username=
      jdbc.default.password=
      2) JNDI name: The data source is configured externally and only its JNDI name is set in the portal-ext.properties file. The connection pool in this case is not managed by Liferay.
      jdbc.default.jndi.name=

Additional Information

  • By default, Liferay is configured to use a Hypersonic database. However, several vendors are supported. For testing purposes, the best option is MySQL in most cases.
  • Always make sure that the vendor-specific JDBC driver is available on the '{Liferay_home}/{Application_Server_home}/lib' path of the application server before starting the portal.
  • For connection pool related settings please check the portal.properties file.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?