Configuration

Clustering and High Availability

Clustering

  1. Liferay seeks to ensure that multiple instances of the product can communicate with each other and reference a single database without error. Subscription Services will provide guidance on configuring clustered instances using the technologies included with the product.
  2. Ensuring that a cluster's non-Liferay elements are configured properly would be the responsibility of the customer.  This would include environment-specific setup involving load balancers, application servers, databases and network configurations.

Distributed Cache

  1. Liferay seeks to ensure that the product will operate without error when utilizing a distributed cache, and Subscription Services will provide guidance on the rudimentary operational configuration using the default technologies for each product.
    1. Liferay DXP and Liferay Commerce's default technology is Cluster Link. 
    2. Liferay Portal EE's default technology is Cluster Link together with Ehcache Cluster EE plugin available on Liferay Marketplace. 
  1. Tuning and optimizing the distributed cache for a particular environment is the responsibility of the customer. 

Distributed Index

  1. 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. Subscription Services will provide guidance on configuring a distributed index for these products (e.g. Liferay Portal EE).
  2. Liferay does not test the compatibility of clustered third-party indexing solutions. As long as coherence is maintained by the external application and the product is able to interact with the application as a single unit, then the product should operate without loss of functionality. If any issues pertaining to a clustered indexing solution are reported, Subscription Services will only test and verify those issues in a single node environment.

Shared File Store

  1. 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 Subscription Services will provide guidance on that configuration. 
  2. In order for File System or Advanced File System to operate correctly files system must support concurrent requests and file locking.
  3. The installation and configuration of a shared file system location is the responsibility of the customer. For more information regarding file system locations please see the Interoperable Technologies policy.

Compatible Versions

Please see the Integrated Technology Compatibility Matrix

On this page