Liferay Support will seek to resolve any reproducible and unintended issues caused by Liferay Digital Experience Platform, Liferay Portal EE or Liferay Commerce ("the product") while configuring the product in a compatible environment within its product service life. For more information please see the Product Defects policy.
Several areas of configuration for the product have specific support policies listed below. Some properties or settings of the product may impact its performance and will be handled by the Performance Issues Policy.
- Liferay seeks to ensure that multiple instances of the product can communicate with each other and reference a single database without error. Liferay Support will provide guidance on configuring clustered instances using the technologies included with the product.
- However, as a cluster is an environment-specific setup involving load balancers, application servers, databases and network configurations, ensuring that a cluster's non-Liferay elements are configured properly would be the responsibility of the customer.
- Liferay seeks to ensure that the product will operate without error when utilizing a distributed cache, and Support will provide guidance on the rudimentary operational configuration using the default technologies for each product.
- Liferay DXP and Liferay Commerce's default technology is Cluster Link.
- Liferay Portal EE's default technology is Cluster Link together with Ehcache Cluster EE plugin available on Liferay Marketplace.
- Tuning and optimizing the distributed cache for a particular environment is the responsibility of the customer.
- Liferay seeks to ensure that the index is properly synced between cluster nodes through Cluster Link for versions of the product which are designed for internal index replication. Liferay Support will provide guidance on configuring a distributed index for these products (e.g. Liferay Portal EE).
- Installing and configuring third-party indexing solutions which do not replicate their index through Cluster Link (e.g., SOLR, Elasticsearch) is the responsibility of the customer unless the customer has purchased an Enterprise Search subscription.
- Liferay does not test the compatibility of clustered third-party indexing solutions. As long as coherence is maintained by the external application and Liferay is able to interact with the application as a single unit, the product should operate without loss of functionality. If any issues pertaining to a clustered indexing solution are reported, Support will only test and verify those issues in a single node environment.
Shared File Store
- Liferay seeks to ensure that all the file stores listed in the portal.properties file can be configured to access a shared file store location, and Liferay Support will provide guidance on that configuration.
- File systems used by the File System or Advanced File System stores must support concurrent requests and file locking.
- The installation and configuration of a shared file store location is the responsibility of the customer. For more information regarding file store locations please see the Interoperable Technologies policy.
Please see the Integrated Technology Compatibility Matrix.
Liferay seeks to ensure that users can authenticate using the default sign in portlet and that the authentication framework can be integrated with common authentication solutions. Liferay has implemented third-party integration points in accordance with their respective policies and protocols. Reproducible and unintended issues that arise with the sign in portlet or authentication framework will be resolved according to the Product Defects policy unless otherwise noted in the LDAP, SAML or SSO policies.
If you have purchased the Enterprise Search offering please see the Enterprise Search policy.
- Liferay seeks to ensure that indexable assets found within the product are correctly indexed by the product, that the search framework functions correctly, and that the search portlet is able to access and retrieve results from the index.
- Liferay will resolve any issues found within the search framework and search portlets.
- Liferay will resolve any issue found in a third-party search platform if the issue is a result of an out-of-the-box integration and it prohibits a feature intended to be released with the product.
- Liferay Support will provide guidance on the configuration and deployment of the search portlet, search facets and utilizing search syntax.
- Liferay Support will provide guidance on the configuration of the product in regards to enabling the product to integrate with a compatible remote search platform.
- Any issues discovered in the third-party library impacting features not intended to be released with the product are the responsibility of the third-party vendor to resolve and at the discretion of the customer.
- The installation, configuration and selection of a remote search platform is the responsibility of the customer, including integrated search platforms operating in a remote mode.
The product is tested as compatible with particular versions of certain search platforms. The compatible versions are in the Integrated Technologies Compatibility Matrix.
Elasticsearch is tested by Elastic as compatible with specific platform and software configurations eligible for support under Elastic's subscription offerings. The compatible versions are listed on the Elastic Support Matrix.
Elasticsearch is not compatible with IBM JDK. If IBM JDK is required for use with Liferay DXP or Liferay Commerce, then Elasticsearch must be used in Remote mode with a compatible JDK.
Liferay DXP 7.1 is not compatible with Amazon's Elasticsearch Service. Liferay DXP 7.1 has implemented Elasticsearch TCP Transport and Amazon's service does not support TCP Transport, only HTTP Transport.
There are several options available for configuring Document Library integration points. The product is tested as compatible with several specific third-party solutions, but there are also several protocols or standards with which the product has been designed to be compliant. The Document Library integration points are document conversion, document repositories, document thumbnails and previews, and WebDAV.