LS, I am using the binary J2 installation with the Derbydatabase. On top of that an Apache webserver is installed to be able to access the J2 Portal, together with my other installs/pages using port 80.
This all workes but I found some specific issues with the installation. 1/ access path. There are (at least) two paths you need to define. 1/ Jetspeed (as expected) but also 2/ j2-admin. The j2-admin path is acessed directly from ouitside and I had to configure the proxy to pass thru to the jetspeed tomcat. Questions : - Are there any other paths required ? - When will a separate path be used/needed ? 2/ Caching Sometimes I only have access to my J2 environment from behind a proxyserver. With the standard install I noticed several occasions when I got "old pages" which were only refreshed to the correct onces after a "forced" get by the browser. I only checked a few pages pages but the most obvious were : - main page, I regulary got the "admin logged in page" instead of the anonymous page where youneed to login. - Portal site manager When working with the PSM The portal site browser and portal site detail are not updated when selecting. I've come around this behaviour nor to forcing all responses to have the directive "cache-control no-cache'. Checking the apache access log I see for example the portal site detail alway being requested as : GET /jetspeed/portal/_ns:YXBkYi0xfGMwfGQwfGY_/Administrative/site.psml, which indeed would allow a proxyserver to serve cached content. Question : - Are there any specific cache-control options to be set in J2 ? 3/ 404 errors I see a number of pages not returned by the J2 environment "GET /jetspeed/decorations/layout/css/data-scoller.css HTTP/1.1" 404 1099 "GET /jetspeed/decorations/portlet/tigris/images/nw_maj_rond.gif HTTP/1.1" 404 1129 Maybe they are missging from the install If more info needed please let me know. Kind regards, Herman Reintke
