Auto Deploy

Auto Deploy is a property in the portal.properties file, which is the default configuration file for Sun GlassFish Web Space Server. You can override this property using portal-ext.properties file.

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.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.LayoutTemplateExplodedTomcatListener,\
com.liferay.portal.deploy.auto.exploded.tomcat.PortletExplodedTomcatListener,\
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 deploy.

auto.deploy.deploy.dir=${resource.repositories.root}/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.server.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.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 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 tries to process a portlet at the same time that Web Space Server 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 Web Space Server to pick it up.

auto.deploy.custom.portlet.xml=false

Set this to 1 if you are using JBoss' PrefixDeploymentSorter. This appends a 1 in front of your WAR name. For example, if you are deploying a portlet called testportlet.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 are 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.quercus.jar=http://lportal.svn.sourceforge.net/viewvc/*
checkout*/lportal/portal/trunk/lib/development/quercus.jar
library.download.url.resin-util.jar=http://lportal.
svn.sourceforge.net/viewvc/*checkout*/lportal/portal/trunk/lib/development/
resin-util.jar
library.download.url.script-10.jar=http://lportal.svn.sourceforge.net/viewvc
/*checkout*/lportal/portal/trunk/lib/development/script-10.jar