Uploaded image for project: 'PUBLIC - Liferay Commerce'
  1. PUBLIC - Liferay Commerce
  2. COMMERCE-2412

UI issues with Commerce 2.0.4 and jBoss 7.1




      1. Oracle JDK 1.8.
      2. JBoss EAP 7.1(Supported version as per the compatibility matrix)
      3. Download the following from the Digital Enterprise 7.1 Downloads Page
        a) Liferay DXP 7.1 WAR
        b) Dependencies zip
        c) OSGi Dependencies
        d) MSSQL database jar
      4. Liferay Fix-Pack 12
      5. Liferay Commerce Enterprise 2.0.4.lpkg
      6. MSSQL Server 2012


      Liferay Home is the folder containing your JBoss server folder. After installing and deploying Liferay DXP, the Liferay Home folder contains the JBoss server folder as well as data, deploy, logs, and osgi folders. $JBOSS_HOME refers to your JBoss server folder. This folder is usually named jboss-eap-[version].

      1) Create the folder $JBOSS_HOME/modules/com/liferay/portal/main. Unzip the Liferay Digital Enterprise 7.1 Dependencies zip file and copy the .jar files to this folder.

      2) Place the database .jar in this folder.

      3) Create the file module.xml in the $JBOSS_HOME/modules/com/liferay/portal/main folder and insert the following contents:

      <?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="com.liferay.petra.io.jar" />
       <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="mysql.jar" />
       <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" />

      4) Create an osgi folder in the Liferay Home folder. Then extract the OSGi ZIP file into the osgi folder.

      5) Next, modify the $JBOSS_HOME/standalone/configuration/standalone.xml file.
      a) Locate the closing </extensions> tag. Directly beneath that tag, insert these 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" />

      b) Add the following <filter-spec> tag within the <console-handler> tag, directly below the <level name="INFO"/> tag:

       <filter-spec value="not(any(match("WFLYSRV0059"),match("WFLYEE0007")))" />

      c) Add a timeout for the deployment scanner by setting deployment-timeout="360" and remove the other properties as seen in the excerpt below.

       <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">
       <deployment-scanner deployment-timeout="360" path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>

      d) 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="com.liferay.portal.security.jaas.PortalLoginModule" flag="required" />

      e) Remove the two code snippets providing welcome content:

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


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

      f) 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"/>

      6) Then navigate to the $JBOSS_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/image/codec/jpeg" />
       <path name="com/sun/org/apache/xml/internal/resolver" />
       <path name="com/sun/org/apache/xml/internal/resolver/tools" />

      7) Navigate to ${JBOSS_HOME}/bin/standalone.conf.bat file in Windows.
      a) Comment out the initial JAVA_OPTS assignment as demonstrated in the following line:

         rem set "JAVA_OPTS~=-Xms1G -Xmx1G -XX:MetaspaceSize~=96M -XX:MaxMetaspaceSize~=256m"

      b) 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 -Djava.net.preferIPv4Stack~=true -Djboss.as.management.blocking.timeout~=480 -Duser.timezone~=GMT -Xmx2048m -XX:MaxMetaspaceSize~=l"

      1. If the folder $JBOSS_HOME/standalone/deployments/ROOT.war already exists in your JBoss installation, delete all of its subfolders and files. Otherwise, create a new folder called $JBOSS_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 $JBOSS_HOME/standalone/deployments/ folder. On startup, JBoss detects the presence of this file and deploys it as a web application.

      4. Stop the Liferay server. Copy fix pack (liferay-fix-pack-dxp-12-7110) and Paste in $JBOSS_HOME /patching-tool/patches folder then run the below command:

            a. Install the latest supported version of patching tool which is required to install Fix              Pack 12. Download patching-tool from liferay and extract to your liferay-home                    folder.
            b. patching-tool install : It will install all patches copied in patches directory.
            c.  Now run the command "patching-tool info" and it will give the list of installed fixes.

      5. Deploy the activation-key-liferay-commerce (.xml activation key) and start the server.

      6. Deploy the Liferay Commerce Enterprise 2.0.4.lpkg.

      7. Start the JBoss application server by navigating to $JBOSS_HOME/bin and running standalone.bat or standalone.sh.

      Liferay Configuration with MSSQL Server 2012:
      8.  Install MSSQL Server 2012.
      9.  Stop the JBoss application server and copy sqljdbc4.jar to the JBoss application server(jboss-eap-7.1\modules\com\liferay\portal\main).
      10. Edit module.xml(jboss-eap-7.1\modules\com\liferay\portal\main) and add an entry for the sqljdbc.jar as below.

      <resource-root path="sqljdbc4.jar" />

      11. Modifty portal-ext.properties to connect Liferay with MSSQL Server 2012.


      12. Start the JBoss application server by navigating to $JBOSS_HOME/bin and running standalone.bat or standalone.sh.


      Steps to reproduce the issues:

      1. ** Hit the URL localhost:8080 in browser

      2. Log in as Administrator(Username: test@liferay.com password: test

      3. Go to Control panel>>Commerce>>Settings

        You will see the below screen. The navigation bar should be on top but it is showing at the bottom.

       4. Now go to Commerce>>Channels and Click on Add Channel.

      5. Select Type as Site as shown below:

      6. You can see the below screen once you select the Site as a type:

      Select Site button is coming on top, that should be below Type dropdown.

      Note: All the above issues are not reproducible with the below configuration:

      Liferay DXP 7.1+ FP 12 + tomcat + Liferay Commerce Enterprise 2.0.4.lpkg + MSSQL Server 2012


        1. image-2019-11-07-10-56-47-472.png
          66 kB
          Prashant Ballal
        2. image-2019-11-07-11-04-55-375.png
          51 kB
          Prashant Ballal
        3. image-2019-11-07-11-08-54-196.png
          53 kB
          Prashant Ballal
        4. image-2019-11-07-11-11-55-904.png
          54 kB
          Prashant Ballal



            prashant.ballal Prashant Ballal
            0 Vote for this issue
            4 Start watching this issue




                Version Package