Does anyone know how the portal calendar communicates with the Berkeley DB (version 2)? I assume it uses JDBC, but really have no clue. I'd like to write some kind of JSP page that outputs the calendar data so I can repurpose that data on some of our web pages.
I am proud to announce, if you haven't read or guessed already, that we are indeed doing another Developer's Lounge at Summit 07 - in Las Vegas! That's right Bob - you and your friends are invited to attend a 3 day, 2 night conference in sunny Las Vegas! Amidst the magic, lights, noise, gambling, mafia and other seedy things, you can attend the safe yet on the edge developer's lounge. 3 days packed with developer talks, hacking, breaking, restoring, idea swapping, comments, consulting, bashing and fun. And if you play your cards right, you could win a BRAND NEW CAR!
Saturday Feb, 9th - The migration and upgrade has been completed. I want to thank our fantastic netowork services guy Jason who did everything - set up the box, the database, Drupal install and configuration, and imported the database. I'll I had to do was change the DNS records to point to the new server.
We made it another year, and this one looks promising with the release of Luminis IV on the way (lets hope we don't need an iv to keep it alive)
LDN has survived another year, growing and growing with over 1300 users (1335 actually), it had become the hub of Luminis development and experimentation. It is referenced in papers, presentations, casual discussions, consulting engagements and business meetings. And its all because of you that its possible. Yea, I have ideas and some hacks, but come one its you all that have made this a community and a resource center.
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 18.104.22.168 (although tests were run in 3.3.1, and 22.214.171.124) 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 126.96.36.199, 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.