Hi,

I try to install Liferay 5.2.2 in a JBOSS 4.2.3 GA server and mysql.

What I have allready done.

1- unzip jboss-4.2.3.GA.zip -d /opt/
2- test jboss => Ok

3- deploy liferay on jboss
mkdir /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferayportal.war
unzip liferay-portal-5.2.2.war -d /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferayportal.war

4- deploy liferay dependencies
cp liferay-portal-dependencies-5.2.2/* /opt/jboss-4.2.3.GA/server/default/lib/

5- copy mysql connector
cp mysql-connector-java-5.1.7/mysql-connector-java-5.1.7-bin.jar /opt/jboss-4.2.3.GA/server/default/lib/mysql.jar

6- Create Database
cd liferay-portal-sql-5.2.2/create-minimal/
mysql -u root -p < create-minimal-mysql.sql

7- Change the Debug attribute
vi /opt/jboss-4.2.3.GA/server/default/deploy/jbossjca-service.xml

8 - remove unnecessary local jar (
cd /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferayportal.war/WEB-INF/lib
rm hibernate3.jar dom4j.jar xercesImpl.jar xml-apis.jar

Test running jboss => Failes

What may I miss ?
May I change /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/ /conf/web.xml ?
May I create /opt/jboss-4.2.3.GA/server/default/deploy/liferay-ds.xml or may I create /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferayportal.war/WEB-INF/classes/portal-ext-properties with only database lines ?

Can you please help me ?

Remy N

Rémy, I am not sure whether you are on a right path of making own configuration.
As far as I can understand, you have JBoss installation, downloaded from JBoss, and then installing liferay as web application onto it.

I am a very long time user of JBoss AS in eBusiness and mission-critical applications, and from my experience when it comes to the need of having liferay and jboss working together, there are three ways of making the system:

#1. Install standard Jboss from jboss.org, then deploy liferay on it. That's what I assume you are trying to do now. Tried it many times about 3 years ago, never worked for me, and I am not going to do it again. Too many clashes.

#2. Download bundled tomcat+liferay from liferay.com, and apply your modifications as required by your system. In my case I always have to separate JBPM databases, some movements of jars around ESB, etc This configuration is good for small and medium size application, does not scale well.

#3. Have JBoss and Liferay running on separate JVMs, initially even on the same box. Disable web container on JBoss, move own web apps onto liferay container This way you can enjoy full JBoss AS environment, including clustering, without disruption from Liferay. When transactions grow, move JBoss out of liferay's box. A typical physical and logical separation between presentation and business domain tiers. This configuration has an enormous scaling (and farming) capability, which you would never be able to achieve just on Liferay, especially for heavy back-end transactional functionality.

Thnaks a lot
OK for me the first one is the more usable for an entreprise.

OK I will try to do this with bundle.

1- unzip liferay-portal-jboss-tomcat-4.2-5.2.2.zip -d /opt
cd /opt/liferay-portal-5.2.2/jboss-tomcat-4.2.3/bin
./run.sh -b 0.0.0.0

OK it's running wth HSQL and SevenCogs Hook and Theme.

2- Remove SevenCogs Hook and Theme
(Note:http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/7Cogs%20sample%20data)
rm /opt/liferay-portal-5.2.2/jboss-tomcat-4.2.3/server/default/deploy/sevencogs-hook.war/ -fr
rm /opt/liferay-portal-5.2.2/jboss-tomcat-4.2.3/server/default/deploy/sevencogs-theme.war/ -fr

I don't know how to drop a database in HSQL ??

3- Connect to a fresh mysql database.
(Note:
mysql -u root -p
create database lportal character set utf8;
exit

cp /home/sun/mysql-connector-java-5.1.7/mysql-connector-java-5.1.7-bin.jar /opt/liferay-portal-5.2.2/jboss-tomcat-4.2.3/server/default/lib/mysql.jar
cd /opt/liferay-portal-5.2.2/jboss-tomcat-4.2.3/server/default/deploy/ROOT.war/WEB-INF/classes/
vi portal-ext.properties

-----
jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username=root
jdbc.default.password=password
jdbc.default.jndi.name=jdbc/LiferayPool
-----

vi /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferayportal.war/WEB-INF/lib/ext-spring.xml

-----
<bean id="liferayDataSource" class="org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy">
<property name="targetDataSource">
<bean class="com.liferay.portal.spring.jndi.JndiObjectFactoryBean">
<property name="jndiName" value="jdbc/LiferayPool" />
</bean>
</property>
</bean>
------

4- restart Liferay and

INFO Loading file:/opt/liferay-portal-5.2.2/jboss-tomcat-4.2.3/server/default/deploy/ROOT.war/WEB-INF/classes/portal-ext.properties
INFO 2009-03-05 11:38:23,965 ERROR com.liferay.portal.dao.jdbc.util.DataSourceFactoryBean - Unable to lookup jdbc/LiferayPool
javax.naming.NameNotFoundException: jdbc not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:774)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.liferay.portal.kernel.jndi.JNDIUtil._lookup(JNDIUtil.java:169)
at com.liferay.portal.kernel.jndi.JNDIUtil.lookup(JNDIUtil.java:65)

What's wrong ?

Remy N

This is a good error.
Please wait until someone else joins the thread with 5.2.2 experience, or continue digging into the manual.
I have not moved there myself yet and there were some changes in the way this connection is specified.

OK I try to redo my solution

based on
http://www.liferay.com/web/guest/community/forums/-/message_boards/message/1343996

So:
unzip jboss-4.2.3.GA.zip -d /opt/

mkdir /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war

export JBOSS_HOME=/opt/jboss-4.2.3.GA/

vi $JBOSS_HOME/server/default/deploy/jboss-web.deployer/conf/web.xml
<servlet>
<servlet-name>default</servlet-name>
<servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>listings</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>input</param-name>
<param-value>4096</param-value>
</init-param>
<init-param>
<param-name>output</param-name>
<param-value>4096</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>

unzip /home/sun/liferay-portal-5.2.2.war -d /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war

cd /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war/WEB-INF/lib/

rm commons-collections.jar dom4j.jar jaxen.jar hibernate3.jar

cd && unzip /home/sun/liferay-portal-dependencies-5.2.2.zip && cp liferay-portal-dependencies-5.2.2/* $JBOSS_HOME/server/default/lib

vi $JBOSS_HOME/server/default/deploy/mail-service.xml (like the post)
vi $JBOSS_HOME/server/default/conf/login-config.xml (like the post)

On HSSQL it works....

Now I have to plug to MySQL database...
(http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/Database%20Configuration#section-Database+Configuration-LiferayV5.2AndLater)

* copy mysql connector
cp mysql-connector-java-5.1.7/mysql-connector-java-5.1.7-bin.jar /opt/jboss-4.2.3.GA/server/default/lib/mysql.jar

* Create Database
cd liferay-portal-sql-5.2.2/create-minimal/
mysql -u root -p < create-minimal-mysql.sql

* create /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war/WEB-INF/classes/portal-ext.properties

jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username=root
jdbc.default.password=password
jdbc.default.jndi.name=jdbc/LiferayPool

*create the datasource

4) Create $JBOSS_HOME/server/default/deploy/liferay-ds.xml with following content:

1 <datasources>
2 <local-tx-datasource>
3 <jndi-name>jdbc/LiferayPool</jndi-name>
4 <connection-url>jdbc:mysql://localhost/lportal?useUnicode=true&amp;characterEncoding=UTF-8</connection-url>
5 <driver-class>com.mysql.jdbc.Driver</driver-class>
6 <user-name>root</user-name>
7 <password>password</password>
8 <min-pool-size>0</min-pool-size>
9 </local-tx-datasource>
10 </datasources>

AND
17:58:09,496 INFO deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
17:58:09,972 WARN Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: com.liferay
.portal:loader=liferay-portal, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.Heirarchic
alLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)
17:58:10,031 INFO deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/liferay-portal.war/
17:58:15,105 INFO Loading jar:file:/opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war/WEB-INF/lib/portal-impl.jar!/syst
em.properties
17:58:15,482 INFO [[/]] Initializing Spring root WebApplicationContext
17:58:16,151 INFO Loading jar:file:/opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war/WEB-INF/lib/portal-impl.jar!/port
al.properties
17:58:16,152 INFO Loading file:/opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war/WEB-INF/classes/portal-ext.properties
17:58:21,098 ERROR [DataSourceFactoryBean] Unable to lookup jdbc/LiferayPool
javax.naming.NameNotFoundException: jdbc not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:774)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.liferay.portal.kernel.jndi.JNDIUtil._lookup(JNDIUtil.java:169)
at com.liferay.portal.kernel.jndi.JNDIUtil.lookup(JNDIUtil.java:65)
at com.liferay.portal.kernel.jndi.JNDIUtil.lookup(JNDIUtil.java:47)
at com.liferay.portal.dao.jdbc.util.DataSourceFactoryBean.createInstance(DataSourceFactoryBean.java:68)
at org.springframework.beans.factory.config.AbstractFactoryBean.afterPropertiesSet(AbstractFactoryBean.java:130)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:219)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:117)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1245)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1010)
......
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
17:58:22,387 INFO Determining dialect for MySQL 5
17:58:22,437 INFO Using dialect org.hibernate.dialect.MySQLDialect
17:58:24,804 INFO Loading jar:file:/opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war/WEB-INF/lib/portal-impl.jar!/capt
cha.properties
17:58:25,773 INFO Portal lib directory /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/liferay-portal.war/WEB-INF/lib/
17:58:34,142 INFO Detected server jboss-tomcat
17:58:36,860 INFO Starting Liferay Portal Standard Edition 5.2.2 (Augustine / Build 5202 / February 20, 2009)
17:58:40,057 INFO Initializing hot deploy manager 2338822
17:58:40,279 INFO Auto deploy scanner started for /opt/deploy
17:58:40,701 INFO deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
17:58:40,790 INFO deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
17:58:40,945 INFO deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
17:58:41,548 INFO deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
17:58:41,911 INFO Mail Service bound to java:/Mail
17:58:41,985 INFO Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
17:58:42,056 INFO Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
17:58:42,070 INFO Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
17:58:42,217 INFO Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
17:58:42,277 INFO Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
17:58:42,339 INFO Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
17:58:42,382 INFO Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
17:58:42,385 INFO [QuartzResourceAdapter] start quartz!!!
17:58:42,909 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'javaefaultDS
'
17:58:43,156 INFO Bound to JNDI name: queue/A
17:58:43,157 INFO Bound to JNDI name: queue/B
17:58:43,158 INFO Bound to JNDI name: queue/C
17:58:43,159 INFO Bound to JNDI name: queue/D
17:58:43,160 INFO Bound to JNDI name: queue/ex
17:58:43,174 INFO Bound to JNDI name: topic/testTopic
17:58:43,175 INFO Bound to JNDI name: topic/securedTopic
17:58:43,176 INFO Bound to JNDI name: topic/testDurableTopic
17:58:43,178 INFO Bound to JNDI name: queue/testQueue
17:58:43,204 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
17:58:43,226 INFO Bound to JNDI name: queue/DLQ
17:58:43,317 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
17:58:43,374 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=jdbc/LiferayPool' to JNDI name 'java:jd
bc/LiferayPool'
17:58:43,392 INFO deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
17:58:43,662 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
17:58:43,913 INFO Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
17:58:43,974 INFO JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 46s:231ms



Why jdbc/LiferayPool is discovered after needed !!!

Remy N

UP...

Yes,I have the exact same problem.I am using tomcat6+liferay5.2
I configed the portal-ext.properties
and ext-spring.xml

but it still says

Loading jar:file:/D:/liferay-portal-5.2.2/tomcat-6.0.18/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/system.properties
Loading jar:file:/D:/liferay-portal-5.2.2/tomcat-6.0.18/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/portal.properties
Loading file:/D:/liferay-portal-5.2.2/tomcat-6.0.18/webapps/ROOT/WEB-INF/classes/portal-ext.properties
14:23:45,876 ERROR [DataSourceFactoryBean:71] Unable to lookup jdbc/LiferayPool
javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
at org.apache.naming.NamingContext.lookup(NamingContext.java:770)
at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
at org.apache.naming.NamingContext.lookup(NamingContext.java:781)

Hi Remy and Kaimin,

I have the same problem. Did you find a solution?

i.e., trying to get LP 5.2.2 and JBoss 4.2.3 working with MySQL but getting an error

2009-05-04 15:47:27,702 INFO (main) 2009-05-04 15:47:27,692 ERROR com.liferay.portal.dao.jdbc.util.DataSourceFactoryBean - Unable to lookup jdbc/LiferayPool
javax.naming.NameNotFoundException: jdbc not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:820)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.liferay.portal.kernel.jndi.JNDIUtil._lookup(JNDIUtil.java:169)
at com.liferay.portal.kernel.jndi.JNDIUtil.lookup(JNDIUtil.java:65)
at com.liferay.portal.kernel.jndi.JNDIUtil.lookup(JNDIUtil.java:47)
at com.liferay.portal.dao.jdbc.util.DataSourceFactoryBean.createInstance(DataSourceFactoryBean.java:68)

Do you create the "portal-ds.xml"? This is the way to configure the jndi binding. This file is like:

Hi, this is a quick and dirty approach: http://grupodot.blogspot.com/2008/06/liferay-portal-en-jboss-as-422-ga.html (spanish).

I hope it helps,

GErmán.