• No results found

A UTO D EPLOY

In document Portal Administrator's Guide (Page 130-134)

C ONFIGURATION ONFIGURATION

A UTO D EPLOY

Input a list of comma delimited class names that implement com.liferay.portal.ker-

nel.deploy.auto.AutoDeployListener. These classes are used to process the auto deploy-

ment of WARs. auto.deploy.listeners=\ com.liferay.portal.deploy.auto.LayoutTemplateAutoDeployListener,\ com.liferay.portal.deploy.auto.PortletAutoDeployListener,\ com.liferay.portal.deploy.auto.ThemeAutoDeployListener,\ com.liferay.portal.deploy.auto.WebAutoDeployListener,\ com.liferay.portal.deploy.auto.exploded.tomcat.LayoutTemplateExplodedTom- catListener,\ com.liferay.portal.deploy.auto.exploded.tomcat.PortletExplodedTomcatLis- tener,\ com.liferay.portal.deploy.auto.exploded.tomcat.ThemeExplodedTomcatListener Set the following to true to enable auto deploy of layout templates, portlets, and themes.

auto.deploy.enabled=true

Set the directory to scan for layout templates, portlets, and themes to auto de- ploy.

auto.deploy.deploy.dir=${resource.repositories.root}/deploy

Set the directory where auto deployed WARs are copied to. The application serv- er or servlet container must know to listen on that directory.

Different containers have different hot deploy paths. For example, Tomcat lis- tens on ${catalina.base}/webapps whereas JBoss listens on ${jboss.server.home.dir}/deploy. Set a blank directory to automatically use the application server specific directory.

Examples:

auto.deploy.default.dest.dir=../webapps auto.deploy.geronimo.dest.dir=${org.apache.geronimo.base.dir}/deploy auto.deploy.geronimo-jetty.dest.dir=${org.apache.geronimo.base.dir}/deploy auto.deploy.geronimo-tomcat.dest.dir=${org.apache.geronimo.base.dir}/deploy auto.deploy.glassfish.dest.dir=${com.sun.aas.instanceRoot}/autodeploy auto.deploy.glassfish-tomcat.dest.dir=${com.sun.aas.instanceRoot}/autodeploy auto.deploy.jboss-jetty.dest.dir=${jboss.server.home.dir}/deploy auto.deploy.jboss-tomcat.dest.dir=${jboss.server.home.dir}/deploy auto.deploy.jetty.dest.dir=${jetty.home}/webapps auto.deploy.jonas-jetty.dest.dir=${jonas.base}/webapps/autoload auto.deploy.jonas-tomcat.dest.dir=${jonas.base}/webapps/autoload auto.deploy.tomcat.dest.dir=${catalina.base}/webapps auto.deploy.weblogic.dest.dir=${env.DOMAIN_HOME}/autodeploy

Set the interval in milliseconds on how often to scan the directory for changes. auto.deploy.interval=10000

Set the number of attempts to deploy a file before blacklisting it. auto.deploy.blacklist.threshold=10

Set the following to true if deployed WARs are unpacked. Set this to false if your application server has concurrency issues with deploying large WARs.

auto.deploy.unpack.war=true

Set the following to true if you want the deployer to rename portlet.xml to port- let-custom.xml. This is only needed when deploying the portal on WebSphere 6.1.x with a version before 6.1.0.7 because WebSphere's portlet container will try to pro- cess a portlet at the same time that Liferay is trying to process a portlet.

Note that according to IBM, on versions after 6.1.0.9, you need to add a context parameter to the web.xml descriptor in your portlet application called com.ibm.web-

sphere.portletcontainer.PortletDeploymentEnabled and set it to false. This parameter caus-

es WebSphere's built-in portlet container to ignore your portlet application when it is deployed, enabling Liferay to pick it up.

auto.deploy.custom.portlet.xml=false

Set this to 1 if you are using JBoss' PrefixDeploymentSorter. This will append a 1 in front of your WAR name. For example, if you are deploying a portlet called test- portlet.war, it will deploy it to 1test-portlet.war. JBoss now knows to load this portlet after the other WARs have loaded; however, it will remove the 1 from the context path.

Modify /server/default/conf/jboss-service.xml.

See org.jboss.deployment.scanner.PrefixDeploymentSorter. auto.deploy.jboss.prefix=1

