Portal Properties

Table of Contents

• Properties Override
• Liferay Home
• Portal Context
• Schema
• Upgrade
• Verify
• Auto Deploy
• Hot Deploy
• Hot Undeploy
• Plugin
• Portlet
• Portlet Config
• Portlet Container
• Portlet Coordination
• # Portlet Dependencies
• Portlet Display Templates
• Portlet Filters
• Portlet Preferences
• Theme
• Resource Actions
• Model Hints
• Model Tree Path
• Spring
• Hibernate
• JDBC
• Custom SQL
• Database
• Transaction
• Transactional Cache
• Ehcache
• JavaScript
• SQL Data
• Weblogic
• Company
• Users
• Groups and Roles
• Organizations
• User Groups
• Membership Policies
• Languages and Time Zones
• Look and Feel
• Request
• Session
• JAAS
• JNDI
• LDAP
• Basic Authentication
• NTLM
• OpenID
• Request Header
• Authenticated User UUID Store
• Authentication Pipeline
• Authentication Verifier
• Authentication Token
• Auto Login
• SSO with MAC (Message Authentication Code)
• Passwords
• Permissions
• Startup Events
• Shutdown Events
• Portal Events
• Default Landing Page
• Default Logout Page
• Default Guest Public Layouts
• Default User Private Layouts
• Default User Public Layouts
• Default Admin
• Layouts
• Layout Prototypes
• Layout Set Prototypes
• Portlet URL
• Preferences
• Redirect
• Images
• Editors
• Fields
• Mime Types
• Browser Cache
• Browser Compatibility
• Browser Launcher
• Control Panel
• Lucene Search
• Multi Value Map
• Setup Wizard
• SourceForge
• Value Object
• Table Mapper
• Audit Message
• Buffered Increment
• Cache
• Cluster Link
• Clusterable Advice
• Combo
• Content Delivery Network
• Counter
• Direct Servlet Context
• DNS
• ETag
• GZip
• HTTP
• HTTP Header Response
• HTTP Tunneling
• ImageMagick
• Intraband
• Invoker
• Javadoc Manager
• JSON
• JSON Web Service
• Live Users
• Lock
• Mail
• Minifier
• Mobile Device Rules
• Module Framework
• Module Framework Web Application Bundles
• Multicast
• Notifications
• OpenOffice
• Phone Number Format
• Poller
• POP
• Portal Fabric
• Portal Resiliency
• Quartz
• REST Proxy
• Retry Advice
• Retry Data Source
• Retry JDBC connection on portal startup.
• Robots.txt
• RSS
• RTL
• Sanitizer
• Scheduler
• Scripting
• Search Container
• Sharepoint
• Sprite
• Staging
• Strip
• Social Activity
• Text Extraction
• Thread Dump
• User Notifications
• Virtual Hosts
• Work Directory
• XML
• Xuggler
• YUI
• JSP
• Servlet Context Class Loader Pool
• Servlet Filters
• Upload Servlet Request
• Web Server
• WebDAV
• Main Servlet
• Atom Servlet
• Axis Servlet
• Dynamic Resource Servlet
• Google Gadget Servlet
• JSON Servlet
• JSON Web Service Servlet
• Netvibes Servlet
• Tunnel Servlet
• Web Server Servlet
• WebDAV Servlet
• Widget Servlet
• Admin Portlet
• Announcements Portlet
• Asset
• Blogs Portlet
• Blogs Service
• Calendar
• Discussion Tag Library
• Document Library Portlet
• Document Library Service
• IFrame Portlet
• Login Portlet
• Menu Tag Libraries
• Message Boards Portlet
• Message Boards Service
• My Places Portlet
• Portlet CSS Portlet
• Ratings Tag Library
• Recent Content Portlet
• My Sites Directory
• Sites Admin Portlet
• Trash
• Workflow
• ZIP

Properties

Properties Override

Specify where to get the overridden properties. Updates should not be made on portal.properties or on portal-bundle.properties, but in portal-ext.properties.

The default read order is: portal.properties, portal-bundle.properties, portal-ext.properties, and then portal-setup-wizard.properties.

Env: LIFERAY_INCLUDE_MINUS_AND_MINUS_OVERRIDE

    include-and-override=portal-bundle.properties
    include-and-override=${liferay.home}/portal-bundle.properties
    include-and-override=portal-ext.properties
    include-and-override=${liferay.home}/portal-ext.properties
    include-and-override=portal-setup-wizard.properties
    include-and-override=${liferay.home}/portal-setup-wizard.properties

Additional property files can be used by setting the "external-properties" system property.

A common use case is to keep legacy property values when upgrading to newer versions of Liferay. To enable:

     java ... -Dexternal-properties=portal-legacy-5.1.properties

The read order will now be: portal.properties, then portal-ext.properties, and then portal-legacy-5.1.properties.

Env: LIFERAY_INCLUDE_MINUS_AND_MINUS_OVERRIDE

    include-and-override=${external-properties}
    include-and-override=${liferay.home}/${external-properties}

Liferay Home

Specify the Liferay home directory.

Env: LIFERAY_LIFERAY_PERIOD_HOME

    liferay.home=${resource.repositories.root}

This property is available for backwards compatibility. Please set the property "liferay.home" instead.

Env: LIFERAY_RESOURCE_PERIOD_REPOSITORIES_PERIOD_ROOT

    resource.repositories.root=${default.liferay.home}

Portal Context

Set the application server's protocol. Lucene will use it to load the index from the cluster when the hostname and port are not detected on the first request. Note that this property refers to the application server's protocol, and not the web server's as specified in the property "web.server.protocol".

Env: LIFERAY_PORTAL_PERIOD_INSTANCE_PERIOD_PROTOCOL

    portal.instance.protocol=

    portal.instance.protocol=http
    portal.instance.protocol=https

Set the application server's hostname and port for the protocol specified in the property "portal.instance.protocol". Lucene will use it to load the index from the cluster when the hostname and port are not detected on the first request. Note that this property must be used with the property "portal.instance.protocol" and it refers to the application server's hostname and port, not the web server's port as specified in the properties "web.server.http.port" and "web.server.https.port".

Env: LIFERAY_PORTAL_PERIOD_INSTANCE_PERIOD_INET_PERIOD_SOCKET_PERIOD_ADDRESS

    portal.instance.inet.socket.address=

    portal.instance.inet.socket.address=localhost:8080
    portal.instance.inet.socket.address=localhost:8443

Set this property if the application server is served behind a proxy and a prefix needs to be added to the portal servlet context path. This prefix will also be added to static resources served by layout templates, portlets, and themes.

Env: LIFERAY_PORTAL_PERIOD_PROXY_PERIOD_PATH

    portal.proxy.path=

Schema

Set this to true to automatically create tables and populate with default data if the database is empty.

Env: LIFERAY_SCHEMA_PERIOD_RUN_PERIOD_ENABLED

    schema.run.enabled=true

Set this to true to automatically upgrade the database when a module's build number has been increased since the last deployment.

Env: LIFERAY_SCHEMA_PERIOD_MODULE_PERIOD_BUILD_PERIOD_AUTO_PERIOD_UPGRADE

    schema.module.build.auto.upgrade=false

Upgrade

Set this to true to execute the upgrade process when the portal starts and modules are activated.

Env: LIFERAY_UPGRADE_PERIOD_DATABASE_PERIOD_AUTO_PERIOD_RUN

    upgrade.database.auto.run=false

Set this to true to disable database transaction management during upgrades. This forces autocommit, which will speed up the upgrade process.

Env: LIFERAY_UPGRADE_PERIOD_DATABASE_PERIOD_TRANSACTIONS_PERIOD_DISABLED

    upgrade.database.transactions.disabled=true

Verify

Input a list of comma delimited class names that implement com.liferay.portal.verify.VerifyProcess. These classes will run on startup to verify and fix any integrity problems found in the database. Please be aware that this may make modifications directly to the database.

Env: LIFERAY_VERIFY_PERIOD_PROCESSES

    verify.processes=com.liferay.portal.verify.VerifyProcessSuite

Specify the frequency for verifying the integrity of the database.

Constants in VerifyProcess:

     public static final int ALWAYS = -1;
     public static final int NEVER = 0;
     public static final int ONCE = 1;

Env: LIFERAY_VERIFY_PERIOD_FREQUENCY

    verify.frequency=1

Set this to true to disable database transaction management during verification. This forces autocommit, which will speed up the verify process.

Env: LIFERAY_VERIFY_PERIOD_DATABASE_PERIOD_TRANSACTIONS_PERIOD_DISABLED

    verify.database.transactions.disabled=true

Set this to true to disable patch level checking on portal-impl and portal-kernel JAR files. This is not recommended as a mixed patch level can cause unexpected behavior.

Env: LIFERAY_VERIFY_PERIOD_PATCH_PERIOD_LEVELS_PERIOD_DISABLED

    verify.patch.levels.disabled=false

Configure this threshold to indicate when to execute certain com.liferay.portal.verify.VerifyProcess tasks concurrently. Each VerifyProcess implementation governs what it may concurrently execute.

Env: LIFERAY_VERIFY_PERIOD_PROCESS_PERIOD_CONCURRENCY_PERIOD_THRESHOLD

    verify.process.concurrency.threshold=5

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.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_LISTENERS

    auto.deploy.listeners=\
        com.liferay.portal.deploy.auto.HookAutoDeployListener,\
        com.liferay.portal.deploy.auto.LayoutTemplateAutoDeployListener,\
        com.liferay.portal.deploy.auto.ModuleAutoDeployListener,\
        com.liferay.portal.deploy.auto.PortletAutoDeployListener,\
        com.liferay.portal.deploy.auto.ThemeAutoDeployListener,\
        com.liferay.portal.deploy.auto.WebAutoDeployListener

Set this to true to enable auto deploy of layout templates, portlets, and themes.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_ENABLED

    auto.deploy.enabled=true

Set the directory to scan for layout templates, portlets, and themes to auto deploy.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_DEPLOY_PERIOD_DIR

    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.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_DEFAULT_PERIOD_DEST_PERIOD_DIR Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_DEST_PERIOD_DIR Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_JBOSS_PERIOD_DEST_PERIOD_DIR Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_JBOSS_PERIOD_DEST_PERIOD_DIR_OPENBRACKET__NUMBER5__CLOSEBRACKET_ Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_TOMCAT_PERIOD_DEST_PERIOD_DIR Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBLOGIC_PERIOD_DEST_PERIOD_DIR Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBSPHERE_PERIOD_DEST_PERIOD_DIR Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WILDFLY_PERIOD_DEST_PERIOD_DIR

    auto.deploy.dest.dir=
    auto.deploy.default.dest.dir=../webapps
    auto.deploy.jboss.dest.dir=${jboss.home.dir}/standalone/deployments
    auto.deploy.jboss.dest.dir[5]=${jboss.server.home.dir}/deploy
    auto.deploy.tomcat.dest.dir=${catalina.base}/webapps
    auto.deploy.weblogic.dest.dir=${env.DOMAIN_HOME}/autodeploy
    auto.deploy.websphere.dest.dir=${env.USER_INSTALL_ROOT}/wsadmin-deploy
    auto.deploy.wildfly.dest.dir=${jboss.home.dir}/standalone/deployments

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

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_INTERVAL

    auto.deploy.interval=3000

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

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_UNPACK_PERIOD_WAR

    auto.deploy.unpack.war=true

Set this to true if plugins should automatically copy Commons Logging.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_COPY_PERIOD_COMMONS_PERIOD_LOGGING

    auto.deploy.copy.commons.logging=true

Set this to true if plugins should automatically copy Log4j.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_COPY_PERIOD_LOG_NUMBER4_J

    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.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_CUSTOM_PERIOD_PORTLET_PERIOD_XML

    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.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_JBOSS_PERIOD_PREFIX

    auto.deploy.jboss.prefix=

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.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_TOMCAT_PERIOD_CONF_PERIOD_DIR

    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.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_TOMCAT_PERIOD_LIB_PERIOD_DIR

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

Set the options used when calling the AdminApp.install command.

See http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.express.doc/info/exp/ae/rxml_adminapp.html#rxml_adminapp__cmd9 for more information.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBSPHERE_PERIOD_WSADMIN_PERIOD_APP_PERIOD_MANAGER_PERIOD_INSTALL_PERIOD_OPTIONS

    auto.deploy.websphere.wsadmin.app.manager.install.options=-appname ${auto.deploy.websphere.wsadmin.app.name} -contextroot /${plugin.servlet.context.name} -usedefaultbindings

Set the options used when calling the AdminApp.list command.

See http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.express.doc/info/exp/ae/rxml_adminapp.html#rxml_adminapp__cmd9 for more information.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBSPHERE_PERIOD_WSADMIN_PERIOD_APP_PERIOD_MANAGER_PERIOD_LIST_PERIOD_OPTIONS

    auto.deploy.websphere.wsadmin.app.manager.list.options=

Set the options used when calling the AdminApp.update command.

See http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.express.doc/info/exp/ae/rxml_adminapp.html#rxml_adminapp__cmd9 for more information.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBSPHERE_PERIOD_WSADMIN_PERIOD_APP_PERIOD_MANAGER_PERIOD_UPDATE_PERIOD_OPTIONS

    auto.deploy.websphere.wsadmin.app.manager.update.options=-contents ${auto.deploy.dest.dir}/${plugin.servlet.context.name}.war -contextroot /${plugin.servlet.context.name} -operation update -usedefaultbindings

WebSphere 6 and 7 do not support the ability to hot deploy a WAR. The portal will attempt to use the wsadmin script to install a hot deployed plugin at runtime if this property is set. The wsadmin script uses this property to query the WebSphere application manager. Set this property to a blank value to disable this feature.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBSPHERE_PERIOD_WSADMIN_PERIOD_APP_PERIOD_MANAGER_PERIOD_QUERY

    auto.deploy.websphere.wsadmin.app.manager.query=type=ApplicationManager,process=server1,*

    auto.deploy.websphere.wsadmin.app.manager.query=

Set the suffix to be added to the plugin servlet context name in order to identify the WebSphere process it is deployed to. Leave it blank to use the plugin servlet context name only.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBSPHERE_PERIOD_WSADMIN_PERIOD_APP_PERIOD_NAME_PERIOD_SUFFIX

    auto.deploy.websphere.wsadmin.app.name.suffix=

Set the properties file name to use when invoking the wsadmin command. Configure this property to change the behavior of the wsadmin command, such as connection port or protocol.

Env: LIFERAY_AUTO_PERIOD_DEPLOY_PERIOD_WEBSPHERE_PERIOD_WSADMIN_PERIOD_PROPERTIES_PERIOD_FILE_PERIOD_NAME

    auto.deploy.websphere.wsadmin.properties.file.name=

Hot Deploy

Env: LIFERAY_HOT_PERIOD_DEPLOY_PERIOD_DEPENDENCY_PERIOD_MANAGEMENT_PERIOD_ENABLED

    hot.deploy.dependency.management.enabled=true

Input a list of comma delimited class names that implement com.liferay.portal.kernel.deploy.hot.HotDeployListener. These classes are used to process the deployment and undeployment of WARs at runtime.

The listeners are invoked in the order defined by this property. PluginPackageHotDeployListener must always be invoked first. SpringHotDeployListener must always be invoked before ServletContextListenerHotDeployListener. MessagingHotDeployListener must always be invoked last.

Env: LIFERAY_HOT_PERIOD_DEPLOY_PERIOD_LISTENERS

    hot.deploy.listeners=\
        com.liferay.portal.deploy.hot.PluginPackageHotDeployListener,\
        \
        com.liferay.portal.deploy.hot.ServletContextListenerHotDeployListener,\
        \
        com.liferay.portal.deploy.hot.ExtHotDeployListener,\
        com.liferay.portal.deploy.hot.HookHotDeployListener,\
        com.liferay.portal.deploy.hot.JSONWebServiceHotDeployListener,\
        com.liferay.portal.deploy.hot.LayoutTemplateHotDeployListener,\
        com.liferay.portal.deploy.hot.PortletHotDeployListener,\
        com.liferay.portal.deploy.hot.SocialHotDeployListener,\
        com.liferay.portal.deploy.hot.ThemeHotDeployListener,\
        com.liferay.portal.deploy.hot.ThemeLoaderHotDeployListener,\
        \
        com.liferay.portal.deploy.hot.OSGiHotDeployListener,\
        \
        com.liferay.portal.deploy.hot.MessagingHotDeployListener

Hot Undeploy

Set this to true to enable undeploying plugins.

Env: LIFERAY_HOT_PERIOD_UNDEPLOY_PERIOD_ENABLED

    hot.undeploy.enabled=true

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

Env: LIFERAY_HOT_PERIOD_UNDEPLOY_PERIOD_INTERVAL

    hot.undeploy.interval=0

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

Env: LIFERAY_HOT_PERIOD_UNDEPLOY_PERIOD_ON_PERIOD_REDEPLOY

    hot.undeploy.on.redeploy=false

Plugin

Input a list of comma delimited supported plugin types.

Env: LIFERAY_PLUGIN_PERIOD_TYPES

    plugin.types=\
        portlet,\
        theme,\
        layout-template,\
        hook,\
        web

Input a list of Liferay plugin repositories separated by \n characters.

Env: LIFERAY_PLUGIN_PERIOD_REPOSITORIES_PERIOD_TRUSTED Env: LIFERAY_PLUGIN_PERIOD_REPOSITORIES_PERIOD_UNTRUSTED

    plugin.repositories.trusted=
    plugin.repositories.untrusted=

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

Env: LIFERAY_PLUGIN_PERIOD_NOTIFICATIONS_PERIOD_ENABLED

    plugin.notifications.enabled=false

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 starts with the previous character.

Env: LIFERAY_PLUGIN_PERIOD_NOTIFICATIONS_PERIOD_PACKAGES_PERIOD_IGNORED

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

Portlet

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

Env: LIFERAY_PORTLET_PERIOD_VIRTUAL_PERIOD_PATH

    portlet.virtual.path=

Set this property to true to validate portlet.xml against the portlet schema.

Env: LIFERAY_PORTLET_PERIOD_XML_PERIOD_VALIDATE

    portlet.xml.validate=true

Portlets that have configured liferay-portlet.xml with the element "add-default-resource" set to true will allow those portlets to be dynamically added to any page by any user. This is useful (and necessary) for some portlets that need to be dynamically added to a page, but it can also pose a security risk because it also allows any user to do it.

Set this property to true to add a security check around this behavior. If set to true, then portlets can only be dynamically added to a page if it contains a proper security token. This security token is automatically passed when using a portlet URL from one portlet to another portlet.

Modify the property "portlet.add.default.resource.check.whitelist" to whitelist certain portlets from this security check.

The security check utilizes the implementation set in the property "auth.token.impl".

Env: LIFERAY_PORTLET_PERIOD_ADD_PERIOD_DEFAULT_PERIOD_RESOURCE_PERIOD_CHECK_PERIOD_ENABLED

    portlet.add.default.resource.check.enabled=true

Set a list of comma delimited portlet IDs that will bypass the security check set in the property "portlet.add.default.resource.check.enabled".

Env: LIFERAY_PORTLET_PERIOD_ADD_PERIOD_DEFAULT_PERIOD_RESOURCE_PERIOD_CHECK_PERIOD_WHITELIST

    portlet.add.default.resource.check.whitelist=\
        com_liferay_calendar_web_portlet_CalendarPortlet,\
        com_liferay_login_web_portlet_FastLoginPortlet,\
        com_liferay_login_web_portlet_LoginPortlet,\
        com_liferay_portlet_configuration_css_web_portlet_PortletConfigurationCSSPortlet,\
        com_liferay_portlet_configuration_web_portlet_PortletConfigurationPortlet,\
        com_liferay_product_navigation_simulation_web_portlet_SimulationPortlet,\
        com_liferay_staging_bar_web_portlet_StagingBarPortlet

Input a list of comma delimited struts actions that will bypass the security check set in the property "portlet.add.default.resource.check.enabled".

Env: LIFERAY_PORTLET_PERIOD_ADD_PERIOD_DEFAULT_PERIOD_RESOURCE_PERIOD_CHECK_PERIOD_WHITELIST_PERIOD_ACTIONS

    portlet.add.default.resource.check.whitelist.actions=

Set a list of comma delimited portlet IDs that will bypass the checks at first login (pages like terms of use, update password, password reminder query, etc.).

Such a portlet can also be embedded in a theme.

Keep in mind that this can be risky, because an attacker can issue POST requests on these portlets, even when there is no portlet embedded in a theme.

Env: LIFERAY_PORTLET_PERIOD_INTERRUPTED_PERIOD_REQUEST_PERIOD_WHITELIST

    portlet.interrupted.request.whitelist=

Input a list of comma delimited struts actions that will bypass the checks at first login (pages like terms of use, update password, password reminder query, etc.).

Env: LIFERAY_PORTLET_PERIOD_INTERRUPTED_PERIOD_REQUEST_PERIOD_WHITELIST_PERIOD_ACTIONS

    portlet.interrupted.request.whitelist.actions=

Input a regular expression to ban paths that cannot be used to serve resources in portlets.

Env: LIFERAY_PORTLET_PERIOD_RESOURCE_PERIOD_ID_PERIOD_BANNED_PERIOD_PATHS_PERIOD_REGEXP

    portlet.resource.id.banned.paths.regexp=.*[\\\\/](?:META-INF|WEB-INF)[\\\\/].*

Set this property to true to enable portlet session replication. This is only needed when session replication is enabled on the application server.

Env: LIFERAY_PORTLET_PERIOD_SESSION_PERIOD_REPLICATE_PERIOD_ENABLED

    portlet.session.replicate.enabled=false

Portlet Config

Set this property to true to show the portlet ID as a subtitle of the portlet configuration modal.

Env: LIFERAY_PORTLET_PERIOD_CONFIG_PERIOD_SHOW_PERIOD_PORTLET_PERIOD_ID

    portlet.config.show.portlet.id=false

Input a list of portlet resources that will be loaded.

Env: LIFERAY_PORTLET_PERIOD_CONFIGS

    portlet.configs=\
        /WEB-INF/portlet-custom.xml,\
        /WEB-INF/portlet-ext.xml,\
        /WEB-INF/liferay-portlet.xml,\
        /WEB-INF/liferay-portlet-ext.xml,\
        /WEB-INF/web.xml

Portlet Container

Set this property to true to restrict portlet communication via request attributes. See the property "layout.parallel.render.enable" on how that property affects this property.

Env: LIFERAY_PORTLET_PERIOD_CONTAINER_PERIOD_RESTRICT

    portlet.container.restrict=true

Portlet Coordination

This property controls how cross layout portlet URLs are invoked. When set to "render", only render URLs will be allowed invocation across different layouts. When set to "all", all portlet URL types will be allowed invocation.

Env: LIFERAY_PORTLET_PERIOD_CROSS_PERIOD_LAYOUT_PERIOD_INVOCATION_PERIOD_MODE

    portlet.cross.layout.invocation.mode=render

Set this property to specify how events are distributed. If the value is "layout-set", then events will be distributed to all portlets contained in a layout set. If the value is "layout", then events will be distributed to all portlets that are present in a layout.

Env: LIFERAY_PORTLET_PERIOD_EVENT_PERIOD_DISTRIBUTION

    portlet.event.distribution=layout

Set this property to specify how public render parameters are distributed. If the value is "layout-set", then public render parameters will be distributed to all portlets contained in a layout set. This will only work correctly if the property "layout.default.p_l_reset" is set to false. If the value is "layout", then public render parameters will be distributed to all portlets that are present in a layout.

Env: LIFERAY_PORTLET_PERIOD_PUBLIC_PERIOD_RENDER_PERIOD_PARAMETER_PERIOD_DISTRIBUTION

    portlet.public.render.parameter.distribution=layout

# Portlet Dependencies

Set the URN for portlet CSS dependencies added via portlet.xml, @Dependency, or HeaderResponse.addDependency. If specified, CSS dependencies will have the following URL pattern:

{portlet.dependency.css.urn}/scope/version/name.css

If not specified, CSS dependencies will have the following URL pattern:

http://{cdn.host.http}/css/scope/version/name.css (unsecure)

https://{cdn.host.https}/css/scope/version/name.css (secure)

If "cdn.host.http" and "cdn.host.http" are not specified, CSS dependencies will have the following URL pattern:

http://localhost:8080/css/scope/version/name.css

Generation of portlet dependency markup can be customized with an OSGi module that provides a service of the following type: com.liferay.portal.kernel.model.portlet.PortletDependencyFactory

Generation of portlet dependency URLs can be customized with an OSGi module that provides a service of the following type: com.liferay.portal.url.builder.AbsolutePortalURLBuilderFactory

Env: LIFERAY_PORTLET_PERIOD_DEPENDENCY_PERIOD_CSS_PERIOD_URN

    portlet.dependency.css.urn=

Set the URN for portlet JavaScript dependencies added via portlet.xml, @Dependency, or HeaderResponse.addDependency. If specified, JavaScript dependencies will have the following URL pattern:

{portlet.dependency.js.urn}/scope/version/name.js

If not specified, JavaScript dependencies will have the following URL pattern:

http://{cdn.host.http}/js/scope/version/name.js (unsecure)

https://{cdn.host.https}/js/scope/version/name.js (secure)

If "cdn.host.http" and "cdn.host.htt"p are not specified, JavaScript dependencies will have the following URL pattern:

http://localhost:8080/js/scope/version/name.js

Generation of portlet dependency markup can be customized with an OSGi module that provides a service of the following type: com.liferay.portal.kernel.model.portlet.PortletDependencyFactory

Generation of portlet dependency URLs can be customized with an OSGi module that provides a service of the following type: com.liferay.portal.url.builder.AbsolutePortalURLBuilderFactory

Env: LIFERAY_PORTLET_PERIOD_DEPENDENCY_PERIOD_JAVASCRIPT_PERIOD_URN

    portlet.dependency.javascript.urn=

Portlet Display Templates

Set the location of the default error content for portlet display templates for each language type.

Env: LIFERAY_PORTLET_PERIOD_DISPLAY_PERIOD_TEMPLATES_PERIOD_ERROR_OPENBRACKET_FTL_CLOSEBRACKET_ Env: LIFERAY_PORTLET_PERIOD_DISPLAY_PERIOD_TEMPLATES_PERIOD_ERROR_OPENBRACKET_VM_CLOSEBRACKET_

    portlet.display.templates.error[ftl]=com/liferay/portlet/portletdisplaytemplate/dependencies/portlet_display_template_error.ftl
    portlet.display.templates.error[vm]=com/liferay/portlet/portletdisplaytemplate/dependencies/portlet_display_template_error.vm

Set the location of the default help content for portlet display templates for each language type.

Env: LIFERAY_PORTLET_PERIOD_DISPLAY_PERIOD_TEMPLATES_PERIOD_HELP_OPENBRACKET_FTL_CLOSEBRACKET_ Env: LIFERAY_PORTLET_PERIOD_DISPLAY_PERIOD_TEMPLATES_PERIOD_HELP_OPENBRACKET_VM_CLOSEBRACKET_

    portlet.display.templates.help[ftl]=com/liferay/portlet/portletdisplaytemplate/dependencies/portlet_display_template_help.ftl
    portlet.display.templates.help[vm]=com/liferay/portlet/portletdisplaytemplate/dependencies/portlet_display_template_help.vm

Portlet Filters

Input a list of portlet filters that will be applied to all portlets.

Env: LIFERAY_PORTLET_PERIOD_FILTERS_PERIOD_SYSTEM

    portlet.filters.system=com.liferay.portlet.ScriptDataPortletFilter

Portlet Preferences

PortletPreferencesFactoryImpl caches the portlet preferences' XML content, where the XML content is used as a cache key. In some cases, the content can be very large (i.e. larger than 1 mb). This property defines a threshold to use XML content as key only below this threshold. Above the threshold, an SHA-1 hash will be generated, but that's an expensive operation, so this property should be specified wisely. The default value is 1 kb.

Env: LIFERAY_PORTLET_PERIOD_PREFERENCES_PERIOD_CACHE_PERIOD_KEY_PERIOD_THRESHOLD_PERIOD_SIZE

    portlet.preferences.cache.key.threshold.size=1024

Set this property to false to break PLT.17.1's restriction to allow portlet preferences to be stored during render phase. This property exists for backwards compatibility with legacy portlets.

Env: LIFERAY_PORTLET_PERIOD_PREFERENCES_PERIOD_STRICT_PERIOD_STORE

    portlet.preferences.strict.store=true

Theme

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 disable fast loading by setting the URL parameter "css_fast_load" to "0" when the property "theme.css.fast.load.check.request.parameter" is also set to true.

Env: LIFERAY_THEME_PERIOD_CSS_PERIOD_FAST_PERIOD_LOAD

    theme.css.fast.load=true

Set this property to false to ignore the URL parameter "css_fast_load". See the property "theme.css.fast.load".

Env: LIFERAY_THEME_PERIOD_CSS_PERIOD_FAST_PERIOD_LOAD_PERIOD_CHECK_PERIOD_REQUEST_PERIOD_PARAMETER

    theme.css.fast.load.check.request.parameter=false

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

Set this property to false for easier debugging for development. You can also disable fast loading by setting the URL parameter "images_fast_load" to "0" when the property "theme.images.fast.load.check.request.parameter" is also set to true.

Env: LIFERAY_THEME_PERIOD_IMAGES_PERIOD_FAST_PERIOD_LOAD

    theme.images.fast.load=true

Set this property to false to ignore the URL parameter "images_fast_load". See the property "theme.images.fast.load".

Env: LIFERAY_THEME_PERIOD_IMAGES_PERIOD_FAST_PERIOD_LOAD_PERIOD_CHECK_PERIOD_REQUEST_PERIOD_PARAMETER

    theme.images.fast.load.check.request.parameter=false

Set this property to true to allow directly invoked JSPs to be overridden by a different version of the JSP that exists in a theme.

Env: LIFERAY_THEME_PERIOD_JSP_PERIOD_OVERRIDE_PERIOD_ENABLED

    theme.jsp.override.enabled=false

Set the theme's shortcut icon.

Env: LIFERAY_THEME_PERIOD_SHORTCUT_PERIOD_ICON

    theme.shortcut.icon=favicon.ico

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

Env: LIFERAY_THEME_PERIOD_VIRTUAL_PERIOD_PATH

    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.

Env: LIFERAY_THEME_PERIOD_LOADER_PERIOD_STORAGE_PERIOD_PATH

    theme.loader.storage.path=

Themes can be imported via LAR files. Set this to true if imported themes should 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.

Env: LIFERAY_THEME_PERIOD_LOADER_PERIOD_NEW_PERIOD_THEME_PERIOD_ID_PERIOD_ON_PERIOD_IMPORT

    theme.loader.new.theme.id.on.import=false

Set this to true to decorate portlets by default.

Env: LIFERAY_THEME_PERIOD_PORTLET_PERIOD_DECORATE_PERIOD_DEFAULT

    theme.portlet.decorate.default=true

Set this to true to expose sharing icons for portlets by default.

Env: LIFERAY_THEME_PERIOD_PORTLET_PERIOD_SHARING_PERIOD_DEFAULT

    theme.portlet.sharing.default=false

Resource Actions

Input a list of comma delimited resource action configurations that will be read from the class path.

Env: LIFERAY_RESOURCE_PERIOD_ACTIONS_PERIOD_CONFIGS

    resource.actions.configs=\
        META-INF/resource-actions/default.xml,\
        resource-actions/default.xml

This should only be set to false when it is called by Service Builder outside of an application server or servlet container.

Env: LIFERAY_RESOURCE_PERIOD_ACTIONS_PERIOD_READ_PERIOD_PORTLET_PERIOD_RESOURCES

    resource.actions.read.portlet.resources=true

Model Hints

Input a list of comma delimited model hints configurations.

Env: LIFERAY_MODEL_PERIOD_HINTS_PERIOD_CONFIGS

    model.hints.configs=\
        META-INF/portal-model-hints.xml,\
        classpath*:META-INF/ext-model-hints.xml,\
        classpath*:META-INF/portlet-model-hints.xml

Model Tree Path

Set the batch size of database query results returned during the tree rebuilding operation. If set to -1, the results will not be paginated and may result in a larger memory footprint.

Env: LIFERAY_MODEL_PERIOD_TREE_PERIOD_REBUILD_PERIOD_QUERY_PERIOD_RESULTS_PERIOD_BATCH_PERIOD_SIZE

    model.tree.rebuild.query.results.batch.size=10000

Spring

Input a list of comma delimited Spring configurations. These will be loaded after the bean definitions specified in the contextConfigLocation parameter in web.xml.

Env: LIFERAY_SPRING_PERIOD_CONFIGS

    spring.configs=\
        META-INF/base-spring.xml,\
        \
        META-INF/util-spring.xml,\
        \
        META-INF/executor-spring.xml,\
        \
        META-INF/messaging-core-spring.xml,\
        META-INF/messaging-misc-spring.xml,\
        \
        META-INF/security-spring.xml,\
        \
        META-INF/company-provider-spring.xml,\
        META-INF/document-library-spring.xml,\
        META-INF/layout-spring.xml,\
        META-INF/model-listener-spring.xml,\
        META-INF/notifications-spring.xml,\
        META-INF/poller-spring.xml,\
        META-INF/prefs-spring.xml,\
        META-INF/repository-spring.xml,\
        META-INF/search-spring.xml,\
        META-INF/social-spring.xml,\
        META-INF/workflow-spring.xml,\
        \
        META-INF/counter-spring.xml,\
        META-INF/mail-spring.xml,\
        META-INF/portal-spring.xml,\
        META-INF/portlet-container-spring.xml,\
        META-INF/staging-spring.xml,\
        META-INF/virtual-layouts-spring.xml,\
        \
        classpath*:META-INF/ext-spring*.xml

Input a list of comma delimited Spring infrastructure configurations. These will be loaded after the module framework is initialized but before it is started.

Env: LIFERAY_SPRING_PERIOD_INFRASTRUCTURE_PERIOD_CONFIGS

    spring.infrastructure.configs=\
        META-INF/infrastructure-spring.xml,\
        \
        META-INF/counter-infrastructure-spring.xml,\
        #META-INF/dynamic-data-source-infrastructure-spring.xml,\
        META-INF/hibernate-spring.xml

Set this property to true to verify that the session factory is owned by the proper transaction manager. Set this property to false to turn off verification for better performance.

Env: LIFERAY_SPRING_PERIOD_HIBERNATE_PERIOD_SESSION_PERIOD_FACTORY_PERIOD_VERIFY

    spring.hibernate.session.factory.verify=true

Set the list of portal classes that will be preloaded by the PreloadClassloader and therefore available to a plugin's Hibernate session factory.

Env: LIFERAY_SPRING_PERIOD_HIBERNATE_PERIOD_CONFIGURATION_PERIOD_PROXY_PERIOD_FACTORY_PERIOD_PRELOAD_PERIOD_CLASSLOADER_PERIOD_CLASSES

    spring.hibernate.configuration.proxy.factory.preload.classloader.classes=\
        javassist.util.proxy.MethodHandler,\
        javassist.util.proxy.ProxyObject,\
        javassist.util.proxy.RuntimeSupport,\
        org.hibernate.proxy.HibernateProxy,\
        org.hibernate.proxy.LazyInitializer

Set the list of portal classes that will be preloaded by the PreloadClassloader and therefore available to a plugin's Hibernate session factory.

Env: LIFERAY_SPRING_PERIOD_HIBERNATE_PERIOD_SESSION_PERIOD_FACTORY_PERIOD_PRELOAD_PERIOD_CLASSLOADER_PERIOD_CLASSES

    spring.hibernate.session.factory.preload.classloader.classes=\
        org.hibernate.engine.jdbc.WrappedBlob

Set this property to false to manually open and close sessions.

Env: LIFERAY_SPRING_PERIOD_HIBERNATE_PERIOD_SESSION_PERIOD_DELEGATED

    spring.hibernate.session.delegated=true

Hibernate

Input a list of comma delimited Hibernate configurations.

Env: LIFERAY_HIBERNATE_PERIOD_CONFIGS

    hibernate.configs=\
        META-INF/mail-hbm.xml,\
        META-INF/portal-hbm.xml,\
        classpath*:META-INF/ext-hbm.xml

Liferay will automatically detect the Hibernate dialect in com.liferay.portal.spring.PortalHibernateConfiguration. Set this property to manually override the automatically detected dialect.

Env: LIFERAY_HIBERNATE_PERIOD_DIALECT

    hibernate.dialect=

Set the Hibernate connection release mode. You should not modify this unless you know what you're doing. The default setting works best for Spring managed transactions. See the method buildSessionFactory in class org.springframework.orm.hibernate3.LocalSessionFactoryBean and search for the phrase "on_close" to understand how this works.

Env: LIFERAY_HIBERNATE_PERIOD_CONNECTION_PERIOD_RELEASE_UNDERLINE_MODE

    hibernate.connection.release_mode=on_close

Set the JDBC batch size to improve performance.

If you're using Hypersonic, you SHOULD set the batch size to 0 as a workaround for a logging bug in the Hypersonic driver. See LPS-5426 for more information.

If you're using Oracle 9i, you MUST set the batch size to 0 as a workaround for a hanging bug in the Oracle driver. See LEP-1234 for more information.

Env: LIFERAY_HIBERNATE_PERIOD_JDBC_PERIOD_BATCH_UNDERLINE_SIZE

    hibernate.jdbc.batch_size=20

    hibernate.jdbc.batch_size=0

Set other miscellaneous Hibernate properties.

Env: LIFERAY_HIBERNATE_PERIOD_BYTECODE_PERIOD_USE_UNDERLINE_REFLECTION_UNDERLINE_OPTIMIZER Env: LIFERAY_HIBERNATE_PERIOD_JDBC_PERIOD_USE_UNDERLINE_SCROLLABLE_UNDERLINE_RESULTSET Env: LIFERAY_HIBERNATE_PERIOD_SHOW_UNDERLINE_SQL

    hibernate.jdbc.use_scrollable_resultset=true
    hibernate.bytecode.use_reflection_optimizer=true
    hibernate.show_sql=false

Use the classic query factory until WebLogic and Hibernate 3 can get along. See http://www.hibernate.org/250.html#A23 for more information.

Env: LIFERAY_HIBERNATE_PERIOD_QUERY_PERIOD_FACTORY_UNDERLINE_CLASS

    hibernate.query.factory_class=org.hibernate.hql.classic.ClassicQueryTranslatorFactory

Set this property to true to enable Hibernate cache monitoring. See LPS-2056 for more information.

Env: LIFERAY_HIBERNATE_PERIOD_GENERATE_UNDERLINE_STATISTICS

    hibernate.generate_statistics=false

Set the regexp pattern to filter a Hibernate session factory imported class name before continuing with classloader resolving.

This is used to fix the infamous Hibernate ReflectHelper.classForName() synchronization problem. For more details, see the Hibernate issues HHH-1810, HHH-4959, HHH-10746, and HHH-11246.

If no regexp pattern is set, classloader resolving is skipped, resulting in the class name being resolved against the configuration's imports map.

The wildcard pattern ".*" disables this optimization, reverting back to the original Hibernate behavior.

Any other pattern resolves the class name against the configuration's imports map first. If it can not be resolved, it attempts to match this pattern. If it matches, continue with classloader resolving; otherwise, return null as unable to resolve.

Env: LIFERAY_HIBERNATE_PERIOD_SESSION_PERIOD_FACTORY_PERIOD_IMPORTED_PERIOD_CLASS_PERIOD_NAME_PERIOD_REGEXP

    hibernate.session.factory.imported.class.name.regexp=

Set this property to true to enable constraint propagation to DDL.

Env: LIFERAY_HIBERNATE_PERIOD_VALIDATOR_PERIOD_APPLY_UNDERLINE_TO_UNDERLINE_DDL

    hibernate.validator.apply_to_ddl=false

JDBC

Set the JNDI name to lookup the JDBC data source. If none is set, then the portal will attempt to create the JDBC data source based on the properties prefixed with "jdbc.default.".

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_JNDI_PERIOD_NAME

    jdbc.default.jndi.name=jdbc/LiferayPool

Set the properties used to create the JDBC data source. These properties will only be read if the property "jdbc.default.jndi.name" is not set.

The default settings are configured for an in-memory database called Hypersonic that is not recommended for production use. Please change the properties to use another database.

To configure the portal to use one data source for read calls and another data source for read-write calls, follow these steps:

1. Similar to the settings prefixed with "jdbc.default.", create a set of properties prefixed with "jdbc.read." to handle read calls and another set of properties prefixed with "jdbc.write." to handle read-write calls.

2. Add "jdbc.read.jndi.name" and "jdbc.write.jndi.name" properties that specify the data source JNDI names.

3. Add dynamic-data-source-spring.xml to the property "spring.configs" and dynamic-data-source-infrastructure-spring.xml to the property "spring.infrastructure.configs"

DB2

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=com.ibm.db2.jcc.DB2Driver
    jdbc.default.url=jdbc:db2://localhost:50000/lportal:deferPrepares=false;fullyMaterializeInputStreams=true;fullyMaterializeLobData=true;progresssiveLocators=2;progressiveStreaming=2;
    jdbc.default.username=db2admin
    jdbc.default.password=lportal

Hypersonic

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=org.hsqldb.jdbc.JDBCDriver
    jdbc.default.url=jdbc:hsqldb:${liferay.home}/data/hypersonic/lportal;hsqldb.lock_file=false,hsqldb.write_delay=false
    jdbc.default.username=sa
    jdbc.default.password=

MariaDB

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=org.mariadb.jdbc.Driver
    jdbc.default.url=jdbc:mariadb://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
    jdbc.default.username=
    jdbc.default.password=

MySQL

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=com.mysql.cj.jdbc.Driver
    jdbc.default.url=jdbc:mysql://localhost/lportal?characterEncoding=UTF-8&dontTrackOpenResources=true&holdResultsOpenOverStatementClose=true&serverTimezone=GMT&useFastDateParsing=false&useUnicode=true
    jdbc.default.username=
    jdbc.default.password=

Oracle

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=oracle.jdbc.OracleDriver
    jdbc.default.url=jdbc:oracle:thin:@localhost:1521:xe
    jdbc.default.username=lportal
    jdbc.default.password=lportal

P6Spy

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=com.p6spy.engine.spy.P6SpyDriver
    jdbc.default.url=jdbc:mysql://localhost/lportal?characterEncoding=UTF-8&dontTrackOpenResources=true&holdResultsOpenOverStatementClose=true&useFastDateParsing=false&useUnicode=true
    jdbc.default.username=
    jdbc.default.password=

PostgreSQL

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=org.postgresql.Driver
    jdbc.default.url=jdbc:postgresql://localhost:5432/lportal
    jdbc.default.username=sa
    jdbc.default.password=

SQL Server

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
    jdbc.default.url=jdbc:sqlserver://localhost;databaseName=lportal
    jdbc.default.username=sa
    jdbc.default.password=

Sybase

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME

    jdbc.default.driverClassName=com.sybase.jdbc4.jdbc.SybDriver
    jdbc.default.url=jdbc:sybase:Tds:localhost:5000/lportal
    jdbc.default.username=sa
    jdbc.default.password=

Liferay can use C3PO, DBCP, HikariCP, or Tomcat for connection pooling. See com.liferay.portal.dao.jdbc.spring.DataSourceFactoryBean for the actual implementation. It is important to understand the strengths and weaknesses of each provider so that you can choose the best one that fits your deployment scenario. Provider specific properties can also be passed along directly to the provider. For example, the property "jdbc.default.acquireIncrement" is read by C3PO, and the property "jdbc.default.maxActive" is read by DBCP.

The default provider is HikariCP.

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_LIFERAY_PERIOD_POOL_PERIOD_PROVIDER

    jdbc.default.liferay.pool.provider=hikaricp

    jdbc.default.liferay.pool.provider=c3po
    jdbc.default.liferay.pool.provider=dbcp
    jdbc.default.liferay.pool.provider=tomcat

The following properties will be read by C3PO if Liferay is configured to use C3PO in the property "jdbc.default.liferay.pool.provider". See http://www.mchange.com/projects/c3p0/index.html#configuration for a list of additional fields used by C3PO for configuring database connections.

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_ACQUIRE_UPPERCASEI_NCREMENT Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_ACQUIRE_UPPERCASER_ETRY_UPPERCASEA_TTEMPTS Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_ACQUIRE_UPPERCASER_ETRY_UPPERCASED_ELAY Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_CONNECTION_UPPERCASEC_USTOMIZER_UPPERCASEC_LASS_UPPERCASEN_AME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_IDLE_UPPERCASEC_ONNECTION_UPPERCASET_EST_UPPERCASEP_ERIOD Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_INITIAL_UPPERCASEP_OOL_UPPERCASES_IZE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MAX_UPPERCASEI_DLE_UPPERCASET_IME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MAX_UPPERCASEP_OOL_UPPERCASES_IZE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MIN_UPPERCASEP_OOL_UPPERCASES_IZE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_NUM_UPPERCASEH_ELPER_UPPERCASET_HREADS Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_TRANSACTION_UPPERCASEI_SOLATION

    jdbc.default.acquireIncrement=5
    jdbc.default.acquireRetryAttempts=3
    jdbc.default.acquireRetryDelay=1000
    jdbc.default.connectionCustomizerClassName=com.liferay.portal.dao.jdbc.pool.c3p0.PortalConnectionCustomizer
    jdbc.default.idleConnectionTestPeriod=60
    jdbc.default.initialPoolSize=10
    jdbc.default.maxIdleTime=3600
    jdbc.default.maxPoolSize=100
    jdbc.default.minPoolSize=10
    jdbc.default.numHelperThreads=10

    jdbc.default.transactionIsolation=1

The following properties will be read by HikariCP if Liferay is configured to use HikariCP in the property "jdbc.default.liferay.pool.provider". See https://github.com/brettwooldridge/HikariCP for a list of additional fields used by HikariCP for configuring database connections.

HikariCP recommends to also tune database settings. See https://github.com/brettwooldridge/HikariCP/wiki for additional setting details for database.

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_AUTO_UPPERCASEC_OMMIT Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_CONNECTION_UPPERCASET_EST_UPPERCASEQ_UERY Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_CONNECTION_UPPERCASET_IMEOUT Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_IDLE_UPPERCASET_IMEOUT Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_INITIALIZATION_UPPERCASEF_AIL_UPPERCASEF_AST Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MAXIMUM_UPPERCASEP_OOL_UPPERCASES_IZE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MAX_UPPERCASEL_IFETIME Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MINIMUM_UPPERCASEI_DLE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_REGISTER_UPPERCASEM_BEANS

    jdbc.default.connectionTimeout=30000
    jdbc.default.idleTimeout=600000
    jdbc.default.maximumPoolSize=100
    jdbc.default.maxLifetime=0
    jdbc.default.minimumIdle=10
    jdbc.default.registerMbeans=true

    jdbc.default.autoCommit=true
    jdbc.default.connectionTestQuery=SELECT releaseId FROM Release_
    jdbc.default.initializationFailFast=false

The following properties will be read by both DBCP and Tomcat JDBC Connection Pool if Liferay is configured to use DBCP or Tomcat JDBC Connection Pool in the property "jdbc.default.liferay.pool.provider". See http://commons.apache.org/dbcp/configuration.html and http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html for a list of additional fields used by DBCP or Tomcat JDBC Connection Pool for configuring database connections.

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DEFAULT_UPPERCASET_RANSACTION_UPPERCASEI_SOLATION Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_LOG_UPPERCASEA_BANDONED Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MAX_UPPERCASEA_CTIVE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_MIN_UPPERCASEI_DLE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_REMOVE_UPPERCASEA_BANDONED_UPPERCASET_IMEOUT Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_TEST_UPPERCASEW_HILE_UPPERCASEI_DLE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_TIME_UPPERCASEB_ETWEEN_UPPERCASEE_VICTION_UPPERCASER_UNS_UPPERCASEM_ILLIS Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_VALIDATION_UPPERCASEQ_UERY

    jdbc.default.maxActive=100
    jdbc.default.minIdle=10
    jdbc.default.testWhileIdle=true
    jdbc.default.timeBetweenEvictionRunsMillis=30000
    jdbc.default.validationQuery=SELECT releaseId FROM Release_

    jdbc.default.defaultTransactionIsolation=READ_UNCOMMITTED
    jdbc.default.logAbandoned=true
    jdbc.default.removeAbandonedTimeout=3600

The following properties will be read by Tomcat JDBC Connection Pool if Liferay is configured to use Tomcat JDBC Connection Pool in the property "jdbc.default.liferay.pool.provider". See http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html for a list of additional fields used by Tomcat JDBC Connection Pool for configuring database connections.

Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_FAIR_UPPERCASEQ_UEUE Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_JDBC_UPPERCASEI_NTERCEPTORS Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_JMX_UPPERCASEE_NABLED Env: LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USE_UPPERCASEE_QUALS

    jdbc.default.jdbcInterceptors=org.apache.tomcat.jdbc.pool.interceptor.ConnectionState
    jdbc.default.jmxEnabled=true
    jdbc.default.fairQueue=true
    jdbc.default.useEquals=false

Custom SQL

Set this property to true to automatically escape wildcards to literal values.

Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_AUTO_PERIOD_ESCAPE_PERIOD_WILDCARDS_PERIOD_ENABLED

    custom.sql.auto.escape.wildcards.enabled=false

Input a list of comma delimited custom SQL configurations.

Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_CONFIGS

    custom.sql.configs=custom-sql/default.xml

Some databases do not recognize a NULL IS NULL check. Set the "custom.sql.function.isnull" and "custom.sql.function.isnotnull" properties for your specific database.

There is no need to manually set these properties because com.liferay.portal.spring.PortalHibernateConfiguration already sets it. However, these properties are available so that you can see how you can override it for a database that PortalHibernateConfiguration does not yet know how to auto configure.

DB2

Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_FUNCTION_PERIOD_ISNOTNULL Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_FUNCTION_PERIOD_ISNULL

    custom.sql.function.isnull=CAST(? AS VARCHAR(32672)) IS NULL
    custom.sql.function.isnotnull=CAST(? AS VARCHAR(32672)) IS NOT NULL

MySQL (for testing only)

Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_FUNCTION_PERIOD_ISNOTNULL Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_FUNCTION_PERIOD_ISNULL

    custom.sql.function.isnull=IFNULL(?, '1') = '1'
    custom.sql.function.isnotnull=IFNULL(?, '1') = '0'

Sybase

Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_FUNCTION_PERIOD_ISNOTNULL Env: LIFERAY_CUSTOM_PERIOD_SQL_PERIOD_FUNCTION_PERIOD_ISNULL

    custom.sql.function.isnull=CONVERT(VARCHAR,?) IS NULL
    custom.sql.function.isnotnull=CONVERT(VARCHAR,?) IS NOT NULL

Database

Set this property to true to update database indexes on startup. This will ensure that all necessary indexes are added and that unnecessary indexes are removed. Only indexes that have names that match "LIFERAY_" OR "IX_" will be updated. Make sure that your custom indexes do not match the Liferay pattern to ensure that your custom indexes are not removed as unnecessary indexes.

Env: LIFERAY_DATABASE_PERIOD_INDEXES_PERIOD_UPDATE_PERIOD_ON_PERIOD_STARTUP

    database.indexes.update.on.startup=false

Set the max number of parameters for an IN clause.

Env: LIFERAY_DATABASE_PERIOD_IN_PERIOD_MAX_PERIOD_PARAMETERS_OPENBRACKET_ORACLE_CLOSEBRACKET_

    database.in.max.parameters[oracle]=1000

Set the max number of columns in an ORDER BY clause.

Env: LIFERAY_DATABASE_PERIOD_ORDER_PERIOD_BY_PERIOD_MAX_PERIOD_COLUMNS_OPENBRACKET_SYBASE_CLOSEBRACKET_

    database.order.by.max.columns[sybase]=31

Set the max length for string type of index.

Env: LIFERAY_DATABASE_PERIOD_STRING_PERIOD_INDEX_PERIOD_MAX_PERIOD_LENGTH_OPENBRACKET_MARIADB_CLOSEBRACKET_ Env: LIFERAY_DATABASE_PERIOD_STRING_PERIOD_INDEX_PERIOD_MAX_PERIOD_LENGTH_OPENBRACKET_MYSQL_CLOSEBRACKET_

    database.string.index.max.length[mariadb]=255
    database.string.index.max.length[mysql]=255

Specify any database vendor specific settings.

MySQL

Set the MySQL engine type. InnoDB is the recommended engine because it provides transactional integrity.

Env: LIFERAY_DATABASE_PERIOD_MYSQL_PERIOD_ENGINE

    database.mysql.engine=InnoDB

Transaction

Set the transaction isolation level for the Counter service. See "transaction.isolation.portal" for more information. The preferred value is 8 when the transaction manager supports it. If the transaction manager does not support it, set this to -1 to use the database's default isolation level.

Env: LIFERAY_TRANSACTION_PERIOD_ISOLATION_PERIOD_COUNTER

    transaction.isolation.counter=2

Set the definition of the "portal" transaction isolation level. The "portal" transaction isolation level is not a real isolation level. It is just a pointer to a real isolation level that can be configured by setting this property. Set the value to -1 to use the database's default isolation level. Set the value to 2 to use "read committed". Set the value to 1 to use "read uncommitted". Set the value to 4 to use "repeatable read". Set the value to 8 to use "serializable".

Env: LIFERAY_TRANSACTION_PERIOD_ISOLATION_PERIOD_PORTAL

    transaction.isolation.portal=2

Additional properties that follow the pattern "transaction.manager.property.*" will be read to call the setters on the transaction manager. For example, the property "transaction.manager.property.globalRollbackOnParticipationFailure", will call the setter "setGlobalRollbackOnParticipationFailure" on the transaction manager.

"allowCustomIsolationLevels" should be set to true when using the JtaTransactionManager.

Env: LIFERAY_TRANSACTION_PERIOD_MANAGER_PERIOD_PROPERTY_PERIOD_ALLOW_UPPERCASEC_USTOM_UPPERCASEI_SOLATION_UPPERCASEL_EVELS Env: LIFERAY_TRANSACTION_PERIOD_MANAGER_PERIOD_PROPERTY_PERIOD_GLOBAL_UPPERCASER_OLLBACK_UPPERCASEO_N_UPPERCASEP_ARTICIPATION_UPPERCASEF_AILURE

    transaction.manager.property.globalRollbackOnParticipationFailure=false

    transaction.manager.property.allowCustomIsolationLevels=true

Transactional Cache

Set this property to true to enable transactional cache. When enabled, changes to caches take effect when transaction commits successfully. Caches rollback when transactions rollback.

Env: LIFERAY_TRANSACTIONAL_PERIOD_CACHE_PERIOD_ENABLE

    transactional.cache.enable=true

Set a list of comma delimited transactional portal cache names. The "?" character represents a single character wildcard. The "*" symbol character a multiple character wildcard. The "%" character is used to escape characters.

Env: LIFERAY_TRANSACTIONAL_PERIOD_CACHE_PERIOD_NAMES

    transactional.cache.names=\
        com.liferay.portal.kernel.dao.orm.EntityCache*,\
        com.liferay.portal.kernel.dao.orm.FinderCache*,\
        com.liferay.portal.kernel.service.persistence.impl.TableMapper-*,\
        com.liferay.portlet.PortalPreferencesWrapperCacheUtil

Ehcache

Set the classpath to the location of the Ehcache config file for internal caches. Edit the file specified in the property "ehcache.multi-vm.config.location" to enable clustered cache.

Env: LIFERAY_EHCACHE_PERIOD_MULTI_PERIOD_VM_PERIOD_CONFIG_PERIOD_LOCATION Env: LIFERAY_EHCACHE_PERIOD_SINGLE_PERIOD_VM_PERIOD_CONFIG_PERIOD_LOCATION

    ehcache.single.vm.config.location=/ehcache/liferay-single-vm.xml
    ehcache.multi.vm.config.location=/ehcache/liferay-multi-vm.xml

Input a list of comma delimited key value pair to set replication properties for the default cache.

Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_DEFAULT

    ehcache.replicator.properties.default=

Input a list of comma delimited key value pair to set replication properties for a specific cache.

Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_DYNAMIC_PERIOD_DATA_PERIOD_MAPPING_PERIOD_DATA_PERIOD_PROVIDER_PERIOD_INTERNAL_PERIOD_REST_PERIOD__UPPERCASED__UPPERCASED__UPPERCASEM__UPPERCASER__UPPERCASEE__UPPERCASES__UPPERCASET__UPPERCASED_ATA_UPPERCASEP_ROVIDER Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_JOURNAL_PERIOD_UTIL_PERIOD__UPPERCASEJ_OURNAL_UPPERCASEC_ONTENT Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_TEMPLATE_PERIOD__UPPERCASET_EMPLATE_UPPERCASER_ESOURCE_UPPERCASEL_OADER_PERIOD_CSS Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_TEMPLATE_PERIOD__UPPERCASET_EMPLATE_UPPERCASER_ESOURCE_UPPERCASEL_OADER_PERIOD_FTL Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_TEMPLATE_PERIOD__UPPERCASET_EMPLATE_UPPERCASER_ESOURCE_UPPERCASEL_OADER_PERIOD_VM Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_WEBSERVER_PERIOD__UPPERCASEW_EB_UPPERCASES_ERVER_UPPERCASES_ERVLET_UPPERCASET_OKEN Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_SECURITY_PERIOD_PERMISSION_PERIOD__UPPERCASEP_ERMISSION_UPPERCASEC_ACHE_UPPERCASEU_TIL_UNDERLINE__UPPERCASEP__UPPERCASEE__UPPERCASER__UPPERCASEM__UPPERCASEI__UPPERCASES__UPPERCASES__UPPERCASEI__UPPERCASEO__UPPERCASEN_ Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_SECURITY_PERIOD_PERMISSION_PERIOD__UPPERCASEP_ERMISSION_UPPERCASEC_ACHE_UPPERCASEU_TIL_UNDERLINE__UPPERCASEP__UPPERCASEE__UPPERCASER__UPPERCASEM__UPPERCASEI__UPPERCASES__UPPERCASES__UPPERCASEI__UPPERCASEO__UPPERCASEN__UNDERLINE__UPPERCASEC__UPPERCASEH__UPPERCASEE__UPPERCASEC__UPPERCASEK__UPPERCASEE__UPPERCASER__UNDERLINE__UPPERCASEB__UPPERCASEA__UPPERCASEG_ Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_SECURITY_PERIOD_PERMISSION_PERIOD__UPPERCASEP_ERMISSION_UPPERCASEC_ACHE_UPPERCASEU_TIL_UNDERLINE__UPPERCASER__UPPERCASEE__UPPERCASES__UPPERCASEO__UPPERCASEU__UPPERCASER__UPPERCASEC__UPPERCASEE__UNDERLINE__UPPERCASEB__UPPERCASEL__UPPERCASEO__UPPERCASEC__UPPERCASEK__UNDERLINE__UPPERCASEI__UPPERCASED__UPPERCASES__UNDERLINE__UPPERCASEB__UPPERCASEA__UPPERCASEG_ Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_SERVLET_PERIOD_FILTERS_PERIOD_CACHE_PERIOD__UPPERCASEC_ACHE_UPPERCASEU_TIL Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTLET_PERIOD_SOCIAL_PERIOD_SERVICE_PERIOD_IMPL_PERIOD__UPPERCASES_OCIAL_UPPERCASEA_CTIVITY_UPPERCASES_ETTING_UPPERCASEL_OCAL_UPPERCASES_ERVICE_UPPERCASEI_MPL Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD_COM_PERIOD_LIFERAY_PERIOD_WIKI_PERIOD_MODEL_PERIOD__UPPERCASEW_IKI_UPPERCASEP_AGE_UPPERCASED_ISPLAY Env: LIFERAY_EHCACHE_PERIOD_REPLICATOR_PERIOD_PROPERTIES_PERIOD__DOLLAR__OPENCURLYBRACE_SPECIFIC_PERIOD_CACHE_PERIOD_NAME_CLOSECURLYBRACE_

    ehcache.replicator.properties.com.liferay.dynamic.data.mapping.data.provider.internal.rest.DDMRESTDataProvider=replicatePuts=false
    ehcache.replicator.properties.com.liferay.journal.util.JournalContent=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.kernel.template.TemplateResourceLoader.css=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.kernel.template.TemplateResourceLoader.ftl=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.kernel.template.TemplateResourceLoader.vm=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.security.permission.PermissionCacheUtil_PERMISSION=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.security.permission.PermissionCacheUtil_PERMISSION_CHECKER_BAG=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.security.permission.PermissionCacheUtil_RESOURCE_BLOCK_IDS_BAG=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.servlet.filters.cache.CacheUtil=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portal.kernel.webserver.WebServerServletToken=replicatePuts=false
    ehcache.replicator.properties.com.liferay.portlet.social.service.impl.SocialActivitySettingLocalServiceImpl=replicatePuts=false
    ehcache.replicator.properties.com.liferay.wiki.model.WikiPageDisplay=replicatePuts=false

    ehcache.replicator.properties.${specific.cache.name}=

Set this to true to enable JMX integration in com.liferay.portal.cache.EhcachePortalCacheManager. Set this to false if the portal needs to be reloaded under WebSphere.

Env: LIFERAY_EHCACHE_PERIOD_PORTAL_PERIOD_CACHE_PERIOD_MANAGER_PERIOD_JMX_PERIOD_ENABLED

    ehcache.portal.cache.manager.jmx.enabled=true

Set this to true to allow Ehcache to use blocking caches. This improves performance significantly by locking on keys instead of the entire cache. The drawback is that threads can hang if the cache is not used properly. Make sure that all queries that return a miss also immediately populate the cache, or else other threads that are blocked on a query of that same key will continue to hang. Reference Ehcache's BlockingCache for more information. The blocking cache is no longer implemented by Ehcache's BlockingCache, but by Liferay's BlockingPortalCache for better safety and faster performance.

Blocking cache together with transactional cache performs poorly, because transactional cache affects the cache population visibility across transactions. When transactional cache is on, blocking cache most likely does nothing useful unless the transaction window time is short. When transactional cache is off, it is better to turn on blocking cache for better database access performance.

Env: LIFERAY_EHCACHE_PERIOD_BLOCKING_PERIOD_CACHE_PERIOD_ALLOWED

    ehcache.blocking.cache.allowed=false

Set the socket timeout in milliseconds.

Env: LIFERAY_EHCACHE_PERIOD_SOCKET_PERIOD_SO_PERIOD_TIMEOUT

    ehcache.socket.so.timeout=10000

Set the start port for Ehcache socket. The port number will increase by 1 until it finds an unused port.

Env: LIFERAY_EHCACHE_PERIOD_SOCKET_PERIOD_START_PERIOD_PORT

    ehcache.socket.start.port=32454

JavaScript

The need to specify two separate lists of JavaScript files for performance reasons (the "javascript.barebone.files" and "javascript.everything.files" properties) in this file is deprecated because it can be configured via OSGi using BND headers. These properties will be removed in a future release.

Set a list of JavaScript files that will be loaded automatically in /html/common/themes/top_js.jsp.

There are two lists of files specified in the properties "javascript.barebone.files" and "javascript.everything.files".

As the name suggests, the barebone list is the minimum list of JavaScript files required for most cases. The everything list includes everything else not listed in the barebone list.

The two lists of files exist for performance reasons because unauthenticated users usually do not utilize all the JavaScript that is available. See the property "javascript.barebone.enabled" for more information on the logic of when the barebone list is used and when the everything list is used and how to customize that logic.

The list of files are also merged and packed for further performance improvements. See the property "javascript.fast.load" for more details.

Specify the list of barebone files.

The ordering of the JavaScript files is important and should follow a specific format. The first grouping denotes utility scripts that are used by the second and third groups. The second grouping denotes utility classes that rely on the first group, but do not rely on the second or third group. The third grouping denotes modules that rely on the first and second group.

This configuration is deprecated because it can be configured in a modular way using the "Liferay-JS-Resources-Top-Head" header in OSGi bundles' manifest files. It will be removed from this file in a future release.

Env: LIFERAY_JAVASCRIPT_PERIOD_BAREBONE_PERIOD_FILES

    javascript.barebone.files=

Specify the list of remaining JavaScript files not already specified in the list of barebone files (i.e., "javascript.barebone.files").

This configuration is deprecated because it can be configured in a modular way using the "Liferay-JS-Resources-Top-Head-Authenticated" header in OSGi bundles' manifest files. It will be removed from this file in a future release.

Env: LIFERAY_JAVASCRIPT_PERIOD_EVERYTHING_PERIOD_FILES

    javascript.everything.files=

Set this property to false to always load JavaScript files listed under the property "Liferay-JS-Resources-Top-Head-Authenticated" of OSGi bundles' manifest files.

Set this to true to sometimes load JavaScript files listed under the property "Liferay-JS-Resources-Top-Head" and sometimes load those under "Liferay-JS-Resources-Top-Head-Authenticated".

The default logic is coded in com.liferay.portal.events.ServicePreAction in such a way that unauthenticated users get the list of "Liferay-JS-Resources-Top-Head" JavaScript files whereas authenticated users get both the list of "Liferay-JS-Resources-Top-Head" JavaScript files and the list of "Liferay-JS-Resources-Top-Head-Authenticated" JavaScript files.

Env: LIFERAY_JAVASCRIPT_PERIOD_BAREBONE_PERIOD_ENABLED

    javascript.barebone.enabled=true

Set this property to true to load the packed version of files listed in the properties "Liferay-JS-Resources-Top-Head" and/or "Liferay-JS-Resources-Top-Head-Authenticated" of OSGi bundles' manifest files.

Set this property to false for easier debugging for development. You can also disable fast loading by setting the URL parameter "js_fast_load" to "0".

Env: LIFERAY_JAVASCRIPT_PERIOD_FAST_PERIOD_LOAD

    javascript.fast.load=true

Input a list of comma delimited properties that are valid bundle IDs for the JavaScript minifier.

This mechanism is deprecated and will be removed in a future release.

Env: LIFERAY_JAVASCRIPT_PERIOD_BUNDLE_PERIOD_IDS

    javascript.bundle.ids=\
        javascript.barebone.files,\
        javascript.everything.files

Define a bundle directory for each property listed in "javascript.bundle.ids".

This mechanism is deprecated and will be removed in a future release.

Env: LIFERAY_JAVASCRIPT_PERIOD_BUNDLE_PERIOD_DIR_OPENBRACKET_JAVASCRIPT_PERIOD_BAREBONE_PERIOD_FILES_CLOSEBRACKET_ Env: LIFERAY_JAVASCRIPT_PERIOD_BUNDLE_PERIOD_DIR_OPENBRACKET_JAVASCRIPT_PERIOD_EVERYTHING_PERIOD_FILES_CLOSEBRACKET_

    javascript.bundle.dir[javascript.barebone.files]=/
    javascript.bundle.dir[javascript.everything.files]=/

Define the bundle dependencies using any property listed in "javascript.bundle.ids".

This mechanism is deprecated and will be removed in a future release.

Env: LIFERAY_JAVASCRIPT_PERIOD_BUNDLE_PERIOD_DEPENDENCIES_OPENBRACKET_JAVASCRIPT_PERIOD_EVERYTHING_PERIOD_FILES_CLOSEBRACKET_

    javascript.bundle.dependencies[javascript.everything.files]=javascript.barebone.files

Set this to true to enable the display of JavaScript logging.

Env: LIFERAY_JAVASCRIPT_PERIOD_LOG_PERIOD_ENABLED

    javascript.log.enabled=false

Set this to true to enable Single Page Application links.

Env: LIFERAY_JAVASCRIPT_PERIOD_SINGLE_PERIOD_PAGE_PERIOD_APPLICATION_PERIOD_ENABLED

    javascript.single.page.application.enabled=true

Set the timeout in milliseconds before SPA navigation times out and falls back to standard navigation.

Env: LIFERAY_JAVASCRIPT_PERIOD_SINGLE_PERIOD_PAGE_PERIOD_APPLICATION_PERIOD_TIMEOUT

    javascript.single.page.application.timeout=0

SQL Data

Set the default SQL IDs for common objects.

Env: LIFERAY_SQL_PERIOD_DATA_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEC_OUNTRY_PERIOD_COUNTRY_PERIOD_ID Env: LIFERAY_SQL_PERIOD_DATA_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_IST_UPPERCASET_YPE_PERIOD_ACCOUNT_PERIOD_ADDRESS Env: LIFERAY_SQL_PERIOD_DATA_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_IST_UPPERCASET_YPE_PERIOD_ACCOUNT_PERIOD_EMAIL_PERIOD_ADDRESS Env: LIFERAY_SQL_PERIOD_DATA_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_IST_UPPERCASET_YPE_PERIOD_CONTACT_PERIOD_EMAIL_PERIOD_ADDRESS Env: LIFERAY_SQL_PERIOD_DATA_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_IST_UPPERCASET_YPE_PERIOD_ORGANIZATION_PERIOD_STATUS Env: LIFERAY_SQL_PERIOD_DATA_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASER_EGION_PERIOD_REGION_PERIOD_ID

    sql.data.com.liferay.portal.kernel.model.Country.country.id=19
    sql.data.com.liferay.portal.kernel.model.Region.region.id=5
    sql.data.com.liferay.portal.kernel.model.ListType.account.address=10000
    sql.data.com.liferay.portal.kernel.model.ListType.account.email.address=10004
    sql.data.com.liferay.portal.kernel.model.ListType.contact.email.address=11003
    sql.data.com.liferay.portal.kernel.model.ListType.organization.status=12017

Set the maximum parameters that a SQL transaction query can contain. Some databases do not allow for more than 2000 parameters in a query.

Env: LIFERAY_SQL_PERIOD_DATA_PERIOD_MAX_PERIOD_PARAMETERS

    sql.data.max.parameters=1000

Weblogic

Set the strategy for non-serializable wrapping on Weblogic. If set to true, the wrapping is done for all objects. If set to false, no wrapping is done, but Weblogic must be configured not serializae request attributes.

Env: LIFERAY_WEBLOGIC_PERIOD_REQUEST_PERIOD_WRAP_PERIOD_NON_PERIOD_SERIALIZABLE

    weblogic.request.wrap.non.serializable=true

Company

Env: LIFERAY_COMPANY_PERIOD_DEFAULT_PERIOD_NAME

    company.default.name=Liferay

This sets the default web ID. Omniadmin users must belong to the company with this web ID.

Env: LIFERAY_COMPANY_PERIOD_DEFAULT_PERIOD_WEB_PERIOD_ID

    company.default.web.id=liferay.com

This sets the default home URL of the portal.

Env: LIFERAY_COMPANY_PERIOD_DEFAULT_PERIOD_HOME_PERIOD_URL

    company.default.home.url=/web/guest

This sets the default locale of the portal, overriding the properties "user.language" and "user.country" specified in system.properties.

Env: LIFERAY_COMPANY_PERIOD_DEFAULT_PERIOD_LOCALE

    company.default.locale=en_US

This sets the default time zone of the portal during initial setup.

To change the default time zone of an existing portal instance, use the Control Panel options.

Env: LIFERAY_COMPANY_PERIOD_DEFAULT_PERIOD_TIME_PERIOD_ZONE

    company.default.time.zone=UTC

Set this to the appropriate encryption algorithm to be used for company level encryption algorithms (except password encryption which is defined via the property "passwords.encryption.algorithm").

If you change this setting, you may need to also change the property "company.encryption.key.size" to configure the desired encryption key size.

For more details about encryption keys, see the Java Cryptography Extension documentation.

Env: LIFERAY_COMPANY_PERIOD_ENCRYPTION_PERIOD_ALGORITHM

    company.encryption.algorithm=AES

    company.encryption.algorithm=Blowfish
    company.encryption.algorithm=DES
    company.encryption.algorithm=DESede

Set this to define the size used for the company wide encryption key. If you change this setting, you may need to also change the property "company.encryption.algorithm" to ensure the algorithm supports your key size. Most encryption algorithm implementations do not support key sizes stronger than 128. Only those with unlimited strength cryptography support stronger keys.

For more details about supported key sizes for encryption keys, see the Java Cryptography Extension documentation.

Env: LIFERAY_COMPANY_PERIOD_ENCRYPTION_PERIOD_KEY_PERIOD_SIZE

    company.encryption.key.size=128

    company.encryption.key.size=56
    company.encryption.key.size=168
    company.encryption.key.size=256
    company.encryption.key.size=384
    company.encryption.key.size=512

The login field is prepopulated with the company's domain name if the login is unpopulated and user authentication is based on email addresses. Set this to false to disable the behavior.

Env: LIFERAY_COMPANY_PERIOD_LOGIN_PERIOD_PREPOPULATE_PERIOD_DOMAIN

    company.login.prepopulate.domain=true

The portal can authenticate users based on their email address, screen name, or user ID.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_AUTH_PERIOD_TYPE

    company.security.auth.type=emailAddress

    company.security.auth.type=screenName
    company.security.auth.type=userId

Set this to true to ensure users login with https. If this is set to true and you want your HTTP session to contain your credentials after logging in, then the property "session.enable.phishing.protection" must be set to false or your credentials will only be available in the HTTPS session.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_AUTH_PERIOD_REQUIRES_PERIOD_HTTPS

    company.security.auth.requires.https=false

Set this to true to allow users to select the "remember me" feature to automatically login to the portal.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_AUTO_PERIOD_LOGIN

    company.security.auto.login=true

Set this to the maximum age (in number of seconds) of the browser cookie that enables the "remember me" feature. A value of 31536000 signifies lifespan of one year. A value of -1 signifies a lifespan of a browser session.

Rather than setting this to 0, set the property "company.security.auto.login" to false to disable the "remember me" feature.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_AUTO_PERIOD_LOGIN_PERIOD_MAX_PERIOD_AGE

    company.security.auto.login.max.age=31536000

Set this to true to allow users to autocomplete the login form based on their previously entered values.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_LOGIN_PERIOD_FORM_PERIOD_AUTOCOMPLETE

    company.security.login.form.autocomplete=true

Set this to true to allow users to autocomplete the reminder query form based on their previously entered values.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_PASSWORD_PERIOD_REMINDER_PERIOD_QUERY_PERIOD_FORM_PERIOD_AUTOCOMPLETE

    company.security.password.reminder.query.form.autocomplete=true

Set this to true to allow users to ask the portal to send them a password reset link.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_SEND_PERIOD_PASSWORD_PERIOD_RESET_PERIOD_LINK

    company.security.send.password.reset.link=true

Set this to true to allow strangers to create accounts and register themselves on the portal.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_STRANGERS

    company.security.strangers=true

Enter a friendly URL of a page that will be used to create new accounts whenever the user clicks the "create account" link in the login portlet. This allows providing custom portlets to create accounts. By default, the portal's create account will be used.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_STRANGERS_PERIOD_URL

    company.security.strangers.url=/create_account

Set this to true if strangers can create accounts with email addresses that match the company mail suffix. This property is not used unless "company.security.strangers" is also set to true.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_STRANGERS_PERIOD_WITH_PERIOD_MX

    company.security.strangers.with.mx=true

Set this to true if strangers who create accounts need to be verified via email.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_STRANGERS_PERIOD_VERIFY

    company.security.strangers.verify=false

Set this to true to allow site administrators to use their own logo instead of the enterprise logo.

Env: LIFERAY_COMPANY_PERIOD_SECURITY_PERIOD_SITE_PERIOD_LOGO

    company.security.site.logo=true

Input a list of sections that will be included as part of the company authentication settings form.

Env: LIFERAY_COMPANY_PERIOD_SETTINGS_PERIOD_FORM_PERIOD_AUTHENTICATION

    company.settings.form.authentication=

Users

Set this to false if users cannot be deleted.

Env: LIFERAY_USERS_PERIOD_DELETE

    users.delete=true

Set this to true when you want the validation to allow for creation of numeric screen names.

Env: LIFERAY_USERS_PERIOD_SCREEN_PERIOD_NAME_PERIOD_ALLOW_PERIOD_NUMERIC

    users.screen.name.allow.numeric=true

Set this to true to always autogenerate user screen names even if the user gives a specific user screen name. If this is set to true, the LDAP importer will fetch users by their email address even if the property "company.security.auth.type" is set to screenName.

Env: LIFERAY_USERS_PERIOD_SCREEN_PERIOD_NAME_PERIOD_ALWAYS_PERIOD_AUTOGENERATE

    users.screen.name.always.autogenerate=false

Input a class name that implements com.liferay.portal.security.auth.ScreenNameGenerator. This class will be called to generate user screen names.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_USERS_PERIOD_SCREEN_PERIOD_NAME_PERIOD_GENERATOR

    users.screen.name.generator=com.liferay.portal.security.auth.DefaultScreenNameGenerator

Input a list of special characters that are allowed in screen names. This property is read by the default screen name validator implementation. Custom implementations need to also use this property to account for screen names with special characters.

Env: LIFERAY_USERS_PERIOD_SCREEN_PERIOD_NAME_PERIOD_SPECIAL_PERIOD_CHARACTERS

    users.screen.name.special.characters=-._

Input a class name that implements com.liferay.portal.security.auth.ScreenNameValidator. This class will be called to validate user screen names.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_USERS_PERIOD_SCREEN_PERIOD_NAME_PERIOD_VALIDATOR

    users.screen.name.validator=com.liferay.portal.security.auth.DefaultScreenNameValidator
    users.screen.name.validator=com.liferay.portal.security.auth.LiberalScreenNameValidator

Set this to false if you want to be able to create users without an email address. An email address will be automatically assigned to a user based on the property "users.email.address.auto.suffix".

Env: LIFERAY_USERS_PERIOD_EMAIL_PERIOD_ADDRESS_PERIOD_REQUIRED

    users.email.address.required=true

Set the suffix of the email address that will be automatically generated for a user that does not have an email address. This property is not used unless the property "users.email.address.required" is set to false. The autogenerated email address will be the user ID plus the specified suffix.

Env: LIFERAY_USERS_PERIOD_EMAIL_PERIOD_ADDRESS_PERIOD_AUTO_PERIOD_SUFFIX

    users.email.address.auto.suffix=@no-emailaddress.com

Input a class name that implements com.liferay.portal.security.auth.EmailAddressGenerator. This class will be called to generate an email address for a user that does not specify an email address. This class will only be used if the property "users.email.address.required" is set to false.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_USERS_PERIOD_EMAIL_PERIOD_ADDRESS_PERIOD_GENERATOR

    users.email.address.generator=com.liferay.portal.security.auth.DefaultEmailAddressGenerator

Input a class name that implements com.liferay.portal.security.auth.EmailAddressValidator. This class will be called to validate user email addresses.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_USERS_PERIOD_EMAIL_PERIOD_ADDRESS_PERIOD_VALIDATOR

    users.email.address.validator=com.liferay.portal.security.auth.DefaultEmailAddressValidator
    users.email.address.validator=com.liferay.portal.security.auth.LiberalEmailAddressValidator

Input a class name that implements com.liferay.portal.security.auth.FullNameGenerator. This class will be called to generate a full name from the user's first, middle, and last names.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_USERS_PERIOD_FULL_PERIOD_NAME_PERIOD_GENERATOR

    users.full.name.generator=com.liferay.portal.security.auth.DefaultFullNameGenerator
    users.full.name.generator=com.liferay.portal.security.auth.FamilyNameFirstFullNameGenerator

Input a class name that implements com.liferay.portal.security.auth.FullNameValidator. This class will be called to validate the user's first, middle, and last names.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_USERS_PERIOD_FULL_PERIOD_NAME_PERIOD_VALIDATOR

    users.full.name.validator=com.liferay.portal.security.auth.DefaultFullNameValidator

Set this to true to record last login information for a user.

Env: LIFERAY_USERS_PERIOD_UPDATE_PERIOD_LAST_PERIOD_LOGIN

    users.update.last.login=true

Set the allowed user list views.

Env: LIFERAY_USERS_PERIOD_LIST_PERIOD_VIEWS

    users.list.views=\
        tree,\
        flat-user-groups

Set this to true to enable reminder queries that are used to help reset a user's password.

Env: LIFERAY_USERS_PERIOD_REMINDER_PERIOD_QUERIES_PERIOD_CUSTOM_PERIOD_QUESTION_PERIOD_ENABLED Env: LIFERAY_USERS_PERIOD_REMINDER_PERIOD_QUERIES_PERIOD_ENABLED

    users.reminder.queries.enabled=true
    users.reminder.queries.custom.question.enabled=true

Set this to false to enable users without a reminder query to reset their password.

Env: LIFERAY_USERS_PERIOD_REMINDER_PERIOD_QUERIES_PERIOD_REQUIRED

    users.reminder.queries.required=false

Input a list of questions used for reminder queries.

Env: LIFERAY_USERS_PERIOD_REMINDER_PERIOD_QUERIES_PERIOD_QUESTIONS

    users.reminder.queries.questions=\
        what-is-your-primary-frequent-flyer-number,\
        what-is-your-library-card-number,\
        what-was-your-first-phone-number,\
        what-was-your-first-teacher's-name,\
        what-is-your-father's-middle-name

Set this to true to search users from the index. Set this to false to search users from the database. Note that setting this to false will disable the ability to search users based on Expando attributes. This setting is not used unless the indexer is enabled through the control panel.

Env: LIFERAY_USERS_PERIOD_SEARCH_PERIOD_WITH_PERIOD_INDEX

    users.search.with.index=true

Set a property with the prefix "users.update.user.name." and a suffix with the class name that should be updated whenever a user's name has changed.

Env: LIFERAY_USERS_PERIOD_UPDATE_PERIOD_USER_PERIOD_NAME_PERIOD_COM_PERIOD_LIFERAY_PERIOD_MESSAGE_PERIOD_BOARDS_PERIOD_MODEL_PERIOD__UPPERCASEM__UPPERCASEB__UPPERCASEM_ESSAGE

    users.update.user.name.com.liferay.message.boards.model.MBMessage=true

Input a list of user attributes that will be included when exporting users to a CSV file. You can include custom fields by adding the prefix "expando:" to the attribute name.

Env: LIFERAY_USERS_PERIOD_EXPORT_PERIOD_CSV_PERIOD_FIELDS

    users.export.csv.fields=\
        fullName,\
        emailAddress

Set the friendly URL to a user's profile page. If none is specified, the portal will query the user's first public page at runtime.

The following variables can be used: ${liferay:screenName} and ${liferay:userId}.

Env: LIFERAY_USERS_PERIOD_PROFILE_PERIOD_FRIENDLY_PERIOD_URL

    users.profile.friendly.url=/web/${liferay:screenName}/profile

Set the maximum number of organizations, roles, and user groups to display for each user in the user's administration search container.

Env: LIFERAY_USERS_PERIOD_ADMIN_PERIOD_ORGANIZATION_PERIOD_COLUMN_PERIOD_LIMIT Env: LIFERAY_USERS_PERIOD_ADMIN_PERIOD_ROLE_PERIOD_COLUMN_PERIOD_LIMIT Env: LIFERAY_USERS_PERIOD_ADMIN_PERIOD_USER_PERIOD_GROUP_PERIOD_COLUMN_PERIOD_LIMIT

    users.admin.organization.column.limit=50
    users.admin.role.column.limit=50
    users.admin.user.group.column.limit=50

Groups and Roles

Input a list of comma delimited system group names that will exist in addition to the standard system groups. When the server starts, the portal checks to ensure all system groups exist. Any missing system group will be created by the portal.

Env: LIFERAY_SYSTEM_PERIOD_GROUPS

    system.groups=

Input a list of comma delimited system role names that will exist in addition to the standard system roles. When the server starts, the portal checks to ensure all system roles exist. Any missing system role will be created by the portal.

The standard system roles are: Administrator, Guest, Power User, and User. These roles cannot be removed or renamed.

Env: LIFERAY_SYSTEM_PERIOD_ROLES

    system.roles=

Set the description of the Administrator system role.

Env: LIFERAY_SYSTEM_PERIOD_ROLE_PERIOD__UPPERCASEA_DMINISTRATOR_PERIOD_DESCRIPTION

    system.role.Administrator.description=Administrators are super users who can do anything.

Set the description of the Analytics Administrator system role.

Env: LIFERAY_SYSTEM_PERIOD_ROLE_PERIOD__UPPERCASEA_NALYTICS_PERIOD__UPPERCASEA_DMINISTRATOR_PERIOD_DESCRIPTION

    system.role.Analytics.Administrator.description=Analytics Administrators are users who can view data across the company but cannot make changes except to the company preferences.

Set the description of the Guest system role.

Env: LIFERAY_SYSTEM_PERIOD_ROLE_PERIOD__UPPERCASEG_UEST_PERIOD_DESCRIPTION

    system.role.Guest.description=Unauthenticated users always have this role.

Set the description of the Owner system role.

Env: LIFERAY_SYSTEM_PERIOD_ROLE_PERIOD__UPPERCASEO_WNER_PERIOD_DESCRIPTION

    system.role.Owner.description=This is an implied role with respect to the objects users create.

Set the description of the Power User system role.

Env: LIFERAY_SYSTEM_PERIOD_ROLE_PERIOD__UPPERCASEP_OWER_PERIOD__UPPERCASEU_SER_PERIOD_DESCRIPTION

    system.role.Power.User.description=Power Users have their own personal site.

Set the description of the User system role.

Env: LIFERAY_SYSTEM_PERIOD_ROLE_PERIOD__UPPERCASEU_SER_PERIOD_DESCRIPTION

    system.role.User.description=Authenticated users should be assigned this role.

Input a list of comma delimited system organization role names that will exist in addition to the standard system organization roles. When the server starts, the portal checks to ensure all system organization roles exist. Any missing system organization role will be created by the portal.

The standard system organization roles are: Organization Administrator, Organization Member, and Organization Owner. These roles cannot be removed or renamed.

Env: LIFERAY_SYSTEM_PERIOD_ORGANIZATION_PERIOD_ROLES

    system.organization.roles=

Set the description of the Organization Administrator system organization role.

Env: LIFERAY_SYSTEM_PERIOD_ORGANIZATION_PERIOD_ROLE_PERIOD__UPPERCASEO_RGANIZATION_PERIOD__UPPERCASEA_DMINISTRATOR_PERIOD_DESCRIPTION

    system.organization.role.Organization.Administrator.description=Organization Administrators are super users of their organization but cannot make other users into Organization Administrators.

Set the description of the Organization Member system organization role.

Env: LIFERAY_SYSTEM_PERIOD_ORGANIZATION_PERIOD_ROLE_PERIOD__UPPERCASEO_RGANIZATION_PERIOD__UPPERCASEU_SER_PERIOD_DESCRIPTION

    system.organization.role.Organization.User.description=All users who belong to an organization have this role within that organization.

Set the description of the Organization Owner system organization role.

Env: LIFERAY_SYSTEM_PERIOD_ORGANIZATION_PERIOD_ROLE_PERIOD__UPPERCASEO_RGANIZATION_PERIOD__UPPERCASEO_WNER_PERIOD_DESCRIPTION

    system.organization.role.Organization.Owner.description=Organization Owners are super users of their organization and can assign organization roles to users.

Input a list of comma delimited system site role names that will exist in addition to the standard system site roles. When the server starts, the portal checks to ensure all system site roles exist. Any missing system site role will be created by the portal.

The standard system site roles are: Site Administrator, Site Member, and Site Owner. These roles cannot be removed or renamed.

Env: LIFERAY_SYSTEM_PERIOD_SITE_PERIOD_ROLES

    system.site.roles=

Set the description of the Site Administrator system site role.

Env: LIFERAY_SYSTEM_PERIOD_SITE_PERIOD_ROLE_PERIOD__UPPERCASES_ITE_PERIOD__UPPERCASEA_DMINISTRATOR_PERIOD_DESCRIPTION

    system.site.role.Site.Administrator.description=Site Administrators are super users of their site but cannot make other users into Site Administrators.

Set the description of the Site Member system site role.

Env: LIFERAY_SYSTEM_PERIOD_SITE_PERIOD_ROLE_PERIOD__UPPERCASES_ITE_PERIOD__UPPERCASEM_EMBER_PERIOD_DESCRIPTION

    system.site.role.Site.Member.description=All users who belong to a site have this role within that site.

Set the description of the Site Owner system site role.

Env: LIFERAY_SYSTEM_PERIOD_SITE_PERIOD_ROLE_PERIOD__UPPERCASES_ITE_PERIOD__UPPERCASEO_WNER_PERIOD_DESCRIPTION

    system.site.role.Site.Owner.description=Site Owners are super users of their site and can assign site roles to users.

Omniadmin users can administer the portal's core functionality: gc, shutdown, etc. Omniadmin users must belong to the default company.

Multiple portal instances might be deployed on one application server, but not all of the administrators should have access to this core functionality. Input the IDs of users who are omniadmin users.

Leave this field blank if users who belong to the right company and have the Administrator role are allowed to administer the portal's core functionality.

Env: LIFERAY_OMNIADMIN_PERIOD_USERS

    omniadmin.users=

Set this to true if all users are required to agree to the terms of use.

Env: LIFERAY_TERMS_PERIOD_OF_PERIOD_USE_PERIOD_REQUIRED

    terms.of.use.required=true

Input a list of group class names that will trigger a complex SQL query to delegate filtering in the database tier. A group class name corresponds to the className column in the Group_ table. Filtering in memory at the application tier after a simple SQL query can be much better on performance.

Env: LIFERAY_GROUPS_PERIOD_COMPLEX_PERIOD_SQL_PERIOD_CLASS_PERIOD_NAMES

    groups.complex.sql.class.names=com.liferay.portal.kernel.model.User

Specify subtypes of roles if you want to be able to search for roles using your custom criteria.

Env: LIFERAY_ROLES_PERIOD_ORGANIZATION_PERIOD_SUBTYPES Env: LIFERAY_ROLES_PERIOD_REGULAR_PERIOD_SUBTYPES Env: LIFERAY_ROLES_PERIOD_SITE_PERIOD_SUBTYPES

    roles.site.subtypes=
    roles.organization.subtypes=
    roles.regular.subtypes=

Set this to true when you want the validation to allow for creation of roles with numeric names.

Env: LIFERAY_ROLES_PERIOD_NAME_PERIOD_ALLOW_PERIOD_NUMERIC

    roles.name.allow.numeric=false

Organizations

Set this property to false if you want any administrator of an organization to be able to assign any user to that organization. By default, he will only be able to assign the users of the organizations and suborganizations that he can manage.

Env: LIFERAY_ORGANIZATIONS_PERIOD_ASSIGNMENT_PERIOD_STRICT

    organizations.assignment.strict=true

Set this property to true if you want users to only be members of the organizations to which they are assigned explicitly. By default, they will also become implicit members of the ancestors of those organizations. For example, if a user belongs to Liferay Spain, he will implicitly be a member of the ancestors Liferay Europe and Liferay Global and will be able to access their private pages.

Env: LIFERAY_ORGANIZATIONS_PERIOD_MEMBERSHIP_PERIOD_STRICT

    organizations.membership.strict=false

Set this to true to search organizations from the index. Set this to false to search organizations from the database. Note that setting this to false will disable the ability to search organizations based on Expando attributes. This setting is not used unless the indexer is enabled through the control panel.

Env: LIFERAY_ORGANIZATIONS_PERIOD_SEARCH_PERIOD_WITH_PERIOD_INDEX

    organizations.search.with.index=true

User Groups

Set this to true when you want the validation to allow for creation of user groups with numeric names.

Env: LIFERAY_USER_PERIOD_GROUPS_PERIOD_NAME_PERIOD_ALLOW_PERIOD_NUMERIC

    user.groups.name.allow.numeric=false

Set this to true to search user groups from the index. Set this to false to search user groups from the database. Note that setting this to false will disable the ability to search user groups based on Expando attributes. This setting is not used unless the indexer is enabled through the control panel.

Env: LIFERAY_USER_PERIOD_GROUPS_PERIOD_SEARCH_PERIOD_WITH_PERIOD_INDEX

    user.groups.search.with.index=true

Membership Policies

Set this to true to verify membership policies every time the server starts or when a membership policy hook is deployed.

Env: LIFERAY_MEMBERSHIP_PERIOD_POLICY_PERIOD_AUTO_PERIOD_VERIFY

    membership.policy.auto.verify=false

Input a class name that implements com.liferay.portal.security.membershippolicy.OrganizationMembershipPolicy. This class will be called whenever a user is added or removed from an organization or when a user is assigned or unassigned to a organization role or when a new organization is added or updated.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_MEMBERSHIP_PERIOD_POLICY_PERIOD_ORGANIZATIONS

    membership.policy.organizations=com.liferay.portal.security.membershippolicy.DummyOrganizationMembershipPolicy

Input a class name that implements com.liferay.portal.security.membershippolicy.RoleMembershipPolicy. This class will be called whenever a user is assign or unassigned from a regular role or when a new role is added or updated.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_MEMBERSHIP_PERIOD_POLICY_PERIOD_ROLES

    membership.policy.roles=com.liferay.portal.security.membershippolicy.DummyRoleMembershipPolicy

Input a class name that implements com.liferay.portal.security.membershippolicy.SiteMembershipPolicy. This class will be called whenever a user is added or removed from a site or when a user is assigned or unassigned to a site role or a new site is added or updated.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_MEMBERSHIP_PERIOD_POLICY_PERIOD_SITES

    membership.policy.sites=com.liferay.portal.security.membershippolicy.DummySiteMembershipPolicy
    membership.policy.sites=com.liferay.portal.security.membershippolicy.DefaultSiteMembershipPolicy

Input a class name that implements com.liferay.portal.security.membershippolicy.UserGroupsMembershipPolicy. This class will be called whenever a user is added or removed from a user group or a new user group is added or updated.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_MEMBERSHIP_PERIOD_POLICY_PERIOD_USER_PERIOD_GROUPS

    membership.policy.user.groups=com.liferay.portal.security.membershippolicy.DummyUserGroupMembershipPolicy

Languages and Time Zones

Specify the available locales. Messages corresponding to a specific language are specified in properties files with file names matching that of content/Language_*.properties. These values can also be overridden in properties files with file names matching that of content/Language-ext_*.properties. Use a comma to separate each entry.

If there is more than one locale for the same language, the first one in the list will be used when a translation is requested in another locale of the same language but a translated value cannot be found. For example, if there are two locales such us pt_BR and pt_PT (in this order), any key not found in pt_PT will be looked for in pt_BR.

Language codes follow the ISO 639-1 standard. Content for each locale must be UTF-8 encoded.

See the following links, which specify language and country codes:

     http://www.loc.gov/standards/iso639-2/php/code_list.php
     http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html

Env: LIFERAY_LOCALES

    locales=\
        ar_SA,\
        eu_ES,\
        bg_BG,\
        ca_AD,\
        ca_ES,\
        zh_CN,\
        zh_TW,\
        hr_HR,\
        cs_CZ,\
        da_DK,\
        nl_NL,\
        nl_BE,\
        en_US,\
        en_GB,\
        en_AU,\
        et_EE,\
        fi_FI,\
        fr_FR,\
        fr_CA,\
        gl_ES,\
        de_DE,\
        el_GR,\
        iw_IL,\
        hi_IN,\
        hu_HU,\
        in_ID,\
        it_IT,\
        ja_JP,\
        kk_KZ,\
        ko_KR,\
        lo_LA,\
        lt_LT,\
        nb_NO,\
        fa_IR,\
        pl_PL,\
        pt_BR,\
        pt_PT,\
        ro_RO,\
        ru_RU,\
        sr_RS,\
        sr_RS_latin,\
        sl_SI,\
        sk_SK,\
        es_ES,\
        sv_SE,\
        ta_IN,\
        th_TH,\
        tr_TR,\
        uk_UA,\
        vi_VN

Specify the locales that are in beta. Go to http://translate.liferay.com to participate in the translation efforts.

Env: LIFERAY_LOCALES_PERIOD_BETA

    locales.beta=\
        eu_ES,\
        bg_BG,\
        ca_AD,\
        zh_TW,\
        hr_HR,\
        cs_CZ,\
        da_DK,\
        nl_BE,\
        en_GB,\
        en_AU,\
        et_EE,\
        gl_ES,\
        el_GR,\
        iw_IL,\
        hi_IN,\
        in_ID,\
        it_IT,\
        kk_KZ,\
        ko_KR,\
        lo_LA,\
        lt_LT,\
        nb_NO,\
        fa_IR,\
        pl_PL,\
        pt_PT,\
        ro_RO,\
        ru_RU,\
        sr_RS,\
        sr_RS_latin,\
        sl_SI,\
        sk_SK,\
        ta_IN,\
        tr_TR,\
        uk_UA,\
        vi_VN

Specify the locales that are enabled by default.

Env: LIFERAY_LOCALES_PERIOD_ENABLED

    locales.enabled=\
        ar_SA,\
        ca_ES,\
        zh_CN,\
        nl_NL,\
        en_US,\
        fi_FI,\
        fr_FR,\
        de_DE,\
        hu_HU,\
        ja_JP,\
        pt_BR,\
        es_ES,\
        sv_SE

Specify the collator rules to be used by the CollatorUtil. These rules, if set, are provided to a RulesBasedCollator for text sorting and are only configurable by locale. A file can also be used by prefixing "file\:" to a path on the file system. Using a file means property escaping can be avoided.

See https://issues.liferay.com/browse/LPS-73600 for more information.

Env: LIFERAY_COLLATOR_PERIOD_RULES_OPENBRACKET_EN_UNDERLINE__UPPERCASEU__UPPERCASES__CLOSEBRACKET_

    collator.rules[en_US]=

Set this to true if unauthenticated users get their preferred language from the Accept-Language header. Set this to false if unauthenticated users get their preferred language from their company.

Env: LIFERAY_LOCALE_PERIOD_DEFAULT_PERIOD_REQUEST

    locale.default.request=false

Set this to 0 if the locale is not automatically prepended to a URL. This means that each URL could potentially point to many different languages. For example, the URL http://localhost:8080/web/guest/home could then be viewed by users in many different languages.

Set this to 1 if the locale is automatically prepended to a URL when the requested locale is not the default locale. This means that each URL points to just one language. For example, the URL http://localhost:8080/web/guest/home would point to the default language. The URL http://localhost:8080/zh/web/guest/home and http://localhost:8080/zh_CN/web/guest/home would both point to the Chinese language.

In cases where the prepended locale is "zh" and not the complete locale "zh_CN", then the full locale returned will be based on the order in which the locales appear in the property "locales". If "zh_CN" appears before "zh_TW", then "zh" will be a short hand for "zh_TW".

The default language is set in system.properties with the properties "user.country" and "user.language".

Set this to 2 if the locale is automatically prepended to every URL. This means that each URL points to just one language.

Set this to 3 if the locale is automatically prepended to a URL when the requested locale is not the default user locale. In the case of guest users, the behavior is the same as having a value of 1.

Note that each language requires an entry in the property "locales" and a servlet mapping in web.xml for the I18n Servlet.

Env: LIFERAY_LOCALE_PERIOD_PREPEND_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_STYLE

    locale.prepend.friendly.url.style=3

Set this to false to return an HTTP 404 status code and page if the requested URL includes a locale that is not available among the locales set in the "locales" and "locales.beta" properties.

For example, if Spanish is not one of the available locales and http://localhost:8080/es/web/guest is requested, then a 404 error code and page is returned.

This can improve SEO since it avoids duplicated pages, if in the installation, there are a set of definded locales available.

Env: LIFERAY_LOCALE_PERIOD_USE_PERIOD_DEFAULT_PERIOD_IF_PERIOD_NOT_PERIOD_AVAILABLE

    locale.use.default.if.not.available=false

Set this to true to disable language translations. When a translation is requested for the key "first-name", instead of returning "First Name" in English (or in its relevant locale), it will return "first-name".

Env: LIFERAY_TRANSLATIONS_PERIOD_DISABLED

    translations.disabled=false

Specify the available time zones. The specified IDs must match those from the class java.util.TimeZone.

Env: LIFERAY_TIME_PERIOD_ZONES

    time.zones=\
        Pacific/Midway,\
        Pacific/Honolulu,\
        America/Anchorage,\
        America/Los_Angeles,\
        America/Phoenix,\
        America/Denver,\
        America/Chicago,\
        America/New_York,\
        America/Caracas,\
        America/Puerto_Rico,\
        America/St_Johns,\
        America/Sao_Paulo,\
        America/Noronha,\
        Atlantic/Azores,\
        UTC,\
        Europe/Lisbon,\
        Europe/Paris,\
        Europe/Istanbul,\
        Asia/Jerusalem,\
        Asia/Baghdad,\
        Asia/Tehran,\
        Asia/Dubai,\
        Asia/Kabul,\
        Asia/Karachi,\
        Asia/Calcutta,\
        Asia/Katmandu,\
        Asia/Dhaka,\
        Asia/Rangoon,\
        Asia/Saigon,\
        Asia/Shanghai,\
        Asia/Tokyo,\
        Asia/Seoul,\
        Australia/Perth,\
        Australia/Eucla,\
        Australia/Darwin,\
        Australia/Sydney,\
        Australia/Lord_Howe,\
        Pacific/Guadalcanal,\
        Pacific/Auckland,\
        Pacific/Enderbury,\
        Pacific/Kiritimati

Specify the normalizer form to be used to normalize unicode text. Values accepted include NFC, NFD, NFKC, NFKD. A blank value will not normalize the text.

Env: LIFERAY_UNICODE_PERIOD_TEXT_PERIOD_NORMALIZER_PERIOD_FORM

    unicode.text.normalizer.form=

Look and Feel

Set this to false if the system does not allow users to modify the look and feel.

Env: LIFERAY_LOOK_PERIOD_AND_PERIOD_FEEL_PERIOD_MODIFIABLE

    look.and.feel.modifiable=true

Set the default layout template ID.

Env: LIFERAY_DEFAULT_PERIOD_LAYOUT_PERIOD_TEMPLATE_PERIOD_ID

    default.layout.template.id=2_columns_ii

Set the default portlet decorator CSS class.

Env: LIFERAY_DEFAULT_PERIOD_PORTLET_PERIOD_DECORATOR_PERIOD_CSS_PERIOD_CLASS

    default.portlet.decorator.css.class=decorate

Set the default portlet decorator ID.

Env: LIFERAY_DEFAULT_PERIOD_PORTLET_PERIOD_DECORATOR_PERIOD_ID

    default.portlet.decorator.id=decorate

Set the default theme ID for regular themes.

Env: LIFERAY_DEFAULT_PERIOD_REGULAR_PERIOD_THEME_PERIOD_ID

    default.regular.theme.id=classic_WAR_classictheme

Set the default color scheme ID for regular themes.

Env: LIFERAY_DEFAULT_PERIOD_REGULAR_PERIOD_COLOR_PERIOD_SCHEME_PERIOD_ID

    default.regular.color.scheme.id=01

Set this to true if you want a change in the theme selection of the public or private group to automatically be applied to the other (i.e. if public and private group themes should always be the same).

Env: LIFERAY_THEME_PERIOD_SYNC_PERIOD_ON_PERIOD_GROUP

    theme.sync.on.group=false

Request

Portlets that have been configured to use private request attributes in liferay-portlet.xml may still want to share some request attributes. This property allows you to configure which request attributes will be shared. Set a comma delimited list of attribute names that will be shared when the attribute name starts with one of the specified attribute names. For example, if you set the value to "hello_,world_", then all attribute names that start with "hello_" or "world_" will be shared.

Env: LIFERAY_REQUEST_PERIOD_SHARED_PERIOD_ATTRIBUTES

    request.shared.attributes=LIFERAY_SHARED_

Set a comma delimited list of Java packages that have to be unwrapped by servlet requests managing. See LPS-67793 for more information.

Env: LIFERAY_REQUEST_PERIOD_UNWRAP_PERIOD_PACKAGES

    request.unwrap.packages=\
        com.liferay.,\
        com.ibm.ws.cache.servlet.

Session

Set the maximum number of key value pairs that can be stored in the session via SessionClicks. See LPS-20096 for more information.

Env: LIFERAY_SESSION_PERIOD_CLICKS_PERIOD_MAX_PERIOD_ALLOWED_PERIOD_VALUES

    session.clicks.max.allowed.values=1024

Set the maximum size of key and value terms that can be stored in the session via SessionClicks. See LPS-20096 for more information.

Env: LIFERAY_SESSION_PERIOD_CLICKS_PERIOD_MAX_PERIOD_SIZE_PERIOD_TERMS

    session.clicks.max.size.terms=1024

Specify the delimiter for parsing compound session IDs.

This addresses an issue with Weblogic and all application servers where the application server appends a unique JVM code to the session ID. See LPS-18587.

Set a blank delimiter for the portal to attempt to detect a delimiter based on the application server.

Env: LIFERAY_SESSION_PERIOD_ID_PERIOD_DELIMITER Env: LIFERAY_SESSION_PERIOD_ID_PERIOD_WEBLOGIC_PERIOD_DELIMITER

    session.id.delimiter=
    session.id.weblogic.delimiter=!

Specify the maximum number of sessions allowed. A value of 0 or less than 0 means there is no limit. A value greater than 0 limits the number of sessions by invalidating newer sessions.

This property is not used unless the session max allowed filter is enabled.

Env: LIFERAY_SESSION_PERIOD_MAX_PERIOD_ALLOWED

    session.max.allowed=0

Specify the number of minutes before a session expires. This value is always overridden by the value set in web.xml.

Env: LIFERAY_SESSION_PERIOD_TIMEOUT

    session.timeout=15

Specify the number of minutes before a warning is sent to the user informing the user of the session expiration. Specify 0 to disable any warnings.

Env: LIFERAY_SESSION_PERIOD_TIMEOUT_PERIOD_WARNING

    session.timeout.warning=1

Set the auto-extend mode to true to avoid having to ask the user whether to extend the session or not. Instead, it will be automatically extended. The purpose of this mode is to keep the session open as long as the user's browser is open with a portal page loaded. It is recommended to use this setting along with a smaller "session.timeout", such as 5 minutes, for better performance.

Env: LIFERAY_SESSION_PERIOD_TIMEOUT_PERIOD_AUTO_PERIOD_EXTEND

    session.timeout.auto.extend=false

When the property "session.timeout.auto.extend" is set to true, set the number of seconds between when the extend process is launched and the actual expiration of the session.

Env: LIFERAY_SESSION_PERIOD_TIMEOUT_PERIOD_AUTO_PERIOD_EXTEND_PERIOD_OFFSET

    session.timeout.auto.extend.offset=10

Set this to true if the user is redirected to the default page when the session expires.

Env: LIFERAY_SESSION_PERIOD_TIMEOUT_PERIOD_REDIRECT_PERIOD_ON_PERIOD_EXPIRE

    session.timeout.redirect.on.expire=false

Portlets that have been configured to use private session attributes in liferay-portlet.xml may still want to share some session attributes. This property allows you to configure which session attributes will be shared. Set a comma delimited list of attribute names that will be shared when the attribute name starts with one of the specified attribute names. For example, if you set the value to "hello_,world_", then all attribute names that start with "hello_" or "world_" will be shared.

Note that this property is used to specify the sharing of session attributes from the portal to the portlet. This is not used to specify session sharing between portlet WARs or from the portlet to the portal.

Env: LIFERAY_SESSION_PERIOD_SHARED_PERIOD_ATTRIBUTES

    session.shared.attributes=\
        COMPANY_,\
        LIFERAY_SHARED_,\
        PORTLET_RENDER_PARAMETERS_,\
        PUBLIC_RENDER_PARAMETERS_POOL_,\
        USER_

Explicitly exclude attributes that are shared from the portal to portlets.

Env: LIFERAY_SESSION_PERIOD_SHARED_PERIOD_ATTRIBUTES_PERIOD_EXCLUDES

    session.shared.attributes.excludes=USER_PASSWORD

Set this to true to store the user's password in the session.

Env: LIFERAY_SESSION_PERIOD_STORE_PERIOD_PASSWORD

    session.store.password=false

Set this to false to disable all persistent cookies. Features like automatically logging in will not work.

Env: LIFERAY_SESSION_PERIOD_ENABLE_PERIOD_PERSISTENT_PERIOD_COOKIES

    session.enable.persistent.cookies=true

Set this to true to enable sessions when cookies are disabled. See LEP-4787. This behavior is configurable because enabling it can break certain setups.

Env: LIFERAY_SESSION_PERIOD_ENABLE_PERIOD_URL_PERIOD_WITH_PERIOD_SESSION_PERIOD_ID

    session.enable.url.with.session.id=false

The login process sets several cookies if persistent cookies are enabled. Set this property to set the domain of those cookies.

Env: LIFERAY_SESSION_PERIOD_COOKIE_PERIOD_DOMAIN

    session.cookie.domain=

Set this to true to use the full hostname for cookie domain values. By default the domain is trimmed to use only the root domain to allow cross domain logins.

Env: LIFERAY_SESSION_PERIOD_COOKIE_PERIOD_USE_PERIOD_FULL_PERIOD_HOSTNAME Env: LIFERAY_SESSION_PERIOD_COOKIE_PERIOD_USE_PERIOD_FULL_PERIOD_HOSTNAME_OPENBRACKET_TOMCAT_CLOSEBRACKET_

    session.cookie.use.full.hostname=false
    session.cookie.use.full.hostname[tomcat]=true

Set this to true to invalidate the session when a user logs into the portal. This helps prevent phishing. Set this to false if you need the guest user and the authenticated user to have the same session.

Set this to false if the property "company.security.auth.requires.https" is set to true and you want to maintain the same credentials across HTTP and HTTPS sessions.

Env: LIFERAY_SESSION_PERIOD_ENABLE_PERIOD_PHISHING_PERIOD_PROTECTION

    session.enable.phishing.protection=true

Set a comma delimited list of attribute names that will be copied to the new session when the property "session.enable.phishing.protection" is set to true.

Env: LIFERAY_SESSION_PERIOD_PHISHING_PERIOD_PROTECTED_PERIOD_ATTRIBUTES

    session.phishing.protected.attributes=\
        CAS_LOGIN,\
        HTTPS_INITIAL,\
        LAST_PATH,\
        OPEN_ID_CONNECT_SESSION,\
        SETUP_WIZARD_PASSWORD_UPDATED

Set this to true to test whether users have cookie support before allowing them to sign in.

Env: LIFERAY_SESSION_PERIOD_TEST_PERIOD_COOKIE_PERIOD_SUPPORT

    session.test.cookie.support=true

Set this to true to allow com.liferay.portal.kernel.servlet.SerializableSessionAttributeListener to test if an added session variable is serializable. Unserializable values stored into the session will cause a session to not replicate if session replication was enabled by the application server.

Env: LIFERAY_SESSION_PERIOD_VERIFY_PERIOD_SERIALIZABLE_PERIOD_ATTRIBUTE

    session.verify.serializable.attribute=true

Set this to true to disable sessions. Doing this will use cookies to remember the user across requests. This is useful if you want to scale very large sites where the user may be sent to a different server for each request. The drawback to this approach is that you must not rely on the API for sessions provided by the servlet and portlet specs.

This feature is only available for Tomcat and requires that you set Tomcat's Manager class to "com.liferay.support.tomcat.session.SessionLessManagerBase".

Setting this to true will forcibly set "layout.ajax.render.enable" to false since ajax rendering requires sessions to be enabled.

Env: LIFERAY_SESSION_PERIOD_DISABLED

    session.disabled=false

Input a list of comma delimited class names that extend com.liferay.portal.struts.SessionAction. These classes will run at the specified event.

Servlet Session Create Event

Env: LIFERAY_SERVLET_PERIOD_SESSION_PERIOD_CREATE_PERIOD_EVENTS

    servlet.session.create.events=com.liferay.portal.events.SessionCreateAction

Servlet Session Destroy Event

Env: LIFERAY_SERVLET_PERIOD_SESSION_PERIOD_DESTROY_PERIOD_EVENTS

    servlet.session.destroy.events=\
        com.liferay.portal.events.SessionDestroyAction,\
        com.liferay.portal.events.ChannelSessionDestroyAction

Set this to true to track user clicks in memory for the duration of a user's session. Setting this to true allows you to view all live sessions in the Admin portlet.

This property is deprecated and will be removed in a future release.

Env: LIFERAY_SESSION_PERIOD_TRACKER_PERIOD_MEMORY_PERIOD_ENABLED

    session.tracker.memory.enabled=true

Set this to true to track user clicks in the database after a user's session is invalidated. Setting this to true allows you to generate usage reports from the database. Use this cautiously because this will store a lot of usage data.

This property is deprecated and will be removed in a future release.

Env: LIFERAY_SESSION_PERIOD_TRACKER_PERIOD_PERSISTENCE_PERIOD_ENABLED

    session.tracker.persistence.enabled=false

Set this to true to convert the tracked paths to friendly URLs.

This property is deprecated and will be removed in a future release.

Env: LIFERAY_SESSION_PERIOD_TRACKER_PERIOD_FRIENDLY_PERIOD_PATHS_PERIOD_ENABLED

    session.tracker.friendly.paths.enabled=false

Enter a list of comma delimited paths that should not be tracked.

This property is deprecated and will be removed in a future release.

Env: LIFERAY_SESSION_PERIOD_TRACKER_PERIOD_IGNORE_PERIOD_PATHS

    session.tracker.ignore.paths=\
        /portal/render_portlet,\
        \
        /document_library/get_file

JAAS

Set this to false to disable JAAS security checks. Disabling JAAS speeds up login. JAAS must be disabled if administrators are to be able to impersonate other users.

Env: LIFERAY_PORTAL_PERIOD_JAAS_PERIOD_ENABLE

    portal.jaas.enable=false

JAAS can authenticate users based on their email address, screen name, user ID, or login as determined by the property "company.security.auth.type".

Env: LIFERAY_PORTAL_PERIOD_JAAS_PERIOD_AUTH_PERIOD_TYPE

    portal.jaas.auth.type=userId

    portal.jaas.auth.type=emailAddress
    portal.jaas.auth.type=screenName
    portal.jaas.auth.type=login

By default, com.liferay.portal.security.jaas.PortalLoginModule loads the correct JAAS login module based on what application server or servlet container the portal is deployed on. Set a JAAS implementation class to override this behavior.

Env: LIFERAY_PORTAL_PERIOD_JAAS_PERIOD_IMPL

    portal.jaas.impl=

Some JAAS login modules only work with a plain text password. Set this property to true to pass plain text passwords to JAAS.

Env: LIFERAY_PORTAL_PERIOD_JAAS_PERIOD_PLAIN_PERIOD_PASSWORD

    portal.jaas.plain.password=false

The JAAS process may pass in an encrypted password and the authentication will only succeed if there is an exact match. Set this property to false to relax that behavior so the user can input an unencrypted password.

Env: LIFERAY_PORTAL_PERIOD_JAAS_PERIOD_STRICT_PERIOD_PASSWORD

    portal.jaas.strict.password=false

Set this to true to enable administrators to impersonate other users.

Env: LIFERAY_PORTAL_PERIOD_IMPERSONATION_PERIOD_ENABLE

    portal.impersonation.enable=true

This sets the default impersonation URL of the portal. This property is not used if the company has a home URL set.

Env: LIFERAY_PORTAL_PERIOD_IMPERSONATION_PERIOD_DEFAULT_PERIOD_URL

    portal.impersonation.default.url=/web/guest

JNDI

Set the configuration values for the JNDI context. Any property prefixed with "jndi.environment." will be passed to the JNDI context as an environment variable. The valid values are those specified in javax.naming.Context.

Env: LIFERAY_JNDI_PERIOD_ENVIRONMENT_PERIOD_JAVA_PERIOD_NAMING_PERIOD_SECURITY_PERIOD_CREDENTIALS Env: LIFERAY_JNDI_PERIOD_ENVIRONMENT_PERIOD_JAVA_PERIOD_NAMING_PERIOD_SECURITY_PERIOD_PRINCIPAL

    jndi.environment.java.naming.security.credentials=
    jndi.environment.java.naming.security.principal=

LDAP

You can write your own class that implements com.liferay.portal.security.ldap.AttributesTransformer to transform the LDAP attributes before a user or group is imported to the LDAP store.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_LDAP_PERIOD_ATTRS_PERIOD_TRANSFORMER_PERIOD_IMPL

    ldap.attrs.transformer.impl=com.liferay.portal.security.ldap.DefaultAttributesTransformer

Basic Authentication

Set this to true to require a password when using basic authentication. Only set this to false if additional security measures are in place to ensure users have been properly authenticated.

Env: LIFERAY_BASIC_PERIOD_AUTH_PERIOD_PASSWORD_PERIOD_REQUIRED

    basic.auth.password.required=true

NTLM

See http://jcifs.samba.org/src/docs/ntlmhttpauth.html for more available properties.

Env: LIFERAY_JCIFS_PERIOD_NETBIOS_PERIOD_CACHE_UPPERCASEP_OLICY Env: LIFERAY_JCIFS_PERIOD_SMB_PERIOD_CLIENT_PERIOD_SO_UPPERCASET_IMEOUT

    jcifs.netbios.cachePolicy=30
    jcifs.smb.client.soTimeout=35000

OpenID

Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_PROVIDERS

    open.id.providers=yahoo

Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_AX_PERIOD_SCHEMA_OPENBRACKET_DEFAULT_CLOSEBRACKET_ Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_AX_PERIOD_TYPE_PERIOD_EMAIL_OPENBRACKET_DEFAULT_CLOSEBRACKET_ Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_AX_PERIOD_TYPE_PERIOD_FIRSTNAME_OPENBRACKET_DEFAULT_CLOSEBRACKET_ Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_AX_PERIOD_TYPE_PERIOD_LASTNAME_OPENBRACKET_DEFAULT_CLOSEBRACKET_

    open.id.ax.schema[default]=email,firstname,lastname
    open.id.ax.type.email[default]=http://schema.openid.net/contact/email
    open.id.ax.type.firstname[default]=http://schema.openid.net/namePerson/first
    open.id.ax.type.lastname[default]=http://schema.openid.net/namePerson/last

Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_AX_PERIOD_SCHEMA_OPENBRACKET_YAHOO_CLOSEBRACKET_ Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_AX_PERIOD_TYPE_PERIOD_EMAIL_OPENBRACKET_YAHOO_CLOSEBRACKET_ Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_AX_PERIOD_TYPE_PERIOD_FULLNAME_OPENBRACKET_YAHOO_CLOSEBRACKET_ Env: LIFERAY_OPEN_PERIOD_ID_PERIOD_URL_OPENBRACKET_YAHOO_CLOSEBRACKET_

    open.id.ax.schema[yahoo]=email,fullname
    open.id.ax.type.email[yahoo]=http://axschema.org/contact/email
    open.id.ax.type.fullname[yahoo]=http://axschema.org/namePerson
    open.id.url[yahoo]=open.login.yahooapis.com

Request Header

Set this to true to automatically import users from LDAP if they do not exist in the portal. The property "auto.login.hooks" must contain a reference to the class com.liferay.portal.security.auto.login.request.header.RequestHeaderAutoLogin to enable request header authentication.

Env: LIFERAY_REQUEST_PERIOD_HEADER_PERIOD_AUTH_PERIOD_IMPORT_PERIOD_FROM_PERIOD_LDAP

    request.header.auth.import.from.ldap=false

Input a list of comma delimited IPs that can automatically authenticate via request headers. Input a blank list to allow any IP to automatically authenticate via request headers. SERVER_IP will be replaced with the IP of the host server.

Env: LIFERAY_REQUEST_PERIOD_HEADER_PERIOD_AUTH_PERIOD_HOSTS_PERIOD_ALLOWED

    request.header.auth.hosts.allowed=

Input a list of comma delimited init parameters that should never be set in the request header by the header filter.

Env: LIFERAY_REQUEST_PERIOD_HEADER_PERIOD_IGNORE_PERIOD_INIT_PERIOD_PARAMS

    request.header.ignore.init.params=\
        url-regex-ignore-pattern,\
        url-regex-pattern

Authenticated User UUID Store

Set this to true to enable user UUID store. User UUID store is deprecated and will be removed in a future release.

Env: LIFERAY_AUTH_PERIOD_USER_PERIOD_UUID_PERIOD_STORE_PERIOD_ENABLED

    auth.user.uuid.store.enabled=false

Authentication Pipeline

Input a list of comma delimited class names that implement com.liferay.portal.security.auth.Authenticator. These classes will run before or after the portal authentication begins.

The Authenticator class defines the constant values that should be used as return codes from the classes implementing the interface. If authentication is successful, return SUCCESS; if the user exists but the passwords do not match, return FAILURE; and if the user does not exist on the system, return DNE.

In the pre-authentication pipeline, if you want to skip password checking by the internal portal authentication, the authenticator should return SKIP_LIFERAY_CHECK. This is needed if passwords are not imported to the portal.

Constants in Authenticator:

     public static final int DNE = 0;
     public static final int FAILURE = -1;
     public static final int SKIP_LIFERAY_CHECK = 2;
     public static final int SUCCESS = 1;

In case you have several classes in the authentication pipeline, all of them have to return SKIP_LIFERAY_CHECK or SUCCESS if you want the user to be able to login. If one of the authenticators returns DNE OR FAILURE, the login fails.

Under certain circumstances, you might want to keep the information in the portal database in sync with an external database or an LDAP server. This can easily be achieved by implementing a class via LDAPAuth that updates the information stored in the portal user database whenever a user signs in.

Each portal instance can be configured at run time to either authenticate based on user IDs or email addresses. See the Admin portlet for more information.

Available authenticators are:

     com.liferay.portal.security.auth.LDAPAuth

See the LDAP properties to configure the behavior of the LDAPAuth class.

This property is deprecated and only provided for documentation purposes.

Env: LIFERAY_AUTH_PERIOD_PIPELINE_PERIOD_POST Env: LIFERAY_AUTH_PERIOD_PIPELINE_PERIOD_PRE

    auth.pipeline.pre=com.liferay.portal.security.auth.LDAPAuth
    auth.pipeline.post=

Set this to true to enable password checking by the internal portal authentication. If set to false, you're essentially delegating password checking to the authenticators configured in "auth.pipeline.pre" and "auth.pipeline.post" settings.

Env: LIFERAY_AUTH_PERIOD_PIPELINE_PERIOD_ENABLE_PERIOD_LIFERAY_PERIOD_CHECK

    auth.pipeline.enable.liferay.check=true

Input a list of comma delimited class names that implement com.liferay.portal.security.auth.AuthFailure. These classes will run when a user has a failed login or when a user has reached the maximum number of failed logins.

This property is deprecated and only provided for documentation purposes.

Env: LIFERAY_AUTH_PERIOD_FAILURE Env: LIFERAY_AUTH_PERIOD_MAX_PERIOD_FAILURES

    auth.failure=com.liferay.portal.security.auth.LoginFailure
    auth.max.failures=com.liferay.portal.security.auth.LoginMaxFailures

Set the following to true if users are allowed to have simultaneous logins from different sessions. This property is not used unless the property "live.users.enabled" is set to true.

Env: LIFERAY_AUTH_PERIOD_SIMULTANEOUS_PERIOD_LOGINS

    auth.simultaneous.logins=true

Set this to true if users are forwarded to the last visited path upon successful login. If set to false, users will be forwarded to their default layout page.

Env: LIFERAY_AUTH_PERIOD_FORWARD_PERIOD_BY_PERIOD_LAST_PERIOD_PATH

    auth.forward.by.last.path=true

The login page reads a redirect by a parameter named "redirect". If this property is set to true, then users will be redirected to the given redirect path upon successful login. If the user does not have permission to view that page, then the rule set by the property "auth.forward.by.last.path" will apply.

You can set the redirect manually from another application by appending the "redirect" parameter in a url that looks like this: /c/portal/login?redirect=%2Fgroup%2Femployees%2Fcalendar. This url will redirect the user to the path "/group/employees/calendar" upon successful login.

Env: LIFERAY_AUTH_PERIOD_FORWARD_PERIOD_BY_PERIOD_REDIRECT

    auth.forward.by.redirect=true

Enter a list of comma delimited paths that can be considered part of the last visited path.

Env: LIFERAY_AUTH_PERIOD_FORWARD_PERIOD_LAST_PERIOD_PATHS

    auth.forward.last.paths=/document_library/get_file

Enter a URL that will be used to login portal users whenever needed. By default, the portal's login page is used.

Env: LIFERAY_AUTH_PERIOD_LOGIN_PERIOD_URL

    auth.login.url=/web/guest/home

Set this to true to prompt a guest user to login when attempting to access a protected page resource in the portal. By setting this value to false, the portal will inform all users that a requested resource is not found if they have no entitlements to view the resource. The portal will not prompt for login even if the user is a guest user. This behavior complies with OWASP best practices.

Env: LIFERAY_AUTH_PERIOD_LOGIN_PERIOD_PROMPT_PERIOD_ENABLED

    auth.login.prompt.enabled=true

Enter a friendly URL of a page that will be used to login portal users whenever the user is navigating a site and authentication is needed. By default, the portal's login page or the URL set in the property "auth.login.url" is used.

Env: LIFERAY_AUTH_PERIOD_LOGIN_PERIOD_SITE_PERIOD_URL

    auth.login.site.url=/login

Enter the name of the login portlet used in a page identified by the URL of the previous property (if one has been set). This will allow the portlet to have access to the redirect parameter and forward the user to the page he was trying to access, when necessary. You should leave the default value unless you have your own custom login portlet.

Env: LIFERAY_AUTH_PERIOD_LOGIN_PERIOD_PORTLET_PERIOD_NAME

    auth.login.portlet.name=com_liferay_login_web_portlet_LoginPortlet

Set this to true to disable any users from logging into the portal. Preventing users from logging into the portal provides a read-only version of the portal that can be used to minimize site outages during upgrades.

Env: LIFERAY_AUTH_PERIOD_LOGIN_PERIOD_DISABLED Env: LIFERAY_AUTH_PERIOD_LOGIN_PERIOD_DISABLED_PERIOD_PATH

    auth.login.disabled=false
    auth.login.disabled.path=/portal/login_disabled

Enter a list of comma delimited paths that do not require authentication.

Env: LIFERAY_AUTH_PERIOD_PUBLIC_PERIOD_PATHS

    auth.public.paths=\
        /activities/rss,\
        \
        /asset/get_categories,\
        \
        /document_library/find_file_entry,\
        /document_library/find_folder,\
        /document_library/get_file,\
        \
        /dynamic_data_lists/find_record,\
        \
        /dynamic_data_mapping/render_structure_field,\
        \
        /flags/edit_flag,\
        \
        /iframe/proxy,\
        \
        /image_gallery_display/find_folder,\
        /image_gallery_display/find_image,\
        \
        /login/facebook_connect_oauth,\
        \
        /message_boards/find_category,\
        /message_boards/find_message,\
        /message_boards/find_thread,\
        /message_boards/get_message_attachment,\
        /message_boards/rss,\
        \
        /portal/comment/edit_discussion,\
        /portal/comment/get_comments,\
        /portal/emoticons,\
        /portal/expire_session,\
        /portal/extend_session,\
        /portal/extend_session_confirm,\
        /portal/json_service,\
        /portal/license,\
        /portal/logout,\
        /portal/open_id_request,\
        /portal/open_id_response,\
        /portal/portlet_url,\
        /portal/robots,\
        /portal/session_click,\
        /portal/session_tree_js_click,\
        /portal/sitemap,\
        /portal/status

Authentication Verifier

Input a list of comma delimited class names that implement com.liferay.portal.security.auth.AuthVerifier. These classes are used to verify whether a request is authenticated or not.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD_PIPELINE

    auth.verifier.pipeline=com.liferay.portal.security.auth.verifier.basic.auth.header.BasicAuthHeaderAuthVerifier,com.liferay.portal.security.auth.verifier.DigestAuthenticationAuthVerifier,com.liferay.portal.security.auth.verifier.request.parameter.RequestParameterAuthVerifier,com.liferay.portal.security.auth.verifier.PortalSessionAuthVerifier,com.liferay.portal.security.auth.verifier.internal.tunnel.TunnelAuthVerifier

Each authentication verifier can have custom properties set via the property prefix "auth.verifier." and the authentication verifier's simple class name. All property suffixes are stripped of their prefix and passed directly to the authentication verifier. For example, the property "auth.verifier.BasicAuthHeaderAuthVerifier.hosts.allowed" is passed to BasicAuthHeaderAuthVerifier as "hosts.allowed".

The expected property suffixes are "hosts.allowed" and "urls". See the property "json.service.auth.token.hosts.allowed" for the accepted values for the property suffix "hosts.allowed".

The property suffix "urls.includes" denotes the valid URLs that apply to an authentication verifier.

The property suffix "urls.excludes" denotes URLs that will not be handled even if they match the patterns set in "urls.includes".

BasicAuthHeaderAuthVerifier

Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASEB_ASIC_UPPERCASEA_UTH_UPPERCASEH_EADER_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_HOSTS_PERIOD_ALLOWED Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASEB_ASIC_UPPERCASEA_UTH_UPPERCASEH_EADER_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_URLS_PERIOD_EXCLUDES Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASEB_ASIC_UPPERCASEA_UTH_UPPERCASEH_EADER_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_URLS_PERIOD_INCLUDES

    auth.verifier.BasicAuthHeaderAuthVerifier.hosts.allowed=
    auth.verifier.BasicAuthHeaderAuthVerifier.urls.includes=/api/*,/xmlrpc/*
    auth.verifier.BasicAuthHeaderAuthVerifier.urls.excludes=/api/liferay/do

DigestAuthenticationAuthVerifier

Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASED_IGEST_UPPERCASEA_UTHENTICATION_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_HOSTS_PERIOD_ALLOWED Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASED_IGEST_UPPERCASEA_UTHENTICATION_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_URLS_PERIOD_INCLUDES

    auth.verifier.DigestAuthenticationAuthVerifier.hosts.allowed=
    auth.verifier.DigestAuthenticationAuthVerifier.urls.includes=N/A

PortalSessionAuthVerifier

Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASEP_ORTAL_UPPERCASES_ESSION_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_HOSTS_PERIOD_ALLOWED Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASEP_ORTAL_UPPERCASES_ESSION_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_URLS_PERIOD_INCLUDES

    auth.verifier.PortalSessionAuthVerifier.hosts.allowed=
    auth.verifier.PortalSessionAuthVerifier.urls.includes=\
        /api/json/*,\
        /api/jsonws/*,\
        /c/portal/json_service/*

RequestParameterAuthVerifier

Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASER_EQUEST_UPPERCASEP_ARAMETER_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_HOSTS_PERIOD_ALLOWED Env: LIFERAY_AUTH_PERIOD_VERIFIER_PERIOD__UPPERCASER_EQUEST_UPPERCASEP_ARAMETER_UPPERCASEA_UTH_UPPERCASEV_ERIFIER_PERIOD_URLS_PERIOD_INCLUDES

    auth.verifier.RequestParameterAuthVerifier.hosts.allowed=
    auth.verifier.RequestParameterAuthVerifier.urls.includes=N/A

Authentication Token

Set this to false to disable CSRF protection in the portal. Disabling CSRF protection is not recommended since all features become vulnerable to CSRF attacks.

The checks can be disabled for specific actions via the property "auth.token.ignore.actions" or for specific portlets via the init parameter "check-auth-token" in portlet.xml.

Env: LIFERAY_AUTH_PERIOD_TOKEN_PERIOD_CHECK_PERIOD_ENABLED

    auth.token.check.enabled=true

Set the authentication token class. This class must implement com.liferay.portal.security.auth.AuthToken. This class is used to prevent CSRF attacks. See https://issues.liferay.com/browse/LPS-8399 for more information.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_AUTH_PERIOD_TOKEN_PERIOD_IMPL

    auth.token.impl=com.liferay.portal.security.auth.SessionAuthToken

Input a list of comma delimited struts actions that will not be checked for an authentication token.

Env: LIFERAY_AUTH_PERIOD_TOKEN_PERIOD_IGNORE_PERIOD_ACTIONS

    auth.token.ignore.actions=\
        /asset/rss,\
        \
        /blogs/rss,\
        /blogs/trackback,\
        \
        /blogs_aggregator/rss,\
        \
        /login/create_account,\
        \
        /message_boards/rss,\
        \
        /portal/comment/get_comments

Set a list of comma delimited origins that will not be checked for an authentication token.

Env: LIFERAY_AUTH_PERIOD_TOKEN_PERIOD_IGNORE_PERIOD_ORIGINS

    auth.token.ignore.origins=\
        com.liferay.portal.action.JSONServiceAction:com.liferay.portlet.expando.service.ExpandoValueServiceUtil#getJSONData,\
        com.liferay.portal.action.LoginAction,\
        com.liferay.portal.jsonwebservice.JSONWebServiceServiceAction:/classname/,\
        com.liferay.portal.jsonwebservice.JSONWebServiceServiceAction:/user/get-user-by-email-address,\
        com.liferay.portlet.asset.action.GetCategoriesAction,\
        com.liferay.portlet.portletconfiguration.action.GetLookAndFeelAction

Set a list of comma delimited portlet IDs that will not be checked for an authentication token.

Env: LIFERAY_AUTH_PERIOD_TOKEN_PERIOD_IGNORE_PERIOD_PORTLETS

    auth.token.ignore.portlets=

Set the length of the authentication token. Longer auth tokens will require more CPU cycles to generate and may impact overall performance.

Env: LIFERAY_AUTH_PERIOD_TOKEN_PERIOD_LENGTH

    auth.token.length=8

Set the shared secret that is used for requests where it is not possible to generate an authentication token (i.e. WSRP).

Env: LIFERAY_AUTH_PERIOD_TOKEN_PERIOD_SHARED_PERIOD_SECRET

    auth.token.shared.secret=

Auto Login

Input a list of comma delimited class names that implement com.liferay.portal.kernel.security.auto.login.AutoLogin. These classes will run in consecutive order for all unauthenticated users until one of them returns a valid user ID and password combination. If no valid combination is returned, then the request continues to process normally. If a valid combination is returned, then the portal will automatically login that user with the returned user ID and password combination.

For example, com.liferay.portal.security.auto.login.remember.me.RememberMeAutoLogin reads from a cookie to automatically log in a user who previously logged in while checking on the "Remember Me" box.

This interface allows deployers to easily configure the portal to work with other SSO servers. See com.liferay.portal.security.sso.cas.internal.auto.login.CASAutoLogin for an example of how to configure the portal with Yale's SSO server.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_AUTO_PERIOD_LOGIN_PERIOD_HOOKS

    auto.login.hooks=com.liferay.portal.security.sso.cas.internal.auto.login.CASAutoLogin,com.liferay.portal.security.sso.facebook.connect.auto.login.FacebookConnectAutoLogin,com.liferay.portal.security.sso.ntlm.auto.login.NtlmAutoLogin,com.liferay.portal.security.sso.openid.auto.login.OpenIdAutoLogin,com.liferay.portal.security.sso.opensso.auto.login.OpenSSOAutoLogin,com.liferay.portal.security.auto.login.remember.me.RememberMeAutoLogin

Set the hosts that will be ignored for auto login.

Env: LIFERAY_AUTO_PERIOD_LOGIN_PERIOD_IGNORE_PERIOD_HOSTS

    auto.login.ignore.hosts=

Set the paths that will be ignored for auto login.

Env: LIFERAY_AUTO_PERIOD_LOGIN_PERIOD_IGNORE_PERIOD_PATHS

    auto.login.ignore.paths=

SSO with MAC (Message Authentication Code)

To use SSO with MAC, post to a URL like:

     http://localhost:8080/c/portal/login?cmd=already-registered&login=&password=

Pass the MAC in the password field. Make sure the MAC gets URL encoded because it might contain characters not allowed in a URL.

SSO with MAC also requires that you set the following property in system.properties:

     com.liferay.util.servlet.SessionParameters=false

See the following links:

     https://issues.liferay.com/browse/LEP-1288
     http://en.wikipedia.org/wiki/Message_authentication_code

Set this to true to enable SSO with MAC.

Env: LIFERAY_AUTH_PERIOD_MAC_PERIOD_ALLOW

    auth.mac.allow=false

Set the algorithm to use for MAC encryption.

Env: LIFERAY_AUTH_PERIOD_MAC_PERIOD_ALGORITHM

    auth.mac.algorithm=MD5

Set the shared key used to generate the MAC. The shared key must not be empty and it should be sufficiently long and complex to withstand a brute force attack.

Env: LIFERAY_AUTH_PERIOD_MAC_PERIOD_SHARED_PERIOD_KEY

    auth.mac.shared.key=

Passwords

Set the following encryption algorithm to designate the password encryption algorithm to migrate from. This is only necessary if upgrading from a release prior to 6.2 or if you wish to switch password encryption algorithms when there are existing users with passwords in the portal.

Env: LIFERAY_PASSWORDS_PERIOD_ENCRYPTION_PERIOD_ALGORITHM_PERIOD_LEGACY

    passwords.encryption.algorithm.legacy=BCRYPT
    passwords.encryption.algorithm.legacy=MD2
    passwords.encryption.algorithm.legacy=MD5
    passwords.encryption.algorithm.legacy=NONE
    passwords.encryption.algorithm.legacy=SHA
    passwords.encryption.algorithm.legacy=SHA-256
    passwords.encryption.algorithm.legacy=SHA-384
    passwords.encryption.algorithm.legacy=SSHA
    passwords.encryption.algorithm.legacy=UFC-CRYPT

Set the following encryption algorithm to encrypt passwords. The default algorithm is PBKDF2WithHmacSHA1/160/128000, generating 160 bit hashes using 128,000 rounds.

It is possible to decrease the rounds value in case of slow production hardware, but be aware that 128,000 is the recommended value for 2014 by OWASP.

If set to NONE, passwords are stored in the database as plain text.

Env: LIFERAY_PASSWORDS_PERIOD_ENCRYPTION_PERIOD_ALGORITHM

    passwords.encryption.algorithm=PBKDF2WithHmacSHA1/160/128000

    passwords.encryption.algorithm=BCRYPT/10
    passwords.encryption.algorithm=MD2
    passwords.encryption.algorithm=MD5
    passwords.encryption.algorithm=NONE
    passwords.encryption.algorithm=SHA
    passwords.encryption.algorithm=SHA-256
    passwords.encryption.algorithm=SHA-384
    passwords.encryption.algorithm=SSHA
    passwords.encryption.algorithm=UFC-CRYPT

Digested passwords are encoded via base64 or hex encoding. The default is base64.

Env: LIFERAY_PASSWORDS_PERIOD_DIGEST_PERIOD_ENCODING

    passwords.digest.encoding=base64

    passwords.digest.encoding=hex

Input a class name that implements com.liferay.portal.security.pwd.Toolkit. This class will be called to generate and validate passwords.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_PASSWORDS_PERIOD_TOOLKIT

    passwords.toolkit=com.liferay.portal.security.pwd.PasswordPolicyToolkit
    passwords.toolkit=com.liferay.portal.security.pwd.RegExpToolkit

If you choose to use com.liferay.portal.security.pwd.PasswordPolicyToolkit as your password toolkit, you can choose either static or dynamic password generation. Static is set through the property "passwords.passwordpolicytoolkit.static" and dynamic uses the class com.liferay.util.PwdGenerator to generate the password. If you are using LDAP password syntax checking, you will also have to use the static generator so that you can guarantee that passwords obey its rules.

Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_GENERATOR Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_STATIC

    passwords.passwordpolicytoolkit.generator=dynamic
    passwords.passwordpolicytoolkit.static=iheartliferay

    passwords.passwordpolicytoolkit.generator=static

Set the character sets for password generation. These must be a subset of validation character sets.

Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_GENERATOR_PERIOD_CHARSET_PERIOD_LOWERCASE Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_GENERATOR_PERIOD_CHARSET_PERIOD_NUMBERS Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_GENERATOR_PERIOD_CHARSET_PERIOD_SYMBOLS Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_GENERATOR_PERIOD_CHARSET_PERIOD_UPPERCASE

    passwords.passwordpolicytoolkit.generator.charset.lowercase=abcdefghjkmnpqrstuvwxyz
    passwords.passwordpolicytoolkit.generator.charset.numbers=0123456789
    passwords.passwordpolicytoolkit.generator.charset.symbols=_.!@$*=-?
    passwords.passwordpolicytoolkit.generator.charset.uppercase=ABCDEFGHJKLMNPQRSTUVWXYZ

Set the character sets for password validation.

Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_VALIDATOR_PERIOD_CHARSET_PERIOD_LOWERCASE Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_VALIDATOR_PERIOD_CHARSET_PERIOD_NUMBERS Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_VALIDATOR_PERIOD_CHARSET_PERIOD_SYMBOLS Env: LIFERAY_PASSWORDS_PERIOD_PASSWORDPOLICYTOOLKIT_PERIOD_VALIDATOR_PERIOD_CHARSET_PERIOD_UPPERCASE

    passwords.passwordpolicytoolkit.validator.charset.lowercase=abcdefghijklmnopqrstuvwxyz
    passwords.passwordpolicytoolkit.validator.charset.numbers=0123456789
    passwords.passwordpolicytoolkit.validator.charset.symbols=_.!@$*=-?
    passwords.passwordpolicytoolkit.validator.charset.uppercase=ABCDEFGHIJKLMNOPQRSTUVWXYZ

If you choose to use com.liferay.portal.security.pwd.RegExpToolkit as your password toolkit, set the regular expression pattern that will be used to generate and validate passwords.

Note that \ is replaced with \\ to work in Java.

The first pattern ensures that passwords must have at least 4 valid characters consisting of digits or letters.

The second pattern ensures that passwords must have at least 8 valid characters consisting of digits or letters.

Env: LIFERAY_PASSWORDS_PERIOD_REGEXPTOOLKIT_PERIOD_PATTERN

    passwords.regexptoolkit.pattern=(?=.{4})(?:[a-zA-Z0-9]*)

    passwords.regexptoolkit.pattern=(?=.{8})(?:[a-zA-Z0-9]*)

Set the length and key for generating passwords.

Env: LIFERAY_PASSWORDS_PERIOD_REGEXPTOOLKIT_PERIOD_CHARSET Env: LIFERAY_PASSWORDS_PERIOD_REGEXPTOOLKIT_PERIOD_LENGTH

    passwords.regexptoolkit.charset=0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
    passwords.regexptoolkit.length=8

    passwords.regexptoolkit.charset=0123456789
    passwords.regexptoolkit.length=4

Set the properties of the default password policy.

Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_ALLOW_PERIOD_DICTIONARY_PERIOD_WORDS Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_CHANGEABLE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_CHANGE_PERIOD_REQUIRED Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_CHECK_PERIOD_SYNTAX Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_EXPIREABLE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_GRACE_PERIOD_LIMIT Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_HISTORY Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_HISTORY_PERIOD_COUNT Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_LOCKOUT Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_LOCKOUT_PERIOD_DURATION Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MAX_PERIOD_AGE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MAX_PERIOD_FAILURE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MIN_PERIOD_AGE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MIN_PERIOD_ALPHANUMERIC Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MIN_PERIOD_LENGTH Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MIN_PERIOD_LOWERCASE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MIN_PERIOD_NUMBERS Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MIN_PERIOD_SYMBOLS Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_MIN_PERIOD_UPPERCASE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_NAME Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_REGEX Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_RESET_PERIOD_FAILURE_PERIOD_COUNT Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_RESET_PERIOD_TICKET_PERIOD_MAX_PERIOD_AGE Env: LIFERAY_PASSWORDS_PERIOD_DEFAULT_PERIOD_POLICY_PERIOD_WARNING_PERIOD_TIME

    passwords.default.policy.allow.dictionary.words=true
    passwords.default.policy.changeable=true
    passwords.default.policy.change.required=true
    passwords.default.policy.check.syntax=false
    passwords.default.policy.expireable=false
    passwords.default.policy.grace.limit=0
    passwords.default.policy.history=false
    passwords.default.policy.history.count=6
    passwords.default.policy.lockout=false
    passwords.default.policy.lockout.duration=0
    passwords.default.policy.max.age=8640000
    passwords.default.policy.max.failure=3
    passwords.default.policy.min.age=0
    passwords.default.policy.min.alphanumeric=0
    passwords.default.policy.min.length=6
    passwords.default.policy.min.lowercase=0
    passwords.default.policy.min.numbers=1
    passwords.default.policy.min.symbols=0
    passwords.default.policy.min.uppercase=1
    passwords.default.policy.name=Default Password Policy
    passwords.default.policy.regex=(?=.{4})(?:[a-zA-Z0-9]*)
    passwords.default.policy.reset.failure.count=600
    passwords.default.policy.reset.ticket.max.age=86400
    passwords.default.policy.warning.time=86400

Permissions

Set the default permission checker class used by com.liferay.portal.security.permission.PermissionCheckerFactory to check permissions for actions on objects. This class can be overriden with a custom class that implements com.liferay.portal.security.permission.PermissionChecker.

Env: LIFERAY_PERMISSIONS_PERIOD_CHECKER

    permissions.checker=com.liferay.portal.security.permission.AdvancedPermissionChecker

    permissions.checker=com.liferay.portal.security.permission.SimplePermissionChecker

Set this to true to configure permission caching to block. See the property "ehcache.blocking.cache.allowed" for more information.

Env: LIFERAY_PERMISSIONS_PERIOD_OBJECT_PERIOD_BLOCKING_PERIOD_CACHE

    permissions.object.blocking.cache=false

Configure this threshold to indicate when to use the custom SQL finder to check resource permissions.

Env: LIFERAY_PERMISSIONS_PERIOD_ROLE_PERIOD_RESOURCE_PERIOD_PERMISSION_PERIOD_QUERY_PERIOD_THRESHOLD

    permissions.role.resource.permission.query.threshold=10

Set this to true to use permission checking when reading custom attributes by default.

Env: LIFERAY_PERMISSIONS_PERIOD_CUSTOM_PERIOD_ATTRIBUTE_PERIOD_READ_PERIOD_CHECK_PERIOD_BY_PERIOD_DEFAULT

    permissions.custom.attribute.read.check.by.default=true

Set this to true to use permission checking when writing custom attributes by default.

Env: LIFERAY_PERMISSIONS_PERIOD_CUSTOM_PERIOD_ATTRIBUTE_PERIOD_WRITE_PERIOD_CHECK_PERIOD_BY_PERIOD_DEFAULT

    permissions.custom.attribute.write.check.by.default=true

Set the following to true to automatically check the view permission on parent categories or folders when checking the permission on a specific item.

For example, if set to true, to be able to have access to a document, a user must have the view permission on the document's folder and all its parent folders. Or, to have access to a comment, a user must have the view permission on the comments's category and all its parent categories.

Env: LIFERAY_PERMISSIONS_PERIOD_VIEW_PERIOD_DYNAMIC_PERIOD_INHERITANCE

    permissions.view.dynamic.inheritance=true

Set the following to true to enable propagation of permissions between models.

For example, when setting the permissions on a specific Wiki node, if you assign a role a permission (e.g. DELETE), then the assignment of that permission is also propagated to all Wiki pages that belong to that Wiki node.

The actual logic of how permissions are propagated among models is specified per portlet. See liferay-portlet.xml's use of the element "permission-propagator".

Env: LIFERAY_PERMISSIONS_PERIOD_PROPAGATION_PERIOD_ENABLED

    permissions.propagation.enabled=false

Set this to true if resources should assume that all users have the Guest role. Set this to false if resources will not assume that all users have the Guest role and, thus, do not automatically inherit permissions that belong to the Guest role.

Setting this property to false may require users to grant permissions to roles like Site Member and User.

Env: LIFERAY_PERMISSIONS_PERIOD_CHECK_PERIOD_GUEST_PERIOD_ENABLED

    permissions.check.guest.enabled=true

Startup Events

Input a list of comma delimited class names that extend com.liferay.portal.struts.SimpleAction. These classes will run at the specified event.

Global startup event that runs once when the portal initializes.

Env: LIFERAY_GLOBAL_PERIOD_STARTUP_PERIOD_EVENTS

    global.startup.events=\
        com.liferay.portal.events.GlobalStartupAction,\
        com.liferay.portal.events.CryptoStartupAction

Application startup event that runs once for every web site instance of the portal that initializes.

Env: LIFERAY_APPLICATION_PERIOD_STARTUP_PERIOD_EVENTS

    application.startup.events=\
        com.liferay.portal.events.AppStartupAction,\
        com.liferay.portal.events.ChannelHubAppStartupAction

    application.startup.events=com.liferay.portal.events.AppStartupAction,com.liferay.portal.events.SampleAppStartupAction

Shutdown Events

Input a list of comma delimited class names that extend com.liferay.portal.struts.SimpleAction. These classes will run at the specified event.

Global shutdown event that runs once when the portal shuts down.

Env: LIFERAY_GLOBAL_PERIOD_SHUTDOWN_PERIOD_EVENTS

    global.shutdown.events=com.liferay.portal.events.GlobalShutdownAction

Application shutdown event that runs once for every web site instance of the portal that shuts down.

Env: LIFERAY_APPLICATION_PERIOD_SHUTDOWN_PERIOD_EVENTS

    application.shutdown.events=\
        com.liferay.portal.events.AppShutdownAction,\
        com.liferay.portal.events.ChannelHubAppShutdownAction

Programmatically kill the Java process on shutdown. This is a workaround for a bug in Tomcat and Linux where the process hangs on forever.

See https://issues.liferay.com/browse/LEP-2048 for more information.

Env: LIFERAY_SHUTDOWN_PERIOD_PROGRAMMATICALLY_PERIOD_EXIT

    shutdown.programmatically.exit=false

Portal Events

Input a list of comma delimited class names that extend com.liferay.portal.kernel.events.Action. These classes will run before or after the specified event.

Servlet service event (the pre-service events have an associated error page and will forward to that page if an exception is thrown during excecution of the events). The pre-service events process before Struts processes the request. The post-service events process after Struts processes the request.

Env: LIFERAY_SERVLET_PERIOD_SERVICE_PERIOD_EVENTS_PERIOD_POST Env: LIFERAY_SERVLET_PERIOD_SERVICE_PERIOD_EVENTS_PERIOD_PRE Env: LIFERAY_SERVLET_PERIOD_SERVICE_PERIOD_EVENTS_PERIOD_PRE_PERIOD_ERROR_PERIOD_PAGE

    servlet.service.events.pre=\
        com.liferay.portal.events.ServicePreAction,\
        com.liferay.portal.events.ThemeServicePreAction
    servlet.service.events.pre.error.page=/common/error.jsp
    servlet.service.events.post=com.liferay.portal.events.ServicePostAction

    servlet.service.events.pre=com.liferay.portal.events.LogMemoryUsageAction,com.liferay.portal.events.LogThreadCountAction,com.liferay.portal.events.ServicePreAction,com.liferay.portal.events.ThemeServicePreAction
    servlet.service.events.pre=com.liferay.portal.events.LogSessionIdAction,com.liferay.portal.events.ServicePreAction,com.liferay.portal.events.ThemeServicePreAction
    servlet.service.events.pre=com.liferay.portal.events.ServicePreAction,com.liferay.portal.events.ThemeServicePreAction,com.liferay.portal.events.RandomLayoutAction
    servlet.service.events.pre=com.liferay.portal.events.ServicePreAction,com.liferay.portal.events.ThemeServicePreAction,com.liferay.portal.events.RandomLookAndFeelAction
    servlet.service.events.pre=com.liferay.portal.events.ServicePreAction,com.liferay.portal.events.ThemeServicePreAction,com.liferay.portal.events.SecureRequestAction

Login Event

Env: LIFERAY_LOGIN_PERIOD_EVENTS_PERIOD_PRE

    login.events.pre=com.liferay.portal.events.LoginPreAction

Env: LIFERAY_LOGIN_PERIOD_EVENTS_PERIOD_POST

    login.events.post=\
        com.liferay.portal.events.ChannelLoginPostAction,\
        com.liferay.portal.events.DefaultLandingPageAction,\
        com.liferay.portal.events.LoginPostAction

Logout Event

Env: LIFERAY_LOGOUT_PERIOD_EVENTS_PERIOD_PRE

    logout.events.pre=com.liferay.portal.events.LogoutPreAction

Env: LIFERAY_LOGOUT_PERIOD_EVENTS_PERIOD_POST

    logout.events.post=\
        com.liferay.portal.events.LogoutPostAction,\
        com.liferay.portal.events.DefaultLogoutPageAction

    logout.events.post=com.liferay.portal.events.LogoutPostAction,com.liferay.portal.events.GarbageCollectorAction

Default Landing Page

Set the default landing page path for logged in users relative to the server path. This is the page users are automatically redirected to after logging in. For example, if you want the default landing page to be http://localhost:8080/web/guest/login, set this to /web/guest/login. To activate this feature, set auth.forward.by.last.path to true. To customize the behavior, see com.liferay.portal.events.DefaultLandingPageAction in the "login.events.post" property above.

The following variables can be used: ${liferay:screenName} and ${liferay:userId}.

Env: LIFERAY_DEFAULT_PERIOD_LANDING_PERIOD_PAGE_PERIOD_PATH

    default.landing.page.path=

    default.landing.page.path=/web/guest/login
    default.landing.page.path=/user/${liferay:screenName}/home

Default Logout Page

Set the default logout page path for users relative to the server path. This is the page users are automatically redirected to after logging out. For example, if you want the default logout page to be http://localhost:8080/web/guest/logout, set this to /web/guest/logout. To activate this feature, set auth.forward.by.last.path to true. To customize the behavior, see com.liferay.portal.events.DefaultLogoutPageAction in the "logout.events.post" property above.

Env: LIFERAY_DEFAULT_PERIOD_LOGOUT_PERIOD_PAGE_PERIOD_PATH

    default.logout.page.path=

    default.logout.page.path=/web/guest/logout

Default Guest Public Layouts

The Guest group must have at least one public page. The settings for the initial public page are specified in the following properties.

If you need to add more than one page, set the property "default.guest.public.layouts.lar" to specifiy a LAR file instead.

For even more complex behavior, override the addDefaultGuestPublicLayouts method in com.liferay.portal.service.impl.GroupLocalServiceImpl.

Set the name of the public layout.

Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_NAME

    default.guest.public.layout.name=Home

Set the layout template ID of the public layout.

Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_TEMPLATE_PERIOD_ID

    default.guest.public.layout.template.id=1_column

Set the portlet IDs for the columns specified in the layout template.

Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER1_ Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER2_ Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER3_ Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER4_

    default.guest.public.layout.column-1=com_liferay_hello_world_web_portlet_HelloWorldPortlet
    default.guest.public.layout.column-2=
    default.guest.public.layout.column-3=
    default.guest.public.layout.column-4=

Set the friendly url of the public layout.

Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL

    default.guest.public.layout.friendly.url=/home

Set the regular theme ID for the public layout.

Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_REGULAR_PERIOD_THEME_PERIOD_ID

    default.guest.public.layout.regular.theme.id=classic_WAR_classictheme

Set the regular color scheme ID for the public layout.

Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_REGULAR_PERIOD_COLOR_PERIOD_SCHEME_PERIOD_ID

    default.guest.public.layout.regular.color.scheme.id=01

Specify a LAR file that can be used to create the guest public layouts. If this property is set, the previous layout properties will be ignored.

Env: LIFERAY_DEFAULT_PERIOD_GUEST_PERIOD_PUBLIC_PERIOD_LAYOUTS_PERIOD_LAR

    default.guest.public.layouts.lar=${liferay.home}/deploy/default_guest_public.lar

Default User Private Layouts

If the properties "layout.user.private.layouts.enabled" and "layout.user.private.layouts.auto.create" are both set to true, then users will have private layouts and they will be automatically created. The settings below are used for the creation of the initial private pages.

If you need to add more than one page, set the property "default.user.private.layouts.lar" to specifiy a LAR file instead.

For even more complex behavior, override the addDefaultUserPrivateLayouts method in com.liferay.portal.events.ServicePreAction.

Set the name of the private layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_NAME

    default.user.private.layout.name=My Dashboard

Set the layout template ID of the private layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_TEMPLATE_PERIOD_ID

    default.user.private.layout.template.id=1_column

Set the portlet IDs for the columns specified in the layout template.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER1_ Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER2_ Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER3_ Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER4_

    default.user.private.layout.column-1=com_liferay_site_my_sites_web_portlet_MySitesPortlet
    default.user.private.layout.column-2=
    default.user.private.layout.column-3=
    default.user.private.layout.column-4=

Set the friendly url of the private layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL

    default.user.private.layout.friendly.url=/home

Set the regular theme ID for the private layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_REGULAR_PERIOD_THEME_PERIOD_ID

    default.user.private.layout.regular.theme.id=classic_WAR_classictheme

Set the regular color scheme ID for the private layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUT_PERIOD_REGULAR_PERIOD_COLOR_PERIOD_SCHEME_PERIOD_ID

    default.user.private.layout.regular.color.scheme.id=01

Specify a LAR file that can be used to create the user private layouts. If this property is set, the previous layout properties will be ignored.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUTS_PERIOD_LAR

    default.user.private.layouts.lar=${liferay.home}/deploy/default_user_private.lar

Default User Public Layouts

If the properties "layout.user.public.layouts.enabled" and "layout.user.public.layouts.auto.create" are both set to true, then users will have public layouts and they will be automatically created. The settings below are used for the creation of the initial public pages.

If you need to add more than one page, set the property "default.user.public.layouts.lar" to specify a LAR file instead.

For even more complex behavior, override the addDefaultUserPublicLayouts method in com.liferay.portal.events.ServicePreAction.

Set the name of the public layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_NAME

    default.user.public.layout.name=My Profile

Set the layout template ID of the public layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_TEMPLATE_PERIOD_ID

    default.user.public.layout.template.id=1_column

Set the portlet IDs for the columns specified in the layout template.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER1_ Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER2_ Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER3_ Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_COLUMN_MINUS__NUMBER4_

    default.user.public.layout.column-1=com_liferay_contacts_web_portlet_ProfilePortlet
    default.user.public.layout.column-2=
    default.user.public.layout.column-3=
    default.user.public.layout.column-4=

Set the friendly url of the public layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL

    default.user.public.layout.friendly.url=/home

Set the regular theme ID for the public layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_REGULAR_PERIOD_THEME_PERIOD_ID

    default.user.public.layout.regular.theme.id=classic_WAR_classictheme

Set the regular color scheme ID for the public layout.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUT_PERIOD_REGULAR_PERIOD_COLOR_PERIOD_SCHEME_PERIOD_ID

    default.user.public.layout.regular.color.scheme.id=01

Specify a LAR file that can be used to create the user public layouts. If this property is set, the previous layout properties will be ignored.

Env: LIFERAY_DEFAULT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUTS_PERIOD_LAR

    default.user.public.layouts.lar=${liferay.home}/deploy/default_user_public.lar

Default Admin

Set the default admin password.

Env: LIFERAY_DEFAULT_PERIOD_ADMIN_PERIOD_PASSWORD

    default.admin.password=test

Set the default admin screen name prefix.

Env: LIFERAY_DEFAULT_PERIOD_ADMIN_PERIOD_SCREEN_PERIOD_NAME

    default.admin.screen.name=test

Set the default admin email address prefix.

Env: LIFERAY_DEFAULT_PERIOD_ADMIN_PERIOD_EMAIL_PERIOD_ADDRESS_PERIOD_PREFIX

    default.admin.email.address.prefix=test

Set the default admin first name.

Env: LIFERAY_DEFAULT_PERIOD_ADMIN_PERIOD_FIRST_PERIOD_NAME

    default.admin.first.name=Test

Set the default admin middle name.

Env: LIFERAY_DEFAULT_PERIOD_ADMIN_PERIOD_MIDDLE_PERIOD_NAME

    default.admin.middle.name=

Set the default admin last name.

Env: LIFERAY_DEFAULT_PERIOD_ADMIN_PERIOD_LAST_PERIOD_NAME

    default.admin.last.name=Test

Layouts

Set whether or not private layouts are enabled. Set whether or not private layouts should be auto created if a user has no private layouts. If private layouts are not enabled, then the property "layout.user.private.layouts.auto.create" is assumed to be false.

Env: LIFERAY_LAYOUT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUTS_PERIOD_AUTO_PERIOD_CREATE Env: LIFERAY_LAYOUT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUTS_PERIOD_ENABLED

    layout.user.private.layouts.enabled=true
    layout.user.private.layouts.auto.create=true

Set this to true if users must have the Power User role to have private pages.

Env: LIFERAY_LAYOUT_PERIOD_USER_PERIOD_PRIVATE_PERIOD_LAYOUTS_PERIOD_POWER_PERIOD_USER_PERIOD_REQUIRED

    layout.user.private.layouts.power.user.required=false

Set whether or not public layouts are enabled. Set whether or not public layouts should be auto created if a user has no public layouts. If public layouts are not enabled, then the property "layout.user.public.layouts.auto.create" is assumed to be false.

Env: LIFERAY_LAYOUT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUTS_PERIOD_AUTO_PERIOD_CREATE Env: LIFERAY_LAYOUT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUTS_PERIOD_ENABLED

    layout.user.public.layouts.enabled=true
    layout.user.public.layouts.auto.create=true

Set this to true if users must have the Power User role to have public pages.

Env: LIFERAY_LAYOUT_PERIOD_USER_PERIOD_PUBLIC_PERIOD_LAYOUTS_PERIOD_POWER_PERIOD_USER_PERIOD_REQUIRED

    layout.user.public.layouts.power.user.required=false

Default settings layouts.

Env: LIFERAY_LAYOUT_PERIOD_CONFIGURATION_PERIOD_ACTION_PERIOD_DELETE Env: LIFERAY_LAYOUT_PERIOD_CONFIGURATION_PERIOD_ACTION_PERIOD_UPDATE Env: LIFERAY_LAYOUT_PERIOD_EDIT_PERIOD_PAGE Env: LIFERAY_LAYOUT_PERIOD_FIRST_PERIOD_PAGEABLE Env: LIFERAY_LAYOUT_PERIOD_PARENTABLE Env: LIFERAY_LAYOUT_PERIOD_SITEMAPABLE Env: LIFERAY_LAYOUT_PERIOD_URL Env: LIFERAY_LAYOUT_PERIOD_URL_PERIOD_FRIENDLIABLE Env: LIFERAY_LAYOUT_PERIOD_VIEW_PERIOD_PAGE

    layout.edit.page=/portal/layout/edit/portlet.jsp
    layout.view.page=/portal/layout/view/portlet.jsp
    layout.url=${liferay:mainPath}/portal/layout?p_l_id=${liferay:plid}&p_v_l_s_g_id=${liferay:pvlsgid}
    layout.url.friendliable=true
    layout.parentable=true
    layout.sitemapable=true
    layout.first.pageable=true

    layout.configuration.action.update=
    layout.configuration.action.delete=

Settings for portlet layouts are inherited from the default settings.

Env: LIFERAY_LAYOUT_PERIOD_CONFIGURATION_PERIOD_ACTION_PERIOD_DELETE_OPENBRACKET_PORTLET_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_CONFIGURATION_PERIOD_ACTION_PERIOD_UPDATE_OPENBRACKET_PORTLET_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_EDIT_PERIOD_PAGE_OPENBRACKET_PORTLET_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_PARENTABLE_OPENBRACKET_PORTLET_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_URL_OPENBRACKET_PORTLET_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_URL_PERIOD_FRIENDLIABLE_OPENBRACKET_PORTLET_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_VIEW_PERIOD_PAGE_OPENBRACKET_PORTLET_CLOSEBRACKET_

    layout.edit.page[portlet]=/portal/layout/edit/portlet.jsp
    layout.view.page[portlet]=/portal/layout/view/portlet.jsp
    layout.url[portlet]=${liferay:mainPath}/portal/layout?p_l_id=${liferay:plid}&p_v_l_s_g_id=${liferay:pvlsgid}
    layout.url.friendliable[portlet]=true
    layout.parentable[portlet]=true
    layout.configuration.action.update[portlet]=
    layout.configuration.action.delete[portlet]=

Specify static portlets that cannot be moved and will always appear on every layout. Static portlets will take precedence over portlets that may have been dynamically configured for the layout.

For example, if you want the Hello World portlet to always appear at the start of the iteration of the first column for user layouts, set the property "layout.static.portlets.start.column-1[user]" to "47". If you want the Hello World portlet to always appear at the end of the second column for user layouts, set the property "layout.static.portlets.end.column-2[user]" to "47". You can input a list of comma delimited portlet IDs to specify more than one portlet. If the portlet is instanceable, add the suffix "_INSTANCE_abcd" to the portlet ID, where "abcd" is any random alphanumeric string.

The static portlets are fetched based on the properties controlled by custom filters using EasyConf. By default, the available filters are user, community, and organization.

Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER1__OPENBRACKET_USER_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER2__OPENBRACKET_USER_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER3__OPENBRACKET_USER_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER1__OPENBRACKET_USER_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER2__OPENBRACKET_USER_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER3__OPENBRACKET_USER_CLOSEBRACKET_

    layout.static.portlets.start.column-1[user]=6
    layout.static.portlets.end.column-1[user]=14
    layout.static.portlets.start.column-2[user]=71_INSTANCE_abcd,7
    layout.static.portlets.end.column-2[user]=34,70
    layout.static.portlets.start.column-3[user]=
    layout.static.portlets.end.column-3[user]=

It is also possible to set static portlets based on the layout's friendly URL.

Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER2__OPENBRACKET_REGULAR_MINUS_SITE_CLOSEBRACKET__OPENBRACKET__SLASH_HOME_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER1__OPENBRACKET_USER_CLOSEBRACKET__OPENBRACKET__SLASH_HOME_CLOSEBRACKET_

    layout.static.portlets.start.column-1[user][/home]=6
    layout.static.portlets.end.column-2[regular-site][/home]=14

Set the static portlets for the pages of regular sites.

Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER1__OPENBRACKET_REGULAR_MINUS_SITE_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER2__OPENBRACKET_REGULAR_MINUS_SITE_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER3__OPENBRACKET_REGULAR_MINUS_SITE_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER1__OPENBRACKET_REGULAR_MINUS_SITE_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER2__OPENBRACKET_REGULAR_MINUS_SITE_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER3__OPENBRACKET_REGULAR_MINUS_SITE_CLOSEBRACKET_

    layout.static.portlets.start.column-1[regular-site]=
    layout.static.portlets.end.column-1[regular-site]=
    layout.static.portlets.start.column-2[regular-site]=
    layout.static.portlets.end.column-2[regular-site]=
    layout.static.portlets.start.column-3[regular-site]=
    layout.static.portlets.end.column-3[regular-site]=

Set the static portlets for the pages of organization sites.

Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER1__OPENBRACKET_ORGANIZATION_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER2__OPENBRACKET_ORGANIZATION_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_END_PERIOD_COLUMN_MINUS__NUMBER3__OPENBRACKET_ORGANIZATION_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER1__OPENBRACKET_ORGANIZATION_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER2__OPENBRACKET_ORGANIZATION_CLOSEBRACKET_ Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_START_PERIOD_COLUMN_MINUS__NUMBER3__OPENBRACKET_ORGANIZATION_CLOSEBRACKET_

    layout.static.portlets.start.column-1[organization]=
    layout.static.portlets.end.column-1[organization]=
    layout.static.portlets.start.column-2[organization]=
    layout.static.portlets.end.column-2[organization]=
    layout.static.portlets.start.column-3[organization]=
    layout.static.portlets.end.column-3[organization]=

Set the static portlets that will appear for every layout. See layout_common taglib for the logic of when these portlets will be shown. For example, these portlets will only show for layouts that can contain portlets and are not in a pop up state.

Env: LIFERAY_LAYOUT_PERIOD_STATIC_PERIOD_PORTLETS_PERIOD_ALL

    layout.static.portlets.all=

Set the private group, private user, and public servlet mapping for com.liferay.friendly.url.internal.servlet.PrivateGroupFriendlyURLServlet, com.liferay.friendly.url.internal.servlet.PrivateUserFriendlyURLServlet, com.liferay.friendly.url.internal.servlet.PublicFriendlyURLServlet respectively. These values must match the value of the property osgi.http.whiteboard.servlet.pattern in component respectively.

For example, if the private group pages are mapped to "/group" and the group's friendly URL is set to "/guest" and the layout's friendly URL is set to "/company/community", then the friendly URL for the page will be http://www.liferay.com/group/guest/company/community. Private group pages map to a site's private pages and are only available to authenticated users with the proper permissions.

For example, if the public pages are mapped to "/web" and the group or user's friendly URL is set to "/guest" and the layout's friendly URL is set to "/company/community", then the friendly URL for the page will be http://www.liferay.com/web/guest/company/community. Public pages are available to unauthenticated users.

The friendly URL's for users, groups, and layouts can be set during runtime.

Env: LIFERAY_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_PRIVATE_PERIOD_GROUP_PERIOD_SERVLET_PERIOD_MAPPING Env: LIFERAY_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_PRIVATE_PERIOD_USER_PERIOD_SERVLET_PERIOD_MAPPING Env: LIFERAY_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_PUBLIC_PERIOD_SERVLET_PERIOD_MAPPING

    layout.friendly.url.private.group.servlet.mapping=/group
    layout.friendly.url.private.user.servlet.mapping=/user
    layout.friendly.url.public.servlet.mapping=/web

Redirect to this resource if the user requested a friendly URL of a page that does not exist. Leave it blank to display nothing.

A similar configuration for sites is managed with the property "sites.friendly.url.page.not.found".

Note: For backward compatibility, this overrides the property "layout.show.http.status" for the 404 status code.

Env: LIFERAY_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_PAGE_PERIOD_NOT_PERIOD_FOUND

    layout.friendly.url.page.not.found=/html/portal/404.html

Set the reserved keywords that cannot be used in a friendly URL.

Env: LIFERAY_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL_PERIOD_KEYWORDS

    layout.friendly.url.keywords=\
        _vti_*,\
        a,\
        api*,\
        c,\
        combo,\
        delegate,\
        display_chart*,\
        dtd,\
        elqNow,\
        facebook,\
        google_gadget,\
        group,\
        html,\
        image,\
        language,\
        lucene,\
        netvibes,\
        o,\
        osgi,\
        page,\
        pbhs,\
        poller,\
        private,\
        public,\
        rest,\
        robots.txt,\
        sharepoint*,\
        sitemap.xml,\
        sprite,\
        tunnel-web,\
        user,\
        wap,\
        web,\
        webdav*,\
        widget*,\
        xmlrpc

Set this to true if guest users should see the maximize window icon.

Env: LIFERAY_LAYOUT_PERIOD_GUEST_PERIOD_SHOW_PERIOD_MAX_PERIOD_ICON

    layout.guest.show.max.icon=false

Set this to true if guest users should see the minimize window icon.

Env: LIFERAY_LAYOUT_PERIOD_GUEST_PERIOD_SHOW_PERIOD_MIN_PERIOD_ICON

    layout.guest.show.min.icon=false

Set this to true if users are shown that they do not have access to a portlet. The portlet init parameter "show-portlet-access-denied" will override this setting.

Env: LIFERAY_LAYOUT_PERIOD_SHOW_PERIOD_PORTLET_PERIOD_ACCESS_PERIOD_DENIED

    layout.show.portlet.access.denied=true

Set this to true if users are shown that a portlet is inactive. The portlet init parameter "show-portlet-inactive" will override this setting.

Env: LIFERAY_LAYOUT_PERIOD_SHOW_PERIOD_PORTLET_PERIOD_INACTIVE

    layout.show.portlet.inactive=true

Set this to true if the portal should show HTTP status codes like 404 if the requested page is not found.

Env: LIFERAY_LAYOUT_PERIOD_SHOW_PERIOD_HTTP_PERIOD_STATUS

    layout.show.http.status=true

Set the default layout template ID used when creating layouts.

Env: LIFERAY_LAYOUT_PERIOD_DEFAULT_PERIOD_TEMPLATE_PERIOD_ID

    layout.default.template.id=2_columns_ii

Set this to false to disable ajax rendering. You can also disable it on a per request basis by setting the attribute key com.liferay.portal.kernel.util.WebKeys.PORTLET_AJAXABLE_RENDER to the Boolean.FALSE in a pre service event or by setting the URL parameter "p_p_ajax" to "0". See the property "session.disabled" on how that property effects this property.

Env: LIFERAY_LAYOUT_PERIOD_AJAX_PERIOD_RENDER_PERIOD_ENABLE

    layout.ajax.render.enable=true

Set this to false to disable server side parallel rendering. You can also disable it on a per request basis by setting the attribute key com.liferay.portal.kernel.util.WebKeys.PORTLET_PARALLEL_RENDER to the Boolean.FALSE in a pre service event or by setting the URL parameter "p_p_parallel" to "0".

Set this to true to forcibly set the property "portlet.container.restrict" to true, as server side parallel rendering requires restricted request attributes.

This feature is only available for Tomcat and will be ignored when the portal is running in other environments.

This property is deprecated and only provided for documentation purposes.

Env: LIFERAY_LAYOUT_PERIOD_PARALLEL_PERIOD_RENDER_PERIOD_ENABLE

    layout.parallel.render.enable=false

Set the number of core threads used for server side parallel rendering.

Env: LIFERAY_LAYOUT_PERIOD_PARALLEL_PERIOD_RENDER_PERIOD_THREAD_PERIOD_POOL_PERIOD_CORE_PERIOD_THREAD_PERIOD_COUNT

    layout.parallel.render.thread.pool.core.thread.count=1

Set the time in seconds to keep a thread alive for server side parallel rendering.

Env: LIFERAY_LAYOUT_PERIOD_PARALLEL_PERIOD_RENDER_PERIOD_THREAD_PERIOD_POOL_PERIOD_KEEP_PERIOD_ALIVE_PERIOD_TIME

    layout.parallel.render.thread.pool.keep.alive.time=600

Set the maximum size of the task queue for server side parallel rendering. An unbounded queue size will never trigger RejectedExecutionHandler. Under heavy load, this will lead to massive memory usage. A bounded queue size with a proper RejectedExecutionHandler can help the server perform graceful degradation.

Env: LIFERAY_LAYOUT_PERIOD_PARALLEL_PERIOD_RENDER_PERIOD_THREAD_PERIOD_POOL_PERIOD_MAX_PERIOD_QUEUE_PERIOD_SIZE

    layout.parallel.render.thread.pool.max.queue.size=100

Set the maximum number of threads used for server side parallel rendering.

Env: LIFERAY_LAYOUT_PERIOD_PARALLEL_PERIOD_RENDER_PERIOD_THREAD_PERIOD_POOL_PERIOD_MAX_PERIOD_THREAD_PERIOD_COUNT

    layout.parallel.render.thread.pool.max.thread.count=20

Set the timeout time for server side parallel rendering. On timeout, all pending portlets will fail back to ajax loading or trigger an error message depending on whether the portlets are ajaxable.

This timeout is an int value rather than long to avoid some atomic set race condition. The Integer.MAX_VALUE is more than enough for a reasonable timeout.

Env: LIFERAY_LAYOUT_PERIOD_PARALLEL_PERIOD_RENDER_PERIOD_TIMEOUT

    layout.parallel.render.timeout=5000

Set the name of a class that implements com.liferay.portal.util.LayoutClone. This class is used to remember maximized and minimized states on shared pages. The default implementation persists the state in the browser session.

Env: LIFERAY_LAYOUT_PERIOD_CLONE_PERIOD_IMPL

    layout.clone.impl=com.liferay.portal.util.SessionLayoutClone

Set this to true to cache the content of layout templates. This is recommended because it improves performance for production servers. Setting it to false is useful during development if you need to make a lot of changes.

Env: LIFERAY_LAYOUT_PERIOD_TEMPLATE_PERIOD_CACHE_PERIOD_ENABLED

    layout.template.cache.enabled=true

Set the default value for the "p_l_reset" parameter. If set to true, render parameters are cleared when different pages are hit. This is not the behavior promoted by the portlet specification, but is the one that most end users seem to prefer.

Env: LIFERAY_LAYOUT_PERIOD_DEFAULT_PERIOD_P_UNDERLINE_L_UNDERLINE_RESET

    layout.default.p_l_reset=true

Set this to true to enable comments for pages.

Env: LIFERAY_LAYOUT_PERIOD_COMMENTS_PERIOD_ENABLED

    layout.comments.enabled=true

Set this to true to remember maximized window states across different pages.

Env: LIFERAY_LAYOUT_PERIOD_REMEMBER_PERIOD_MAXIMIZED_PERIOD_WINDOW_PERIOD_STATE

    layout.remember.maximized.window.state=false

Set the initial number of child pages to display in the Manage Pages tree. Set this to -1 to show all.

Env: LIFERAY_LAYOUT_PERIOD_MANAGE_PERIOD_PAGES_PERIOD_INITIAL_PERIOD_CHILDREN

    layout.manage.pages.initial.children=20

Set this to true to enable finding scoped layouts with a table join of the Layout and Group_ tables which is not cached. Set this to false to allow in memory joining. Conditional memory joining can be customized with the property "layout.scope.group.finder.threshold".

Env: LIFERAY_LAYOUT_PERIOD_SCOPE_PERIOD_GROUP_PERIOD_FINDER_PERIOD_ENABLED

    layout.scope.group.finder.enabled=true

Set the threshold for when to use in memory joining. In memory joining will be used when the number of scoped layouts is less than the threshold. Setting the value to negative will ensure in memory joining is always used. This property is ignored if "layout.scope.group.finder.enabled" is set to false.

Env: LIFERAY_LAYOUT_PERIOD_SCOPE_PERIOD_GROUP_PERIOD_FINDER_PERIOD_THRESHOLD

    layout.scope.group.finder.threshold=100

Layout Prototypes

Set this to true to enable the propagation of changes to a page from its page template by default.

Env: LIFERAY_LAYOUT_PERIOD_PROTOTYPE_PERIOD_LINK_PERIOD_ENABLED_PERIOD_DEFAULT

    layout.prototype.link.enabled.default=true

In the case that a page template would fail to merge, make sure that we prevent repeated attempts that will inevitably fail by setting a fail threshold.

Env: LIFERAY_LAYOUT_PERIOD_PROTOTYPE_PERIOD_MERGE_PERIOD_FAIL_PERIOD_THRESHOLD

    layout.prototype.merge.fail.threshold=3

Set the number of seconds we should expect a lock to last before we recognize that an error occurred and some other process should be able to attempt to take it over.

Env: LIFERAY_LAYOUT_PERIOD_PROTOTYPE_PERIOD_MERGE_PERIOD_LOCK_PERIOD_MAX_PERIOD_TIME

    layout.prototype.merge.lock.max.time=300

Layout Set Prototypes

In the case that a site template would fail to merge, make sure that we prevent repeated attempts that will inevitably fail by setting a fail threshold.

Env: LIFERAY_LAYOUT_PERIOD_SET_PERIOD_PROTOTYPE_PERIOD_MERGE_PERIOD_FAIL_PERIOD_THRESHOLD

    layout.set.prototype.merge.fail.threshold=3

Set the number of seconds we should expect a lock to last before we recognize that an error occurred and some other process should be able to attempt to take it over.

Env: LIFERAY_LAYOUT_PERIOD_SET_PERIOD_PROTOTYPE_PERIOD_MERGE_PERIOD_LOCK_PERIOD_MAX_PERIOD_TIME

    layout.set.prototype.merge.lock.max.time=600

Set this to true to propagate a site template's logo to a site when the propagation of changes is enabled. Set this to false to propagate a site template's logo only when a site is first created from its site template. Further changes to a site template's logo is not propagated even if the propagation of changes is enabled.

Env: LIFERAY_LAYOUT_PERIOD_SET_PERIOD_PROTOTYPE_PERIOD_PROPAGATE_PERIOD_LOGO

    layout.set.prototype.propagate.logo=false

Portlet URL

Set this to true if calling setParameter on a portlet URL appends the parameter value versus replacing it. There is some disagreement in the interpretation of the JSR 168 spec among portlet developers over this specific behavior. Liferay Portal successfully passes the portlet TCK tests whether this value is set to true or false.

See https://issues.liferay.com/browse/LEP-426 for more information.

Env: LIFERAY_PORTLET_PERIOD_URL_PERIOD_APPEND_PERIOD_PARAMETERS

    portlet.url.append.parameters=false

Set this to true to allow portlet URLs to generate with an anchor tag.

Env: LIFERAY_PORTLET_PERIOD_URL_PERIOD_ANCHOR_PERIOD_ENABLE

    portlet.url.anchor.enable=false

JSR 286 specifies that portlet URLs are escaped by default. Set this to false to provide for better backwards compatibility.

If this is set to true, but a specific portlet application requires that its portlet URLs not be escaped by default, then modify portlet.xml and set the container runtime option "javax.portlet.escapeXml" to false.

Env: LIFERAY_PORTLET_PERIOD_URL_PERIOD_ESCAPE_PERIOD_XML

    portlet.url.escape.xml=false

Set a list of comma delimited reserved parameters that will not be added to refresh URL.

Env: LIFERAY_PORTLET_PERIOD_URL_PERIOD_REFRESH_PERIOD_URL_PERIOD_RESERVED_PERIOD_PARAMETERS

    portlet.url.refresh.url.reserved.parameters=\
        password,\
        password1,\
        password2,\
        pop3Password,\
        properties--jdbc.default.password,\
        settings--google.apps.password,\
        smtpPassword,\
        settings--ldap.security.credentials

Set this to true to allow portlet URLs to be generated using /c/portal/portlet_url. Enabling can pose a security risk.

Env: LIFERAY_PORTLET_PERIOD_URL_PERIOD_GENERATE_PERIOD_BY_PERIOD_PATH_PERIOD_ENABLED

    portlet.url.generate.by.path.enabled=false

Preferences

Set this to true to validate portlet preferences on startup.

Env: LIFERAY_PREFERENCE_PERIOD_VALIDATE_PERIOD_ON_PERIOD_STARTUP

    preference.validate.on.startup=false

Redirect

Set this property to "ip" or "domain" for the redirect security method. If set to "domain", the portal will only redirect users to domains listed in the property "redirect.url.domain.allowed". If set to "ip", the portal will only redirect to domains whose IP address resolve to an IP address listed in the property "redirect.url.ip.allowed".

Env: LIFERAY_REDIRECT_PERIOD_URL_PERIOD_SECURITY_PERIOD_MODE

    redirect.url.security.mode=ip

    redirect.url.security.mode=domain

Input a list of comma delimited domains which the portal is allowed to redirect to. Input a blank list to allow any domain. Specifying a domain with a leading "*." allows redirects to subdomains.

Env: LIFERAY_REDIRECT_PERIOD_URL_PERIOD_DOMAINS_PERIOD_ALLOWED

    redirect.url.domains.allowed=

Input a list of comma delimited IPs which the portal is allowed to redirect to. Input a blank list to allow any IP. SERVER_IP will be replaced with the IP of the host server.

Env: LIFERAY_REDIRECT_PERIOD_URL_PERIOD_IPS_PERIOD_ALLOWED

    redirect.url.ips.allowed=\
        127.0.0.1,\
        SERVER_IP

Images

Set this to true if the Image servlet will automatically scale an image based on the request "height" and "width" parameters.

Env: LIFERAY_IMAGE_PERIOD_AUTO_PERIOD_SCALE

    image.auto.scale=false

Set the location of the default spacer image that is used for missing images. This image must be available in the class path.

Env: LIFERAY_IMAGE_PERIOD_DEFAULT_PERIOD_SPACER

    image.default.spacer=com/liferay/portal/dependencies/spacer.gif

Set the location of the default company logo image that is used for missing company logo images. This image must be available in the class path.

Env: LIFERAY_IMAGE_PERIOD_DEFAULT_PERIOD_COMPANY_PERIOD_LOGO

    image.default.company.logo=com/liferay/portal/dependencies/company_logo.png

Set the location of the default organization logo image that is used for missing organization logo images. This image must be available in the class path.

Env: LIFERAY_IMAGE_PERIOD_DEFAULT_PERIOD_ORGANIZATION_PERIOD_LOGO

    image.default.organization.logo=com/liferay/portal/dependencies/organization_logo.png

Set the locations of the default user portrait images that are used for missing user portrait images. This image must be available in the class path.

Env: LIFERAY_IMAGE_PERIOD_DEFAULT_PERIOD_USER_PERIOD_FEMALE_PERIOD_PORTRAIT Env: LIFERAY_IMAGE_PERIOD_DEFAULT_PERIOD_USER_PERIOD_MALE_PERIOD_PORTRAIT Env: LIFERAY_IMAGE_PERIOD_DEFAULT_PERIOD_USER_PERIOD_PORTRAIT

    image.default.user.female.portrait=com/liferay/portal/dependencies/user_female_portrait.png
    image.default.user.male.portrait=com/liferay/portal/dependencies/user_male_portrait.png
    image.default.user.portrait=com/liferay/portal/dependencies/user_portrait.png

In versions prior to 6.1, the Image Gallery portlet supported persisting images via com.liferay.portal.image.DatabaseHook, com.liferay.portal.image.DLHook, or com.liferay.portal.image.FileSystemHook. Since 6.1, only DLHook is supported.

Set this property to the hook implementation to trigger automatic data migration during an upgrade.

Env: LIFERAY_IMAGE_PERIOD_HOOK_PERIOD_IMPL

    image.hook.impl=com.liferay.portal.image.DatabaseHook
    image.hook.impl=com.liferay.portal.image.DLHook
    image.hook.impl=com.liferay.portal.image.FileSystemHook

This is a legacy property used by the FileSystemHook to allow data migration from other hooks.

Env: LIFERAY_IMAGE_PERIOD_HOOK_PERIOD_FILE_PERIOD_SYSTEM_PERIOD_ROOT_PERIOD_DIR

    image.hook.file.system.root.dir=${liferay.home}/data/images

ImageIO's stream cache may reside in memory or on the file system. Setting this to false tells ImageIO to use memory for caching. Memory caches offer better performance since nothing is written to the file system. However, memory is usually more limited and more expensive.

Env: LIFERAY_IMAGE_PERIOD_IO_PERIOD_USE_PERIOD_DISK_PERIOD_CACHE

    image.io.use.disk.cache=false

Set the maximum image height and width in pixels that can be read by the image tool. A value of 0 indicates no restrictions. See LPS-63358 for more information.

Env: LIFERAY_IMAGE_PERIOD_TOOL_PERIOD_IMAGE_PERIOD_MAX_PERIOD_HEIGHT Env: LIFERAY_IMAGE_PERIOD_TOOL_PERIOD_IMAGE_PERIOD_MAX_PERIOD_WIDTH

    image.tool.image.max.height=10000
    image.tool.image.max.width=10000

Editors

You can configure individual JSP pages to use a specific implementation of the available WYSIWYG editors: alloyeditor, alloyeditor_bbcode, alloyeditor_creole, ckeditor, ckeditor_bbcode, ckeditor_creole, simple, tinymce, or tinymce_simple.

Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_DEFAULT Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_IMPL_PERIOD_PORTLET_PERIOD_DDM_PERIOD_TEXT_UNDERLINE_HTML_PERIOD_FTL Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_PORTLET_PERIOD_ANNOUNCEMENTS_PERIOD_EDIT_UNDERLINE_ENTRY_PERIOD_JSP Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_PORTLET_PERIOD_BLOGS_PERIOD_EDIT_UNDERLINE_ENTRY_PERIOD_JSP Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_PORTLET_PERIOD_MAIL_PERIOD_EDIT_PERIOD_JSP Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_PORTLET_PERIOD_MAIL_PERIOD_EDIT_UNDERLINE_MESSAGE_PERIOD_JSP Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_PORTLET_PERIOD_MESSAGE_UNDERLINE_BOARDS_PERIOD_EDIT_UNDERLINE_MESSAGE_PERIOD_BB_UNDERLINE_CODE_PERIOD_JSP Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_PORTLET_PERIOD_MESSAGE_UNDERLINE_BOARDS_PERIOD_EDIT_UNDERLINE_MESSAGE_PERIOD_HTML_PERIOD_JSP Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_TAGLIB_PERIOD_UI_PERIOD_DISCUSSION_PERIOD_JSP Env: LIFERAY_EDITOR_PERIOD_WYSIWYG_PERIOD_PORTAL_MINUS_WEB_PERIOD_DOCROOT_PERIOD_HTML_PERIOD_TAGLIB_PERIOD_UI_PERIOD_EMAIL_UNDERLINE_NOTIFICATION_UNDERLINE_SETTINGS_PERIOD_JSP

    editor.wysiwyg.default=ckeditor
    editor.wysiwyg.portal-impl.portlet.ddm.text_html.ftl=alloyeditor
    editor.wysiwyg.portal-web.docroot.html.portlet.announcements.edit_entry.jsp=alloyeditor
    editor.wysiwyg.portal-web.docroot.html.portlet.blogs.edit_entry.jsp=alloyeditor
    editor.wysiwyg.portal-web.docroot.html.portlet.mail.edit.jsp=ckeditor
    editor.wysiwyg.portal-web.docroot.html.portlet.mail.edit_message.jsp=ckeditor
    editor.wysiwyg.portal-web.docroot.html.portlet.message_boards.edit_message.bb_code.jsp=alloyeditor_bbcode
    editor.wysiwyg.portal-web.docroot.html.portlet.message_boards.edit_message.html.jsp=alloyeditor
    editor.wysiwyg.portal-web.docroot.html.taglib.ui.discussion.jsp=alloyeditor
    editor.wysiwyg.portal-web.docroot.html.taglib.ui.email_notification_settings.jsp=ckeditor

Fields

Set the following fields to false so users cannot see them. Some company policies require gender and birthday information to always be hidden.

Env: LIFERAY_FIELD_PERIOD_ENABLE_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEC_ONTACT_PERIOD_BIRTHDAY Env: LIFERAY_FIELD_PERIOD_ENABLE_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEC_ONTACT_PERIOD_MALE Env: LIFERAY_FIELD_PERIOD_ENABLE_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT_PERIOD_JAVASCRIPT Env: LIFERAY_FIELD_PERIOD_ENABLE_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT_UPPERCASES_ET_PERIOD_JAVASCRIPT Env: LIFERAY_FIELD_PERIOD_ENABLE_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEO_RGANIZATION_PERIOD_STATUS

    field.enable.com.liferay.portal.kernel.model.Contact.male=false
    field.enable.com.liferay.portal.kernel.model.Contact.birthday=true
    field.enable.com.liferay.portal.kernel.model.Layout.javascript=true
    field.enable.com.liferay.portal.kernel.model.LayoutSet.javascript=true
    field.enable.com.liferay.portal.kernel.model.Organization.status=false

Input a list of comma delimited user types. Users that match one of these user types have permission to edit all of their own fields. Valid user types are "user-with-mx" and "user-without-mx". A value of "user-with-mx" is a user who has an email address that matches the company mail suffix, and "user-without-mx" is a user who does not have an email address that matches the company mail suffix.

Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_USER_PERIOD_TYPES

    field.editable.user.types=\
        user-with-mx,\
        user-without-mx

Input a list of comma delimited role names. Users associated with one of these roles have permission to edit all of their own fields.

Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_ROLES

    field.editable.roles=administrator

Input a list of comma delimited domain names. Users with an email address that match one of these domain names have permission to edit all of their own fields.

Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS

    field.editable.domains=

Input a list of comma delimited domain names. Users with an email address that match one of these domain names have permission to edit the specified field. Input "*" to allow all users to modify the specified field.

Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_BIRTHDAY_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_EMAIL_UPPERCASEA_DDRESS_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_FIRST_UPPERCASEN_AME_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_GENDER_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_JOB_UPPERCASET_ITLE_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_LAST_UPPERCASEN_AME_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_MIDDLE_UPPERCASEN_AME_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_PORTRAIT_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_PREFIX_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_SCREEN_UPPERCASEN_AME_CLOSEBRACKET_ Env: LIFERAY_FIELD_PERIOD_EDITABLE_PERIOD_DOMAINS_OPENBRACKET_SUFFIX_CLOSEBRACKET_

    field.editable.domains[birthday]=
    field.editable.domains[emailAddress]=
    field.editable.domains[firstName]=
    field.editable.domains[gender]=
    field.editable.domains[jobTitle]=
    field.editable.domains[lastName]=
    field.editable.domains[middleName]=
    field.editable.domains[portrait]=
    field.editable.domains[prefix]=
    field.editable.domains[screenName]=
    field.editable.domains[suffix]=

Mime Types

Input a list of comma delimited extensions for which the content disposition header has to be set to "inline". Note that including "swf" in the list may expose you to a CSRF attack.

Env: LIFERAY_MIME_PERIOD_TYPES_PERIOD_CONTENT_PERIOD_DISPOSITION_PERIOD_INLINE

    mime.types.content.disposition.inline=\
        flv,\
        gif,\
        jpg,\
        pdf,\
        png,\
        wmv

Input a list of comma delimited MIME types that are optimized for displaying images on the Internet. One of the use cases for this property is to limit the image file types that a user can upload as a company logo, organization logo, or user portrait.

Env: LIFERAY_MIME_PERIOD_TYPES_PERIOD_WEB_PERIOD_IMAGES

    mime.types.web.images=\
        image/gif,\
        image/jpeg,\
        image/pjpeg,\
        image/png,\
        image/x-png

Browser Cache

Set this to true if you want the portal to force the browser cache to be disabled. It will only disable the cache for the rendered HTML response. It will not have an impact on static content or other resources.

Env: LIFERAY_BROWSER_PERIOD_CACHE_PERIOD_DISABLED

    browser.cache.disabled=true

Set this true if you want to disable the cache for authenticated users. This property is not read when the property "browser.cache.signed.in.disabled" is true. This is useful to ensure that authenticated users cannot go to the sign in page by clicking on the back button in their browsers.

Env: LIFERAY_BROWSER_PERIOD_CACHE_PERIOD_SIGNED_PERIOD_IN_PERIOD_DISABLED

    browser.cache.signed.in.disabled=true

Browser Compatibility

Enter which versions of IE your browser should emulate to render the portal. Enter "edge" to always use IE's latest standards rendering mode.

Env: LIFERAY_BROWSER_PERIOD_COMPATIBILITY_PERIOD_IE_PERIOD_VERSIONS

    browser.compatibility.ie.versions=IE=edge

Browser Launcher

Enter a URL to automatically launch a browser to that URL when the portal has fully initialized. Enter a blank URL to disable this feature.

Env: LIFERAY_BROWSER_PERIOD_LAUNCHER_PERIOD_URL

    browser.launcher.url=http://localhost:8080

Control Panel

Set the name of the layout.

Env: LIFERAY_CONTROL_PERIOD_PANEL_PERIOD_LAYOUT_PERIOD_NAME

    control.panel.layout.name=Control Panel

Set the friendly URL of the layout.

Env: LIFERAY_CONTROL_PERIOD_PANEL_PERIOD_LAYOUT_PERIOD_FRIENDLY_PERIOD_URL

    control.panel.layout.friendly.url=/manage

Set the theme of the layout.

Env: LIFERAY_CONTROL_PERIOD_PANEL_PERIOD_LAYOUT_PERIOD_REGULAR_PERIOD_THEME_PERIOD_ID

    control.panel.layout.regular.theme.id=admin_WAR_admintheme

Set the maximum number of sites that will be shown in the navigation menus. A large value might cause performance problems if the number of sites a user can administer is very large.

Env: LIFERAY_CONTROL_PERIOD_PANEL_PERIOD_NAVIGATION_PERIOD_MAX_PERIOD_SITES

    control.panel.navigation.max.sites=100

Set the name of a class that implements com.liferay.portal.kernel.portlet.ControlPanelEntry. This class denotes the default value of of the element "control-panel-entry-class" in liferay-portlet.xml and is called by the Control Panel to decide whether the portlet should be shown to a specific user in a specific context.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_CONTROL_PERIOD_PANEL_PERIOD_DEFAULT_PERIOD_ENTRY_PERIOD_CLASS

    control.panel.default.entry.class=com.liferay.portal.kernel.portlet.DefaultControlPanelEntry

Lucene Search

Set this to true to enable spell checking the query.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_COLLATED_PERIOD_SPELL_PERIOD_CHECK_PERIOD_RESULT_PERIOD_ENABLED

    index.search.collated.spell.check.result.enabled=true

Set the limit for considering the returned results as valid. When this threshold is not met, the most relevant spell checked query will be displayed.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_COLLATED_PERIOD_SPELL_PERIOD_CHECK_PERIOD_RESULT_PERIOD_SCORES_PERIOD_THRESHOLD

    index.search.collated.spell.check.result.scores.threshold=50

Set the fragment size returned from the search result highlighter.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_HIGHLIGHT_PERIOD_FRAGMENT_PERIOD_SIZE

    index.search.highlight.fragment.size=80

Set this to true to require field match when highlighting.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_HIGHLIGHT_PERIOD_REQUIRE_PERIOD_FIELD_PERIOD_MATCH

    index.search.highlight.require.field.match=true

Set the number of lines for the snippet returned by a search engine.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_HIGHLIGHT_PERIOD_SNIPPET_PERIOD_SIZE

    index.search.highlight.snippet.size=3

Set the limit for results used when performing index searches.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_LIMIT

    index.search.limit=10000

Set this to true to enable indexing of related queries based on successful searches. This does not affect indexing of related queries in the search portlet. To control indexing of related queries in the search portlet, configure the search portlet preferences.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_INDEXING_PERIOD_ENABLED

    index.search.query.indexing.enabled=false

Set the limit for considering the returned results as valid. When this threshold is met, the query will be indexed as related query.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_INDEXING_PERIOD_THRESHOLD

    index.search.query.indexing.threshold=50

Set the location of the query suggestion dictionary files for specific locales. Specify a comma delimited list of files if a locale has more than one dictionary file. A group ID (e.g. 123456) can also be added to specify a dictionary that only applies to one group.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_SUGGESTION_PERIOD_DICTIONARY_OPENBRACKET_EN_UNDERLINE__UPPERCASEU__UPPERCASES__CLOSEBRACKET_ Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_SUGGESTION_PERIOD_DICTIONARY_OPENBRACKET_EN_UNDERLINE__UPPERCASEU__UPPERCASES__CLOSEBRACKET__OPENBRACKET__NUMBER1__NUMBER2__NUMBER3__NUMBER4__NUMBER5__NUMBER6__CLOSEBRACKET_ Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_SUGGESTION_PERIOD_DICTIONARY_OPENBRACKET_ES_UNDERLINE__UPPERCASEE__UPPERCASES__CLOSEBRACKET_

    index.search.query.suggestion.dictionary[en_US]=com/liferay/portal/search/dependencies/querysuggestions/en_US.txt
    index.search.query.suggestion.dictionary[es_ES]=com/liferay/portal/search/dependencies/querysuggestions/es_ES.txt
    index.search.query.suggestion.dictionary[en_US][123456]=com/liferay/portal/search/dependencies/querysuggestions/en_US_123456.txt

Set this to true to enable query suggestion if insufficient scoring or no results are returned for the user's original query. This does not affect suggestion in the search portlet. To control suggestion in the search portlet, configure the search portlet preferences.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_SUGGESTION_PERIOD_ENABLED

    index.search.query.suggestion.enabled=false

Set the maximum number of query suggestions.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_SUGGESTION_PERIOD_MAX

    index.search.query.suggestion.max=5

Set the limit of the search result score for triggering query suggestions. Setting this to 0 will ignore scoring thresholds and only suggest queries if no results are returned for the original search query.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_QUERY_PERIOD_SUGGESTION_PERIOD_SCORES_PERIOD_THRESHOLD

    index.search.query.suggestion.scores.threshold=0

Set this to true to enable scoring of results.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_SCORING_PERIOD_ENABLED

    index.search.scoring.enabled=true

Set the location of the spell checker dictionary files for specific locales. Specify a comma delimited list of files if a locale has more than one dictionary file. A group ID (e.g. 123456) can also be added to specify a dictionary that only applies to one group.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_SPELL_PERIOD_CHECKER_PERIOD_DICTIONARY_OPENBRACKET_EN_UNDERLINE__UPPERCASEU__UPPERCASES__CLOSEBRACKET_ Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_SPELL_PERIOD_CHECKER_PERIOD_DICTIONARY_OPENBRACKET_EN_UNDERLINE__UPPERCASEU__UPPERCASES__CLOSEBRACKET__OPENBRACKET__NUMBER1__NUMBER2__NUMBER3__NUMBER4__NUMBER5__NUMBER6__CLOSEBRACKET_ Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_SPELL_PERIOD_CHECKER_PERIOD_DICTIONARY_OPENBRACKET_ES_UNDERLINE__UPPERCASEE__UPPERCASES__CLOSEBRACKET_

    index.search.spell.checker.dictionary[en_US]=com/liferay/portal/search/dependencies/spellchecker/en_US.txt
    index.search.spell.checker.dictionary[es_ES]=com/liferay/portal/search/dependencies/spellchecker/es_ES.txt

    index.search.spell.checker.dictionary[en_US][123456]=com/liferay/portal/search/dependencies/spellchecker/en_US_123456.txt

Specify the locales supported by the spell checker. This is used by the search engine's spell checker when determining whether to execute spell checking for a particular language.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_SPELL_PERIOD_CHECKER_PERIOD_SUPPORTED_PERIOD_LOCALES

    index.search.spell.checker.supported.locales=\
        en_US,\
        es_ES

Specify the maximum queue size of the index search writer. Set this to a negative value to allow the queue size to grow until the server runs out of memory.

Env: LIFERAY_INDEX_PERIOD_SEARCH_PERIOD_WRITER_PERIOD_MAX_PERIOD_QUEUE_PERIOD_SIZE

    index.search.writer.max.queue.size=1000

Set the amplification factor for permission filtered searches, it must be a number that is larger than 1.

Env: LIFERAY_INDEX_PERIOD_PERMISSION_PERIOD_FILTER_PERIOD_SEARCH_PERIOD_AMPLIFICATION_PERIOD_FACTOR

    index.permission.filter.search.amplification.factor=1.5

Set this to false to disable an indexer with given name by default, otherwise all indexers are enabled by default. This setting can be overridden in portal preferences by enabling or disabling the indexer in the control panel.

Env: LIFERAY_INDEXER_PERIOD_ENABLED_OPENBRACKET_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEU_SER_CLOSEBRACKET_

    indexer.enabled[com.liferay.portal.kernel.model.User]=false

Set this to true if you want to index your entire library of files on startup. This property is available so that automated test environments index on startup. Do not set this to true on production systems or else your index will be indexed on every startup.

Env: LIFERAY_INDEX_PERIOD_ON_PERIOD_STARTUP

    index.on.startup=false

Set this to true to add a delay before indexing on startup. A delay may be necessary if a lot of plugins need to be loaded and reindexed. This property is only valid if "index.on.startup" is set to true.

Env: LIFERAY_INDEX_PERIOD_ON_PERIOD_STARTUP_PERIOD_DELAY

    index.on.startup.delay=60

Set this to true if you want to index your entire library of files after an upgrade. Only set this property to false if you are running a small upgrade and you do not need to reindex everything.

Env: LIFERAY_INDEX_PERIOD_ON_PERIOD_UPGRADE

    index.on.upgrade=true

Set this to true if you want the indexing on startup to be executed on a separate thread to speed up execution.

Env: LIFERAY_INDEX_PERIOD_WITH_PERIOD_THREAD

    index.with.thread=true

Set the date format used for storing dates as text in the index.

Env: LIFERAY_INDEX_PERIOD_DATE_PERIOD_FORMAT_PERIOD_PATTERN

    index.date.format.pattern=yyyyMMddHHmmss

Set this to true if you want to compress index files before they are dumped.

Env: LIFERAY_INDEX_PERIOD_DUMP_PERIOD_COMPRESSION_PERIOD_ENABLED

    index.dump.compression.enabled=true

Enter a list of comma delimited field names that will be copied to an untokenized field for sorting.

Env: LIFERAY_INDEX_PERIOD_SORTABLE_PERIOD_TEXT_PERIOD_FIELDS

    index.sortable.text.fields=\
        firstName,\
        jobTitle,\
        lastName,\
        name,\
        screenName,\
        title

Set the maximum length for sortable keyword fields before they are truncated.

Env: LIFERAY_INDEX_PERIOD_SORTABLE_PERIOD_TEXT_PERIOD_FIELDS_PERIOD_TRUNCATED_PERIOD_LENGTH

    index.sortable.text.fields.truncated.length=255

Set the maximum number of clauses to allow in a boolean query. The default is 1024.

Env: LIFERAY_LUCENE_PERIOD_BOOLEAN_PERIOD_QUERY_PERIOD_CLAUSE_PERIOD_MAX_PERIOD_SIZE

    lucene.boolean.query.clause.max.size=1024

Multi Value Map

Set the multi value map property to 0 to store the map in memory and 1 to store the map in the file system.

Env: LIFERAY_MULTI_PERIOD_VALUE_PERIOD_MAP_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_CONVERT_PERIOD__UPPERCASEC_ONVERT_UPPERCASEP_ERMISSION_UPPERCASEA_LGORITHM_PERIOD_CONVERT_UPPERCASER_ESOURCE_UPPERCASEP_ERMISSION Env: LIFERAY_MULTI_PERIOD_VALUE_PERIOD_MAP_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_CONVERT_PERIOD__UPPERCASEC_ONVERT_UPPERCASEP_ERMISSION_UPPERCASEA_LGORITHM_PERIOD_CONVERT_UPPERCASER_OLES

    multi.value.map.com.liferay.portal.convert.ConvertPermissionAlgorithm.convertResourcePermission=0
    multi.value.map.com.liferay.portal.convert.ConvertPermissionAlgorithm.convertRoles=0

Setup Wizard

Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_DB_NUMBER2__CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_HYPERSONIC_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_MARIADB_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_MYSQL_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_ORACLE_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_POSTGRESQL_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_SQLSERVER_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME_OPENBRACKET_SYBASE_CLOSEBRACKET_

    setup.database.driverClassName[db2]=com.ibm.db2.jcc.DB2Driver
    setup.database.driverClassName[hypersonic]=org.hsqldb.jdbc.JDBCDriver
    setup.database.driverClassName[mariadb]=org.mariadb.jdbc.Driver
    setup.database.driverClassName[mysql]=com.mysql.cj.jdbc.Driver
    setup.database.driverClassName[oracle]=oracle.jdbc.OracleDriver
    setup.database.driverClassName[postgresql]=org.postgresql.Driver
    setup.database.driverClassName[sqlserver]=com.microsoft.sqlserver.jdbc.SQLServerDriver
    setup.database.driverClassName[sybase]=com.sybase.jdbc4.jdbc.SybDriver

Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_JAR_PERIOD_NAME_OPENBRACKET_COM_PERIOD_MYSQL_PERIOD_CJ_PERIOD_JDBC_PERIOD__UPPERCASED_RIVER_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_JAR_PERIOD_URL_OPENBRACKET_COM_PERIOD_MYSQL_PERIOD_CJ_PERIOD_JDBC_PERIOD__UPPERCASED_RIVER_CLOSEBRACKET_

    setup.database.jar.name[com.mysql.cj.jdbc.Driver]=mysql.jar
    setup.database.jar.url[com.mysql.cj.jdbc.Driver]=https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.15/mysql-connector-java-8.0.15.jar

Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_DB_NUMBER2__CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_HYPERSONIC_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_MARIADB_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_MYSQL_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_ORACLE_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_POSTGRESQL_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_SQLSERVER_CLOSEBRACKET_ Env: LIFERAY_SETUP_PERIOD_DATABASE_PERIOD_URL_OPENBRACKET_SYBASE_CLOSEBRACKET_

    setup.database.url[db2]=jdbc:db2://localhost:50000/lportal:deferPrepares=false;fullyMaterializeInputStreams=true;fullyMaterializeLobData=true;progresssiveLocators=2;progressiveStreaming=2;
    setup.database.url[hypersonic]=jdbc:hsqldb:${liferay.home}/data/hypersonic/lportal
    setup.database.url[mariadb]=jdbc:mariadb://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
    setup.database.url[mysql]=jdbc:mysql://localhost/lportal?characterEncoding=UTF-8&dontTrackOpenResources=true&holdResultsOpenOverStatementClose=true&serverTimezone=GMT&useFastDateParsing=false&useUnicode=true
    setup.database.url[oracle]=jdbc:oracle:thin:@localhost:1521:xe
    setup.database.url[postgresql]=jdbc:postgresql://localhost:5432/lportal
    setup.database.url[sqlserver]=jdbc:sqlserver://localhost;databaseName=lportal
    setup.database.url[sybase]=jdbc:sybase:Tds:localhost:5000/lportal

Set this property to true to automatically add sample data to a new database on startup. This will happen even if the Setup Wizard is disabled.

Env: LIFERAY_SETUP_PERIOD_WIZARD_PERIOD_ADD_PERIOD_SAMPLE_PERIOD_DATA

    setup.wizard.add.sample.data=false

Set this property to true if the Setup Wizard should be displayed the first time the portal is started.

Env: LIFERAY_SETUP_PERIOD_WIZARD_PERIOD_ENABLED

    setup.wizard.enabled=true

SourceForge

Env: LIFERAY_SOURCE_PERIOD_FORGE_PERIOD_MIRRORS

    source.forge.mirrors=\
        http://downloads.sourceforge.net,\      # Redirect
        http://internap.dl.sourceforge.net,\    # San Jose, CA
        http://superb-east.dl.sourceforge.net,\ # McLean, Virginia
        http://superb-west.dl.sourceforge.net,\ # Seattle, Washington
        http://easynews.dl.sourceforge.net,\    # Phoenix, AZ
        http://kent.dl.sourceforge.net,\        # Kent, UK
        http://ufpr.dl.sourceforge.net,\        # Curitiba, Brazil
        http://belnet.dl.sourceforge.net,\      # Brussels, Belgium
        http://switch.dl.sourceforge.net,\      # Lausanne, Switzerland
        http://mesh.dl.sourceforge.net,\        # Duesseldorf, Germany
        http://ovh.dl.sourceforge.net,\         # Paris, France
        http://dfn.dl.sourceforge.net,\         # Berlin, Germany
        http://heanet.dl.sourceforge.net,\      # Dublin, Ireland
        http://garr.dl.sourceforge.net,\        # Bologna, Italy
        http://surfnet.dl.sourceforge.net       # Amsterdam, The Netherlands
        http://jaist.dl.sourceforge.net,\       # Ishikawa, Japan
        http://nchc.dl.sourceforge.net,\        # Tainan, Taiwan
        http://optusnet.dl.sourceforge.net      # Sydney, Australia

Value Object

You can add a listener for a specific class by setting the property "value.object.listener" with a list of comma delimited class names that implement com.liferay.portal.kernel.model.ModelListener. These classes are pooled and reused and must be thread safe.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_LISTENER_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEC_ONTACT Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_LISTENER_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_LISTENER_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT_UPPERCASES_ET Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_LISTENER_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEP_ORTLET_UPPERCASEP_REFERENCES Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_LISTENER_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEU_SER Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_LISTENER_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEU_SER_UPPERCASEG_ROUP

    value.object.listener.com.liferay.portal.kernel.model.Contact=com.liferay.portal.model.ContactModelListener
    value.object.listener.com.liferay.portal.kernel.model.Layout=com.liferay.portal.model.LayoutModelListener,com.liferay.portal.service.impl.LayoutSetPrototypeLayoutModelListener
    value.object.listener.com.liferay.portal.kernel.model.LayoutSet=com.liferay.portal.model.LayoutSetModelListener,com.liferay.portal.service.impl.LayoutSetPrototypeLayoutSetModelListener
    value.object.listener.com.liferay.portal.kernel.model.PortletPreferences=com.liferay.portal.model.PortletPreferencesModelListener
    value.object.listener.com.liferay.portal.kernel.model.User=com.liferay.portal.model.UserModelListener
    value.object.listener.com.liferay.portal.kernel.model.UserGroup=com.liferay.portal.model.UserGroupModelListener

Value objects are cached at three levels. They first level is "entity", the second level is "finder", and the third level is "Hibernate".

The entity level cache stores a value object's primary key to the value object itself.

The finder level cache stores the many paths that return a value object and the many paths that return a list of value objects. The finder level cache only caches primary keys and is further helped by the entity level cache that caches the value object to the primary key.

The Hibernate level cache is provided by the "hibernate.cache.provider_class" property.

Set this to true to enable entity level caching.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_ENTITY_PERIOD_CACHE_PERIOD_ENABLED

    value.object.entity.cache.enabled=true

Set this to true to configure entity level caching to block. See the property "ehcache.blocking.cache.allowed" for more information.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_ENTITY_PERIOD_BLOCKING_PERIOD_CACHE

    value.object.entity.blocking.cache=true

The entity level cache uses a thread local map to store the most frequently accessed items to lower the number of queries to the underlying cache. Set the maximum map size to 0 to disable the thread level cache.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_ENTITY_PERIOD_THREAD_PERIOD_LOCAL_PERIOD_CACHE_PERIOD_MAX_PERIOD_SIZE

    value.object.entity.thread.local.cache.max.size=100

Entity level caching for a specific type of value object can be configured by using a property name that includes the value object's class name.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_ENTITY_PERIOD_CACHE_PERIOD_ENABLED_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_ENTITY_PERIOD_CACHE_PERIOD_ENABLED_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEU_SER

    value.object.entity.cache.enabled.com.liferay.portal.kernel.model.Layout=true
    value.object.entity.cache.enabled.com.liferay.portal.kernel.model.User=true

Set this property to true to enable MVCC entity level caching. This feature only applies to entities with that are MVCC enabled. See the attribute "mvcc-enabled" in the Service Builder DTD.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_MVCC_PERIOD_ENTITY_PERIOD_CACHE_PERIOD_ENABLED

    value.object.mvcc.entity.cache.enabled=true

Set this to true to enable finder level caching.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_FINDER_PERIOD_CACHE_PERIOD_ENABLED

    value.object.finder.cache.enabled=true

Set this to configure the list threshold for the maximum number of objects to cache with the same finder path and arguments. Setting this to 0 disables finder level caching. Setting this to -1 disables the threshold.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_FINDER_PERIOD_CACHE_PERIOD_LIST_PERIOD_THRESHOLD

    value.object.finder.cache.list.threshold=10000

The finder level cache uses a thread local map to store the most frequently accessed items to lower the number of queries to the underlying cache. Set the maximum map size to 0 to disable the thread level cache.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_FINDER_PERIOD_THREAD_PERIOD_LOCAL_PERIOD_CACHE_PERIOD_MAX_PERIOD_SIZE

    value.object.finder.thread.local.cache.max.size=100

Finder level caching for a specific type of value object can be configured by using a property name that includes the value object's class name. Mapping tables can also be specified to configure the caching of value object relationships.

Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_FINDER_PERIOD_CACHE_PERIOD_ENABLED_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_FINDER_PERIOD_CACHE_PERIOD_ENABLED_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEU_SER Env: LIFERAY_VALUE_PERIOD_OBJECT_PERIOD_FINDER_PERIOD_CACHE_PERIOD_ENABLED_PERIOD__UPPERCASEU_SERS_UNDERLINE__UPPERCASER_OLES

    value.object.finder.cache.enabled.com.liferay.portal.kernel.model.Layout=true
    value.object.finder.cache.enabled.com.liferay.portal.kernel.model.User=true
    value.object.finder.cache.enabled.Users_Roles=true

Table Mapper

Set a list of comma delimited mapping table names that will not be using cache in their table mappers.

Env: LIFERAY_TABLE_PERIOD_MAPPER_PERIOD_CACHELESS_PERIOD_MAPPING_PERIOD_TABLE_PERIOD_NAMES

    table.mapper.cacheless.mapping.table.names=\
        Users_Groups,\
        Users_Orgs,\
        Users_Roles,\
        Users_Teams,\
        Users_UserGroups

Audit Message

Env: LIFERAY_AUDIT_PERIOD_MESSAGE_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT_PERIOD__UPPERCASEV__UPPERCASEI__UPPERCASEE__UPPERCASEW_

    audit.message.com.liferay.portal.kernel.model.Layout.VIEW=false

Buffered Increment

Buffered incrementing provides logic to batch together requests for writing view count increments to the database. Minimizing these database hits can improve overall performance.

Buffered incrementing only applies to service methods annotated with the @BufferedIncrement(...) annotation. By default, it is used with methods that increment view counters for Message Boards threads, Document Library file entries, and Asset entries.

Disabling buffered increment logic will result in the service methods annotated with the @BufferedIncrement annotation being skipped. Only do this if you want to completely disable the view counters.

If you want to keep the view counters enabled but avoid using the buffered increment logic, one option is to remove the BufferedIncrementAdvice bean from base-spring.xml. As an alternative to disabling the buffered increment logic, consider disabling its standby logic by setting the "buffered.increment.standby.queue.threshold" and "buffered.increment.standby.time.upper.limit" properties to 0.

Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_ENABLED

    buffered.increment.enabled=true

The standby properties manage the time the dispatcher waits to process an increment requests. The longer the dispatcher waits to process a request, the greater the probability that incoming requests, involving the same entity instances (entries), can be batched together.

For example, if the same Message Boards thread (MBThread instance) is viewed multiple times (n times) while an existing view increment request for that MBThread is waiting to be dispatched, then the incoming increments can be added to the increment value of the existing request. The resulting view count increment for the existing entry then would be modified to 1 + n times and the incoming requests would be discarded. This minimizes the database hits for incrementing that entry. Since the incoming requests were no longer needed, and hence discarded, the memory required for incrementing the view count of the entry was minimized too.

Worker threads submit new increment requests to a BatchablePipe and notify the dispatcher thread pool of the requests. The pipe acts as a mailbox holding increment requests in a queue for the dispatcher to process. On receiving a new increment request, the pipe checks if it already has a request for the same entry. If it does, the pipe adds the incoming increment to the existing entry's increment value and discards the incoming increment request. If it doesn't find an existing request for the same entry, the incoming request is simply added to the tail of the queue.

On being notified by the worker thread of increment requests submitted to the BatchablePipe, the thread pool checks the status of its dispatch threads. If no dispatch threads exist, it creates one. If an idle thread exists, it wakes it up. If threads exist but they are all active, the thread pool leaves them alone. Active dispatch threads check the pipe's queue for requests to process.

The dispatch threads apply the standby logic before processing each request from the pipe. They calculate the standby time for the request at the head of the pipe's queue based on the queue threshold. If the number of requests in the queue exceeds the threshold, the dispatch thread processes the head request as quickly as possible, without waiting. If the number of requests is within the threshold, the dispatch thread calculates the standby time for the head request to be the standby time upper limit (in seconds) divided by the number of requests in the queue. The fewer requests in the queue, the longer the head request waits on standby.

Consider the tradeoff between overall performance and delay in view count updates as you configure standby waiting. The standby times applied to the requests have a linear inverse ratio relationship to the number of requests in the pipe. The standby time is not constant. The fewer requests inside the queue, the longer they wait in standby. This logic increases the probability of maximizing the batching of requests for dispatch. The following chart illustrates the relationship:

     ^ standby time
     |
     |\<---buffered.increment.standby.time.upper.limit
     | \
     |  \
     |   \
     |    \
     --------------> current BatchablePipe size
     0 ^
       |
       buffered.increment.standby.queue.threshold

Typical settings for the queue threshold and upper time limit of a heavy loaded system could be 10000 requests and 60 seconds, respectively.

If either the queue threshold or upper time limit are set to 0, requests are processed from the queue as quickly as possible, without waiting. Negative values for either property are treated as 0.

Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_QUEUE_PERIOD_THRESHOLD Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_TIME_PERIOD_UPPER_PERIOD_LIMIT

    buffered.increment.standby.queue.threshold=0
    buffered.increment.standby.time.upper.limit=0

The dispatcher thread pool manages the lifecycle of the dispatch threads. By default, the thread pool is configured to use a single dispatch thread. Buffered incrementing is designed for optimal performance using a single dispatch thread.

Set the "buffered.increment.threadpool.keep.alive.time" property to the maximum idle time before a dispatch thread can be recycled. Negative values for this property are treated as 0.

The "buffered.increment.threadpool.max.size" property value should, in in most cases, remain set to 1. If for some reason, more than one dispatch thread is desired, know that this goes against the design of buffered incrementing and may result in less than optimal performance. Values less than or equal to 0 for this property are treated as 1.

Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_KEEP_PERIOD_ALIVE_PERIOD_TIME Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_MAX_PERIOD_SIZE

    buffered.increment.threadpool.keep.alive.time=60
    buffered.increment.threadpool.max.size=1

Override the global buffered increment settings with specific settings for the AssetEntry view counter.

Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_ENABLED_OPENBRACKET__UPPERCASEA_SSET_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_QUEUE_PERIOD_THRESHOLD_OPENBRACKET__UPPERCASEA_SSET_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_TIME_PERIOD_UPPER_PERIOD_LIMIT_OPENBRACKET__UPPERCASEA_SSET_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_KEEP_PERIOD_ALIVE_PERIOD_TIME_OPENBRACKET__UPPERCASEA_SSET_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_MAX_PERIOD_SIZE_OPENBRACKET__UPPERCASEA_SSET_UPPERCASEE_NTRY_CLOSEBRACKET_

    buffered.increment.enabled[AssetEntry]=true
    buffered.increment.standby.queue.threshold[AssetEntry]=0
    buffered.increment.standby.time.upper.limit[AssetEntry]=0
    buffered.increment.threadpool.keep.alive.time[AssetEntry]=60
    buffered.increment.threadpool.max.size[AssetEntry]=1

Override the global buffered increment settings with specific settings for the DLFileEntry view counter.

Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_ENABLED_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_ILE_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_QUEUE_PERIOD_THRESHOLD_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_ILE_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_TIME_PERIOD_UPPER_PERIOD_LIMIT_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_ILE_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_KEEP_PERIOD_ALIVE_PERIOD_TIME_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_ILE_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_MAX_PERIOD_SIZE_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_ILE_UPPERCASEE_NTRY_CLOSEBRACKET_

    buffered.increment.enabled[DLFileEntry]=true
    buffered.increment.standby.queue.threshold[DLFileEntry]=0
    buffered.increment.standby.time.upper.limit[DLFileEntry]=0
    buffered.increment.threadpool.keep.alive.time[DLFileEntry]=60
    buffered.increment.threadpool.max.size[DLFileEntry]=1

Override the global buffered increment settings with specific settings for the DLFolderEntry last post date.

Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_ENABLED_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_OLDER_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_QUEUE_PERIOD_THRESHOLD_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_OLDER_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_TIME_PERIOD_UPPER_PERIOD_LIMIT_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_OLDER_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_KEEP_PERIOD_ALIVE_PERIOD_TIME_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_OLDER_UPPERCASEE_NTRY_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_MAX_PERIOD_SIZE_OPENBRACKET__UPPERCASED__UPPERCASEL__UPPERCASEF_OLDER_UPPERCASEE_NTRY_CLOSEBRACKET_

    buffered.increment.enabled[DLFolderEntry]=true
    buffered.increment.standby.queue.threshold[DLFolderEntry]=0
    buffered.increment.standby.time.upper.limit[DLFolderEntry]=0
    buffered.increment.threadpool.keep.alive.time[DLFolderEntry]=60
    buffered.increment.threadpool.max.size[DLFolderEntry]=1

Override the global buffered increment settings with specific settings for the MBThread view counter.

Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_ENABLED_OPENBRACKET__UPPERCASEM__UPPERCASEB__UPPERCASET_HREAD_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_QUEUE_PERIOD_THRESHOLD_OPENBRACKET__UPPERCASEM__UPPERCASEB__UPPERCASET_HREAD_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_STANDBY_PERIOD_TIME_PERIOD_UPPER_PERIOD_LIMIT_OPENBRACKET__UPPERCASEM__UPPERCASEB__UPPERCASET_HREAD_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_KEEP_PERIOD_ALIVE_PERIOD_TIME_OPENBRACKET__UPPERCASEM__UPPERCASEB__UPPERCASET_HREAD_CLOSEBRACKET_ Env: LIFERAY_BUFFERED_PERIOD_INCREMENT_PERIOD_THREADPOOL_PERIOD_MAX_PERIOD_SIZE_OPENBRACKET__UPPERCASEM__UPPERCASEB__UPPERCASET_HREAD_CLOSEBRACKET_

    buffered.increment.enabled[MBThread]=true
    buffered.increment.standby.queue.threshold[MBThread]=0
    buffered.increment.standby.time.upper.limit[MBThread]=0
    buffered.increment.threadpool.keep.alive.time[MBThread]=60
    buffered.increment.threadpool.max.size[MBThread]=1

Cache

Clear cache when plugins are undeployed.

Env: LIFERAY_CACHE_PERIOD_CLEAR_PERIOD_ON_PERIOD_PLUGIN_PERIOD_UNDEPLOY

    cache.clear.on.plugin.undeploy=true

The cache filter caches processed web content. Set the threshold size to prevent caching resources that are too large. The default value is 500 kb.

Env: LIFERAY_CACHE_PERIOD_CONTENT_PERIOD_THRESHOLD_PERIOD_SIZE

    cache.content.threshold.size=512000

Set this to false to disable user agent matching in the cache filter. Excluding the user agent improves the cache hit ratio but should not be used when content is browser specific. Each cache filter can be individually configured with the "includeUserAgent" init parameter.

Env: LIFERAY_CACHE_PERIOD_FILTER_PERIOD_INCLUDE_PERIOD_USER_PERIOD_AGENT

    cache.filter.include.user.agent=true

Cluster Link

Set the cluster node bootup response timeout in milliseconds.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_NODE_PERIOD_BOOTUP_PERIOD_RESPONSE_PERIOD_TIMEOUT

    cluster.link.node.bootup.response.timeout=10000

Set this to true to enable the cluster link. This is required if you want to cluster indexing and other features that depend on the cluster link.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_ENABLED

    cluster.link.enabled=false

Set the logic name for each JGroups channel. The logic name must be unique for each node in the cluster. If it is not set, a random logic name will be generated. We support up to 10 transport channels and 1 single required control channel.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_LOGIC_PERIOD_NAME_PERIOD_CONTROL Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_LOGIC_PERIOD_NAME_PERIOD_TRANSPORT_PERIOD__NUMBER0_ Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_LOGIC_PERIOD_NAME_PERIOD_TRANSPORT_PERIOD__NUMBER1_

    cluster.link.channel.logic.name.control=
    cluster.link.channel.logic.name.transport.0=

    cluster.link.channel.logic.name.transport.1=

Set the name for each JGroups channel. We support up to 10 transport channels and 1 single required control channel.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_NAME_PERIOD_CONTROL Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_NAME_PERIOD_TRANSPORT_PERIOD__NUMBER0_ Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_NAME_PERIOD_TRANSPORT_PERIOD__NUMBER1_

    cluster.link.channel.name.control=liferay-channel-control
    cluster.link.channel.name.transport.0=liferay-channel-transport-0

    cluster.link.channel.name.transport.1=liferay-channel-transport-1

Set the JGroups properties for each channel, we support up to 10 transport channels and 1 single required control channel. Use as few transport channels as possible for best performance. By default, only one UDP control channel and one UDP transport channel are enabled. The value can be a file containing a JGroups XML configuration, a URL pointing to an XML configuration, or a path of XML configuration in class path.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_PROPERTIES_PERIOD_CONTROL Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_PROPERTIES_PERIOD_TRANSPORT_PERIOD__NUMBER0_ Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_PROPERTIES_PERIOD_TRANSPORT_PERIOD__NUMBER1_ Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_PROPERTIES_PERIOD_TRANSPORT_PERIOD__NUMBER2_

    cluster.link.channel.properties.control=jgroups/udp_control.xml
    cluster.link.channel.properties.transport.0=jgroups/udp_transport.xml

    cluster.link.channel.properties.transport.1=udp.xml
    cluster.link.channel.properties.transport.2=mping.xml

Set JGroups' system properties. System properties are only used when individual properties are not set.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_CHANNEL_PERIOD_SYSTEM_PERIOD_PROPERTIES

    cluster.link.channel.system.properties=
        #
        # Common
        #
        #\
        #jgroups.bind_addr:${cluster.link.bind.addr["cluster-link-udp"]},\
        #jgroups.bind_interface:eth0,\
        #\
        #
        # Multicast
        #
        #\
        #jgroups.mping.mcast_addr:${multicast.group.address["cluster-link-mping"]},\
        #jgroups.mping.mcast_port:${multicast.group.port["cluster-link-mping"]},\
        #jgroups.mping.ip_ttl:8

Set this property to autodetect the default outgoing IP address so that JGroups can bind to it. The property must point to an address that is accessible to the portal server, www.google.com, or your local gateway.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_AUTODETECT_PERIOD_ADDRESS

    cluster.link.autodetect.address=www.google.com:80

Set the bind address for JGroups directly, it only works when the property "cluster.link.autodetect.address" is not set. See the property "cluster.link.channel.properties.control" for more information.

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_BIND_PERIOD_ADDR_OPENBRACKET__QUOTE_CLUSTER_MINUS_LINK_MINUS_CONTROL_QUOTE__CLOSEBRACKET_

    cluster.link.bind.addr["cluster-link-control"]=localhost

Set bind address for jgroups directly, it only works when "cluster.link. autodetect.address" is not set. See the properties "cluster.link.channel. properties.transport.0" and "cluster.link.channel.system.properties".

Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_BIND_PERIOD_ADDR_OPENBRACKET__QUOTE_CLUSTER_MINUS_LINK_MINUS_UDP_QUOTE__CLOSEBRACKET_

    cluster.link.bind.addr["cluster-link-udp"]=localhost

Clusterable Advice

Set the clusterable advice call master timeout in seconds.

Env: LIFERAY_CLUSTERABLE_PERIOD_ADVICE_PERIOD_CALL_PERIOD_MASTER_PERIOD_TIMEOUT

    clusterable.advice.call.master.timeout=10

Combo

A file extension of * will permit all file extensions.

Env: LIFERAY_COMBO_PERIOD_ALLOWED_PERIOD_FILE_PERIOD_EXTENSIONS

    combo.allowed.file.extensions=\
        .css,\
        .js

The combo servlet combines multiple JavaScript files into a bundle based on shared dependencies. This makes loading JavaScript files much faster. Set this to false if the combination should refresh when one of its JavaScript files has changed. This property should be set to true during development for easier debugging but set to false during production for faster performance.

Env: LIFERAY_COMBO_PERIOD_CHECK_PERIOD_TIMESTAMP

    combo.check.timestamp=false

Set the minimum wait interval in milliseconds between timestamp checks on resource files. This property is only used if the property "combo.check.timestamp" is set to true.

Env: LIFERAY_COMBO_PERIOD_CHECK_PERIOD_TIMESTAMP_PERIOD_INTERVAL

    combo.check.timestamp.interval=1000

Content Delivery Network

Set the hostname that will be used to serve static content via a CDN for requests made over the HTTP protocol. This property can be disabled dynamically at runtime by setting the URL parameter "cdn_enabled" to "0". The value must always include the full protocol.

Env: LIFERAY_CDN_PERIOD_HOST_PERIOD_HTTP

    cdn.host.http=

Set the hostname that will be used to serve static content via a CDN for requests made over the HTTPS protocol. This property can be disabled dynamically at runtime by setting the URL parameter "cdn_enabled" to "0". The value must always include the full protocol.

Env: LIFERAY_CDN_PERIOD_HOST_PERIOD_HTTPS

    cdn.host.https=

Set this to true to enable serving dynamically generated CSS, JavaScript, and images via a CDN. Setting this to false allows the usage of CDNs that do not support lazy loading of resources (e.g. Amazon CloudFront).

Env: LIFERAY_CDN_PERIOD_DYNAMIC_PERIOD_RESOURCES_PERIOD_ENABLED

    cdn.dynamic.resources.enabled=true

Counter

Specify the total number of deployment data centers. Each data center is independent of each other (e.g. not clustered together) and connected via a two way database replication.

Env: LIFERAY_COUNTER_PERIOD_DATA_PERIOD_CENTER_PERIOD_COUNT

    counter.data.center.count=1

Set the unique identifier for a data center deployment between 0 and the value in the property "counter.data.center.count" minus 1. This will ensure that each data center will generate unique counter values without fear of collision.

The data center algorithm will first shift the counter value to the right by the number of bits needed to represent the value in the property "counter.data.center.count" and then prepend the bits needed to represent the value in "counter.data.center.deployment.id" to the left most byte of the counter value.

Env: LIFERAY_COUNTER_PERIOD_DATA_PERIOD_CENTER_PERIOD_DEPLOYMENT_PERIOD_ID

    counter.data.center.deployment.id=0

The counter operates with its own data source to prevent deadlocks. By default, the data source created for the counter uses the same settings as those used to create the data source used for the rest of the portal. That happens because the counter service will look up the properties prefixed with "jdbc.default." to create its data source. See the JDBC properties prefixed with "jdbc.default." for more information.

Setting a different value for the counter JDBC prefix allows you to better fine tune the counter data source with its own set of configuration settings for high availability installations. Note that these settings, though separate, are a copy of the default settings with the newly overridden values.

Env: LIFERAY_COUNTER_PERIOD_JDBC_PERIOD_PREFIX

    counter.jdbc.prefix=jdbc.default.

Set the number of increments between database updates to the Counter table. Set this value to a higher number for better performance.

Env: LIFERAY_COUNTER_PERIOD_INCREMENT

    counter.increment=100

You can further fine tune the counter increment for specific counter names. This entry will ensure that the counter name "com.liferay.portal.kernel.model.Layout" or anything that starts with "com.liferay.portal.kernel.model.Layout#" will only increment by 1.

Env: LIFERAY_COUNTER_PERIOD_INCREMENT_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASEL_AYOUT

    counter.increment.com.liferay.portal.kernel.model.Layout=1

Direct Servlet Context

Set this to true to enable dispatching to a servlet directly to speed up request dispatching. This property only takes effect when a developer programmatically wraps a normal ServletContext with a DirectServletContext. See LPS-13776 for more information.

Env: LIFERAY_DIRECT_PERIOD_SERVLET_PERIOD_CONTEXT_PERIOD_ENABLED

    direct.servlet.context.enabled=true

Set this to true to refresh the servlet associated with a JSP when the JSP has been modified. This property is not used unless the property "direct.servlet.context.enabled" is set to true.

Env: LIFERAY_DIRECT_PERIOD_SERVLET_PERIOD_CONTEXT_PERIOD_RELOAD

    direct.servlet.context.reload=true

DNS

Configure the seconds to wait for resolving an external domain. This limit helps prevent DoS attacks when trying to resolve an external domain. By default, the Oracle Java implementation has a 15 second timeout for DNS queries, so you must enter a number of less than 15.

Env: LIFERAY_DNS_PERIOD_SECURITY_PERIOD_ADDRESS_PERIOD_TIMEOUT_PERIOD_SECONDS

    dns.security.address.timeout.seconds=2

Configure the maximum number of threads when resolving an external domain. This limit helps prevent DoS attacks.

Env: LIFERAY_DNS_PERIOD_SECURITY_PERIOD_THREAD_PERIOD_LIMIT

    dns.security.thread.limit=10

ETag

The ETag filter needs to process the response in order to calculate the ETag value. A large response may use too much memory. Set the maximum response size that will trigger an ETag calculation. The default maximum response size is 1 megabyte.

Env: LIFERAY_ETAG_PERIOD_RESPONSE_PERIOD_SIZE_PERIOD_MAX

    etag.response.size.max=1048576

GZip

The GZip filter will compress files using the specified compression level. Set the value to -1 to use the default compression level. Set the value between 0 and 9 for other compression levels as documented in java.util.zip.Deflater.

Env: LIFERAY_GZIP_PERIOD_COMPRESSION_PERIOD_LEVEL

    gzip.compression.level=-1

HTTP

See system.properties for more HTTP settings.

Set the maximum number of connections per host.

Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_MAX_PERIOD_CONNECTIONS_PERIOD_PER_PERIOD_HOST Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_MAX_PERIOD_CONNECTIONS_PERIOD_PER_PERIOD_HOST_OPENBRACKET_RSS_PERIOD_NEWS_PERIOD_YAHOO_PERIOD_COM_CLOSEBRACKET_

    com.liferay.portal.util.HttpImpl.max.connections.per.host=2
    com.liferay.portal.util.HttpImpl.max.connections.per.host[rss.news.yahoo.com]=2

Set the maximum number of connections.

Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_MAX_PERIOD_TOTAL_PERIOD_CONNECTIONS

    com.liferay.portal.util.HttpImpl.max.total.connections=20

Set the proxy authentication type.

Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_PROXY_PERIOD_AUTH_PERIOD_TYPE

    com.liferay.portal.util.HttpImpl.proxy.auth.type=username-password
    com.liferay.portal.util.HttpImpl.proxy.auth.type=ntlm

Set user name and password used for HTTP proxy authentication.

Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_PROXY_PERIOD_PASSWORD Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_PROXY_PERIOD_USERNAME

    com.liferay.portal.util.HttpImpl.proxy.username=
    com.liferay.portal.util.HttpImpl.proxy.password=

Set additional properties for NTLM authentication.

Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_PROXY_PERIOD_NTLM_PERIOD_DOMAIN Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_PROXY_PERIOD_NTLM_PERIOD_HOST

    com.liferay.portal.util.HttpImpl.proxy.ntlm.domain=
    com.liferay.portal.util.HttpImpl.proxy.ntlm.host=

Set the connection timeout when fetching HTTP content.

Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_TIMEOUT Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_UTIL_PERIOD__UPPERCASEH_TTP_UPPERCASEI_MPL_PERIOD_TIMEOUT_OPENBRACKET_RSS_PERIOD_NEWS_PERIOD_YAHOO_PERIOD_COM_CLOSEBRACKET_

    com.liferay.portal.util.HttpImpl.timeout=10000

    com.liferay.portal.util.HttpImpl.timeout[rss.news.yahoo.com]=10000

HTTP Header Response

See system.properties for more HTTP Header Response settings.

Set the level of verbosity to use for the Liferay-Portal field in the HTTP header response. Valid values are "full", which gives all of the version information (e.g. Liferay Portal Community Edition 6.1.0 CE etc.), "partial", which gives only the name portion (e.g. Liferay Portal Community Edition), or "off" which prevents the Portal from adding the Liferay-Portal field in the HTTP header response.

Env: LIFERAY_HTTP_PERIOD_HEADER_PERIOD_VERSION_PERIOD_VERBOSITY

    http.header.version.verbosity=full

HTTP Tunneling

Do not set this property to false in production environments. It overrides the SSL hostname verification and is used for self assigned certificates. See LPS-18038.

Env: LIFERAY_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_SERVICE_PERIOD_HTTP_PERIOD__UPPERCASET_UNNEL_UPPERCASEU_TIL_PERIOD_VERIFY_PERIOD_SSL_PERIOD_HOSTNAME

    com.liferay.portal.kernel.service.http.TunnelUtil.verify.ssl.hostname=true

Set this to the appropriate encryption algorithm that will be used for tunnel level encryption algorithms.

If you change this setting, you may need to also change the property "tunneling.servlet.shared.secret" to make sure that the shared secret length is a valid length for the encryption algorithm.

For more details about encryption keys, see the Java Cryptography Extension documentation.

Env: LIFERAY_TUNNELING_PERIOD_SERVLET_PERIOD_ENCRYPTION_PERIOD_ALGORITHM

    tunneling.servlet.encryption.algorithm=AES

    tunneling.servlet.encryption.algorithm=Blowfish
    tunneling.servlet.encryption.algorithm=DESede

Set this shared secret to secure communications from one portal to another via the tunneling servlet. This portal will refuse communications from other portals that do not share the same secret.

Secrets must be at least 8 bytes long. Please note that using a secret that is larger than 16 bytes requires that the Java Cryptography Extension Unlimited Strength Jurisdiction Policy Files are installed and that the property "tunneling.servlet.encryption.algorithm" supports that particular key size.

For more details about supported key sizes for encryption keys, see the Java Cryptography Extension documentation.

Env: LIFERAY_TUNNELING_PERIOD_SERVLET_PERIOD_SHARED_PERIOD_SECRET

    tunneling.servlet.shared.secret=

When set to true, tunneling.servlet.shared.secret must be encoded using a hexadecimal encoding.

Env: LIFERAY_TUNNELING_PERIOD_SERVLET_PERIOD_SHARED_PERIOD_SECRET_PERIOD_HEX

    tunneling.servlet.shared.secret.hex=true

Set a timeout to enforce a connection timeout for connections between servers via the tunneling servlet. Without setting this value, the actual timeout enforced may vary between environments.

Env: LIFERAY_TUNNELING_PERIOD_SERVLET_PERIOD_TIMEOUT

    tunneling.servlet.timeout=30000

ImageMagick

Set this to true to enable ImageMagick. You must install Ghostscript and Imagemagick. See http://www.ghostscript.com and http://www.imagemagick.org for more information.

The search path should point to the directories for the ImageMagick and Ghostscript executables. You may also need to configure the path for fonts used by Ghostscript when in Apple or Unix environments.

Env: LIFERAY_IMAGEMAGICK_PERIOD_ENABLED Env: LIFERAY_IMAGEMAGICK_PERIOD_GLOBAL_PERIOD_SEARCH_PERIOD_PATH_OPENBRACKET_APPLE_CLOSEBRACKET_ Env: LIFERAY_IMAGEMAGICK_PERIOD_GLOBAL_PERIOD_SEARCH_PERIOD_PATH_OPENBRACKET_UNIX_CLOSEBRACKET_ Env: LIFERAY_IMAGEMAGICK_PERIOD_GLOBAL_PERIOD_SEARCH_PERIOD_PATH_OPENBRACKET_WINDOWS_CLOSEBRACKET_

    imagemagick.enabled=false
    imagemagick.global.search.path[apple]=/opt/local/bin:/opt/local/share/ghostscript/fonts:/opt/local/share/fonts/urw-fonts
    imagemagick.global.search.path[unix]=/usr/local/bin:/usr/local/share/ghostscript/fonts:/usr/local/share/fonts/urw-fonts
    imagemagick.global.search.path[windows]=C:\\Program Files\\gs\\bin;C:\\Program Files\\ImageMagick

Set these limits to configure the cache and resource usage of ImageMagick. To determine the current setting of these limits, run the command:

identify -list resource

See http://www.imagemagick.org/script/architecture.php for more information.

Env: LIFERAY_IMAGEMAGICK_PERIOD_RESOURCE_PERIOD_LIMIT_PERIOD_AREA Env: LIFERAY_IMAGEMAGICK_PERIOD_RESOURCE_PERIOD_LIMIT_PERIOD_DISK Env: LIFERAY_IMAGEMAGICK_PERIOD_RESOURCE_PERIOD_LIMIT_PERIOD_FILE Env: LIFERAY_IMAGEMAGICK_PERIOD_RESOURCE_PERIOD_LIMIT_PERIOD_MAP Env: LIFERAY_IMAGEMAGICK_PERIOD_RESOURCE_PERIOD_LIMIT_PERIOD_MEMORY Env: LIFERAY_IMAGEMAGICK_PERIOD_RESOURCE_PERIOD_LIMIT_PERIOD_THREAD Env: LIFERAY_IMAGEMAGICK_PERIOD_RESOURCE_PERIOD_LIMIT_PERIOD_TIME

    imagemagick.resource.limit.area=2GiB
    imagemagick.resource.limit.map=1GiB
    imagemagick.resource.limit.memory=2GiB

    imagemagick.resource.limit.disk=16GiB
    imagemagick.resource.limit.file=256
    imagemagick.resource.limit.thread=2
    imagemagick.resource.limit.time=3600

Intraband

Specify the class name of an Intraband implementation. The class must implement the com.liferay.portal.kernel.nio.intraband.Intraband interface.

If you leave the value blank, the portal makes a best effort in choosing an implementation for optimal performance on your system, considering your Intraband welder.

If com.liferay.portal.kernel.nio.intraband.welder.socket.SocketWelder is your Intraband welder, either explicitly configured for your "intraband.welder.impl" property value or automatically chosen by the portal, then the portal chooses the com.liferay.portal.kernel.nio.intraband.nonblocking.SelectorIntraband class as the Intraband implementation.

Otherwise the portal chooses the com.liferay.portal.kernel.nio.intraband.blocking.ExecutorIntraband class as the Intraband implementation.

Performance tips:

FIFO, if provided by your Linux or Unix OS, only works with ExecutorIntraband. To use FIFO, you must either specify the ExecutorIntraband class as the Intraband implementation or leave the value blank for the portal to automatically choose it.

SelectorIntraband uses a Selector instance to manage all registered SelectableChannels. It uses the Selector instance with a single polling thread to serve all read/write requests. SelectorIntraband has a lower CPU overhead than ExecutorIntraband. However, SelectorIntraband can potentially have unnecessary read/write latency (if any callback is holding the polling thread).

ExecutorIntraband works with any ScatteringByteChannel/GatheringByteChannel registered pair. ExecutorIntraband launches a dedicated polling thread for each channel, in blocking mode. So ExecutorIntraband has higher CPU overhead than SelectorIntraband, but since each channel polling is isolated, ExecutorIntraband can provide better throughput and response time.

For a system that requires tons of connections over Intraband, it is best to use SelectorIntraband to avoid massive polling threads.

For a system that requires limited connections over Intraband, it is best to use ExecutorIntraband to maximize throughput and response time.

Env: LIFERAY_INTRABAND_PERIOD_IMPL

    intraband.impl=

    intraband.impl=com.liferay.portal.kernel.nio.intraband.blocking.ExecutorIntraband
    intraband.impl=com.liferay.portal.kernel.nio.intraband.nonblocking.SelectorIntraband

Set this to true to launch a separate dedicated thread to reap overdue mail. Otherwise, the overdue mail is reaped in a lazy manner--reaped only when new mail comes in and old mail goes out.

Performance tips:

With the dedicated reaper thread, overdue mail is reaped in a timely manner, reducing the memory footprint but costing more CPU power. Without the dedicated reaper thread, CPU power is conserved but the memory footprint can potentially grow large.

Generally, for small and frequent mail messages, it is better to turn this off. For huge and infrequent mail messages, it is better to turn this on.

Env: LIFERAY_INTRABAND_PERIOD_MAILBOX_PERIOD_REAPER_PERIOD_THREAD_PERIOD_ENABLED

    intraband.mailbox.reaper.thread.enabled=false

Set the number of milliseconds to keep mail living in the mailbox.

Env: LIFERAY_INTRABAND_PERIOD_MAILBOX_PERIOD_STORAGE_PERIOD_LIFE

    intraband.mailbox.storage.life=10000

Set the directory name to contain the dump out class files. This directory will be created under operation system's temporary directory.

Env: LIFERAY_INTRABAND_PERIOD_PROXY_PERIOD_DUMP_PERIOD_CLASSES_PERIOD_DIR

    intraband.proxy.dump.classes.dir=IntrabandProxyClasses

Set this to true to dump out generated proxy classes as class files into the directory specified by the property "intraband.proxy.dump.classes.dir".

Env: LIFERAY_INTRABAND_PERIOD_PROXY_PERIOD_DUMP_PERIOD_CLASSES_PERIOD_ENABLED

    intraband.proxy.dump.classes.enabled=true

Set default Intraband synchronized operation timeout time in milliseconds.

Env: LIFERAY_INTRABAND_PERIOD_TIMEOUT_PERIOD_DEFAULT

    intraband.timeout.default=10000

Specify the class name of an Intraband welder. The class must implement the com.liferay.portal.kernel.nio.intraband.welder.Welder interface.

If you leave the value blank, the portal makes a best effort in choosing an implementation for optimal performance on your system.

If your system's OS is not Windows and the portal finds mkfifo command in your system's PATH, the portal chooses the FIFO welder class com.liferay.portal.kernel.nio.intraband.welder.fifo.FIFOWelder.

Otherwise, the portal chooses the socket welder class com.liferay.portal.kernel.nio.intraband.welder.socket.SocketWelder.

Consider the following example that compares the performance of these two welders:

On average, the FIFO welder outperforms the socket welder on both throughput and response latency, until packages reach about 2 to 4 megabytes in size.

On an uncustomized modern Linux kernel, the best package size for the FIFO FIFO welder is 64 kilobytes. The FIFO welder's best package size is the system's maximum non-blocking package size. To calculate it for your system, multiply your system's pipe size (ulimit -p) by the number of kernel buffers your system can allocate.

Executing 'ulimit -p' returns the following pipe size:

     pipe size (512 bytes) * 8 = 4 kilobytes

The kernel can allocate up to 16 buffers. Multiplying the pipe size by the the number of buffers results in the system's maximum non-blocking package size:

     4 kilobytes * 16 kernel buffers = 64 kilobytes

As package size grows past this best size, the FIFO welder's performance declines, but is still better than the socket welder's performance; that is, until the package size reaches about 2 to 4 megabytes. At that package size, FIFO welder performs the same as socket welder. It's only when packages are greater than that size that socket welder performs better. For these huge packages, you can either use the socket welder class or recompile the Linux kernel to support a larger pipe size and more kernel buffers.

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_IMPL

    intraband.welder.impl=

    intraband.welder.impl=com.liferay.portal.kernel.nio.intraband.welder.fifo.FIFOWelder
    intraband.welder.impl=com.liferay.portal.kernel.nio.intraband.welder.socket.SocketWelder

Set the send and receive buffer size, in bytes, for both the server and client socket peers.

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_SOCKET_PERIOD_BUFFER_PERIOD_SIZE

    intraband.welder.socket.buffer.size=65536

Specify whether to keep the socket on both the server and client socket peers alive.

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_SOCKET_PERIOD_KEEP_PERIOD_ALIVE

    intraband.welder.socket.keep.alive=false

Specify whether to recycle the address on the server and client socket peers and on the temporary server socket channel.

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_SOCKET_PERIOD_REUSE_PERIOD_ADDRESS

    intraband.welder.socket.reuse.address=true

Specify a port number from which the SocketWelder automatically starts searching for an available port to open up a temporary ServerSocketChannel to bind the server and client. Since it doesn't matter which port this ServerSocketChannel listens on, SocketWelder uses to the first available port.

After one client socket is accepting, the ServerSocketChannel is closed and recycled.

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_SOCKET_PERIOD_SERVER_PERIOD_START_PERIOD_PORT

    intraband.welder.socket.server.start.port=32354

Specify how long, if at all, the socket should linger on both the server and client socket peers. This value is used as the integer parameter in the call to Socket.setSoLinger(boolean, int).

A non-positive value turns off lingering resulting in calling Socket.setSoLinger(false, int).

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_SOCKET_PERIOD_SO_PERIOD_LINGER

    intraband.welder.socket.so.linger=0

Specify the SO_TIMEOUT on both the server and client socket peers. This value is used in calling to Socket.setSoTimeout(int).

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_SOCKET_PERIOD_SO_PERIOD_TIMEOUT

    intraband.welder.socket.so.timeout=0

Specify whether to enable TCP_NODELAY on both the server and client socket peers. This value is used in the calling Socket.setTcpNoDelay(boolean).

Env: LIFERAY_INTRABAND_PERIOD_WELDER_PERIOD_SOCKET_PERIOD_TCP_PERIOD_NO_PERIOD_DELAY

    intraband.welder.socket.tcp.no.delay=true

Invoker

The invoker filter will attempt to cache InvokerFilterChain objects based on the request URI and dispatcher. Set this property to false to disable caching of InvokerFilterChain objects.

Env: LIFERAY_INVOKER_PERIOD_FILTER_PERIOD_CHAIN_PERIOD_CACHE_PERIOD_ENABLED

    invoker.filter.chain.cache.enabled=true

The invoker filter will reject any request to the portal where the request URI is longer than this value. For technical reasons, we should generally not allow more than 4000 characters.

Env: LIFERAY_INVOKER_PERIOD_FILTER_PERIOD_URI_PERIOD_MAX_PERIOD_LENGTH

    invoker.filter.uri.max.length=4000

Javadoc Manager

Set this property to true to enable runtime querying of Javadoc information. This is used by the JSON web service at http://localhost:8080/api/jsonws to give users better information about the API. The Javadoc manager uses very little memory and has little effect on the startup time, but both can be optimized by disabling this feature.

Env: LIFERAY_JAVADOC_PERIOD_MANAGER_PERIOD_ENABLED

    javadoc.manager.enabled=true

JSON

Input a list of comma delimited class names that can be deserialized using JSONFactory.

Env: LIFERAY_JSON_PERIOD_DESERIALIZATION_PERIOD_WHITELIST_PERIOD_CLASS_PERIOD_NAMES

    json.deserialization.whitelist.class.names=\
        com.liferay.portal.kernel.cal.DayAndPosition,\
        com.liferay.portal.kernel.cal.Duration,\
        com.liferay.portal.kernel.cal.TZSRecurrence,\
        com.liferay.portal.kernel.messaging.Message,\
        com.liferay.portal.kernel.model.PortletPreferencesIds,\
        com.liferay.portal.kernel.security.auth.HttpPrincipal,\
        com.liferay.portal.kernel.service.permission.ModelPermissions,\
        com.liferay.portal.kernel.service.ServiceContext,\
        com.liferay.portal.kernel.util.GroupSubscriptionCheckSubscriptionSender,\
        com.liferay.portal.kernel.util.LongWrapper,\
        com.liferay.portal.kernel.util.SubscriptionSender,\
        java.util.GregorianCalendar,\
        java.util.Locale,\
        java.util.TimeZone,\
        sun.util.calendar.ZoneInfo

Set this to true to require JSON service calls to have a valid authentication token. This property is not used unless the property "auth.token.check.enabled" is also set to true.

Env: LIFERAY_JSON_PERIOD_SERVICE_PERIOD_AUTH_PERIOD_TOKEN_PERIOD_ENABLED

    json.service.auth.token.enabled=true

Input a list of comma delimited IPs that can access the JSON service without specifying an authentication token. Input a blank list to allow any IP to access the JSON service. SERVER_IP will be replaced with the IP of the host server.

The default value of 255.255.255.255 means that no one can access the JSON service without an authentication token since 255.255.255.255 is an invalid IP.

IPs can be configured with subnet masks or CIDR notation to allow ranges of allowed hosts. For example, 192.168.1.0/255.0.0.0 or 192.168.1.0/8 are both equivalent and valid configurations.

Env: LIFERAY_JSON_PERIOD_SERVICE_PERIOD_AUTH_PERIOD_TOKEN_PERIOD_HOSTS_PERIOD_ALLOWED

    json.service.auth.token.hosts.allowed=255.255.255.255

Input a list of comma delimited class names that cannot be invoked via JSON.

Env: LIFERAY_JSON_PERIOD_SERVICE_PERIOD_INVALID_PERIOD_CLASS_PERIOD_NAMES

    json.service.invalid.class.names=\
        com.liferay.documentlibrary.service.DLAppServiceUtil,\
        com.liferay.mail.kernel.service.MailServiceUtil,\
        com.liferay.portal.kernel.service.CompanyServiceUtil,\
        com.liferay.portal.kernel.service.PortalServiceUtil,\
        com.liferay.portal.kernel.service.PortletServiceUtil

Input a list of comma delimited method names that cannot be invoked via JSON.

Env: LIFERAY_JSON_PERIOD_SERVICE_PERIOD_INVALID_PERIOD_METHOD_PERIOD_NAMES

    json.service.invalid.method.names=\
        getOSGiServiceIdentifier

JSON Web Service

Set this property to true to enable JSON web services. Note that setting this to false will cause portlets that make JSON web service calls from working.

Env: LIFERAY_JSON_PERIOD_WEB_PERIOD_SERVICE_PERIOD_ENABLED

    json.web.service.enabled=true

Input a list of comma delimited class names that are allowed to be used for JSON web service request object parameters.

Env: LIFERAY_JSONWS_PERIOD_WEB_PERIOD_SERVICE_PERIOD_PARAMETER_PERIOD_TYPE_PERIOD_WHITELIST_PERIOD_CLASS_PERIOD_NAMES

    jsonws.web.service.parameter.type.whitelist.class.names=\
        \
        #
        # java.lang.Object in
        # com.liferay.expando.kernel.service.ExpandoColumnService
        #
        \
        com.liferay.portal.json.JSONObjectImpl,\
        java.util.Date,\
        \
        #
        # com.liferay.portal.kernel.search.Query
        #
        \
        com.liferay.portal.kernel.search.generic.BooleanQueryImpl,\
        com.liferay.portal.kernel.search.generic.DisMaxQuery,\
        com.liferay.portal.kernel.search.generic.FuzzyQuery,\
        com.liferay.portal.kernel.search.generic.MatchAllQuery,\
        com.liferay.portal.kernel.search.generic.MatchQuery,\
        com.liferay.portal.kernel.search.generic.MoreLikeThisQuery,\
        com.liferay.portal.kernel.search.generic.MultiMatchQuery,\
        com.liferay.portal.kernel.search.generic.NestedQuery,\
        com.liferay.portal.kernel.search.generic.StringQuery,\
        com.liferay.portal.kernel.search.generic.TermQueryImpl,\
        com.liferay.portal.kernel.search.generic.TermRangeQueryImpl,\
        com.liferay.portal.kernel.search.generic.WildcardQueryImpl,\
        \
        #
        # com.liferay.portal.kernel.util.OrderByComparator
        #
        \
        com.liferay.asset.list.util.comparator.AssetListEntryCreateDateComparator,\
        com.liferay.asset.list.util.comparator.AssetListEntryTitleComparator,\
        com.liferay.asset.list.util.comparator.AssetListEntryUsageModifiedDateComparator,\
        com.liferay.asset.util.comparator.AssetEntryUsageModifiedDateComparator,\
        com.liferay.asset.util.comparator.AssetTagCountComparator,\
        com.liferay.background.task.kernel.util.comparator.BackgroundTaskCompletionDateComparator,\
        com.liferay.background.task.kernel.util.comparator.BackgroundTaskCreateDateComparator,\
        com.liferay.background.task.kernel.util.comparator.BackgroundTaskNameComparator,\
        com.liferay.blogs.util.comparator.EntryDisplayDateComparator,\
        com.liferay.blogs.util.comparator.EntryIdComparator,\
        com.liferay.blogs.util.comparator.EntryModifiedDateComparator,\
        com.liferay.blogs.util.comparator.EntryTitleComparator,\
        com.liferay.blogs.util.comparator.StatsUserLastPostDateComparator,\
        com.liferay.bookmarks.util.comparator.EntryCreateDateComparator,\
        com.liferay.bookmarks.util.comparator.EntryModifiedDateComparator,\
        com.liferay.bookmarks.util.comparator.EntryNameComparator,\
        com.liferay.bookmarks.util.comparator.EntryPriorityComparator,\
        com.liferay.bookmarks.util.comparator.EntryURLComparator,\
        com.liferay.bookmarks.util.comparator.FolderIdComparator,\
        com.liferay.calendar.util.comparator.CalendarBookingStartTimeComparator,\
        com.liferay.calendar.util.comparator.CalendarNameComparator,\
        com.liferay.calendar.util.comparator.CalendarResourceCodeComparator,\
        com.liferay.calendar.util.comparator.CalendarResourceNameComparator,\
        com.liferay.document.library.content.util.comparator.DLContentVersionComparator,\
        com.liferay.document.library.file.rank.util.comparator.FileRankCreateDateComparator,\
        com.liferay.document.library.kernel.util.comparator.FolderIdComparator,\
        com.liferay.document.library.kernel.util.comparator.FolderNameComparator,\
        com.liferay.document.library.kernel.util.comparator.RepositoryModelCreateDateComparator,\
        com.liferay.document.library.kernel.util.comparator.RepositoryModelModifiedDateComparator,\
        com.liferay.document.library.kernel.util.comparator.RepositoryModelReadCountComparator,\
        com.liferay.document.library.kernel.util.comparator.RepositoryModelSizeComparator,\
        com.liferay.document.library.kernel.util.comparator.RepositoryModelTitleComparator,\
        com.liferay.dynamic.data.lists.util.comparator.DDLRecordCreateDateComparator,\
        com.liferay.dynamic.data.lists.util.comparator.DDLRecordIdComparator,\
        com.liferay.dynamic.data.lists.util.comparator.DDLRecordModifiedDateComparator,\
        com.liferay.dynamic.data.lists.util.comparator.DDLRecordSetCreateDateComparator,\
        com.liferay.dynamic.data.lists.util.comparator.DDLRecordSetModifiedDateComparator,\
        com.liferay.dynamic.data.lists.util.comparator.DDLRecordSetNameComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.DataProviderInstanceModifiedDateComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.DataProviderInstanceNameComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.DDMFormInstanceModifiedDateComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.DDMFormInstanceNameComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.DDMFormInstanceRecordIdComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.DDMFormInstanceRecordModifiedDateComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.StructureCreateDateComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.StructureIdComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.StructureLayoutNameComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.StructureLinkStructureNameComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.StructureModifiedDateComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.StructureNameComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.StructureStructureKeyComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.TemplateIdComparator,\
        com.liferay.dynamic.data.mapping.util.comparator.TemplateModifiedDateComparator,\
        com.liferay.exportimport.kernel.lar.StagedModelModifiedDateComparator,\
        com.liferay.exportimport.util.comparator.ExportImportConfigurationNameComparator,\
        com.liferay.fragment.util.comparator.FragmentCollectionCreateDateComparator,\
        com.liferay.fragment.util.comparator.FragmentCollectionNameComparator,\
        com.liferay.fragment.util.comparator.FragmentEntryCreateDateComparator,\
        com.liferay.fragment.util.comparator.FragmentEntryLinkLastPropagationDateComparator,\
        com.liferay.fragment.util.comparator.FragmentEntryNameComparator,\
        com.liferay.friendly.url.util.comparator.FriendlyURLEntryCreateDateComparator,\
        com.liferay.journal.util.comparator.ArticleCreateDateComparator,\
        com.liferay.journal.util.comparator.ArticleDisplayDateComparator,\
        com.liferay.journal.util.comparator.ArticleIDComparator,\
        com.liferay.journal.util.comparator.ArticleModifiedDateComparator,\
        com.liferay.journal.util.comparator.ArticleResourcePKComparator,\
        com.liferay.journal.util.comparator.ArticleReviewDateComparator,\
        com.liferay.journal.util.comparator.ArticleTitleComparator,\
        com.liferay.journal.util.comparator.ArticleVersionComparator,\
        com.liferay.journal.util.comparator.FeedIDComparator,\
        com.liferay.journal.util.comparator.FeedNameComparator,\
        com.liferay.journal.util.comparator.FolderArticleArticleIdComparator,\
        com.liferay.journal.util.comparator.FolderArticleDisplayDateComparator,\
        com.liferay.journal.util.comparator.FolderArticleModifiedDateComparator,\
        com.liferay.journal.util.comparator.FolderArticleTitleComparator,\
        com.liferay.journal.util.comparator.FolderIdComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticleCreateDateComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticleModifiedDateComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticlePriorityComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticleStatusComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticleTitleComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticleUserNameComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticleVersionComparator,\
        com.liferay.knowledge.base.util.comparator.KBArticleViewCountComparator,\
        com.liferay.knowledge.base.util.comparator.KBCommentCreateDateComparator,\
        com.liferay.knowledge.base.util.comparator.KBCommentModifiedDateComparator,\
        com.liferay.knowledge.base.util.comparator.KBCommentStatusComparator,\
        com.liferay.knowledge.base.util.comparator.KBCommentUserNameComparator,\
        com.liferay.knowledge.base.util.comparator.KBFolderNameComparator,\
        com.liferay.knowledge.base.util.comparator.KBObjectsModifiedDateComparator,\
        com.liferay.knowledge.base.util.comparator.KBObjectsPriorityComparator,\
        com.liferay.knowledge.base.util.comparator.KBObjectsTitleComparator,\
        com.liferay.knowledge.base.util.comparator.KBObjectsViewCountComparator,\
        com.liferay.knowledge.base.util.comparator.KBTemplateCreateDateComparator,\
        com.liferay.knowledge.base.util.comparator.KBTemplateModifiedDateComparator,\
        com.liferay.knowledge.base.util.comparator.KBTemplateTitleComparator,\
        com.liferay.knowledge.base.util.comparator.KBTemplateUserNameComparator,\
        com.liferay.layout.page.template.util.comparator.LayoutPageTemplateCollectionCreateDateComparator,\
        com.liferay.layout.page.template.util.comparator.LayoutPageTemplateCollectionNameComparator,\
        com.liferay.layout.page.template.util.comparator.LayoutPageTemplateEntryCreateDateComparator,\
        com.liferay.layout.page.template.util.comparator.LayoutPageTemplateEntryNameComparator,\
        com.liferay.layout.portlets.web.internal.util.comparator.PortletDisplayNameComparator,\
        com.liferay.layout.util.comparator.LayoutCreateDateComparator,\
        com.liferay.marketplace.util.comparator.AppTitleComparator,\
        com.liferay.membership.requests.kernel.util.comparator.MembershipRequestCreateDateComparator,\
        com.liferay.message.boards.util.comparator.CategoryModifiedDateComparator,\
        com.liferay.message.boards.util.comparator.CategoryTitleComparator,\
        com.liferay.message.boards.util.comparator.MBObjectsComparator,\
        com.liferay.message.boards.util.comparator.MBObjectsModifiedDateComparator,\
        com.liferay.message.boards.util.comparator.MBObjectsTitleComparator,\
        com.liferay.message.boards.util.comparator.MessageCreateDateComparator,\
        com.liferay.message.boards.util.comparator.ThreadLastPostDateComparator,\
        com.liferay.message.boards.util.comparator.ThreadModifiedDateComparator,\
        com.liferay.message.boards.util.comparator.ThreadTitleComparator,\
        com.liferay.microblogs.util.comparator.EntryCreateDateComparator,\
        com.liferay.mobile.device.rules.util.comparator.ActionCreateDateComparator,\
        com.liferay.mobile.device.rules.util.comparator.RuleCreateDateComparator,\
        com.liferay.mobile.device.rules.util.comparator.RuleGroupCreateDateComparator,\
        com.liferay.mobile.device.rules.util.comparator.RuleGroupInstancePriorityComparator,\
        com.liferay.polls.util.comparator.PollsQuestionCreateDateComparator,\
        com.liferay.polls.util.comparator.PollsQuestionTitleComparator,\
        com.liferay.portal.background.task.internal.comparator.BackgroundTaskCompletionDateComparator,\
        com.liferay.portal.background.task.internal.comparator.BackgroundTaskCreateDateComparator,\
        com.liferay.portal.background.task.internal.comparator.BackgroundTaskNameComparator,\
        com.liferay.portal.kernel.util.comparator.GroupFriendlyURLComparator,\
        com.liferay.portal.kernel.util.comparator.GroupIdComparator,\
        com.liferay.portal.kernel.util.comparator.GroupNameComparator,\
        com.liferay.portal.kernel.util.comparator.GroupTypeComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutPriorityComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutPrototypeCreateDateComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutRevisionCreateDateComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutRevisionIdComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutRevisionModifiedDateComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutSetBranchCreateDateComparator,\
        com.liferay.portal.kernel.util.comparator.LayoutSetPrototypeCreateDateComparator,\
        com.liferay.portal.kernel.util.comparator.OrganizationIdComparator,\
        com.liferay.portal.kernel.util.comparator.OrganizationNameComparator,\
        com.liferay.portal.kernel.util.comparator.OrganizationTypeComparator,\
        com.liferay.portal.kernel.util.comparator.PasswordPolicyDescriptionComparator,\
        com.liferay.portal.kernel.util.comparator.PasswordPolicyNameComparator,\
        com.liferay.portal.kernel.util.comparator.ResourceActionBitwiseValueComparator,\
        com.liferay.portal.kernel.util.comparator.RoleDescriptionComparator,\
        com.liferay.portal.kernel.util.comparator.RoleNameComparator,\
        com.liferay.portal.kernel.util.comparator.RoleRoleIdComparator,\
        com.liferay.portal.kernel.util.comparator.RoleTypeComparator,\
        com.liferay.portal.kernel.util.comparator.TeamNameComparator,\
        com.liferay.portal.kernel.util.comparator.UserEmailAddressComparator,\
        com.liferay.portal.kernel.util.comparator.UserFirstNameComparator,\
        com.liferay.portal.kernel.util.comparator.UserGroupDescriptionComparator,\
        com.liferay.portal.kernel.util.comparator.UserGroupIdComparator,\
        com.liferay.portal.kernel.util.comparator.UserGroupNameComparator,\
        com.liferay.portal.kernel.util.comparator.UserIdComparator,\
        com.liferay.portal.kernel.util.comparator.UserJobTitleComparator,\
        com.liferay.portal.kernel.util.comparator.UserLastNameComparator,\
        com.liferay.portal.kernel.util.comparator.UserLoginDateComparator,\
        com.liferay.portal.kernel.util.comparator.UserScreenNameComparator,\
        com.liferay.portal.reports.engine.console.util.comparator.DefinitionCreateDateComparator,\
        com.liferay.portal.reports.engine.console.util.comparator.EntryCreateDateComparator,\
        com.liferay.portal.reports.engine.console.util.comparator.SourceCreateDateComparator,\
        com.liferay.portal.security.audit.storage.comparator.AuditEventCreateDateComparator,\
        com.liferay.portal.security.service.access.policy.util.comparator.SAPEntryNameComparator,\
        com.liferay.portal.workflow.kaleo.forms.util.comparator.KaleoProcessCreateDateComparator,\
        com.liferay.portal.workflow.kaleo.forms.util.comparator.KaleoProcessModifiedDateComparator,\
        com.liferay.portal.workflow.kaleo.util.comparator.KaleoDefinitionVersionIdComparator,\
        com.liferay.portal.workflow.kaleo.util.comparator.KaleoDefinitionVersionModifiedDateComparator,\
        com.liferay.portal.workflow.kaleo.util.comparator.KaleoDefinitionVersionNameComparator,\
        com.liferay.portal.workflow.kaleo.util.comparator.KaleoDefinitionVersionTitleComparator,\
        com.liferay.portal.workflow.kaleo.util.comparator.KaleoDefinitionVersionVersionComparator,\
        com.liferay.portal.workflow.web.internal.util.comparator.WorkflowDefinitionActiveComparator,\
        com.liferay.portal.workflow.web.internal.util.comparator.WorkflowDefinitionModifiedDateComparator,\
        com.liferay.portal.workflow.web.internal.util.comparator.WorkflowDefinitionNameComparator,\
        com.liferay.portal.workflow.web.internal.util.comparator.WorkflowDefinitionTitleComparator,\
        com.liferay.portlet.asset.util.comparator.AssetCategoryCreateDateComparator,\
        com.liferay.portlet.asset.util.comparator.AssetTagAssetCountComparator,\
        com.liferay.portlet.asset.util.comparator.AssetTagNameComparator,\
        com.liferay.portlet.asset.util.comparator.AssetVocabularyCreateDateComparator,\
        com.liferay.portlet.configuration.web.internal.util.comparator.ArchivedSettingsModifiedDateComparator,\
        com.liferay.portlet.configuration.web.internal.util.comparator.ArchivedSettingsNameComparator,\
        com.liferay.push.notifications.util.comparator.PushNotificationsDevicePlatformComparator,\
        com.liferay.segments.web.internal.util.comparator.SegmentsEntryModifiedDateComparator,\
        com.liferay.segments.web.internal.util.comparator.SegmentsEntryNameComparator,\
        com.liferay.sharing.util.comparator.SharingEntryModifiedDateComparator,\
        com.liferay.site.admin.web.internal.display.context.comparator.SiteInitializerNameComparator,\
        com.liferay.site.navigation.util.comparator.SiteNavigationMenuCreateDateComparator,\
        com.liferay.site.navigation.util.comparator.SiteNavigationMenuItemOrderComparator,\
        com.liferay.site.navigation.util.comparator.SiteNavigationMenuNameComparator,\
        com.liferay.social.kernel.util.comparator.SocialActivitySetModifiedDateComparator,\
        com.liferay.subscription.util.comparator.SubscriptionClassNameIdComparator,\
        com.liferay.sync.util.comparator.SyncDLObjectModifiedTimeComparator,\
        com.liferay.trash.kernel.util.comparator.EntryCreateDateComparator,\
        com.liferay.trash.kernel.util.comparator.EntryTypeComparator,\
        com.liferay.trash.kernel.util.comparator.EntryUserNameComparator,\
        com.liferay.trash.util.comparator.EntryCreateDateComparator,\
        com.liferay.trash.util.comparator.EntryTypeComparator,\
        com.liferay.trash.util.comparator.EntryUserNameComparator,\
        com.liferay.users.admin.web.internal.util.comparator.OrganizationUserNameComparator,\
        com.liferay.wiki.util.comparator.NodeLastPostDateComparator,\
        com.liferay.wiki.util.comparator.NodeNameComparator,\
        com.liferay.wiki.util.comparator.PageCreateDateComparator,\
        com.liferay.wiki.util.comparator.PageModifiedDateComparator,\
        com.liferay.wiki.util.comparator.PageTitleComparator,\
        com.liferay.wiki.util.comparator.PageVersionComparator

Set this property to true if JSON web services are discoverable through the API page.

Env: LIFERAY_JSONWS_PERIOD_WEB_PERIOD_SERVICE_PERIOD_API_PERIOD_DISCOVERABLE

    jsonws.web.service.api.discoverable=true

Input a list of comma delimited HTTP methods that are not accessible. For example, if you want to have a read only API, then set this property to "DELETE,POST,PUT".

Env: LIFERAY_JSONWS_PERIOD_WEB_PERIOD_SERVICE_PERIOD_INVALID_PERIOD_HTTP_PERIOD_METHODS

    jsonws.web.service.invalid.http.methods=

Set this property to true to ensure that a JSON web service action can only be invoked by its expected HTTP method.

For example, the annotation com.liferay.portal.kernel.jsonwebservice.JSONWebService may configure the expected HTTP method for an action to be a GET request. However, the URL for that GET request may be too long, and so you may need to call that with a POST request. Setting this property to false loosens this requirement and allows the POST request to invoke an action that is supposed to only be called by a GET request.

Env: LIFERAY_JSONWS_PERIOD_WEB_PERIOD_SERVICE_PERIOD_STRICT_PERIOD_HTTP_PERIOD_METHOD

    jsonws.web.service.strict.http.method=false

The property "jsonws.web.service.paths.excludes" denotes patterns for JSON web service action paths that are not allowed even if they match one of the patterns set in "jsonws.web.service.paths.includes".

Env: LIFERAY_JSONWS_PERIOD_WEB_PERIOD_SERVICE_PERIOD_PATHS_PERIOD_EXCLUDES

    jsonws.web.service.paths.excludes=\
        /user/update-password

The property "jsonws.web.service.paths.includes" denotes patterns for JSON web service action paths that are allowed. Set a blank pattern to allow any service action path.

Env: LIFERAY_JSONWS_PERIOD_WEB_PERIOD_SERVICE_PERIOD_PATHS_PERIOD_INCLUDES

    jsonws.web.service.paths.includes=

Live Users

Set this to true to enable tracking via Live Users.

This property is deprecated and will be removed in a future release.

Env: LIFERAY_LIVE_PERIOD_USERS_PERIOD_ENABLED

    live.users.enabled=false

Lock

Input a list of comma delimited class names that implement com.liferay.portal.kernel.lock.LockListener. A lock listener allows you to specify logic around how an object is locked. The implementation must be thread safe.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_LOCK_PERIOD_LISTENERS

    lock.listeners=com.liferay.portlet.documentlibrary.util.DLFileEntryLockListener

Set the lock expiration time for each class.

Locks for publishing processes should expire after 10 minutes.

Env: LIFERAY_LOCK_PERIOD_EXPIRATION_PERIOD_TIME_PERIOD_COM_PERIOD_LIFERAY_PERIOD_PORTAL_PERIOD_KERNEL_PERIOD_STAGING_PERIOD__UPPERCASES_TAGING

    lock.expiration.time.com.liferay.portal.kernel.staging.Staging=600000

Locks for document library folders should expire after 1 day.

Env: LIFERAY_LOCK_PERIOD_EXPIRATION_PERIOD_TIME_PERIOD_COM_PERIOD_LIFERAY_PERIOD_DOCUMENT_PERIOD_LIBRARY_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASED__UPPERCASEL__UPPERCASEF_OLDER

    lock.expiration.time.com.liferay.document.library.kernel.model.DLFolder=86400000

Locks for document library files should expire after 1 day.

Env: LIFERAY_LOCK_PERIOD_EXPIRATION_PERIOD_TIME_PERIOD_COM_PERIOD_LIFERAY_PERIOD_DOCUMENT_PERIOD_LIBRARY_PERIOD_KERNEL_PERIOD_MODEL_PERIOD__UPPERCASED__UPPERCASEL__UPPERCASEF_ILE_UPPERCASEE_NTRY

    lock.expiration.time.com.liferay.document.library.kernel.model.DLFileEntry=86400000

Locks for message board threads should never expire.

Env: LIFERAY_LOCK_PERIOD_EXPIRATION_PERIOD_TIME_PERIOD_COM_PERIOD_LIFERAY_PERIOD_MESSAGE_PERIOD_BOARDS_PERIOD_MODEL_PERIOD__UPPERCASEM__UPPERCASEB__UPPERCASET_HREAD

    lock.expiration.time.com.liferay.message.boards.model.MBThread=0

Mail

Set the batch size for outbound emails. Set this property to 0 to submit to the mail server a request to send an email with multiple recipients all at once. Set a value greater than 0 to split up the list of recipients by the batch size so that multiple requests are submitted to the mail server to ensure that the mail server's recipient size limit is not reached.

Env: LIFERAY_MAIL_PERIOD_BATCH_PERIOD_SIZE

    mail.batch.size=0

Input a list of comma delimited email addresses that will be blacklisted when sending emails. The specified email addresses will be ignored and a warning will be logged.

Env: LIFERAY_MAIL_PERIOD_SEND_PERIOD_BLACKLIST

    mail.send.blacklist=\
        noreply@liferay.com,\
        test@liferay.com,\
        noreply@domain.invalid,\
        test@domain.invalid

Set the JNDI name to lookup the Java Mail session. If none is set, then the portal will attempt to create the Java Mail session based on the properties prefixed with "mail.session.".

Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_JNDI_PERIOD_NAME

    mail.session.jndi.name=mail/MailSession

Set the properties used to create the Java Mail session. The property prefix "mail.session." will be removed before it is used to create the session object. These properties will only be read if the property "mail.session.jndi.name" is not set.

Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_POP_NUMBER3__PERIOD_HOST Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_POP_NUMBER3__PERIOD_PASSWORD Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_POP_NUMBER3__PERIOD_PORT Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_POP_NUMBER3__PERIOD_USER Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_SMTP_PERIOD_AUTH Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_SMTP_PERIOD_HOST Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_SMTP_PERIOD_PASSWORD Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_SMTP_PERIOD_PORT Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_SMTP_PERIOD_USER Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_STORE_PERIOD_PROTOCOL Env: LIFERAY_MAIL_PERIOD_SESSION_PERIOD_MAIL_PERIOD_TRANSPORT_PERIOD_PROTOCOL

    mail.session.mail=false
    mail.session.mail.pop3.host=localhost
    mail.session.mail.pop3.password=
    mail.session.mail.pop3.port=110
    mail.session.mail.pop3.user=
    mail.session.mail.smtp.auth=false
    mail.session.mail.smtp.host=localhost
    mail.session.mail.smtp.password=
    mail.session.mail.smtp.port=25
    mail.session.mail.smtp.user=
    mail.session.mail.store.protocol=pop3
    mail.session.mail.transport.protocol=smtp

Set this to false if an administrator should not be allowed to change the mail domain via the Admin portlet.

Env: LIFERAY_MAIL_PERIOD_MX_PERIOD_UPDATE

    mail.mx.update=true

Input a list of comma delimited email addresses that will receive a BCC of every email sent through the mail server.

Env: LIFERAY_MAIL_PERIOD_AUDIT_PERIOD_TRAIL

    mail.audit.trail=

Set the name of a class that implements com.liferay.mail.util.Hook. The mail server will use this class to ensure that the mail and portal servers are synchronized on user information. The portal will not know how to add, update, or delete users from the mail server except through this hook.

This property is not read by the portal except for portal properties overridden by liferay-hook.xml. It remains here only as a reference.

Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_IMPL

    mail.hook.impl=com.liferay.mail.util.DummyHook
    mail.hook.impl=com.liferay.mail.util.SendmailHook
    mail.hook.impl=com.liferay.mail.util.ShellHook

SendmailHook

Set the commands for adding, updating, and deleting a user where %1% is the user ID and %2% is the password. Set the home and virtual user table information.

Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_SENDMAIL_PERIOD_ADD_PERIOD_USER Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_SENDMAIL_PERIOD_CHANGE_PERIOD_PASSWORD Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_SENDMAIL_PERIOD_DELETE_PERIOD_USER Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_SENDMAIL_PERIOD_HOME Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_SENDMAIL_PERIOD_VIRTUSERTABLE Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_SENDMAIL_PERIOD_VIRTUSERTABLE_PERIOD_REFRESH

    mail.hook.sendmail.add.user=adduser %1% -s /bin/false
    mail.hook.sendmail.change.password=autopasswd %1% %2%
    mail.hook.sendmail.delete.user=userdel -r %1%
    mail.hook.sendmail.home=/home
    mail.hook.sendmail.virtusertable=/etc/mail/virtusertable
    mail.hook.sendmail.virtusertable.refresh=bash -c "makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable"

ShellHook

Set the location of the shell script that will interface with any mail server.

Env: LIFERAY_MAIL_PERIOD_HOOK_PERIOD_SHELL_PERIOD_SCRIPT

    mail.hook.shell.script=/usr/sbin/mailadmin.ksh

Set this to true to throw an exception when com.liferay.util.mail.MailEngine fails to send an email.

Env: LIFERAY_MAIL_PERIOD_THROWS_PERIOD_EXCEPTION_PERIOD_ON_PERIOD_FAILURE

    mail.throws.exception.on.failure=false

Minifier

Set this to true to enable minification of CSS and JavaScript resources.

Env: LIFERAY_MINIFIER_PERIOD_ENABLED

    minifier.enabled=true

The strip filter will attempt to cache inline minified CSS and JavaScript content. Set this property to false to disable caching of inline minified content.

Env: LIFERAY_MINIFIER_PERIOD_INLINE_PERIOD_CONTENT_PERIOD_CACHE_PERIOD_ENABLED

    minifier.inline.content.cache.enabled=true

Input a list of comma delimited values that will cause the minified CSS to not be cached if those values are contained in the content.

Env: LIFERAY_MINIFIER_PERIOD_INLINE_PERIOD_CONTENT_PERIOD_CACHE_PERIOD_SKIP_PERIOD_CSS

    minifier.inline.content.cache.skip.css=

Input a list of comma delimited values that will cause the minified JavaScript to not be cached if those values are contained in the content.

Env: LIFERAY_MINIFIER_PERIOD_INLINE_PERIOD_CONTENT_PERIOD_CACHE_PERIOD_SKIP_PERIOD_JAVASCRIPT

    minifier.inline.content.cache.skip.javascript=\
        getSessionId,\
        encryptedUserId

Mobile Device Rules

Set this property to true to cache the user's device profile to the HTTP session. If this property is false, then the portal will perform device detection for each request.

Env: LIFERAY_MOBILE_PERIOD_DEVICE_PERIOD_SESSION_PERIOD_CACHE_PERIOD_ENABLED

    mobile.device.session.cache.enabled=true

Set this to true if mobile device rules should be published to live by default.

Env: LIFERAY_MOBILE_PERIOD_DEVICE_PERIOD_RULES_PERIOD_PUBLISH_PERIOD_TO_PERIOD_LIVE_PERIOD_BY_PERIOD_DEFAULT

    mobile.device.rules.publish.to.live.by.default=true

This property defines the postfix that will be localized and appended to the name of a copied rule group.

Env: LIFERAY_MOBILE_PERIOD_DEVICE_PERIOD_RULES_PERIOD_RULE_PERIOD_GROUP_PERIOD_COPY_PERIOD_POSTFIX

    mobile.device.rules.rule.group.copy.postfix=copy

Module Framework

Set the module framework beginning start level. The module framework will proceed to this start level after all static bundles are installed. All static bundles will be configured to this start level by default during installation.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_BEGINNING_PERIOD_START_PERIOD_LEVEL

    module.framework.beginning.start.level=6

Set the module framework runtime start level. The module framework will proceed to this start level after all dynamic bundles are installed.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_DYNAMIC_PERIOD_INSTALL_PERIOD_START_PERIOD_LEVEL

    module.framework.dynamic.install.start.level=10

Set the module framework runtime start level. The module framework will proceed to this start level after all web bundles are installed.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_START_PERIOD_LEVEL

    module.framework.web.start.level=15

Set the module framework runtime start level. The module framework will proceed to this start level after the Spring context is initialized.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_RUNTIME_PERIOD_START_PERIOD_LEVEL

    module.framework.runtime.start.level=20

Set the module framework asynchronous stop wait timeout in milliseconds.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_STOP_PERIOD_WAIT_PERIOD_TIMEOUT

    module.framework.stop.wait.timeout=30000

Set the directory which will form the base path of the module framework.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_BASE_PERIOD_DIR

    module.framework.base.dir=${liferay.home}/osgi

Set a comma delimited list of directories to scan for modules and configurations to auto deploy.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_AUTO_PERIOD_DEPLOY_PERIOD_DIRS

    module.framework.auto.deploy.dirs=\
        ${module.framework.configs.dir},\
        ${module.framework.marketplace.dir},\
        ${module.framework.modules.dir},\
        ${module.framework.war.dir}

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

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_AUTO_PERIOD_DEPLOY_PERIOD_INTERVAL

    module.framework.auto.deploy.interval=5000

Set this to true to enable concurrency during startup.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_CONCURRENT_PERIOD_STARTUP_PERIOD_ENABLED

    module.framework.concurrent.startup.enabled=true

Set the directory where the module framework configurations will be placed.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_CONFIGS_PERIOD_DIR

    module.framework.configs.dir=${module.framework.base.dir}/configs

Set the Symbolic Names for Configuration Bundles to Be Started First

Env: LIFERAY_CONFIGURATION_PERIOD_BUNDLE_PERIOD_SYMBOLIC_PERIOD_NAMES

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_CONFIGURATION_PERIOD_BUNDLE_PERIOD_SYMBOLIC_PERIOD_NAMES

    module.framework.configuration.bundle.symbolic.names=\
        com.liferay.portal.configuration.persistence.impl,\
        com.liferay.portal.configuration.persistence.api,\
        org.apache.felix.configadmin

Set the directory where the module framework marketplace applications will be placed.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_MARKETPLACE_PERIOD_DIR

    module.framework.marketplace.dir=${module.framework.base.dir}/marketplace

Set the directory where the module framework modules libraries will be placed.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_MODULES_PERIOD_DIR

    module.framework.modules.dir=${module.framework.base.dir}/modules

Set the directory where the module framework portal libraries will be placed.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PORTAL_PERIOD_DIR

    module.framework.portal.dir=${module.framework.base.dir}/portal

Set the directory where the module framework WAR applications will be placed.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WAR_PERIOD_DIR

    module.framework.war.dir=${module.framework.base.dir}/war

Set the directory where the module framework will persist its state.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_STATE_PERIOD_DIR

    module.framework.state.dir=${module.framework.base.dir}/state

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_SERVICES_PERIOD_IGNORED_PERIOD_INTERFACES

    module.framework.services.ignored.interfaces=\
        com.liferay.portal.dao.orm.hibernate.SessionFactoryImpl,\
        com.liferay.portal.kernel.dao.orm.SessionFactory,\
        com.liferay.portal.service.persistence.impl.*,\
        com.liferay.portal.verify.model.*,\
        com.liferay.trash.kernel.service.*,\
        com.mchange.*,\
        com.sun.*,\
        java.*,\
        org.apache.lucene.*,\
        org.apache.tika.*,\
        org.hibernate.*,\
        org.springframework.*

Set a comma delimited list of jars that are deployed to the app server's "/WEB-INF/lib" directory to be statically included in all bundles.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_STATIC_PERIOD_JARS

    module.framework.static.jars=\
        com.liferay.portal.osgi.web.jasper.plugins.taglib.jar,\
        util-taglib.jar

Set a comma delimited list of Java packages that are exported to the module framework as extra system packages.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_SYSTEM_PERIOD_PACKAGES_PERIOD_EXTRA

    module.framework.system.packages.extra=\
        com.ibm.crypto.provider,\
        com.ibm.db2.jcc,\
        com.microsoft.sqlserver.jdbc,\
        com.mysql.cj.jdbc,\
        com.mysql.jdbc,\
        com.p6spy.engine.spy,\
        com.sun.security.auth.module,\
        com.sybase.jdbc4.jdbc,\
        oracle.jdbc,\
        org.postgresql,\
        org.hsqldb.jdbc,\
        org.mariadb.jdbc,\
        sun.misc,\
        sun.net.util,\
        sun.security.provider,\
        \
        #
        # WebSocket Support
        #
        \
        com.ibm.websphere.wsoc,\
        io.undertow.websockets.jsr,\
        javax.websocket,\
        javax.websocket.server,\
        org.apache.tomcat.websocket.server,\
        weblogic.websocket.tyrus

Set the batch size for resolving bundle revisions.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_RESOLVER_PERIOD_REVISION_PERIOD_BATCH_PERIOD_SIZE

    module.framework.resolver.revision.batch.size=1000

Pass arbitrary extra properties to the framework using the prefix: "module.framework.properties." to avoid avoid colliding with other frameworks that may be running within the same JVM.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_DEPENDENCY_PERIOD_MANAGER_PERIOD_SYNC_PERIOD_TIMEOUT Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_DEPENDENCY_PERIOD_MANAGER_PERIOD_THREAD_PERIOD_POOL_PERIOD_ENABLED Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_DS_PERIOD_LOCK_PERIOD_TIMEOUT_PERIOD_MILLISECONDS Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_DS_PERIOD_STOP_PERIOD_TIMEOUT_PERIOD_MILLISECONDS Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_ECLIPSE_PERIOD_STATE_UPPERCASES_AVE_UPPERCASED_ELAY_UPPERCASEI_NTERVAL Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_CM_PERIOD_PM Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_BUNDLES_PERIOD_NEW_PERIOD_START Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_BUNDLES_PERIOD_START_UPPERCASEA_CTIVATION_UPPERCASEP_OLICY Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_BUNDLES_PERIOD_START_UPPERCASET_RANSIENT Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_DISABLE_UPPERCASEN_IO_NUMBER2_ Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_LOG_PERIOD_LEVEL Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_NO_UPPERCASEI_NITIAL_UPPERCASED_ELAY Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_OPTIONAL_UPPERCASEI_MPORT_UPPERCASER_EFRESH_UPPERCASES_COPE Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_FELIX_PERIOD_FILEINSTALL_PERIOD_SUBDIR_PERIOD_MODE Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_GOSH_PERIOD_ARGS Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_INITIAL_PERIOD_SYSTEM_PERIOD_CHECK_PERIOD_ENABLED Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_LPKG_PERIOD_DEPLOYER_PERIOD_DIR Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_ORG_PERIOD_APACHE_PERIOD_FELIX_PERIOD_EVENTADMIN_PERIOD__UPPERCASET_HREAD_UPPERCASEP_OOL_UPPERCASES_IZE

    module.framework.properties.dependency.manager.sync.timeout=60
    module.framework.properties.dependency.manager.thread.pool.enabled=true
    module.framework.properties.ds.lock.timeout.milliseconds=1800000
    module.framework.properties.ds.stop.timeout.milliseconds=1800000
    module.framework.properties.eclipse.stateSaveDelayInterval=60000
    module.framework.properties.felix.cm.pm=com.liferay.portal.configuration.persistence.internal.ConfigurationPersistenceManager
    module.framework.properties.felix.fileinstall.bundles.new.start=true
    module.framework.properties.felix.fileinstall.bundles.startActivationPolicy=false
    module.framework.properties.felix.fileinstall.bundles.startTransient=false
    module.framework.properties.felix.fileinstall.disableNio2=true
    module.framework.properties.felix.fileinstall.log.level=2
    module.framework.properties.felix.fileinstall.noInitialDelay=true
    module.framework.properties.felix.fileinstall.optionalImportRefreshScope=managed
    module.framework.properties.felix.fileinstall.subdir.mode=skip
    module.framework.properties.gosh.args=--noshutdown
    module.framework.properties.initial.system.check.enabled=false
    module.framework.properties.lpkg.deployer.dir=${module.framework.base.dir}/marketplace
    module.framework.properties.org.apache.felix.eventadmin.ThreadPoolSize=2

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_ORG_PERIOD_OSGI_PERIOD_FRAMEWORK_PERIOD_BOOTDELEGATION

    module.framework.properties.org.osgi.framework.bootdelegation=\
        __redirected,\
        com.liferay.aspectj,\
        com.liferay.aspectj.*,\
        com.liferay.expando.kernel.model,\
        com.liferay.portal.servlet.delegate,\
        com.liferay.portal.servlet.delegate*,\
        com.sun.ccpp,\
        com.sun.ccpp.*,\
        com.sun.crypto.*,\
        com.sun.image.*,\
        com.sun.jmx.*,\
        com.sun.jna,\
        com.sun.jndi.*,\
        com.sun.mail.*,\
        com.sun.management.*,\
        com.sun.media.*,\
        com.sun.msv.*,\
        com.sun.org.*,\
        com.sun.syndication,\
        com.sun.tools.*,\
        com.sun.xml.*,\
        com.yourkit.*,\
        jdk.*,\
        sun.*,\
        weblogic.jndi,\
        weblogic.jndi.*

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_ORG_PERIOD_OSGI_PERIOD_FRAMEWORK_PERIOD_BUNDLE_PERIOD_PARENT

    module.framework.properties.org.osgi.framework.bundle.parent=framework

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_ORG_PERIOD_OSGI_PERIOD_FRAMEWORK_PERIOD_SYSTEM_PERIOD_CAPABILITIES_PERIOD_EXTRA

    module.framework.properties.org.osgi.framework.system.capabilities.extra=

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_OSGI_PERIOD_BUNDLEFILE_PERIOD_LIMIT Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_OSGI_PERIOD_COMPATIBILITY_PERIOD_EAGER_UPPERCASES_TART_PERIOD__UPPERCASEL_AZY_UPPERCASEA_CTIVATION Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_OSGI_PERIOD_CONTEXT_PERIOD_BOOTDELEGATION Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_OSGI_PERIOD_MODULE_PERIOD_LOCK_PERIOD_TIMEOUT

    module.framework.properties.osgi.bundlefile.limit=100000
    module.framework.properties.osgi.compatibility.eagerStart.LazyActivation=false
    module.framework.properties.osgi.context.bootdelegation=false
    module.framework.properties.osgi.module.lock.timeout=3600

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_PROPERTIES_PERIOD_SPIFLY_PERIOD_SPI_PERIOD_CONSUMER_PERIOD_HEADER_PERIOD_ENABLED

    module.framework.properties.spifly.spi.consumer.header.enabled=false

Set this true to enable exporting passwords to configuration files.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_EXPORT_PERIOD_PASSWORD_PERIOD_ATTRIBUTES

    module.framework.export.password.attributes=false

Module Framework Web Application Bundles

Web Application Bundles (WABs) are defined by the OSGi standard and represent web applications as valid OSGi bundles.

Enable or disable specific bnd plugins used by the web generator.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_GENERATOR_PERIOD_BND_PERIOD_PLUGIN_PERIOD_ENABLED_OPENBRACKET_A_UPPERCASEQ_UTE_PERIOD_BND_PERIOD_CDI_PERIOD__UPPERCASEC__UPPERCASED__UPPERCASEI__UPPERCASEA_NNOTATIONS_CLOSEBRACKET_ Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_GENERATOR_PERIOD_BND_PERIOD_PLUGIN_PERIOD_ENABLED_OPENBRACKET_A_UPPERCASEQ_UTE_PERIOD_BND_PERIOD_METATYPE_PERIOD__UPPERCASEM_ETATYPE_UPPERCASEA_NNOTATIONS_CLOSEBRACKET_

    module.framework.web.generator.bnd.plugin.enabled[aQute.bnd.cdi.CDIAnnotations]=true
    module.framework.web.generator.bnd.plugin.enabled[aQute.bnd.metatype.MetatypeAnnotations]=true

Set a comma delimited list of packages to include for all WABs.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_GENERATOR_PERIOD_DEFAULT_PERIOD_SERVLET_PERIOD_PACKAGES

    module.framework.web.generator.default.servlet.packages=\
        com.liferay.portal.model,\
        com.liferay.portal.security.access.control,\
        com.liferay.portal.security.auth,\
        com.liferay.portal.security.permission,\
        com.liferay.portal.service,\
        com.liferay.portal.servlet,\
        com.liferay.portal.servlet.filters.aggregate,\
        com.liferay.portal.servlet.filters.dynamiccss,\
        com.liferay.portal.osgi.web.servlet.jsp.compiler,\
        com.liferay.portal.spring.context,\
        com.liferay.portal.theme,\
        com.liferay.portal.util,\
        com.liferay.portlet,\
        com.sun.el,\
        com.sun.el.lang,\
        com.sun.el.parser,\
        com.sun.el.stream,\
        com.sun.el.util,\
        org.apache.commons.chain.generic,\
        org.apache.naming.java,\
        \
        #
        # WebSocketSupport
        #
        \
        com.ibm.websphere.wsoc,\
        io.undertow.websockets.jsr,\
        javax.websocket,\
        javax.websocket.server,\
        org.apache.tomcat.websocket.server,\
        weblogic.websocket.tyrus

Set a comma delimited list of paths to exclude from all WABs.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_GENERATOR_PERIOD_EXCLUDED_PERIOD_PATHS

    module.framework.web.generator.excluded.paths=\
        WEB-INF/lib/ant.jar,\
        WEB-INF/lib/asm-debug-all.jar,\
        WEB-INF/lib/aspectj-rt.jar,\
        WEB-INF/lib/bnd.jar,\
        WEB-INF/lib/ccpp.jar,\
        WEB-INF/lib/commons-beanutils.jar,\
        WEB-INF/lib/commons-chain.jar,\
        WEB-INF/lib/commons-codec.jar,\
        WEB-INF/lib/commons-collections.jar,\
        WEB-INF/lib/commons-discovery.jar,\
        WEB-INF/lib/commons-fileupload.jar,\
        WEB-INF/lib/commons-httpclient.jar,\
        WEB-INF/lib/commons-io.jar,\
        WEB-INF/lib/commons-lang.jar,\
        WEB-INF/lib/commons-logging.jar,\
        WEB-INF/lib/commons-logging-1.1.1.jar,\
        WEB-INF/lib/dom4j.jar,\
        WEB-INF/lib/el-api.jar,\
        WEB-INF/lib/ext-util-bridges.jar,\
        WEB-INF/lib/ext-util-java.jar,\
        WEB-INF/lib/ext-util-taglib.jar,\
        WEB-INF/lib/hibernate-commons-annotations.jar,\
        WEB-INF/lib/hibernate-core.jar,\
        WEB-INF/lib/jackson-databind.jar,\
        WEB-INF/lib/jaxen.jar,\
        WEB-INF/lib/jaxrpc.jar,\
        WEB-INF/lib/jdom.jar,\
        WEB-INF/lib/jms.jar,\
        WEB-INF/lib/jodd.jar,\
        WEB-INF/lib/json-java.jar,\
        WEB-INF/lib/jstl-api.jar,\
        WEB-INF/lib/jstl-impl.jar,\
        WEB-INF/lib/liferay-icu4j.jar,\
        WEB-INF/lib/log4j.jar,\
        WEB-INF/lib/log4j-extras.jar,\
        WEB-INF/lib/mail.jar,\
        WEB-INF/lib/persistence.jar,\
        WEB-INF/lib/portal-impl.jar,\
        WEB-INF/lib/portal-kernel.jar,\
        WEB-INF/lib/portlet.jar,\
        WEB-INF/lib/portletmvc4spring-framework.jar,\
        WEB-INF/lib/rome.jar,\
        WEB-INF/lib/servlet-api.jar,\
        WEB-INF/lib/slf4j-api.jar,\
        WEB-INF/lib/spring-aop.jar,\
        WEB-INF/lib/spring-aspects.jar,\
        WEB-INF/lib/spring-beans.jar,\
        WEB-INF/lib/spring-context.jar,\
        WEB-INF/lib/spring-context-support.jar,\
        WEB-INF/lib/spring-core.jar,\
        WEB-INF/lib/spring-expression.jar,\
        WEB-INF/lib/spring-jdbc.jar,\
        WEB-INF/lib/spring-jms.jar,\
        WEB-INF/lib/spring-orm.jar,\
        WEB-INF/lib/spring-oxm.jar,\
        WEB-INF/lib/spring-tx.jar,\
        WEB-INF/lib/spring-web.jar,\
        WEB-INF/lib/spring-webmvc.jar,\
        WEB-INF/lib/tika-core.jar,\
        WEB-INF/lib/tika-parsers.jar,\
        WEB-INF/lib/util-taglib.jar,\
        WEB-INF/lib/xalan.jar,\
        WEB-INF/lib/xercesImpl.jar,\
        WEB-INF/lib/xercesImpl-2.9.1.jar,\
        WEB-INF/lib/xml-apis.jar,\
        WEB-INF/lib/xml-apis-1.3.04.jar,\
        WEB-INF/lib/xmlsec.jar,\
        WEB-INF/lib/xstream.jar

Set this to true to store the generated WABs.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_GENERATOR_PERIOD_GENERATED_PERIOD_WABS_PERIOD_STORE

    module.framework.web.generator.generated.wabs.store=false

Set the directory where the generated WABs will be stored. This property is not used unless the property "module.framework.web.generator.generated.wabs.store" is set to true.

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_GENERATOR_PERIOD_GENERATED_PERIOD_WABS_PERIOD_STORE_PERIOD_DIR

    module.framework.web.generator.generated.wabs.store.dir=${module.framework.base.dir}/wabs

Set the custom header for all bundles which are deployed through the WAB mechanism. The text within the angle brackets should be replaced with the custom header/value. The header/value format is BND (http://www.aqute.biz/Bnd/Format).

Env: LIFERAY_MODULE_PERIOD_FRAMEWORK_PERIOD_WEB_PERIOD_GENERATOR_PERIOD_HEADERS_PERIOD__LESSTHAN_HEADER_GREATERTHAN_

    module.framework.web.generator.headers.
=

Set the specific WAB bundle for which the custom header defined in "module.framework.web.generator.headers.

    module.framework.web.generator.headers.Import-Package[my-hook]=

    module.framework.web.generator.headers.DynamicImport-Package=

    module.framework.web.generator.headers.Export-Package=

    module.framework.web.generator.headers.Import-Package=

    module.framework.web.generator.jsp.compiler.dependencies=\
        com.liferay.portal.PortalException,\
        com.liferay.portal.util.PortalImpl,\
        javax.el.ELException,\
        javax.portlet.PortletException,\
        javax.servlet.ServletException,\
        javax.servlet.jsp.JspException

    module.framework.web.servlet.annotation.scanning.blacklist=\
        com/google/,\
        com/ibm/,\
        com/liferay/,\
        com/sun/,\
        de/odysseus/el/,\
        javax/,\
        net/oauth/,\
        net/sf/ehcache/,\
        nu/validator/,\
        org/aopalliance/,\
        org/apache/axis/,\
        org/apache/commons/,\
        org/apache/el/,\
        org/apache/http/,\
        org/apache/sanselan/,\
        org/apache/shindig/,\
        org/apache/shiro/,\
        org/apache/taglibs/,\
        org/cyberneko/,\
        org/eclipse/,\
        org/jdom/,\
        org/joda/,\
        org/json/,\
        org/osgi/,\
        org/slf4j/,\
        org/xmlpull/

    module.framework.web.servlet.annotation.scanning.whitelist=\
        com/liferay/faces/

    multicast.group.address["cluster-link-control"]=239.255.0.1
    multicast.group.port["cluster-link-control"]=23301

    multicast.group.address["cluster-link-control"]=ff0e::8:8:1

    multicast.group.address["cluster-link-udp"]=239.255.0.2
    multicast.group.port["cluster-link-udp"]=23302

    multicast.group.address["cluster-link-udp"]=ff0e::8:8:2

    multicast.group.address["cluster-link-mping"]=239.255.0.3
    multicast.group.port["cluster-link-mping"]=23303

    multicast.group.address["cluster-link-mping"]=ff0e::8:8:3

    multicast.group.address["multi-vm"]=239.255.0.5
    multicast.group.port["multi-vm"]=23305

    notifications.max.events=100

    openoffice.conversion.source.extensions[drawing]=odg

    openoffice.conversion.source.extensions[presentation]=\
        odp,\
        ppt,\
        pptx,\
        sxi

    openoffice.conversion.source.extensions[spreadsheet]=\
        csv,\
        ods,\
        sxc,\
        tsv,\
        xls,\
        xlsx

    openoffice.conversion.source.extensions[text]=\
        doc,\
        docx,\
        html,\
        odt,\
        rtf,\
        sxw,\
        txt,\
        wpd

    openoffice.conversion.target.extensions[drawing]=\
        pdf,\
        svg,\
        swf

    openoffice.conversion.target.extensions[presentation]=\
        odp,\
        pdf,\
        ppt,\
        swf,\
        sxi

    openoffice.conversion.target.extensions[spreadsheet]=\
        csv,\
        ods,\
        pdf,\
        sxc,\
        tsv,\
        xls

    openoffice.conversion.target.extensions[text]=\
        doc,\
        odt,\
        pdf,\
        rtf,\
        sxw,\
        txt

    phone.number.format.impl=com.liferay.portal.format.IdenticalPhoneNumberFormatImpl
    phone.number.format.impl=com.liferay.portal.format.InternationalPhoneNumberFormatImpl
    phone.number.format.impl=com.liferay.portal.format.USAPhoneNumberFormatImpl

    phone.number.format.international.regexp=^\\+[0-9]{1,3}\.[0-9]{4,14}(?:x.+)?$

    phone.number.format.usa.regexp=^(?:\\+?1[-. ]?)?(?:\\(?([0-9]{3})\\)?[-. ]?)?([0-9]{3})[-. ]?([0-9]{4})$

    poller.notifications.timeout=1000

    poller.request.timeout=1000

    pop.server.notifications.enabled=false

    pop.server.notifications.interval=1

    pop.server.subdomain=events

    portal.fabric.enabled=false

    portal.fabric.agent.selector.class=com.liferay.portal.fabric.agent.selectors.MinSystemCPULoadFabricAgentSelector

    portal.fabric.server.host=0.0.0.0

    portal.fabric.server.port=8923

    portal.fabric.server.boss.group.thread.count=1

    portal.fabric.server.worker.group.thread.count=1

    portal.fabric.server.worker.startup.timeout=60000

    portal.fabric.server.file.server.folder.compression.level=1

    portal.fabric.server.file.server.group.thread.count=1

    portal.fabric.server.registeration.group.thread.count=1

    portal.fabric.server.repository.parent.folder=NettyFabricServer-repository-parent

    portal.fabric.server.repository.get.file.timeout=600000

    portal.fabric.server.rpc.group.thread.count=1

    portal.fabric.server.rpc.relay.timeout=600000

    portal.fabric.server.warmup.agent.on.register=true

    portal.fabric.shutdown.quiet.period=0

    portal.fabric.shutdown.timeout=60000

    portal.resiliency.enabled=false

    portal.resiliency.portlet.show.footer=false

    portal.resiliency.spi.agent.client.pool.max.size=20

    memory.scheduler.org.quartz.jobStore.class=org.quartz.simpl.RAMJobStore

    memory.scheduler.org.quartz.scheduler.instanceId=AUTO
    memory.scheduler.org.quartz.scheduler.instanceName=MemoryQuartzSchedulerEngineInstance

    memory.scheduler.org.quartz.scheduler.jobFactory.class=org.quartz.simpl.PropertySettingJobFactory

    memory.scheduler.org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool

    memory.scheduler.org.quartz.threadPool.threadCount=5
    memory.scheduler.org.quartz.threadPool.threadPriority=5

    persisted.scheduler.org.quartz.dataSource.ds.connectionProvider.class=com.liferay.portal.scheduler.quartz.internal.QuartzConnectionProvider

    persisted.scheduler.org.quartz.jobStore.class=com.liferay.portal.scheduler.quartz.internal.PortalJobStore

    persisted.scheduler.org.quartz.jobStore.dataSource=ds

    persisted.scheduler.org.quartz.jobStore.misfireThreshold=60000

    persisted.scheduler.org.quartz.jobStore.tablePrefix=QUARTZ_

    persisted.scheduler.org.quartz.jobStore.useProperties=false
    persisted.scheduler.org.quartz.scheduler.instanceId=AUTO
    persisted.scheduler.org.quartz.scheduler.instanceName=PersistedQuartzSchedulerEngineInstance

    persisted.scheduler.org.quartz.scheduler.jobFactory.class=org.quartz.simpl.PropertySettingJobFactory

    persisted.scheduler.org.quartz.scheduler.skipUpdateCheck=true

    persisted.scheduler.org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool

    persisted.scheduler.org.quartz.threadPool.threadCount=5
    persisted.scheduler.org.quartz.threadPool.threadPriority=5

    rest.proxy.url.prefixes.allowed=http://search.yahooapis.com/ContentAnalysisService

    retry.advice.max.retries=5

    retry.data.source.max.retries=0

    retry.jdbc.on.startup.delay=0

    retry.jdbc.on.startup.max.retries=0

    robots.txt.with.sitemap=com/liferay/portal/dependencies/robots_txt_with_sitemap.tmpl
    robots.txt.without.sitemap=com/liferay/portal/dependencies/robots_txt_without_sitemap.tmpl

    rss.connection.timeout=2000

    rss.feeds.enabled=true

    rss.feed.display.style.default=full-content

    rss.feed.type.default=atom_1.0

    rss.feed.types=\
        atom_1.0,\
        rss_1.0,\
        rss_2.0

    rss.feeds.hosts.allowed=
    rss.feeds.https.required=false

    rss.publish.to.live.by.default=true

    rtl.css.excluded.paths.regexp=.*\\/ckeditor\\/.*

    sanitizer.impl=

    scheduler.enabled=true

    scheduler.description.max.length=120
    scheduler.group.name.max.length=80
    scheduler.job.name.max.length=80

    scheduler.event.message.listener.lock.timeout=0

    scripting.jruby.compile.mode=jit

    scripting.jruby.compile.mode=force
    scripting.jruby.compile.mode=off

    scripting.jruby.compile.threshold=5

    search.container.page.default.delta=20

    search.container.page.delta.values=\
        5,\
        10,\
        20,\
        30,\
        50,\
        75

    search.container.page.iterator.max.pages=25

    search.container.show.pagination.top=true
    search.container.show.pagination.bottom=true

    search.container.show.pagination.top.delta=10

    sharepoint.storage.tokens=document_library

    sharepoint.storage.class[document_library]=com.liferay.portlet.documentlibrary.sharepoint.DLSharepointStorageImpl

    sprite.enabled=false

    sprite.file.name=_sprite.png
    sprite.properties.file.name=_sprite.properties

    sprite.root.dir=

    staging.live.group.locking.enabled=true

    staging.live.group.remote.staging.enabled=false

    staging.remote.transfer.buffer.size=10485760

    staging.system.event.check.interval=24

    staging.system.event.max.age=0

    strip.ignore.paths=/document_library/get_file

    strip.js.language.attribute.support.enabled=false

    strip.mime.types=\
        text/html*,\
        text/xml*

    social.activity.counter.period.length=month

    social.activity.lock.retry.delay=100

    social.activity.lock.timeout=10000

    social.activity.filter.search.limit=200

    social.activity.sets.selector=

    text.extraction.fork.process.enabled=false

    text.extraction.fork.process.mime.types=application/x-tika-ooxml

    thread.dump.speed.threshold=5

    user.notification.event.confirmation.enabled=false

    virtual.hosts.ignore.extensions=\
        .css,\
        .gif,\
        .image/company_logo,\
        .ico,\
        .js,\
        .jpeg,\
        .jsp,\
        .png,\
        /portal/layout,\
        /portal/login,\
        /portal/logout

    virtual.hosts.ignore.hosts=\
        127.0.0.1,\
        localhost

    virtual.hosts.ignore.paths=\
        /c,\
        \
        /c/portal/change_password,\
        /c/portal/edit_layout,\
        /c/portal/extend_session,\
        /c/portal/extend_session_confirm,\
        /c/portal/json_service,\
        /c/portal/layout,\
        /c/portal/login,\
        /c/portal/logout,\
        /c/portal/portlet_url,\
        /c/portal/progress_poller,\
        /c/portal/render_portlet,\
        /c/portal/reverse_ajax,\
        /c/portal/session_tree_js_click,\
        /c/portal/status,\
        /c/portal/update_layout,\
        /c/portal/update_terms_of_use

    virtual.hosts.default.site.name=Guest

    virtual.hosts.valid.hosts=*

    virtual.hosts.valid.hosts=localhost,127.0.0.1,[::1],[0:0:0:0:0:0:0:1]

    work.dir.override.enabled=false

    xml.security.enabled=true

    xml.sitemap.index.enabled=true

    xml.validation.enabled=true

    xuggler.enabled=false

    xuggler.jar.file[32-linux]=xuggle-xuggler-arch-i686-pc-linux-gnu.jar
    xuggler.jar.file[32-mac]=xuggle-xuggler-arch-i386-xuggle-darwin11.jar
    xuggler.jar.file[32-win]=xuggle-xuggler-arch-i686-w64-mingw32.jar
    xuggler.jar.file[64-linux]=xuggle-xuggler-arch-x86_64-pc-linux-gnu.jar
    xuggler.jar.file[64-mac]=xuggle-xuggler-arch-x86_64-xuggle-darwin11.jar
    xuggler.jar.file[64-win]=xuggle-xuggler-arch-x86_64-w64-mingw32_LIFERAY-PATCHED-1.jar
    xuggler.jar.name[32-linux]=Linux 32-bit JVM (with GNU libc v6)
    xuggler.jar.name[32-mac]=Mac OS X 10.7 32-bit JVM
    xuggler.jar.name[32-win]=Windows 32-bit JVM
    xuggler.jar.name[64-linux]=Linux 64-bit JVM (with GNU libc v6)
    xuggler.jar.name[64-mac]=Mac OS X 10.7 64-bit JVM
    xuggler.jar.name[64-win]=Windows 64-bit JVM
    xuggler.jar.url=https://files.liferay.com/mirrors/xuggle.googlecode.com/svn/trunk/repo/share/java/xuggle/xuggle-xuggler/5.4/

    xuggler.jar.options=\
        32-linux,\
        32-mac,\
        32-win,\
        64-linux,\
        64-mac,\
        64-win

    xuggler.ffpreset.8x8dct=0
    xuggler.ffpreset.bf=0
    xuggler.ffpreset.cmp=+chroma
    xuggler.ffpreset.coder=0
    xuggler.ffpreset.flags=+loop
    xuggler.ffpreset.i_qfactor=0.71
    xuggler.ffpreset.mbtree=1
    xuggler.ffpreset.me_method=umh
    xuggler.ffpreset.me_range=16
    xuggler.ffpreset.qcomp=0.6
    xuggler.ffpreset.qdiff=4
    xuggler.ffpreset.qmin=10
    xuggler.ffpreset.qmax=51
    xuggler.ffpreset.sc_threshold=40
    xuggler.ffpreset.subq=8
    xuggler.ffpreset.trellis=0
    xuggler.ffpreset.wpredp=0

    xuggler.ffpreset.flags2=-wpred-dct8x8+mbtree

    yui.compressor.css.line.break=-1

    jsp.page.context.force.get.attribute=true

    jsp.servlet.init.param.keepgenerated=true

    jsp.servlet.init.param.compilerClassName=
    jsp.servlet.init.param.compilerSourceVM=
    jsp.servlet.init.param.compilerTargetVM=

    jsp.servlet.init.param.enablePooling=false

    jsp.writer.buffer.size=0

    servlet.context.class.loader.pool.fallback=false

    com.liferay.portal.servlet.filters.absoluteredirects.AbsoluteRedirectsFilter=true

    com.liferay.portal.servlet.filters.aggregate.AggregateFilter=true

    com.liferay.portal.servlet.filters.authverifier.AuthVerifierFilter=true

    com.liferay.portal.servlet.filters.autologin.AutoLoginFilter=true

    com.liferay.portal.servlet.filters.cache.CacheFilter=true

    com.liferay.portal.servlet.filters.sso.cas.CASFilter=true

    com.liferay.portal.servlet.filters.dynamiccss.DynamicCSSFilter=true

    com.liferay.portal.servlet.filters.etag.ETagFilter=true

    com.liferay.portal.servlet.filters.gzip.GZipFilter=false

    com.liferay.portal.servlet.filters.header.HeaderFilter=true

    com.liferay.portal.servlet.filters.ignore.IgnoreFilter=true

    com.liferay.portal.servlet.filters.i18n.I18nFilter=true

    com.liferay.portal.servlet.filters.jsoncontenttype.JSONContentTypeFilter=false

    com.liferay.portal.servlet.filters.language.LanguageFilter=true

    com.liferay.portal.servlet.filters.password.modified.PasswordModifiedFilter=true

    com.liferay.portal.servlet.filters.sso.ntlm.NtlmFilter=true

    com.liferay.portal.servlet.filters.sso.ntlm.NtlmPostFilter=true

    com.liferay.portal.servlet.filters.sso.opensso.OpenSSOFilter=true

    com.liferay.portal.servlet.filters.servletauthorizing.ServletAuthorizingFilter=true

    com.liferay.portal.servlet.filters.sessionid.SessionIdFilter=false

    com.liferay.portal.servlet.filters.sessionmaxallowed.SessionMaxAllowedFilter=false

    com.liferay.portal.sharepoint.SharepointFilter=true

    com.liferay.portal.servlet.filters.strip.StripFilter=false

    com.liferay.portal.servlet.filters.themepreview.ThemePreviewFilter=false

    com.liferay.portal.servlet.filters.threaddump.ThreadDumpFilter=false

    com.liferay.portal.servlet.filters.threadlocal.ThreadLocalFilter=true

    com.liferay.portal.servlet.filters.unsyncprintwriterpool.UnsyncPrintWriterPoolFilter=true

    com.liferay.portal.servlet.filters.uploadservletrequest.UploadServletRequestFilter=true

    com.liferay.portal.servlet.filters.urlrewrite.UrlRewriteFilter=true

    com.liferay.portal.servlet.filters.validhostname.ValidHostNameFilter=true

    com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter=true

    com.liferay.portal.upload.LiferayFileItem.threshold.size=262144

    com.liferay.portal.upload.LiferayInputStream.threshold.size=10485760

    web.server.http.port=-1
    web.server.https.port=-1

    web.server.host=

    web.server.protocol=https

    web.server.display.node=false

    web.server.forwarded.host.enabled=false

    web.server.forwarded.host.header=X-Forwarded-Host

    web.server.forwarded.port.enabled=false

    web.server.forwarded.port.header=X-Forwarded-Port

    web.server.forwarded.protocol.enabled=false

    web.server.forwarded.protocol.header=X-Forwarded-Proto

    web.server.proxy.legacy.mode=false

    webdav.ignore=\
        .DS_Store,\
        .metadata_index_homes_only,\
        .metadata_never_index,\
        .Spotlight-V100,\
        .TemporaryItems,\
        .Trashes,\
        Backups.backupdb

    webdav.nonce.cluster.timeout=10000

    webdav.nonce.expiration=30

    main.servlet.hosts.allowed=

    main.servlet.https.required=false

    atom.servlet.hosts.allowed=\
        127.0.0.1,\
        SERVER_IP

    atom.servlet.https.required=false

    axis.servlet.hosts.allowed=\
        127.0.0.1,\
        SERVER_IP

    axis.servlet.https.required=false

    dynamic.resource.servlet.allowed.paths=\
        /sprite

    google.gadget.servlet.mapping=/google_gadget

    json.servlet.hosts.allowed=
    json.servlet.https.required=false

    jsonws.servlet.hosts.allowed=
    jsonws.servlet.https.required=false

    netvibes.servlet.mapping=/netvibes

    tunnel.servlet.hosts.allowed=\
        127.0.0.1,\
        SERVER_IP

    tunnel.servlet.https.required=false

    web.server.servlet.accept.ranges.mime.types=\
        audio/basic,\
        audio/mid,\
        audio/midi,\
        audio/mod,\
        audio/mp3,\
        audio/mp4,\
        audio/mpeg,\
        audio/mpeg3,\
        audio/ogg,\
        audio/vorbis,\
        audio/wav,\
        audio/x-m4a,\
        audio/x-mid,\
        audio/x-midi,\
        audio/x-mod,\
        audio/x-mpeg,\
        audio/x-pn-realaudio,\
        audio/x-realaudio,\
        audio/x-wav,\
        video/avi,\
        video/mp4,\
        video/mpeg,\
        video/ogg,\
        video/quicktime,\
        video/x-flv,\
        video/x-m4v,\
        video/x-ms-wmv,\
        video/x-msvideo

    web.server.servlet.check.image.gallery=false

    web.server.servlet.directory.indexing.enabled=false

    web.server.servlet.max.range.fields=10

    web.server.servlet.version.verbosity=full

    webdav.servlet.hosts.allowed=
    webdav.servlet.https.required=false

    widget.servlet.mapping=/widget

    admin.default.group.names=

    admin.default.organization.group.names=

    admin.default.role.names=User

    admin.default.user.group.names=

    admin.sync.default.associations=false

    admin.mail.host.names=

    admin.reserved.screen.names=

    admin.reserved.email.addresses=

    admin.email.from.name=Joe Bloggs
    admin.email.from.address=test@domain.invalid

    admin.email.user.added.enabled=true
    admin.email.user.added.subject=com/liferay/portlet/admin/dependencies/email_user_added_subject.tmpl
    admin.email.user.added.no.password.body=com/liferay/portlet/admin/dependencies/email_user_added_no_password_body.tmpl
    admin.email.user.added.reset.password.body=com/liferay/portlet/admin/dependencies/email_user_added_reset_password_body.tmpl

    admin.email.password.changed.subject=com/liferay/portlet/admin/dependencies/email_password_changed_subject.tmpl
    admin.email.password.changed.body=com/liferay/portlet/admin/dependencies/email_password_changed_body.tmpl

    admin.email.password.reset.subject=com/liferay/portlet/admin/dependencies/email_password_reset_subject.tmpl
    admin.email.password.reset.body=com/liferay/portlet/admin/dependencies/email_password_reset_body.tmpl

    admin.email.verification.subject=com/liferay/portlet/admin/dependencies/email_verification_subject.tmpl
    admin.email.verification.body=com/liferay/portlet/admin/dependencies/email_verification_body.tmpl

    admin.analytics.types=google\npiwik

    admin.obfuscated.properties=\
        auth.mac.shared.key,\
        auth.token.shared.secret,\
        default.admin.password,\
        dl.file.entry.preview.generation.decrypt.passwords.pdfbox,\
        dl.repository.guest.password,\
        jdbc.default.password,\
        mail.session.mail.pop3.password,\
        mail.session.mail.smtp.password,\
        tunneling.servlet.shared.secret

    announcements.email.from.name=
    announcements.email.from.address=

    announcements.email.to.name=
    announcements.email.to.address=noreply@domain.invalid

    announcements.email.subject=com/liferay/portlet/announcements/dependencies/email_subject.tmpl
    announcements.email.body=com/liferay/portlet/announcements/dependencies/email_body.tmpl

    announcements.entry.types=\
        general,\
        news,\
        test

    announcements.entry.check.interval=15

    announcements.entry.page.delta.values=\
        5,\
        10,\
        20,\
        30,\
        50,\
        75

    asset.categories.properties.default=

    asset.categories.search.hierarchical=true

    asset.categories.selector.max.entries=50

    asset.filter.search.limit=200

    asset.vocabulary.default=Topic

    asset.renderer.enabled.com.liferay.portlet.documentlibrary.asset.DLFileEntryAssetRendererFactory=false

    blogs.entry.comments.enabled=true

    blogs.email.from.name=
    blogs.email.from.address=

    blogs.email.entry.added.enabled=true
    blogs.email.entry.added.subject=${resource:com/liferay/portlet/blogs/dependencies/email_entry_added_subject.tmpl}
    blogs.email.entry.added.body=${resource:com/liferay/portlet/blogs/dependencies/email_entry_added_body.tmpl}

    blogs.email.entry.updated.enabled=true
    blogs.email.entry.updated.subject=${resource:com/liferay/portlet/blogs/dependencies/email_entry_updated_subject.tmpl}
    blogs.email.entry.updated.body=${resource:com/liferay/portlet/blogs/dependencies/email_entry_updated_body.tmpl}

    blogs.page.abstract.length=400

    blogs.rss.abstract.length=200

    blogs.linkback.excerpt.length=200

    blogs.pingback.enabled=true

    blogs.trackback.enabled=false

    blogs.ping.google.enabled=true

    blogs.entry.page.delta.values=\
        5,\
        10,\
        20,\
        30,\
        50,\
        75

    blogs.entry.previous.and.next.navigation.enabled=true

    blogs.publish.to.live.by.default=false

    calendar.publish.to.live.by.default=true

    discussion.subscribe=true

     allowed-content : element (; element)*
         element : element-name | element-name[attribute (, atribute)*]

    discussion.comments.allowed.content=a[href];em;p;span[class];strong;u

    discussion.comments.allowed.content=a[href,title];em;p;strong;u

    discussion.comments.always.editable.by.owner=false

    discussion.comments.delta.value=50

    discussion.comments.format=html

    discussion.comments.format=bbcode

    discussion.max.comments=1000

    dl.actions.visible=false

    dl.comment.ratings.enabled=true

    dl.display.views=\
        icon,\
        descriptive,\
        list

    dl.entry.columns=\
        name,\
        document-type,\
        size,\
        status,\
        modified-date,\
        create-date,\
        action

    dl.file.entry.columns=\
        name,\
        size,\
        locked

    dl.folder.columns=\
        name,\
        num-of-folders,\
        num-of-documents

    dl.folders.search.visible=true

    dl.ratings.enabled=true

    dl.related.assets.enabled=true

    dl.subfolders.visible=true

    dl.email.from.name=
    dl.email.from.address=

    dl.email.file.entry.added.enabled=true
    dl.email.file.entry.added.subject=${resource:com/liferay/portlet/documentlibrary/dependencies/email_file_entry_added_subject.tmpl}
    dl.email.file.entry.added.body=${resource:com/liferay/portlet/documentlibrary/dependencies/email_file_entry_added_body.tmpl}

    dl.email.file.entry.updated.enabled=true
    dl.email.file.entry.updated.subject=${resource:com/liferay/portlet/documentlibrary/dependencies/email_file_entry_updated_subject.tmpl}
    dl.email.file.entry.updated.body=${resource:com/liferay/portlet/documentlibrary/dependencies/email_file_entry_updated_body.tmpl}

    dl.store.antivirus.enabled=false

    dl.store.antivirus.impl=com.liferay.portlet.documentlibrary.antivirus.DummyAntivirusScannerImpl

    dl.store.antivirus.impl=com.liferay.portlet.documentlibrary.antivirus.ClamAntivirusScannerImpl

    dl.store.file.impl.safe.file.name.2.ampersand=_AMP_
    dl.store.file.impl.safe.file.name.2.close.parenthesis=_CP_
    dl.store.file.impl.safe.file.name.2.open.parenthesis=_OP_
    dl.store.file.impl.safe.file.name.2.semicolon=_SEM_

    dl.store.impl=com.liferay.portal.store.file.system.FileSystemStore

    dl.store.impl=com.liferay.portal.store.db.DBStore
    dl.store.impl=com.liferay.portal.store.file.system.AdvancedFileSystemStore
    dl.store.impl=com.liferay.portal.store.s3.S3Store

    dl.file.extensions.strict.check=false

    dl.char.blacklist=\\\\,//,:,*,?,\",<,>,|,../,/..

    dl.char.last.blacklist=\\u0020,.

    dl.name.blacklist=\
        con,\
        prn,\
        aux,\
        nul,\
        com1,\
        com2,\
        com3,\
        com4,\
        com5,\
        com6,\
        com7,\
        com8,\
        com9,\
        lpt1,\
        lpt2,\
        lpt3,\
        lpt4,\
        lpt5,\
        lpt6,\
        lpt7,\
        lpt8,\
        lpt9

    dl.file.generic.names=\
        compressed,\
        document,\
        flash,\
        image,\
        music,\
        pdf,\
        presentation,\
        spreadsheet,\
        video

    dl.file.generic.extensions[compressed]=\
        lar,\
        rar,\
        zip

    dl.file.generic.extensions[document]=\
        doc,\
        docx,\
        pages,\
        rtf,\
        odt

    dl.file.generic.extensions[flash]=\
        flv,\
        swf

    dl.file.generic.extensions[image]=\
        bmp,\
        gif,\
        jpeg,\
        jpg,\
        odg,\
        png,\
        svg

    dl.file.generic.extensions[music]=\
        acc,\
        mid,\
        mp3,\
        oga,\
        ogg,\
        wav,\
        wma

    dl.file.generic.extensions[pdf]=pdf

    dl.file.generic.extensions[presentation]=\
        key,\
        keynote,\
        odp,\
        pps,\
        ppt,\
        pptx

    dl.file.generic.extensions[spreadsheet]=\
        csv,\
        numbers,\
        ods,\
        xls,\
        xlsx

    dl.file.generic.extensions[video]=\
        avi,\
        m4v,\
        mov,\
        mp4,\
        mpg,\
        ogv,\
        qt,\
        rm,\
        wmv

    dl.file.indexing.max.size=1048576

    dl.file.indexing.ignore.extensions=\
        .bmp,\
        .gif,\
        .jpeg,\
        .jpg,\
        .lar,\
        .odg,\
        .png,\
        .svg

    dl.file.indexing.ignore.extensions=.pdf,.ppt

    dl.file.indexing.interval=500

    dl.file.icons=\
        .bmp,\
        .css,\
        .doc,\
        .docx,\
        .dot,\
        .gif,\
        .gz,\
        .htm,\
        .html,\
        .jpeg,\
        .jpg,\
        .js,\
        .lar,\
        .odb,\
        .odf,\
        .odg,\
        .odp,\
        .ods,\
        .odt,\
        .pdf,\
        .png,\
        .ppt,\
        .pptx,\
        .rtf,\
        .swf,\
        .sxc,\
        .sxi,\
        .sxw,\
        .tar,\
        .tiff,\
        .tgz,\
        .txt,\
        .vsd,\
        .xls,\
        .xlsx,\
        .xml,\
        .zip,\
        .jrxml

    dl.folder.icon.check.count=true

    dl.comparable.file.extensions=\
        .css,\
        .doc,\
        .docx,\
        .js,\
        .htm,\
        .html,\
        .odt,\
        .rtf,\
        .sxw,\
        .txt,\
        .xml

    dl.file.entry.comments.enabled=true

    dl.file.entry.conversions.enabled=true

    dl.file.entry.drafts.enabled=false

    dl.file.entry.lock.policy=0

    dl.file.entry.open.in.ms.office.manual.check.in.required=false

    dl.file.entry.processors=\
        com.liferay.portlet.documentlibrary.util.AudioProcessorImpl,\
        com.liferay.portlet.documentlibrary.util.ImageProcessorImpl,\
        com.liferay.portlet.documentlibrary.util.PDFProcessorImpl,\
        com.liferay.portlet.documentlibrary.util.RawMetadataProcessorImpl,\
        com.liferay.portlet.documentlibrary.util.VideoProcessorImpl

    dl.file.entry.raw.metadata.processor.excluded.mime.types=application/zip

    dl.file.entry.version.policy=1

    dl.file.entry.preview.enabled=true
    dl.file.entry.preview.document.depth=8
    dl.file.entry.preview.document.dpi=300
    dl.file.entry.preview.document.max.height=0
    dl.file.entry.preview.document.max.width=1000
    dl.file.entry.preview.video.height=360
    dl.file.entry.preview.video.width=640
    dl.file.entry.thumbnail.enabled=true
    dl.file.entry.thumbnail.max.height=300
    dl.file.entry.thumbnail.max.width=300
    dl.file.entry.thumbnail.video.frame.percentage=25

    dl.file.entry.thumbnail.custom1.max.height=100
    dl.file.entry.thumbnail.custom1.max.width=100
    dl.file.entry.thumbnail.custom2.max.height=0
    dl.file.entry.thumbnail.custom2.max.width=0

    dl.file.entry.preview.audio.containers=\
        mp3,\
        ogg

    dl.file.entry.preview.audio.containers=mp3
    dl.file.entry.preview.audio.containers=ogg

    dl.file.entry.preview.audio.bit.rate[mp3]=64000
    dl.file.entry.preview.audio.sample.rate[mp3]=44100

    dl.file.entry.preview.audio.bit.rate[ogg]=64000
    dl.file.entry.preview.audio.sample.rate[ogg]=44100