Upgrade or Reinstall 5.04 to 5.3

Submitted by lyounger on Thu, 10/06/2016 - 17:37


We've fallen very far behind on our upgrading schedule for Luminis. We are at a critical point that we need to get the new version running. I'm wondering if this group has any advice regarding the path to take...Upgrade our 5.04 HF version to 5.3? or do a complete reinstall of the 5.3 system?

The tech who did our original install is long gone and we have never had a true replacement for that position. The original server architecture and installation documentation doesn't exist.

5.3 Portlets

Submitted by sumphrey on Tue, 10/04/2016 - 16:32


My Luminis 5.2 portlets do not work when we upgrade to Luminis 5.3. The 5.2 portlets are based of of personDetails from Ellucian. Has anyone got homemade portlets to work in 5.3 Thanks. Scott U.

Getting User Information in Web Content Display

Submitted by cparsons on Tue, 10/04/2016 - 10:54


We are try to create a simple popup that user must agree to before continuing in the system. The popup need to be able to pull some identifiable information such as Luminis id and then pass that to the database and check to see if a comment is stored that they have accepted the agreement.

Here is the break down:

Portal position at Lehigh University

Submitted by gskinner on Wed, 09/14/2016 - 09:57

Hello Lumdev'ers! Sadly my portal developer relocated with her family and I am once again looking for someone to lead the direction of our portal. We did successfully migrate to Luminis 5.2 about 18 months ago, so if anyone is still fighting Luminis 4 and wants to be on Luminis 5.... well come at work at Lehigh University! I'm also wanting the ideal candidate to be able to pick up and work with Drupal. We do a lot of web development on campus using Drupal and we've also tied some portal content in via SSO and Drupal.

CMS with Luminis 5?

Submitted by baumli on Thu, 09/01/2016 - 10:53

I'm still working on our migration from Lum4 to 5, and one sticking point has been with our CMS. We use cascade server to manage all of our web pages and documents. On Luminis 4 we used a directory that was already there to publish secure documents to, so that users would have to be logged in to see them. With Luminis 5, we lose this feature due to Liferay. There is no directory that we can publish to that will allow only logged in users to have access to them. Ellucian said this is due to the document library in Liferay that forces you to use their process.

error with Luminus 5 SSO JSP script

Submitted by amoverall on Wed, 06/22/2016 - 17:09


I am trying to convert a fantastic Luminus 4 SSO JSP script to Luminus 5. I've gotten most of the bugs out but continue to get the following error. If I take the myPerson variables and place them in a separate JSP script, everything outputs without a problem. Any help would be greatly appreciated!

Error Message: com.sghe.luminis.security.myqa.MyQAForcedSetupFilter:140 Unable to compile class for JSP:

NOTE: All keys and school information have been made generic for posting.

Has anyone upgraded from 5.2.2 to 5.3 in Production yet? How did it go?

Submitted by epturnere on Thu, 06/02/2016 - 21:23


We upgraded our Development environment from 5.2.2 to 5.3 right after the eLive 2016 conference without incident, but unfortunately our Development environment is not a true reflection of Production. We plan to upgrade Production to 5.3 this summer. Has anyone else gone live with 5.3 and if so, how was the upgrade process?

Subscribe to LDN - Luminis Developer Network RSS