I've finally been able to figure out the steps required to get JetSpeed successfully running under WebSphere 3.5.4. Although I haven't tried it with 4.0, the same procedures should be required. Thought I would post back the proper steps into the list so that there's a record of it for the next new-bie to search on and discover. Someone (?) may also want to add this information to the FAQ or install page?
Pre-requisites: - NT 4.0 SP6 or Windows 2000 SP2 - WebSphere 3.5 with FixPack 4 applied - WinCVS (or other) to download the source code for JetSpeed 1.3a2dev from the CVS respository - minimum 1.2 JDK for compiling the jetspeed source into a .war file; WebSphere's JDK will do just fine. - JAVA_HOME environment variable set to the <%WebSphere_Root%>\jdk directory (or to the JDK that you are using to build JetSpeed). On my default installation, %WebSphere_Root% is C:\WebSphere\AppServer. Steps: Step 1 - Get the latest build from the jakarta-jetspeed CVS library. The procedures for doing this are contained here: http://jakarta.apache.org/site/cvsindex.html I use WinCVS and had no problems at all. Step 2 - Build the jetspeed.war file. The procedures for doing this are contained here: http://jakarta.apache.org/jetspeed/site/install.html under "Build JetSpeed". *NB one change*: for 1.3a2dev, use "build war" instead of "build webapp". Step 3 - Create or modify your application server in WebSphere. In the Command line edit box under the General Tab, enter "-classpath <dir>xalan-2.0.1.jar;<dir>xerces_1_3_1.jar" where <dir> is the directory where those jar files reside. This is to solve a problem with the WebSphere xalan.jar being loaded before the JetSpeed one and overriding a method required for XML parsing. Step 4 - Modify the servlet engine you will running JetSpeed under to use Servlet 2.2/JSP 1.1 Full Compliance mode instead of WebSphere 3.5 compatibility mode. This may or may not be required as I haven't tested it the other way. Good to use anyway if you're just starting to write an application. Step 5 - Use the Administration Wizard "Convert a warfile" to load the jetspeed.war file into your servlet engine as a web application. For location, select the servlet engine contained within the application server with the classpath as modified above. Select the target virtual host, the jetspeed.war file and finally enter a name for the web application. I chose "jetspeed"......you might be more original than me ;o) Step 6 - Start 'er up! Check the jetspeed.log to see if there were any errors generated during startup; hopefully there were none and you are now a happy Portal-ite. Hope that helps the next person..... Mark Miskiman IT Architect - Sell and Support IBM Global Services 700 - 201 Portage Avenue Winnipeg, Manitoba R3B 3K6 14/AKJ/201/WPG (204) 934-2792 office (204) 782-3436 cell [EMAIL PROTECTED] http://w3.ibm.com/services/bisglobal/solutions/sell_support.html "What enables the wise sovereign and the good general to strike and conquer, and achieve things beyond the reach of ordinary men, is knowledge" -- Sun Tzu, The Art of War Mark Miskiman/CanWest To: [EMAIL PROTECTED] /IBM@IBMCA cc: Subject: JetSpeed running on WebSphere 3.5 - has anyone actually got 23/10/2001 08:29 it to work? AM Please respond to jetspeed-user I've been trying to get JetSpeed to run within WebSphere 3.5.4 with no luck at all. Originally I was using the JetSpeed 1.3a1 code but I quickly discovered an init() error with the RegistryManager. When I searched within the user archive, it looked like this is an error that has occured before in similar installations (WebSphere 3.5.3). This thread had several useful tips, like using the code from the CVS repository instead of the 1.3a1 build. One user also noted that they had successfully built and ran a version of JetSpeed in WebSphere taken from the CVS repository as of 6 April 01. I first tried taking the latest versions of each of the library files out of the CVS repository, but I received null pointer errors in the TurbineLog interface. As there was a user who seemed to have successfully compiled a version of JetSpeed from 6 April 01, I tried to put a project together based on that date, but I was unable to successfully build it to test. Next I directly contacted one of the users who was having the same problems on WebSphere hoping that he had discovered a solution that just wasn't posted back to the community. Unfortunately, his problem had never been solved. I'm going to assume that someone out there has got this to work..... Would that someone please share the magic mix of WebSphere config and .jar versions to make it happen? My Technical Info: OS: NT 4.0 SP6 JDK: 1.3 App Engine: WebSphere AS 3.5.4 PS. Error logs available upon request.....too long to fit nicely in a this e-mail though Mark Miskiman [EMAIL PROTECTED] "What enables the wise sovereign and the good general to strike and conquer, and achieve things beyond the reach of ordinary men, is knowledge" -- Sun Tzu, The Art of War --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
