Hi Pasquale,
Unfortunately Itanium is not on of our supported platforms, so apart from guessing what's wrong, I'm not sure how much I can help.
At 18:54 17.06.2004, you wrote:
Hello,
I'm trying in migrating our Jahia enterprise site from windows 2000 to Red
Hat Advanced Server 2.1, Itanium2 64-bit cpu. Well, first step is to install a
fresh Jahia 4.0.4 on it, and downloaded binary distribution from your site.
I'm not able in running startup script (/bin/jahia.sh), get
JAVA_HOME does not seems to contain a valid JDK installation
The script tests for the existence of a file called lib/tools.jar that is necessary to compile JSP. Maybe this file is in a different location on Itanium SDK or has a different name ? If this is the case you should modify the script to point to it.
but I have a SUN J2SDK 1.4.1 64-bit edition installed, and typing
%JAVA_HOME%/bin/java -version
get a valid output referencing the jdk version.
Tried also in starting catalina (/tomcat/bin/catalina.sh run), but I get errors
on loading the main page to configure the CMS (http://localhost:8080/jahia).
Jahia shows me an error page counciling in contacting my site admin, but examining html source code of this page I've taked a look at exception stack trace, seems there are problems in compiling some jsp page.
This is probably also due to the fact that the Tomcat JSP compiler couldn't find the tools.jar that contains the Java compiler tool. This is required to compile JSPs. Maybe you'll want to look in the Tomcat mailing lists to see if anybody is having the same problem with JSP compilation on Itanium.
I'm making some efforts in compiling Jahia (on an XP box), but with there are problems with Maven: I nevers have used it, and read me files in your source code are a little confusing, it speeks about a build.properties, but I'm not able in retrieving it. 3. Modify the ${user.home}/build.properties file to include the
following lines :
catalina.home.dir=PATH_TO_YOUR_TOMCAT_HOME_DIRECTORY
In "core" dir, founded ant.build.properties, so I assume some lapsus has happened, and modified this one.
No these are not the same. The build.properties might not exist, and in which case you should create it with just the line we ask for.
Not very enthusiastic for on-line download of components on compiling process, it is possible to avoid this features?
This is the way Maven works, and the only other way would be to download all the JARs manually and manually place them in the Maven repository (you would need to be familiar with the way Maven works).
I should point out that the current CVS head is *extremely* unstable right now, and I is *not* designed for production work. I recommend, if you need to compile Jahia, to extract from the JAHIA-4-0-BRANCH, as indicated in this document : http://cvspub.jahia.org/cvstags.html .
However, at end I get a jahia.war file on target dir, then suppose to deploy it
on tomcat, no bin dir has been made, so I need to manually start tomcat by using
catalina run.
You cannot just use the WAR file, you will also need to setup Jahia to be a cross context application for it to work.
But still problems arise, get a
GRAVE: Skipped installing application listeners
Hmm no that's a new one, and I guess it might be related to Tomcat again, as Jahia doesn't have a "GRAVE" error level.
when tomcat tryes to start jahia web app (standardHost.start/jahia).
Have you an idea of what's wrong?
Both on Itanium and XP I used Tomcat 5.0 version.
Again, we do not officially support Tomcat 5, but Tomcat 4. I think you should try to stick to supported platforms as much as possible in order to reduce problems. We are looking at packaging with Tomcat 5, but we don't test with it on a regular basis, nor use it for development yet, since a few things have been moved around (like context descriptors and some JARs).
Regards, Serge Huber.
- -- --- -----=[ serge.huber at jahia dot com ]=---- --- -- -
Jahia : A collaborative source CMS and Portal Server
www.jahia.org Community and product web site
www.jahia.com Commercial services company
