Attached are files to complete a CPIP for Groupwise 7.0.1. See Brian Ferris' article on the original Groupwise CPIP for an explanation on how it all works.
Analysis of Luminis et al log files can be a time consuming and error prone affair. While using tools like SawMill and Logmeister can be of assistance, they attract a license fee. Other efforts, such as Chainsaw, have limitations and do not offer an effective plugin architecture to extend the viewers capability. Therefore, I have the first incarnation of a log viewer to address these, and other, issues; hence the purpose of this message.
Tomorrow, barring any issues, we will be going live with an implementation of Luminis that runs purely in SSL. In this story I'm going to talk about what we had to do to accomplish this.
We are currently running Luminis 126.96.36.199 (although tests were run in 3.3.1, and 188.8.131.52) parallel deployment on Windows servers. We are using a Big5 load balancer for our parallel deployment. On our resource server we have a web service that contains content in JSPs for targeted content channels and a web service for the GCF as per Sungard's instructions.
Recently we upgraded to Luminis 184.108.40.206, we were quite happy with the newer version as it solved a number of load issues, and seemed to be slightly more stable. I had heard that there were problems with the icons, but after perusing the articles here I discovered that there were a couple different solutions. Once we installed and got everything running however; there was nothing but issues.
We've implemented Novell's Net Storage, a web interface to the network. It's pretty slick actually, as it will display a list of your network drives once you've logged in, no weird ftp paths or clients to configure.
Much like other ingrated functionality its good and bad at the same time : Fantastic if you're on the road and need a file. Terrible if you walk away from your PC and you're a faculty member logged into the portal! :)
Improved RSS Feeds - Part 1
In our installation of Luminis we make heavy use of RSS feeds. Some are delivered from external sources and others from our internal systems.
A recent software failure of our content management system that was delivering some of our RSS feeds had a severe knock on effect on our portal as each RSS feed waited for it's timeout before displaying the error message and failing to render.
This lead me to have a rethink about how we deliver RSS feeds into our portal.
Although Luminis IV is reported to have an improved layout manager where we will be able to add channels to a default tab that a particular group of users do not have access to and have them suppressed when they log in this ability is currently lacking in Luminis III.
We want to open up our portal to people who have applied to the institution to provide them with info on their application and other generic info on the school. We've already made the necessary change so that applicant information is passed thru to Luminis and accounts are created.
The problem is that applicatants, through BannerWeb, have a different login page than students - they use bwskalog.P_DispLoginNon instead of twbkwbis.P_GenMenu?name=homepage