Liferay Symposium 2015 | Reserve your seat today.

« Torna a Documentation Errata

Errata for the Liferay Portal Administrator's Guide, 3rd Edition

(Redirezionato da 3rd Edition)

Page 28: Glassfish 2.x #

  • In the "Deploy Liferay" section, in steps 1-4, there is no selection for "Application Server" in the tree hierarchy o the left. in Glassfish 2.1.

Page 36: JBoss 4.2.x #

  • The material to be replaced in Step 4 should be found in lines 127-140 in $JBOSS_HOME/server/default/deploy/jboss-web.deployer/conf/web.xml.
  • Deploy Liferay
    • The third bullet point should contain the filepath $JBOSS_HOME/server/default/deploy/liferay-portal.war/WEB-INF/lib.
    • Disregard the fourth bullet point, instead remove files jaxrpc.jar, stax.jar, xercesImpl.jar, and xml-apis.jar
    • The fifth bullet point should read "Move commons-collections.jar to $JBOSS_HOME/server/default/lib" and account for an overwrite when performing this action.

Page 41: JBoss 5.x #

  • Disregard Step 3 in the "Deploy Liferay" instructions

Page 50, Tomcat 5.5 #

The instructions for Tomcat 5.5 are missing a few steps. Use these instructions in addition to the Admin Guide:

[Installing Liferay 5.2.2 on Existing Tomcat 5.5]

Page 52, WebLogic #

WebLogic uses an XML parser library that is different than the one Liferay ships with. Unfortunately some of the libraries Liferay relies on require the Xerces parser, and will not work with another parser. So while we seek to work around this problem, the solution outlined in the book tells WebLogic users to copy Xerces to a location on the global class path. This causes Xerces to become the default SAX parser for the WebLogic server, and allows Liferay to operate normally.

Some organizations understandably object to this, as this solution changes the SAX parser server wide, for all domains. While Liferay works through this issue, there is another workaround which will get Liferay working, but affects how Liferay and plugins are deployed to WebLogic.

Note: The method described in the installation guide is still the one recommended for most cases. Use that method unless it's really necessary to use the alternative described here.

1. Create an EAR file which contains the Liferay .war file and any plugins you wish to install.

2. Inside this EAR file, create an APP-INF/lib folder and put the following .jars from Liferay's Dependencies and from Liferay's .war file into this folder:

  • annotations.jar
  • portal-kernel.jar
  • portal-service.jar
  • portlet.jar
  • serializer.jar
  • stax.jar
  • wstx.jar
  • xalan.jar
  • xercesImpl.jar
  • xml-apis.jar
  • Your database's JDBC driver

3. In the META-INF folder of the EAR file, create an application.xml file which defines the web modules that will be a part of this EAR. In our example, we have added two plugins: sample-service-builder-portlet.war and sample-jsp-portlet.war.

<?xml version='1.0' encoding='UTF-8'?>
<application xmlns="" xmlns:xsi="">


4. Deploy this EAR file to WebLogic. Liferay will run normally, but you will not be able to hot deploy plugins to it. If you wish to deploy another plugin, you will need to package it with Liferay and re-deploy Liferay and the plugin in the EAR file together. 

To install Liferay 5.2 in Weblogic 9.2 you have to modify the weblogic.xml file included in the .war file.

# Weblogic 9.2 and 10.3 use different and incompatible DTD. By default, it is used the Weblogic 10.3 compatible version. In order to use the DTD compatible with Weblogic 9.2 you need to the change the DOCTYPE to be
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"  "">
  1. It is needed to add the optimistic-serialization attribute to weblogic.xml, enclosed in <weblogic-web-app/> tag.

If you are building an .ear file, you also need to change the application.xml file defined for Weblogic 10.3, so the <application/> tag is set as

<application xmlns="" xmlns:xsi="" version="1.4">

Page 148, Properties #

After the first full paragraph on the page, add the following paragraph:

One more statement should be made about the file and Liferay's configuration files in general. Do not modify, web.xml, portlet.xml, or any configuration file while Liferay is running, as there may be unpredictable results. One of the reasons the Liferay Home folder was added as a configuration option for the 5.2 release is to provide a more convenient place to store Liferay's configuration that is outside of the application server. But the same rule still applies: you should not modify any of Liferay's configuration files while Liferay is running. Always shut Liferay down, modify the file, and then start it back up.

Page 184, Permissions Algorithm #

Set the algorithm used to check permissions for a user. This is useful so that you can optimize the search for different databases. See com.liferay.portal.service.impl.PermissionLocalServiceImpl.

Algorithms 1 through 4 are essentially the same but make calls in different orders depending on how the database is optimized and how the portal permissions are used. Algorithm 5 is is the recommended algorithm because it is the fastest and relies on only role assignments. Algorithm 6 is like Algorithm 5, except that it uses bitwise operations for even faster speed.

Algorithm 6 is currently experimental, but will be the new recommended algorithm in a future release.

Tomcat 6.X #

Installation to Tomcat 6.x is missing from the documentation.

The instructions for Tomcat 6.x are similar to the Tomcat 5.5.X instructions. A few minor changes:

Step 4:
Instead of:

Create a $TOMCAT_HOME/common/lib/ext directory... }}} Should be:
Create a $TOMCAT_HOME/lib/ext directory... }}}
Step 5:
Instead of:


Should be:


Step 8: Before you do Step 8, you need to create the /Catalina/localhost/ directory structure.ann

Page 99, Roles #

When it says "For other Roles, you only see the portlet permissions". If you create a Organization Role, you can see also some Portal Permissions.

0 Allegati
24424 Visualizzazioni
Media (0 Voti)
La media del punteggio è 0.0 stelle su 5.