Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- Portal Administrators may require a connection to the database through a Java Naming and Directory Interface (following: JNDI) instead of the JDBC properties through the traditional portal-ext.properties file. How can this be configured in a dockerized environment like Liferay PaaS?
Environment
- Liferay PaaS
Resolution
- While Liferay PaaS does not have a standard out-of-the-box way to achieve JNDI connection, the best approach to resolve this technical requirement is through scripts (see also: V4 specific changes here).
- In order to edit or override the necessary Tomcat files, you may craft a script that performs the changes.
- Please note, this is considered to be a customization topic for which Liferay Support may only provide limited assistance.
Additional Information
- Apache Tomcat docs: JNDI Datasource HOW-TO
- Liferay Community Blogs: Liferay DB configuration using JNDI