After a lot of tweaking I finally got the Apache Jetspeed application portal up and 
running on SuSE 9.0 Pro.
It was sort of tricky, so I thought I'd post my notes, just in case someone else tries 
to do the same thing.
A kind of nano-howto...

=========================================================================
DISCLAIMER
I do not guarantee that these steps will work for you. They worked for me on two 
completely different
hardware platforms, both running SuSE 9.0 Pro, so there is a *fair* chance...
Neither do I explain any purposes or features of said application(s), just how to make 
them run on SuSE 9.0.
The rest is up to you!
=========================================================================


INSTALLING THE APACHE JETSPEED APPLICATION PORTAL ON SuSE 9.0 PRO.
-----------------------------------------------------------------------------

Be sure that the following are installed. 

From the SuSE CD:s
- Java2 SDK 1.4.2
- Java2 JRE 1.4.2
- Apache-ant 1.5.3

(you can download newer one's from Sun/Apache, but then you have to change some 
environment variables and so on.
I will not cover that in this document).


Then install Tomcat (from source)
----------------------------------

Tomcat ver 4.1.27 (RPM) is already on the CDs, but the first tests showed that 
tweaking is required,
so I decided to go directly to Tomcat 5.

Download:    jakarta-tomcat-5.0.19-src.tar.gz

Unpack:
master:~>�tar -zxvf jakarta-tomcat5-5.0.19.src.tar.gz

Tar unpacks all the source files, but actually only one 'build.xml'-file is 
interesting.

Then you need to decide where to build Tomcat. I wanted to install it under /opt.

As root:
master:~>�md /opt/jakarta
master:~>�cp jakarta-tomcat-5.0.19-src/build.xml /opt/jakarta/build.xml
master:~>�cd /opt/jakarta
master:~>�ant

When the installation is complete (hopefully without errors) Tomcat is installed in

/opt/jakarta/jakarta-tomcat-5/build

We'll call that directory $CATALINA_HOME


Add a manager user to Tomcat
-------------------------------

In a text editor, open the file $CATALINA_HOME/conf/tomcat-users.xml
Edit one of the existing users or add a new user, with password, and assign her/him 
the roles as "tomcat,manager".
Save and exit.


Testing Tomcat.
----------------

Start Tomcat.
master:~>�cd $CATALINA_HOME/bin/startup.sh

Now, in a browser window go to http://localhost:8080

If everything went right you should see the Tomcat main page.

Stop Tomcat again.
master:~>�cd $CATALINA_HOME/bin/shutdown.sh


Now install Jetspeed.
---------------------

Download:   jetspeed-1.4-src.zip
and unpack.

Lets call the top expanded directory $JETSPEED.

Change to
master:~>�cd $JETSPEED/build

In a text editor, open the script 'build.sh'.
With SuSE 9.0 and Sun Java 1.4.2 [from SuSE's RPM's]  the following line should look 
like this:

JAR_DEPENDENCIES='ls /usr/share/java/jaxen-1.0-FCS/lib/jdom*.jar 2>/dev/null'

Save and exit.

Compile and build the war-archive:
master:~>�./build.sh war

Then copy:

master:~>�cp $CATALINA_HOME/build/bin/commons-logging-api.jar 
/usr/lib/java/lib/commons-logging-api.jar
master:~>�cp $CATALINA_HOME/build/bin/commons-logging-api.jar 
/usr/lib/java/jre/lib/ext/commons-logging-api.jar
master:~>�cp $JETSPEED/lib/xalan-2.3.1.jar 
$CATALINA_HOME/common/endorsed/xalan-2.3.1.jar

and finally Jetspeed itself:

master:~>�cp $JETSPEED/bin/jetspeed.war $CATALINA_HOME/build/webapps/jetspeed.war

DONE!

Start Tomcat:
master:~>�cd $CATALINA_HOME/bin/startup.sh

Tomcat will automatically deploy Jetspeed. Now browse to Tomcat at 
http://localhost:8080 (it might be a little slower the
first time while the war is being deployed).

In the administration section click on Tomcat Manager and login.
Look for the entry /jetspeed in the Applications list. If the column 'Running' says 
'true' it means Jetspeed has been
successfully deployed.

Click on /jetspeed to proceed.

Good luck.

##################

OK, that's all. Hope that this is useful for someone :-)

rgds,
Marty

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to