LDN - Luminis Developer Network

Discussion question: what are the major functional changes to Luminis that you have seen released in the 4.x.x releases of Luminis?

There are often technical reasons for upgrading Luminis due to bug fixes, technical capabilities, etc. But I am curious to hear what functional changes between the minor releases of Luminis 4 have stood out to the lumdev community as valuable or noticable?

Another way to ask the same question, if you were recently on a "recommended build" of Luminis 4.2.x.x, what reasons (other than bug fixes) have motivated you to upgrade to the next minor version?

Hi all

Is there any way we can create an inventory list of luminis system running 3.3.3.64 version? (like Content, Channels, Groups and roles) So after we migrate, we can know everything is ok or not? Thanks!

Alan
PCOM

We have the race & ethnicity self service page working in Banner, but there should be a luminis channel for this feature. I don't see it and assume it was never installed in our Luminis system. I understand I need a .car file. Any I idea where I get this file? I'm not having luck on the Sungard site. I see there is a Banner Channels upgrade 8.0.0.1 for this purpose, but that appears to be a SSB upgrade, and we're already at 8.4 in Banner SSB.

Ever since I applied hotfix 4.2.1.125 I have had many problems with the CPIP connectors. I was on the prior hotfix, 4.2.1.78, and there were very few CPIP connector issues. The problems with the cpip servers have become so bad that I restart them hourly with cron. Has anyone experienced problems like this? Also, has anyone upgraded to either the 4.2.2 or 4.2.3 branch and experienced CPIP connector problems?

Hi,
I'm curious about what other schools do for documenting and communicating changes to end users, as a result of Luminis upgrades and patches. Are there any standards or best practices for the same? Do you just use the release notes or document changes in a more user friendly way?

Any input/suggestions will be greatly appreciated.

Thanks,
Shyam

Upgrading from 4.2.0.67 to 4.2.2.68 and have encountered the following problem (in development testing): The login screen no longer displays.

When we attempt to login by going to the portal login page (http://devbox.bc.ca) we are immediatately redirected to https://devbox.bc.ca/cp/home/displaylogin and 'Unable to Connect' browser message comes up. Note that we do not have the extended site-wide SSL enabled, and so ignore the 'Reenable SSL' steps in the upgrade guide.

Hello, all!!!!!

My question is the exact same as found here:
http://www.lumdev.net/node/927
This poster posed the problem perfectly:
"We've had a request from our accounting office to find a way to make student billing and payment information available online to parents. The catch, of course, is that they don't want parents to have access to the student's other information. Is this something that any of you have done? If so, would you be willing to share your strategies? " (kellyda, aka David).

Hi,

How many schools out there installed the integrated mail server (Sun One Messaging Server) on a RH 3 Linux box? RedHat will discontinue the support for RH 3 this October. So I want to see what is your plan on the mail server. Possible solutions are:

• upgrade to RH 4 even though SunGard says it's not supported
• stick with RH 3 (with no security update) until Luminis 5 is out and then upgrade
• better yet, move the mail service to Google or other solutions

Hi,
I'm in the process of upgrading from Luminis 4.1.1.51 to 4.2.2.34 on a Solaris 10 platform. I'm planning to do this on a new TEST environment - so, I need to install 4.1.1.51 on our new Solaris zone, replicate data from our PROD environment and then upgrade to 4.2.2.34. In order to get to 4.1.1.51, I need to install the following versions in the order shown below:
LP-4.0.0.0-solaris.iso
LP-4.0.1.0-solaris
LP-4.0.2.0-solaris
LP-4.1.0.0-solaris
LP-4.1.1.0-solaris and
LP-4.1.1.51-solaris

Hi all!

I am working on a script that we would use when we need a Banner outage. The script will basically redirect all SSB/INB links to an outage page and change the banner channels' audience in order to hide them. All is done and working in development! ...Except that the new channel audience rules do not get pushed until Tomcat is restarted. The whole point of the script is to avoid Luminis restart.