P. 1
Liferay Administration Guide

Liferay Administration Guide

|Views: 5|Likes:
Published by David Choi

More info:

Published by: David Choi on Dec 22, 2010
Copyright:Attribution Non-commercial


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





Installing plugins manually is almost as easy as installing plugins via the Plugin
Installer. There are several scenarios in which you would need to install plugins
manually rather than from Liferay's repositories:

Your server is firewalled without access to the Internet. This makes it im-
possible for your instance of Liferay to connect to the plugin repositories.

You are installing portlets which you have either purchased from a vendor,
downloaded separately, or developed yourself.

For security reasons, you do not want to allow portal administrators to in-
stall plugins from the Internet before they are evaluated.
You can still use the Control Panel to install plugins that are not available from
the on line repositories. This is by far the easiest way to install plugins.
If your server is firewalled, you will not see any plugins displayed in the Portlet
Plugins tab or in the Theme Plugins tab. Instead, you will need to click the Upload File
tab. This gives you a simple interface for uploading a .war file containing a plugin to
your Liferay Portal.

Click the Browse button and navigate your file system to find the portlet or theme
.war you have downloaded. The other field on the page is optional: you can specify
your own context for deployment. If you leave this field blank, the default context
defined in the plugin (or the .war file name itself) will be used.
That's all the information the Plugin Installer needs in order to deploy your port-
let, theme, layout template, hook, or web module. Click the Install button, and your
plugin will be uploaded to the server and deployed. If it is a portlet, you should see it
in the Add Content window. If it is a theme, it will be available on the Look and Feel tab
in the page definition.

If you do not wish to use the Update Manager or Plugin Installer to deploy plu-
gins, you can also deploy them at the operating system level. The first time Liferay
starts, it creates a hot deploy folder which is by default created inside the Liferay Home
folder. This folder generally resides one directory up from where your application
server is installed, though it sometimes is elsewhere depending on which application
server you are running. To find out where the Liferay Home folder is for your applica-
tion server, please see the section on your server in Chapter 1. The first time Liferay is
launched, it will create a folder structure in Liferay Home to house various configura-
tion and administrative data. One of the folders it creates is called deploy. If you copy a


Plugin Management

Advanced Liferay Configuration

portlet or theme plugin into this folder, Liferay will deploy it and make it available for
use just as though you'd installed it via the Plugin Installer in the Control Panel. In
fact, this is what the Plugin Installer is doing behind the scenes.
You can change the defaults for this directory structure so that it is stored any-
where you like by modifying the appropriate properties in your portal-ext.properties
file. Please see the above section on the portal-ext..properties file for more information.
To have Liferay hot deploy a portlet or theme plugin, copy the plugin into your
hot deploy folder, which by default is in [Liferay Home]/deploy. If you are watching the
Liferay console, you should see messages like the following:

16:16:19,450 INFO [AutoDeployDir:183] Processing web-form-portlet-
16:16:19,452 INFO [PortletAutoDeployListener:77] Copying portlets for /opt/
Expanding: /opt/liferay/liferay-portal-5.2.2/deploy/web-form-portlet- into /opt/liferay/liferay-portal-5.2.2/tomcat-
Copying 1 file to /opt/liferay/liferay-portal-5.2.2/tomcat-
Copying 1 file to /opt/liferay/liferay-portal-5.2.2/tomcat-
Copying 1 file to /opt/liferay/liferay-portal-5.2.2/tomcat-
Copying 1 file to /opt/liferay/liferay-portal-5.2.2/tomcat-
Copying 38 files to /opt/liferay/liferay-portal-5.2.2/tomcat-
Copying 1 file to /opt/liferay/liferay-portal-5.2.2/tomcat-5.5.27/webapps/

Deleting directory /opt/liferay/liferay-portal-5.2.2/tomcat-
16:16:20,925 INFO [PortletAutoDeployListener:87] Portlets for /opt/liferay/
liferay-portal-5.2.2/deploy/web-form-portlet- copied success-
fully. Deployment will start in a few seconds.
16:16:27,993 INFO [PortletHotDeployListener:333] Unregistering portlets for
16:16:28,000 INFO [PortletHotDeployListener:362] 1 portlet for web-form-
portlet was unregistered
Apr 23, 2009 4:16:27 PM org.apache.catalina.startup.HostConfig checkRe-
INFO: Undeploying context [/web-form-portlet]
16:16:28,408 INFO [PortletHotDeployListener:219] Registering portlets for
Loading file:/opt/liferay/liferay-portal-5.2.2/tomcat-5.5.27/temp/6-web-
16:16:28,570 INFO [PortletHotDeployListener:298] 1 portlet for web-form-
portlet is available for use

As long as you see the available for use message, your plugin was installed cor-
rectly, and will be available for use in the portal.

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)//-->