Auto Deploy

Input a list of comma delimited class names that implement com.liferay.portal.kernel.deploy.auto.AutoDeployListener. These classes are used to process the auto deployment of WARs.

auto.deploy.listeners=\
    com.liferay.portal.deploy.auto.OSGiAutoDeployListener,\
    com.liferay.portal.deploy.auto.ExtAutoDeployListener,\
    com.liferay.portal.deploy.auto.HookAutoDeployListener,\
    com.liferay.portal.deploy.auto.LayoutTemplateAutoDeployListener,\
    com.liferay.portal.deploy.auto.LiferayPackageAutoDeployListener,\
    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.HookExplodedTomcatListener,\
    com.liferay.portal.deploy.auto.exploded.tomcat.LayoutTemplateExplodedTomcatListener,\
    com.liferay.portal.deploy.auto.exploded.tomcat.PortletExplodedTomcatListener,\
    com.liferay.portal.license.deploy.auto.LicenseAutoDeployListener,\
    com.liferay.portal.deploy.auto.exploded.tomcat.ThemeExplodedTomcatListener

Set this 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 deploy.

auto.deploy.deploy.dir=${liferay.home}/deploy

Set the directory where auto deployed WARs are copied to. The application server or servlet container must know to listen on that directory. Different containers have different hot deploy paths. For example, Tomcat listens on ${catalina.base}/webapps whereas JBoss listens on ${jboss.home.dir}/deploy. Set a blank directory to automatically use the application server specific directory.

Examples:

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

Set the interval in milliseconds for how often to scan the directory for changes.

auto.deploy.interval=3000

Set the number of attempts to deploy a file before blacklisting it.

auto.deploy.blacklist.threshold=10

Set this 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 this to true if plugins should automatically copy Commons Logging.

auto.deploy.copy.commons.logging=true

Set this to true if plugins should automatically copy Log4j.

auto.deploy.copy.log4j=true

Set this to true if you want the deployer to rename portlet.xml to portlet-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 process 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.websphere.portletcontainer.PortletDeploymentEnabled and set it to false. This parameter causes 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=

Set the Glassfish settings to enable JSR 88 application deployment.

auto.deploy.glassfish.jee.deployment.enabled=false
auto.deploy.glassfish.jee.dm.id=deployer:Sun:AppServer::localhost:4848
auto.deploy.glassfish.jee.dm.user=admin
auto.deploy.glassfish.jee.dm.passwd=adminadmin
auto.deploy.glassfish.jee.df.classname=com.sun.enterprise.deployapi.SunDeploymentFactory

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 will be copied to Tomcat’s configuration directory. The context XML file must have a docBase attribute that points to a valid WAR 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 deploy process.

library.download.url.resin.jar=http://cdn.files.liferay.com/public/quercus/4.0.11/resin.jar
library.download.url.script-10.jar=http://cdn.files.liferay.com/public/quercus/3.1.9/script-10.jar