Set the path to Tomcat's configuration directory. This property is used to auto deploy exploded WARs. Tomcat context XML files found in the auto deploy directory

auto.deploy.tomcat.conf.dir=../conf/Catalina/localhost

Set the path to Tomcat's global class loader. This property is only used by Tomcat in a standalone environment.

auto.deploy.tomcat.lib.dir=../common/lib/ext

Set the URLs of Libraries that might be needed to download during the auto de- ploy process library.download.url.quercus.jar=http://lportal.svn.sourceforge.net/viewvc/* checkout*/lportal/portal/trunk/lib/development/quercus.jar library.download.url.resin-util.jar=http://lpor- tal.svn.sourceforge.net/viewvc/*checkout*/lportal/portal/trunk/lib/develop- ment/resin-util.jar library.download.url.script-10.jar=http://lportal.svn.sourceforge.net/viewvc /*checkout*/lportal/portal/trunk/lib/development/script-10.jar

H

OT

D

EPLOY

Input a list of comma delimited class names that implement com.liferay.portal.ker-

nel.deploy.hot.HotDeployListener. These classes are used to process the deployment and

undeployment of WARs at runtime.

Note: PluginPackageHotDeployListener must always be first. hot.deploy.listeners=\ com.liferay.portal.deploy.hot.PluginPackageHotDeployListener,\ com.liferay.portal.deploy.hot.HookHotDeployListener,\ com.liferay.portal.deploy.hot.LayoutTemplateHotDeployListener,\ com.liferay.portal.deploy.hot.PortletHotDeployListener,\ com.liferay.portal.deploy.hot.ThemeHotDeployListener,\ com.liferay.portal.deploy.hot.ThemeLoaderHotDeployListener

H

OT

U

NDEPLOY

Set the following to true to enable undeploying plugins. hot.undeploy.enabled=true

Set the undeploy interval in milliseconds on how long to wait for the undeploy process to finish.

hot.undeploy.interval=0

Set the following to true to undeploy a plugin before deploying a new version. This property will only be used if the property hot.undeploy.enabled is set to true.

hot.undeploy.on.redeploy=false

P

LUGIN

Input a list of comma delimited supported plugin types. plugin.types=portlet,theme,layout-template,web

Input a list of Liferay plugin repositories separated by \n characters. plugin.repositories.trusted=http://plugins.liferay.com/official plugin.repositories.untrusted=http://plugins.liferay.com/community

Set this property to false to avoid receiving on screen notifications when there is a new version of an installed plugin.

plugin.notifications.enabled=true

Input a list of plugin packages ids separated by \n characters. Administrators won't be notified when a new version of these plugins are available. The ids are of the form groupId/artifactId. You can also end the id with an asterisk to match any id that start with the previous character.

plugin.notifications.packages.ignored=liferay/sample-jsp-portlet

P

ORTLET

Set this property for the portlet container implementation to use. The default implementation is the internal implementation and provides for the best backwards compatibility. The Sun implementation provides more features and will be the recom- mended implementation in the future.

portlet.container.impl=internal #portlet.container.impl=sun

Set this property to define the default virtual path for all hot deployed portlets. See liferay-portlet-app_4_3_0.dtd and the virtual-path element for more information.

portlet.virtual.path=

T

HEME

Set this property to true to load the theme's merged CSS files for faster loading for production.

Set this property to false for easier debugging for development. You can also dis- able fast loading by setting the URL parameter css_fast_load to 0.

theme.css.fast.load=true Set the theme's shorcut icon. theme.shortcut.icon=liferay.ico

Set this property to set the default virtual path for all hot deployed themes. See liferay-look-and-feel_4_3_0.dtd and the virtual-path element for more information.

theme.virtual.path=

Set this with an absolute path to specify where imported theme files from a LAR will be stored. This path will override the file-storage path specified in liferay-theme- loader.xml.

use a new theme id on every import. This will ensure that a copy of the old theme is preserved in the theme loader storage path. However, this also means that a lot of themes that are no longer used remain in the file system. It is recommended that you set this to false.

theme.loader.new.theme.id.on.import=false Set this to true to decorate portlets by default. theme.portlet.decorate.default=true

In document Portal Administrator's Guide (Page 130-134)