Installing on WildFly

Installing on WildFly requires deploying dependencies, modifying scripts, modifying config xml files, and deploying the DXP WAR file. In addition, make the optional database and mail server configurations to optimize the DXP instance.

Liferay DXP requires Java JDK 8 or 11. See the compatibility matrix for further information.

Download these files from the Help Center (subscription) or from Liferay Community Downloads. Administrators must download the following:

  • DXP WAR file

  • Dependencies ZIP file

  • OSGi Dependencies ZIP file

Before proceeding, you should understand the difference between Liferay Home and $WILDFLY_HOME because they are referenced below as shorthand:

  • Liferay.home is the folder containing the WildFly server folder. After installing and deploying DXP, the Liferay Home folder contains the WildFly server folder as well as data, deploy, logs, and osgi folders.

  • $WILDFLY_HOME refers to the WildFly server folder. It is usually named wildfly-[version].

Installing Liferay DXP on WildFly requires the following steps:

  1. Installing dependencies to the application server

  2. Configuring the application server for DXP

  3. Connect to a Database

  4. Connect to a Mail Server

  5. Deploying the DXP WAR file to the application server

Installing Dependencies

  1. Create the folder $WILDFLY_HOME/modules/com/liferay/portal/main if it does not already exist and extract the Dependencies ZIP JARs here.

  2. The Portal/DXP 7.4+ WAR includes drivers for MariaDB, MySQL, and PostgreSQL. Earlier WARs don’t have them. If your WAR doesn’t have the driver you want, download your database vendor’s JDBC JAR file to the $WILDFLY_HOME/modules/com/liferay/portal/main folder. Please see the compatibility matrix for a list of supported databases.

  3. Create the file module.xml in the $WILDFLY_HOME/modules/com/liferay/portal/main folder. In the file, declare the portal module and all of its required resources and dependencies:

    <?xml version="1.0"?>
    <module xmlns="urn:jboss:module:1.0" name="com.liferay.portal">
            <resource-root path="[place your database vendor's JAR file name here]" />
            <resource-root path="[place a Liferay dependencies ZIP JAR file name here]" />
            <!-- Add a resource-root element for each Liferay dependencies ZIP JAR -->
            <module name="javax.api" />
            <module name="javax.mail.api" />
            <module name="javax.servlet.api" />
            <module name="javax.servlet.jsp.api" />
            <module name="javax.transaction.api" />

    Replace [place your database vendor's JAR file name here] with the driver JAR for your database.

    For each JAR in the Liferay dependencies ZIP, add a resource-root element with its path attribute set to the JAR name. For example, add a resource-root element like this for the com.liferay.petra.concurrent.jar file:

    <resource-root path="com.liferay.petra.concurrent.jar" />
  4. Create an osgi folder in your Liferay Home folder. Extract the OSGi Dependencies ZIP file that you downloaded into the [Liferay Home]/osgi folder.

    The osgi folder provides the necessary modules for the OSGi runtime.


A Hypersonic database is bundled with DXP and is useful for testing purposes. Do not use HSQL for production DXP instances.


  1. The contents of the Dependencies zip have been placed in the $WILDFLY_HOME/modules/com/liferay/portal/main folder.

  2. Your database vendor’s JDBC driver is installed.

  3. The module.xml has listed all JARs in the <resource-root> elements.

  4. The OSGi dependencies have been unzipped in the osgi folder located inside the ${Liferay.home} folder.

Running DXP on WildFly in Standalone Mode vs. Domain Mode

WildFly can be launched in either standalone mode or domain mode. Domain mode allows multiple application server instances to be managed from a single control point. A collection of such application servers is known as a domain. For more information on standalone mode vs. domain mode, please refer to the section on this topic in the WildFly Admin Guide. DXP fully supports WildFly in standalone mode but not in domain mode.

Administrators can run DXP on WildFly in domain mode, but this method is not fully supported. In particular, DXP’s auto-deploy does not work with a managed deployment, since WildFly manages the content of a managed deployment by copying files (exploded or non-exploded). This prevents JSP hooks and Ext plugins from working as intended. For example, JSP hooks don’t work on WildFly running in managed domain mode, since DXP’s JSP override mechanism relies on the application server. Since JSP hooks and Ext plugins are deprecated, however, you may not be using them.

The command line interface is recommended for domain mode deployments.


This does not prevent DXP from running in a clustered environment on multiple WildFly servers. Administrators can set up a cluster of DXP instances running on WildFly servers running in standalone mode. Please refer to the DXP clustering articles for more information.

Configuring WildFly

Configuring WildFly to run DXP includes these things:

  • Setting environment variables

  • Setting properties and descriptors

  • Removing unnecessary configurations

Make the following modifications to $WILDFLY_HOME/standalone/configuration/standalone.xml:

  1. In the <jsp-config> tag, set the Java VM compatibility for Liferay source and class files. They are compatible with Java 8 by default.

    <jsp-config development="true" source-vm="1.8" target-vm="1.8" />
  2. Locate the closing </extensions> tag. Directly beneath that tag, insert the following system properties:

        <property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8" />
        <property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true" />
  3. Add the following <filter-spec> tag within the <console-handler> tag which is directly below the <level name="INFO"/> tag:

    <filter-spec value="not(any(match(&quot;WFLYSRV0059&quot;),match(&quot;WFLYEE0007&quot;)))" />
  4. Add a timeout for the deployment scanner by setting deployment-timeout="600" as seen in the excerpt below.

    <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">
        <deployment-scanner deployment-timeout="600" path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" runtime-failure-causes-rollback="${jboss.deployment.scanner.rollback.on.failure:false}"/>
  5. Add the following JAAS security domain to the security subsystem <security-domains> defined in the element <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">.

    <security-domain name="PortalRealm">
            <login-module code="" flag="required" />
  6. Remove the welcome content code snippets:

    <location name="/" handler="welcome-content"/>


        <file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>


Before continuing, verify the following properties have been set in the standalone.xml file:

  1. The new <system-property> is added.

  2. The new <filter-spec> is added.

  3. The <deployment-timeout> is set to 600.

  4. The new <security-domain> is created.

  5. Welcome content is removed.

Next, configure the JVM and startup scripts:

In the $WILDFLY_HOME/bin/ folder, open the standalone domain’s configuration script file standalone.conf (standalone.conf.bat on Windows):

  • Set the file encoding to UTF-8

  • Set the user time zone to GMT

  • Set the preferred protocol stack

  • Increase the default amount of memory available.


For DXP to work properly, the application server JVM must use the GMT time zone and UTF-8 file encoding.

Make the following edits as applicable for the respective operating system:


  1. Comment out the initial JAVA_OPTS assignment:

    rem set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=2560m"
  2. Add the following JAVA_OPTS assignment one line above the :JAVA_OPTS_SET line found at end of the file:

    set "JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=UTF-8 -Duser.timezone=GMT -Xms2560m -Xmx2560m -XX:MaxMetaspaceSize=512m -XX:MetaspaceSize=200m"


  1. Below the if [ "x$JAVA_OPTS" = "x" ]; statement, replace this JAVA_OPTS statement:

    JAVA_OPTS="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m"

    with this:

  2. Add the following statement to the bottom of the file:

    JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF-8 -Duser.timezone=GMT -Xms2560m -Xmx2560m -XX:MaxMetaspaceSize=512m -XX:MetaspaceSize=200m"

This sets the file encoding to UTF-8, prefers an IPv4 stack over IPv6, sets the time zone to GMT, gives the JVM 2GB of RAM, and limits Metaspace to 512MB.

On JDK 11, add this JVM argument to display four-digit years.


After installation, tune the system (including these JVM options) for performance.

If using the IBM JDK with the WildFly server, complete the following additional steps:

  1. Navigate to the $WILDFLY_HOME/modules/com/liferay/portal/main/module.xml file and insert the following dependency within the <dependencies> element:

    <module name="ibm.jdk" />

  2. Navigate to the $WILDFLY_HOME/modules/system/layers/base/sun/jdk/main/module.xml file and insert the following path names inside the <paths>...</paths> element:

    <path name="com/sun/crypto" />
    <path name="com/sun/crypto/provider" />
    <path name="com/sun/org/apache/xml/internal/resolver" />
    <path name="com/sun/org/apache/xml/internal/resolver/tools" />

The added paths resolve issues with deployment exceptions and image uploading problems.


  1. The file encoding, user time-zone, preferred protocol stack have been set in the JAVA_OPTS in the standalone.conf.bat file.

  2. The default amount of memory available has been increased.

The prescribed script modifications are now complete for the DXP installation on WildFly.

Connect to a Database

The easiest way to handle database configuration is to let DXP manage the data source. Use Basic Configuration to configure DXP’s built-in data source. If using the built-in data source, skip this section.

If using WildFly to manage the data source, follow these steps:

  1. Get the JDBC JAR from your Portal/DXP WAR (7.4+) or from the database vendor and copy it to the $WILDFLY_HOME/modules/com/liferay/portal/main folder.

  2. Add the data source inside the $WILDFLY_HOME/standalone/configuration/standalone.xml file’s <datasources> element:

    <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" jta="true" use-java-context="true" use-ccm="true">
        <connection-url>[place the URL to your database here]</connection-url>
        <driver>[place your driver name here]</driver>
            <user-name>[place your user name here]</user-name>
            <password>[place your password here]</password>

    Make sure to replace the database URL, user name, and password with the appropriate values.


    If the data source jndi-name must be changed, edit the datasource element in the <default-bindings> tag.

  3. Add the driver to the standalone.xml file’s <drivers> element also found within the <datasources> element.

        <driver name="[name of database driver]" module="com.liferay.portal">
            <driver-class>[JDBC driver class]</driver-class>

    A final data sources subsystem that uses MySQL should look like this:

    <subsystem xmlns="urn:jboss:domain:datasources:1.0">
            <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" jta="true" use-java-context="true" use-ccm="true">
                <driver name="mysql" module="com.liferay.portal">
  4. In a file in the Liferay Home folder, specify the data source:

The data source is now configured and ready to go.

Connect to a Mail Server

As with database configuration, the easiest way to configure mail is to let DXP handle the mail session. If you want to use DXP’s built-in mail session, skip this section and configure the mail session in the Control Panel.

If you want to manage your mail session with WildFly, follow these steps:

  1. Specify your mail subsystem in the $WILDFLY_HOME/standalone/configuration/standalone.xml file like this:

    <subsystem xmlns="urn:jboss:domain:mail:3.0">
        <mail-session jndi-name="java:jboss/mail/MailSession" name="mail-smtp">
            <smtp-server ssl="true" outbound-socket-binding-ref="mail-smtp" username="USERNAME" password="PASSWORD"/>
    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    <outbound-socket-binding name="mail-smtp">
            <remote-destination host="[place SMTP host here]" port="[place SMTP port here]"/>
  2. In the file in Liferay Home, reference the mail session:

Deploying DXP

  1. If the folder $WILDFLY_HOME/standalone/deployments/ROOT.war already exists in the WildFly installation, delete all of its subfolders and files. Otherwise, create a new folder called $WILDFLY_HOME/standalone/deployments/ROOT.war.

  2. Unzip the DXP .war file into the ROOT.war folder.

  3. To trigger deployment of ROOT.war, create an empty file named ROOT.war.dodeploy in the $WILDFLY_HOME/standalone/deployments/ folder. On startup, WildFly detects this file and deploys it as a web application.

  4. Start the WildFly application server by navigating to $WILDFLY_HOME/bin and running standalone.bat or


After deploying DXP, you may see excessive warnings and log messages, such as the ones below, involving PhaseOptimizer. These are benign and can be ignored. Make sure to adjust your app server’s logging level or log filters to avoid excessive benign log messages.

May 02, 2018 9:12:27 PM$NamedPass process
WARNING: Skipping pass gatherExternProperties
May 02, 2018 9:12:27 PM$NamedPass process
WARNING: Skipping pass checkControlFlow
May 02, 2018 9:12:27 PM$NamedPass process
INFO: pass supports: [ES3 keywords as identifiers, getters, reserved words as properties, setters, string continuation, trailing comma, array pattern rest, arrow function, binary literal, block-scoped function declaration, class, computed property, const declaration, default parameter, destructuring, extended object literal, for-of loop, generator, let declaration, member declaration,, octal literal, RegExp flag 'u', RegExp flag 'y', rest parameter, spread expression, super, template literal, modules, exponent operator (**), async function, trailing comma in param list]
current AST contains: [ES3 keywords as identifiers, getters, reserved words as properties, setters, string continuation, trailing comma, array pattern rest, arrow function, binary literal, block-scoped function declaration, class, computed property, const declaration, default parameter, destructuring, extended object literal, for-of loop, generator, let declaration, member declaration,, octal literal, RegExp flag 'u', RegExp flag 'y', rest parameter, spread expression, super, template literal, exponent operator (**), async function, trailing comma in param list, object literals with spread, object pattern rest