Liferay Clustering

    Step 1: Webserver  configuration.
    Before configuring Liferay server for clustering some configuration need to be done at
    apache server level. These include installing and configuring ModJk which is a  connector
    for connecting tomcat container with webserver. Also configure the portal to use a sticky
    session and load balacer related configuration need to be done. You can refer this link 
    more info for detailed information about this configuration.
    Step 2:- Liferay  Configuration
    In  portal-ext.properties put the following properties
        cluster.link.enabled=true
        cluster.link.autodetect.address=<some-address>:<some-port>
        lucene.replicate.write=true
        ehcache.multi.vm.config.location=/mycache/liferay-multi-vm.xml
        net.sf.ehcache.configurationResourceName=/mycache/hibernate-clustered.xml
 
        multicast.group.address["hibernate"]=224.0.0.1
        multicast.group.port["hibernate"]=4446

        multicast.group.address["multi-vm"]=224.0.0.1
        multicast.group.port["multi-vm"]=4447
        


          The first will enable Liferay to replicate both database caches (ehcache) and search
          indexes (lucene) through a multicast communication.
          The second will tell Liferay what network interface to use for the multicast communication. 

          Install ehcache-plugin-portlet from plugins-installation and upload war file
          
          Put your multicast address in the portal-ext.properties file.

           Copy files hibernate-clustered-linked.xml and liferay-multi-vm-clustered.xml in    
          ROOT.war/WEB-INF/classes/mycache. 

         In ROOT.war/WEB-INF/web.xml add entry <distributable> before </webapp> tag.


         Configure jvmRoute="node1/node2" as defined in workers.properties in server.xml(in        
         deploy/jboss-web.sar for jboss)

      Document Library and Image gallery related configuration :
    put the following entries in the portal-ext.properties file to store the document library and
    image gallery related files in a common location accessible by both node instead of the 
    default location under Liferay server/data folder.
    dl.hook.file.system.root.dir=/mystoragepath/document_library
    image.hook.file.system.root.dir=/mystorageapth/images
    Now your liferay cluster is ready for use.



.

Comments

Post a Comment

Popular posts from this blog

React development in Liferay - Overview

Image
Liferay is one of the leading opensource digital experience platform based on Java. On the other hand React is  the most popular and widely used java script framework currently available in the market.  With the release of Lifeay DXP platform we can create pure javascript based portlet in Liferay. This feature enable us to run single page application created using (React/Angular/ Vue) in Liferay DXP platform which allow developer to take advantages of both Liferay and SPA platform. This article explain about the things we consider and challenges faced during React portlet development in Liferay. SPA vs Portal Architecture A Portal is designed to have number of pages and child pages under a site and provide option to add multiple application in a single page. SPA have a completely opposite approach compared to Portal, SPA application have only single page which accommodate all your functionality. When we design a Liferay Portal application with SPA this is the first challenge ...
Read more

Liferay React with Webpack

Image
  Liferay is using its own bundler called Liferay NPM bundler for the normal build process. This article explains the challenges we faced while developing react portlet with liferay-npm-bundler and how to overcome those using a webpack build.   Why Liferay using its own bundler (liferay-npm-bundler)  Multiple Portlets can be added in a page In a Portal page we can add multiple application/portlets, The normal bundler like webpack will fail in this case since its designed to have one application in a page. Liferay NPM bundler is designed to support the following features. Reuse common module across the page   When you have multiple portlets in a page and all this portlet using some common module, liferay npm bundler will allow to load only one common module in the page and share it among the portlets. Avoid common module conflict   Use different version of same module in a page :  It allow you to use 2 version of the same module in a page OSGI modular a...
Read more

Deploy Liferay DXP on google cloud

Image
  In this article we will see how to deploy a Liferay DXP cluster in google cloud platform. The reference architecture will look like below. Here I have created a global https load balancer which will distribute the traffic to 2 liferay node in the cluster. I have created an unmanaged instance group for this purpose. I have created 2 Compute engine virtual machine for deploying Liferay DXP. We have used cloud SQL service from gcloud for Liferay schema. Filestore service used for document repository and a separate virtual machine with elastic search installed used as an elastic server.                                                                                                    ...
Read more