Installing Liferay DXP on Wildfly

Installing Liferay DXP on Wildfly 11 takes three steps:

Now, download the Liferay DXP WAR and Dependency JARs:

  • Liferay DXP WAR file
  • Dependencies ZIP file
  • OSGi Dependencies ZIP file

Note that Liferay Home is the folder containing your Wildfly server folder. After installing and deploying Liferay DXP, the Liferay Home folder contains the Wildfly server folder as well as data, deploy, logs, and osgi folders. $WILDFLY_HOME refers to your Wildfly server folder. It is usually named wildfly-[version].

Installing Dependencies

Liferay DXP depends on a driver for your database and the JARs in the Dependencies ZIP and OSGi Dependencies ZIP files you downloaded. Here’s how to install them:

  1. Create the folder $WILDFLY_HOME/modules/com/liferay/portal/main if it doesn’t exist and extract the Dependencies ZIP JARs to it.

  2. Download your database driver .jar file and copy it into the same folder.

  3. Create the file module.xml in the $WILDFLY_HOME/modules/com/liferay/portal/main folder and insert this configuration:

    <?xml version="1.0"?>
    <module xmlns="urn:jboss:module:1.0" name="com.liferay.portal">
            <resource-root path="com.liferay.petra.concurrent.jar" />
            <resource-root path="com.liferay.petra.executor.jar" />
            <resource-root path="com.liferay.petra.function.jar" />
            <resource-root path="" />
            <resource-root path="com.liferay.petra.lang.jar" />
            <resource-root path="com.liferay.petra.memory.jar" />
            <resource-root path="com.liferay.petra.nio.jar" />
            <resource-root path="com.liferay.petra.process.jar" />
            <resource-root path="com.liferay.petra.reflect.jar" />
            <resource-root path="com.liferay.petra.string.jar" />
            <resource-root path="com.liferay.registry.api.jar" />
            <resource-root path="hsql.jar" />
            <resource-root path="[place your database vendor's jar here]" />
            <resource-root path="portal-kernel.jar" />
            <resource-root path="portlet.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 here] with the driver JAR for your database.

  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 Liferay DXP’s OSGi runtime.

Running Liferay 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. Liferay DXP fully supports Wildfly in standalone mode but not in domain mode.

You can run Liferay DXP on Wildfly in domain mode, but this method is not fully supported. In particular, Liferay DXP’s hot-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 Liferay 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.

Configuring Wildfly

Configuring Wildfly to run Liferay DXP includes these things:

  • Setting environment variables
  • Setting properties and descriptors
  • Removing unnecessary configurations

Optionally, you can configure Wildfly to manage Liferay DXP’s data source and mail session.

Start with configuring Wildfly to run Liferay DXP.

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

  1. 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" />
  2. Add the following <filter-spec> tag within the <console-handler> tag, directly below the <level name="INFO"/> tag:

    <filter-spec value="not(any(match(&quot;WFLYSRV0059&quot;),match(&quot;WFLYEE0007&quot;)))" />
  3. 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}"/>
  4. Add the following JAAS security domain to the security subsystem <security-domains> defined in element <subsystem xmlns="urn:jboss:domain:security:2.0">.

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

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


        <file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>
  6. Find the <jsp-config/> tag and set the development, source-vm, and target-vm attributes in the tag. Once finished, the tag should look like this:

    <jsp-config development="true" source-vm="1.8" target-vm="1.8" />


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.

  6. The <jsp-config> tag contains its new attributes.

Now you must configure your JVM and startup scripts.

In the $WILDFLY_HOME/bin/ folder, modify your 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.

Make the following edits as applicable for your operating system:


  1. Comment out the initial JAVA_OPTS assignment like this:

    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, it’s recommended to add this JVM argument to display four-digit years.


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


You’ve configured the application server’s JVM settings.

  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 your Liferay DXP installation on Wildfly. Next you’ll configure your database.

Database Configuration

The easiest way to handle database configuration is to let Liferay DXP manage your data source. The Basic Configuration page lets you configure Liferay DXP’s built-in data source. If you want to use the built-in data source, skip this section.

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

  1. 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. For example JDBC connection values, please see Database Templates

  2. 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">
  3. In a file in your Liferay Home, specify your data source:

Now that you’ve configured your data source, the mail session is next.

Mail Configuration

As with database configuration, the easiest way to configure mail is to let Liferay DXP handle your mail session. If you want to use Liferay 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 your file in Liferay Home, reference your mail session:

Next, you’ll deploy Liferay DXP to your Wildfly app server.

Deploying Liferay DXP

Now you’re ready to deploy Liferay DXP using the Liferay DXP WAR file.

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

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

  3. To trigger deployment of ROOT.war, create an empty file named ROOT.war.dodeploy in your $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

Congratulations; you’ve deployed Liferay DXP on Wildfly!

« Installing Liferay DXP on TomcatInstalling Liferay DXP on JBoss EAP »
Was this article helpful?
0 out of 0 found this helpful