0. Shutdown tomcat.
1. In the ogce-portal-only directory, run the command mvn clean install -f global-config/pom.xml
2. Remove our versions of hibernate, hsqldb, and ehcache (probably these crept in from GS 2.1--I don't think we need them). Specifically,
rm global-config/common/target/cog-common-1.0/lib/hibernate2-OGCE.jar
rm global-config/common/target/cog-common-1.0/lib/hsqldb-1.7.1.jar
rm global-config/common/target/cog-common-1.0/lib/ehcache-0.9.jar
3. Copy the remaining jars into your Tomcat's shared/lib. Something like
cp global-config/common/target/cog-common-1.0/lib/* /Users/mpierce/GridSphere31/apache-tomcat-5.5.20/shared/lib/
4. Copy the OGCE portlet as is from the ogce-portal-only dir. That is, from ogce-portal-only, run "mvn clean install -f portlets/proxymanager-portlet" and then
cp -r portal_deploy/apache-tomcat-5.5.12/webapps/proxymanager-portlet/ /Users/mpierce/GridSphere31/apache-tomcat-5.5.20/webapps/proxymanager-portlet
5. Create empty files named after the portlets for Gridsphere. This used to be done in $CATALINA_HOME/webapps/gridsphere/WEB-INF/CustomPortal/portlets
Now these apparently go in $HOME/.gridsphere, so do this:
touch ~/.gridsphere/portlets/proxymanager-portlet.2
6. Edit the proxymanager's web.xml file to use the correct namespace for the PortletServlet (i.e., remove the "gridlab" section from the full name):
<servlet>
<servlet-name>PortletServlet</servlet-name>
<servlet-class>org.gridsphere.provider.portlet.jsr.PortletServlet</servlet-class>
</servlet>
7. In proxymanager-portlet/WEB-INF/lib, delete gridsphere-ui-tags-2.1.jar
8. Start tomcat and add the portlet using the Gridsphere Layout Manager.
6 comments:
That is going to help me A LOT!
I have tried to put OGCE framework on GS3 before but could not make it work... so I just continued my development using uPortal.
I am developing a portlet for job submission to a grid environment, and I will have to make it work in more than one portlet container.
I suggest you take a look at the OGCE's GTLAB--you can build in standalone mode and then use the JSF portlet bridge to convert your application to a portlet. I haven't tried it with GS3, so probably you will need to get the jar versions worked out--we can help you with that.
I already got my project to not use proprietary classes such as GS3 new-project wizard recommends.
The main reason I am using OGCE is for its portlet oriented velocity view (which I had to adapt a little anyway, but it has most of the work done).
Thanks for the fast answer and advice!
Oh, ok, that's great. Let us know if you have problems with Velocity in GS3. Also, the Velocity bridge code itself is pretty simple and in the project SVN.
I was forgetting the SVN repository, and the best of it, it has public access... maybe there already is a way for using velocity tools (which was the reason why I adapted). Gonna check it out. Thanks again!
Here's the code:
http://ogce.svn.sourceforge.net/viewvc/ogce/VelocityPortlet/
Post a Comment