This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. Wiki
Installing 5.2 SP4 WAR on JBoss 4
INSTALLING FROM THE LIFERAY WAR FILE**#
The main difference between 5.2 SP3 and SP4 is that SP4 requires you to remove two additional files. Otherwise, the two wikis are the same.
Make sure your JBoss installation starts and runs before continuing.
Starting Out**#
Put the Liferay Dependencies bundle in your JBoss installation first. Do this by copying the .jar files into the $JBOSS_HOME/server/default/lib directory.
Configure JAAS**#
Edit $JBOSS_HOME/server/default/conf/login-config.xml and comment out the entire section where application policy is equal to "other" in lines 140-156.
<!--<application-policy name = "other">... <authentication> <login-module code = "org.jboss.security.auth. spi.UsersRolesLoginModule" flag = "required" /> </authentication> </application-policy>-->}}}
Deploying the Liferay WAR**#
Create a folder in the $JBOSS_HOME/server/default/deploy directory. For this example, call it ROOT.war
Use an archive program such as WinRAR or 7Zip to unarchive the Liferay WAR file to $JBOSS_HOME/server/default/deploy/ROOT.war
Delete these files from $JBOSS_HOME/server/default/deploy/ROOT.war/WEB-INF/lib
- xercesImpl.jar
- xml-apis.jar
- jaxrpc.jar
- stax.jar
If you do not remove jaxrpc.jar and stax.jar, Liferay will still start up normally. However, when you try to login, you will get Javax Servlet and QName exceptions.
Additional Editing**#
Edit the $JBOSS_HOME/server/default/deploy/jms/jbossmq-destinations-service.xml. Delete/comment out the text between the <server> tags. Logically speaking, it will look like this:
<?xml version="1.0"?><server> </server>}}}
Add the code "set JAVA_OPTS=%JAVA_OPTS% -Xmx1024m -XX:MaxPermSize=256m -Dfile.encoding=UTF-8 -Duser.timezone=GMT" in the "run.bat" located in the $JBOSS_HOME/bin directory. This line of code will prevent Java memory issues.
Finally, to startup JBoss, execute "run.bat"
Hooray!
