P. 1
Liferay Administration Guide

Liferay Administration Guide

|Views: 574|Likes:
Publicado pornicolargo
THE administration guide provided by Liferay
THE administration guide provided by Liferay

More info:

Published by: nicolargo on Oct 09, 2009
Direitos Autorais:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less






Lucene, the search indexer which Liferay uses, can be in a shared configuration
for a clustered environment, or an index can be created on each node of the cluster. If
you wish to have a shared index, you will need to either share the index on the file
system or in the database.
The Lucene configuration can be changed by modifying values in your portal-ext.-
properties file. Open your portal.properties file and search for the text Lucene. Copy that
section and then paste it into your portal-ext.properties file.
If you wish to store the Lucene search index on a file system that is shared by all
of the Liferay nodes, you can modify the location of the search index by changing the
lucene.dir property. By default, this property points to the lucene folder inside the
home folder of the user that is running Liferay:


Change this to the folder of your choice. To make the change take effect, you will
need to restart Liferay. You can point all of the nodes to this folder, and they will use
the same index.

Like Jackrabbit, however, this is not the best way to share the search index, as it
could result in file corruption if different nodes try reindexing at the same time. We
do not recommend this for a production system. A better way is to share the index is
via a database, where the database can enforce data integrity on the index. This is
very easy to do; it is a simple change to your portal-ext.properties file.
There is a single property called lucene.store.type. By default this is set to go to the
file system. You can change this so that the index is stored in the database by making
it the following:


The next time Liferay is started, new tables will be created in the Liferay data-
base, and the index will be stored there. If all the Liferay nodes point to the same
database tables, they will be able to share the index. Performance on this is not al-
ways as good as it could be. Your DBAs may be able to tweak the database indexes a
bit to improve performance. For better performance, you should consider using a sep-
arate search server (see the section on Solr above).
Note: MySQL users need to modify their JDBC connection string for this to work.
Add the following parameter to your connection string:

Liferay Clustering


Enterprise Configuration


Alternatively, you can leave the configuration alone, and each node will then
have its own index. This ensures that there are no collisions when multiple nodes up-
date the index, because they all will have separate indexes. This, however, creates du-
plicate indexes and may not be the best use of resources. Again, for a better configur-
ation, you should consider using a separate search server (see the section on Solr

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->