Steps to build and deploy Jetspeed 2 in Websphere 6.0

["Krishna Kumar (krishkum)" <kr...@cisco.com>]

Hi Guys,
 
The following is the steps to deploy Jetspeed 2 in WAS 6.0.
First Do a successfull build and deploy in Tomcat and do the following.
 
 

1.	Package jetspeed.war(Create jetspeed.war from the <Tomcat_Home>
dir, j2-admin.war, demo.war and rss.war into myportal.ear file. Include
application.xml in the META-INF directory. 
2.	<?xml version="1.0" encoding="UTF-8"?>
	<application xmlns="http://java.sun.com/xml/ns/j2ee
<http://java.sun.com/xml/ns/j2ee> "
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> " id="Application_ID"
version="1.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
<http://java.sun.com/xml/ns/j2ee>
http://java.sun.com/xml/ns/j2ee/application_1_4.xsd
<http://java.sun.com/xml/ns/j2ee/application_1_4.xsd> ">
	    <display-name>My Portal</display-name>
	    <module id="WebModule_1">
	        <web>
	            <web-uri>jetspeed.war</web-uri>
	            <context-root>/myportal</context-root>
	        </web>
	    </module>
	    <module id="WebModule_2">
	        <web>
	            <web-uri>demo.war</web-uri>
	            <context-root>/demo</context-root>
	        </web>
	    </module>
	    <module id="WebModule_3">
	        <web>
	            <web-uri>j2-admin.war</web-uri>
	            <context-root>/j2-admin</context-root>
	        </web>
	    </module>
	    <module id="WebModule_4">
	        <web>
	            <web-uri>rss.war</web-uri>
	            <context-root>/rss</context-root>
	        </web>
	    </module>
	</application>
3.	Deploy this ear file into WAS 6. Make sure that at the
application level the following parameters (important ones) are set with
the following values. It is assumed that all other normal
application/web properties in WAS will be set.

	a.	WAR class loader policy: Module
	b.	Class loader mode: Parent Last
	c.	For each web module i.e. jetspeed, j2-admin etc., the
class loader mode should be: Parent Last. 
	d.	Point to the following shared
libraries:jetspeed-api-2.0.jar, jetspeed-commons-2.0.jar,
pluto-1.0.1.jar, portal-bridges-common-1.0.jar and portlet-api-1.0.jar.
	e.	Map resource references to resources: For all resource
references set JNDI name to JetspeedDS. Note: JetspeedDS needs to be
configured as a JDBC provider.

4.	In the following directory
<WAS_DEPLOY>\IBM\WebSphere\AppServer\lib, modify the
ws-commons-logging.jar. Remove commons-logging.properties from this jar
and save it. This is the only tweak that is necessary for WAS 6.
5.	Restart the WAS application server and go to the portal url i.e.
http://localhost:9080/myportal

Regards,
KK