Hi Doug Was this issue resolved? i am facing the same issue and wanted to know wherher u were able to fix it.
any help would be great! Paul Timony, Michael wrote: > > Minor correction: > > Jetspeed won't work on Versions of WebSphere 6.1 that are less > than 6.1.3. > > Should read: > > Jetspeed won't work on Versions of WebSphere 6.1 that are less > than 6.1.0.2. > > So make sure you have at least Fix Pack 2. Also, if possible upgrade to > 6.1.0.9, as there may be problems/conflicts with 6.1.0.5 where the > portlet-api-1.0.jar used by Jetspeed conflicts with the a portal > container that comes with WebSphere. > > Michael Timony > > > > > -----Original Message----- > From: Timony, Michael > Sent: Tuesday, September 11, 2007 5:52 PM > To: '[EMAIL PROTECTED]'; [email protected] > Subject: RE: Moved Install to Websphere - Can't Login to Admin > > The default Jetspeed login portlet doesn't work with WebSphere. > > If you look at the web.xml there should be a 2nd login portlet > referenced (but commented out). There are 3 steps to use it (on > WebSphere 6.1.3 or higher). Jetspeed won't work on Versions of WebSphere > 6.1 that are less than 6.1.3. I'm not sure if the following will work on > WebSphere 6.0.x or 5.0.x. > > 1. Comment out the existing login portlet, and comment in the other > portlet (I think it's called PortalFilter). > > 2. Update the reference in your psml files (by default in > default-page.psml). Change j2-admin::LoginPortlet to > j2-admin::PortalLoginPortlet. > > 3. Add the following to j2-admin's jetspeed-portlet.xml: > > <portlet> > <portlet-name>PortalLoginPortlet</portlet-name> > > <js:security-constraint-ref>public-view</js:security-constraint-ref> > <dc:title>Portal Login Portlet</dc:title> > <dc:creator>J2 Team</dc:creator> </portlet> > > > Restart WebSphere. > > Michael Timony > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 06, 2007 4:11 PM > To: [email protected] > Subject: Moved Install to Websphere - Can't Login to Admin > > Hello All, > > I've been trying to get JetSpeed running on WebSphere. I > successfully deployed and setup the application using the Jetspeed > installer (running Tomcat on Debian, and using an Oracle Database) on > one computer. Running ./startup.sh everything works great. I then > repackaged this and deployed it as an EAR file to a WebSphere server > (different computer). Jetspeed came up great, all the portlets loaded, > but I am unable to log into the admin panel. Each time I put in the > login credentials it comes back to the same page I started with (no > error message). Checking the WebSphere error logs I received the > following: > > > > [9/6/07 15:53:45:941 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 17] > : $decorator cannot be resolved. > > [9/6/07 15:53:45:953 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 29] > : ${decoTop} cannot be resolved. > > [9/6/07 15:53:45:964 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 42] > : ${decoBottom} cannot be resolved. > > [9/6/07 15:53:46:011 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 17] > : $decorator cannot be resolved. > > [9/6/07 15:53:46:027 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 29] > : ${decoTop} cannot be resolved. > > [9/6/07 15:53:46:032 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 42] > : ${decoBottom} cannot be resolved. > > [9/6/07 15:53:46:075 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 17] > : $decorator cannot be resolved. > > [9/6/07 15:53:46:083 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 29] > : ${decoTop} cannot be resolved. > > [9/6/07 15:53:46:088 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > '/WEB-INF/templates/layout/html/columns/layout.vm', line 40, column 42] > : ${decoBottom} cannot be resolved. > > [9/6/07 15:53:46:097 EDT] 00000067 velocity I > org.apache.jetspeed.webapp.logging.velocity.CommonsLoggingLog4JLogSystem > logVelocityMessage Null reference [template > 'decorations/layout/tigris/header.vm', line 1, column 1] : $Id cannot be > resolved. > > > > I verified that the files referenced are in fact in the EAR file (and > extracted when deployed to the appropriate paths). Any ideas of what is > going on? Thanks. > > > > Doug Logan > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Moved-Install-to-Websphere---Can%27t-Login-to-Admin-tf4394410.html#a12798699 Sent from the Jetspeed - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
