Vista Combinata Vista Piatta Vista ad Albero
Discussioni [ Precedente | Successivo ]
toggle
Lij Achu
What does liferay.war lacks as compared to the bundle
25 luglio 2012 17.47
Risposta

Lij Achu

Punteggio: Junior Member

Messaggi: 36

Data di Iscrizione: 12 marzo 2011

Messaggi recenti

Hi All,

How can I install liferay.war on tomcat as non root context so it'll run smoothly as the liferay bundle does. I've noticed some plugins are missed in the liferay.war and 'm in trouble to install those plugins manually after setting up the .war on tomcat, its portal instance management is also bit different. I also want to use the db sharding thing here.

Thanks.
Olaf Kock
RE: What does liferay.war lacks as compared to the bundle
28 luglio 2012 12.32
Risposta

Olaf Kock

LIFERAY STAFF

Punteggio: Liferay Legend

Messaggi: 3425

Data di Iscrizione: 23 settembre 2008

Messaggi recenti

There's a chapter "Installing Liferay on Tomcat 7" in the documentation - also the mechanics are explained well in there.
Hitoshi Ozawa
RE: What does liferay.war lacks as compared to the bundle
29 luglio 2012 5.49
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7949

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

I've noticed some plugins are missed in the liferay.war


liferay.war contains all that's necessary to run liferay. You'll need to deploy other plugin as you need it. Bundled demo version contains some portlets used in the demo.
Lij Achu
RE: What does liferay.war lacks as compared to the bundle
29 luglio 2012 8.32
Risposta

Lij Achu

Punteggio: Junior Member

Messaggi: 36

Data di Iscrizione: 12 marzo 2011

Messaggi recenti

Hi,

@ Olaf, thank you for the reference link.

@ Hitoshi, I have configured liferay6.0.5.war on tomcat6.0.32 and I couldn't get the web form and work flow portlets. I have downloaded and installed them via Liferay's control panel, it confirms that the portlets are installed successfully but not able to list them in the repository for use. I can't also install a custom page layout template in this way.

The bundle has a deploy directory in the same directory level to the tomcat server. How should this deploy directory has to be for multiple liferay portals on a single tomcat server, so the plugins can be installed for a particular one selectively? or Is there any other alternative?

Thank you.
Hitoshi Ozawa
RE: What does liferay.war lacks as compared to the bundle
29 luglio 2012 16.02
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7949

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

Have you set the following property in each portal-ext.properties

#
# Set the directory to scan for layout templates, portlets, and themes to
# auto deploy.
#
auto.deploy.deploy.dir=${liferay.home}/deploy
Lij Achu
RE: What does liferay.war lacks as compared to the bundle
30 luglio 2012 6.15
Risposta

Lij Achu

Punteggio: Junior Member

Messaggi: 36

Data di Iscrizione: 12 marzo 2011

Messaggi recenti

Yeah, I put the following lines in portal-ext.properties in each liferay installations I have
auto.deploy.dir=C:\tomcat6032\webapps\liferay1\deploy --> in the first and
auto.deploy.dir=C:\tomcat6032\webapps\liferay2\deploy --> in the second
But still it's not working.
David H Nebinger
RE: What does liferay.war lacks as compared to the bundle
30 luglio 2012 6.30
Risposta

David H Nebinger

Community Moderator

Punteggio: Liferay Legend

Messaggi: 11046

Data di Iscrizione: 1 settembre 2006

Messaggi recenti

You should not be putting the directories within tomcat's webapps directory.

There's a reason the bundle, by default, uses a directory outside of tomcat for these purposes...

Besides, the plugins that you drop in apply (in large part) directly to the webapps folder (hooks would be the exception). Drop a portlet plugin in either deploy folder, it goes to webapps and (after container restart) would be available to both instances, regardless which one deployed it originally.
Hitoshi Ozawa
RE: What does liferay.war lacks as compared to the bundle
30 luglio 2012 7.20
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7949

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

As David replied, shouldn't be putting deploy directories under webapp.

Try something like:
auto.deploy.dir=C:\liferay1\deploy --> in the first and
auto.deploy.dir=C:\liferay2\deploy --> in the second
Arno Broekhof
RE: What does liferay.war lacks as compared to the bundle
31 luglio 2012 3.47
Risposta

Arno Broekhof

Punteggio: Junior Member

Messaggi: 42

Data di Iscrizione: 18 ottobre 2011

Messaggi recenti

Also don't forget the data directory emoticon
Hitoshi Ozawa
RE: What does liferay.war lacks as compared to the bundle
31 luglio 2012 7.08
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7949

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

Yes, and beginning with liferay 6.1.0 CE, portal-setup-wizard.properties is created too. Probably better to turn off setup wizard.
Lij Achu
RE: What does liferay.war lacks as compared to the bundle
31 luglio 2012 10.22
Risposta

Lij Achu

Punteggio: Junior Member

Messaggi: 36

Data di Iscrizione: 12 marzo 2011

Messaggi recenti

Hi

@Hitoshi, thanks for your explicit guide, it works to deploy the plugins in the desired liferay target. But those plugins are not yet available for use in the list of available portlets and layout templates. Is there any thing I should configure further?

@Arno, thanks for the reminder, what is the data directory and how it should be configured?

Thanks
Hitoshi Ozawa
RE: What does liferay.war lacks as compared to the bundle
31 luglio 2012 16.29
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7949

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

Data directory contains the followings:
1. liferay's default database (when no database is defined) puts the data
2. Lucene index (default)
3. Document and Media library files (default)

Change the followings to specify it:
jdbc.default.url=jdbc:hsqldb:${liferay.home}/data/hsql/lportal
setup.database.url=jdbc:hsqldb:${liferay.home}/data/hsql/lportal

#
# Set the directory where Lucene indexes are stored. This is only referenced
# if Lucene stores indexes in the file system.
#
lucene.dir=${liferay.home}/data/lucene/

jcr.jackrabbit.repository.root=${liferay.home}/data/jackrabbit

#
# This is a legacy property used by the FileSystemHook to allow data
# migration from other hooks.
#
image.hook.file.system.root.dir=${liferay.home}/data/images
#
# FileSystemStore
#
dl.store.file.system.root.dir=${liferay.home}/data/document_library

#
# Set the directory where the OSGi framework will store it's files.
#
osgi.framework.storage=${liferay.home}/data/osgi
Hitoshi Ozawa
RE: What does liferay.war lacks as compared to the bundle
31 luglio 2012 16.32
Risposta

Hitoshi Ozawa

Punteggio: Liferay Legend

Messaggi: 7949

Data di Iscrizione: 23 marzo 2010

Messaggi recenti

To all additional plugins, do the following:
1. Startup liferay and login as administrator
2. Goto -> Control Panel -> Plugins Installation
3. Choose Portlet Plugins, Theme Plugins, and Layout Template Plugins tab and select "Install More Portlets" to install new portlets which you need.