Legacy Knowledge Base
Published Jul. 2, 2025

Setting Up Liferay Portal 6.1 EE on JBoss 5.1 EAP

Written By

Liferay Support

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

This guide will assist you in the startup of JBoss EAP 5.1 with Liferay 6.1 EE GA1.

Resolution

  1. Download JBoss EAP 
     
  2. Download the liferay-dependencies.zip
     
  3. Navigate to [L:/$JBOSS_BUNDLE/../server/default/lib]:
    • Add the Liferay dependencies (hsql.jar, portlet.jar, portal-service.jar)
    • Add mysql.jar
  4. Delete the following in [L:/$JBOSS_BUNDLE/../common/lib]:
    • hibernate-validator.jar
    • hsqldb.jar
    • hsqldb-plugin.jar 
  5. Navigate to [L:/$JBOSS_BUNDLE/../server/default/conf]:
    • Edit login-config.xml
    • Comment out the blocks with the name "HsqlDBRealm" and "JmsXARealm"
  6. Delete the following in [L:/$JBOSS_BUNDLE/../server/default/deploy]:
    • /messaging
    • ejb2-container-jboss-beans.xml
    • ejb2-timer-service.xml
    • ejb3-connections-jboss-beans.xml
    • ejb3-container-jboss-beans.xml
    • ejb3-interceptors-aop.xml
    • ejb3-timerservice-jboss-beans.xml
    • hsqldb-ds.xml
    • jms-ra.rar
    • mail-ra.rar
    • mail-service.xml
    • profile-service-secured.jar
    • uuid-key-generator.sar
  7. Delete the following in [L:/$JBOSS_BUNDLE/../server/default/deployers]:
    • jboss-ejb3-endpoint-deployer.jar
    • messaging-definitions-jboss-beans.xml
  8. Navigate to [L:/$JBOSS_BUNDLE/../server/default/deploy/ROOT.war]:
    • Clear contents in folder
    • Extract the liferay.war
  9. By defining the portal domain, it will not allow parent classes to load first, and instead export all portal classes
    <classloading xmlns="urn:jboss:classloading:1.0"
    	parent-first="false"
    	domain="LiferayDomain"
    	export-all="NON_EMPTY"
    	import-all="true">
    </classloading>
    • Add jboss-classloading.xml to [L:/$JBOSS_BUNDLE/../ROOT.war/WEB-INF] with the following content:
  10. Add the following to portal-ext.properties:
     
    hibernate.validator.apply_to_ddl=false
    hibernate.validator.autoregister_listeners=false
  11. Delete the following in [L:/$JBOSS_BUNDLE/../ROOT.war/WEB-INF/lib]:
  • jaxrpc.jar
  • stax.jar
  • xercesImpl.jar
  • xml-­apis.jar

Startup

  1. Start Liferay by running the following command in [L:/$JBOSS_BUNDLE/bin]:
    run.bat

Shutdown

  1. Shutdown Liferay by running the following command in [L:/$JBOSS_BUNDLE/bin]:
    shutdown.bat

Deployment

  • Add jboss-classloading.xml to the WEB-INF folder of each plugin, with the following content:
     
    <classloading xmlns="urn:jboss:classloading:1.0"
        domain="PLUGINNAME-portlet"
        parent-domain="LiferayDomain"
        parent-first="false"
        top-level-classloader="false"
        export-all="NON_EMPTY"
        import-all="false">
    </classloading>

Plugins

  • In order to hot deploy in the correct place, configure the portal-ext.properties with the following:
     
    auto.deploy.jboss.dest.dir=${jboss.home.dir}/server/default/deploy
    #(This one can be left like this, it will usually always detect)
    
    auto.deploy.deploy.dir=G:/jboss-eap-5.1/deploy
    #(This one needs to be the exact folder where you are going to be placing your .war files into.)
 
Did this article resolve your issue ?

Legacy Knowledge Base