LDN - Luminis Developer Network

Thanks to the previous posts on Lumdev, we are almost done with our Luminis - WebCT integration. We were able to load up our extracts into WebCT and get everything working on the Blackboard side. However, I am having trouble with the es.webct.courseURL value. I put in the target_sourcedid.id:// as previously noted. When I go through My Courses as an instructor, that gives me this URL without a server base.

http://cougarweb.ccccd.edu/cp/ip/login?sys=webct&url=target_sourcedid.id%3A%2F%2F12938.200910

At the opening session for Luminis, we were treated to a talk from Joshua Horner, the Senior Product Manager for Luminis. After talking about several Luminis case studies and alluding to past performance issues with the early releases of Luminis IV, he gave us a preview of the Product Roadmap.

Even if you did not get to go to Summit, you have probably seen some posts about Liferay - the new open source application server that Luminis is looking at for Luminis 5 - and the new emphasis on portlets over channels. There was also some welcome news about Luminis IV.1 and Luminis IV.2.

Is there any interest in holding a Birds of a Feather session on Tuesday, April 15th from 4:30pm - 5:30pm at Summit? I had been looking forward to the Google Apps presentation since we are in the middle of our implementation and tying Google into our Luminis IV servers. However, I received the following e-mail last Thursday:

Please be advised that the session entitled, Luminis Platform/Google Apps scheduled to be held on Tuesday, April 15 4:30 - 5:30 PM has been cancelled. Unfortunately the presenter is unable to attend the conference.

Attached is the presentation that I gave at SETA Dallas this past week. It deals with the Generic Connector Framework and touches on both the External Authentication Service and older CPIP Connector. We are currently running Luminis IV.0.1.17 and have hooked Luminis with Banner and Novell eDirectory. It covers determining whether your system is a good candidate for GCF, lays out the architecture, talks about setting up your xml and properties file, and then explains the difference between a remote pickup and a pickup response.