LDN - Luminis Developer Network

We're trying to get from redhat 3 to redhat 4 for Luminis IV. The sys admin who set up our current systems is gone. Working with the new sys admin, I'm trying to replicate the functionality of our RH 3 system on RH 4.

The sticking point is that from the luminis admin OS account, I can't issue startcp or stopcp, it is demanding the root password.

The sudo-ers setup has been replicated. It looks good ... at least it's the same on the new RH 4 host as it is on the production RH 3 host. Far as I can tell, I have /etc/passwd and /etc/group right.

I'm about to start a new position as a portal administrator. I am lucky enough to have the former admin around to show me the ropes, but documentation would still be very beneficial. We are currently running v4 and plan to upgrade to v5 in the near future. If anyone can point me toward any decent documentation I would appreciate it.

Thanks

I'm looking for information that supports some of the advantages or disadvantage with having a fluid vs a static layout for luminis. What is the normal practice, in regards to fixed/fluid width, for your institution? By default luminis provides a fluid layout that allow for the width of the portal and the channels to scaled. However, I've heard arguments that support having a fixed width will allow more control and confidence over the presentation layer and the user experience with the exception that width consideration over developing channels is a little more involved.

Our Luminis implementation has been largely successful. We've got the data to show that people are using it. They routinely give us positive feedback for a few of our more popular channels that have made their lives easier (yay us!) and they will tell us pretty darn quickly if they find a typo (boo us!) However, the one piece of feedback we get most often is not positive.

What is a typical processing rate handled by your LMB? We're currently processing 50 events per minute.

We are having people reporting an immediate time-out from the luminis system in Internet Explorer 6, 7, 8. The behavior began on Aug 12, and a cumulative security patch for Internet Explorer went out on Aug 11 for IE 6, 7 and 8. Is anyone else noticing this?

Symptoms are inability to see images, and following banner links displays the "system time out" (timedout2.jsp) message and returns them to the luminis login screen.

Hi.
From time to time we get the message:

CPIP Notification: loginuser request failed for comexp
If you need assistance, contact your system administrator.

The message appears when the user clics on the e-mail Icon or in the e-mail channel.

This error goes away just by stopping and restarting the e-mail server (we're using the sun mail server that comes with luminis).

I was wondering if someone has a correction or a workaround for this.

Thanks in advance

Hi Guys,

Has anyone tired to create a Portal Tab (e.g. My report) which display the SSO SSB frame (something like: https://fm.edu/cp/ip/login?sys=sctssb&url=https://SSB/pls/PROD/gwpkmenu.p_report_function)?

We have been experienced a 10 mins timeout on this tab. TCC, channel are fine with 1 hr timeout. Sungardhe Support said that it is defect....SIGH...

But we have a system due to be launched in Sept. We have tried to create pop up and it's still fail.

Any suggestion? workaround?

Thanks.

Hi, we're looking to use Luminis' CAS, but not for Luminis itself. We want other apps (like Moodle) to leverage it.

We have it working fine. But, people basically get our Luminis login page if they want to log into Moodle.

I'm wondering if there is a way to customize the login page to look differently if the user is trying to access one of the CASified resources.

In theory, I could test to see if the URL has the "goto" parameter in login.jsp and change the display of the page accordingly.

Has anyone done this? Do you have any code to share? Thanks.

This week our Luminis web server has started having issues. It is running on a Sun T5220 Solaris 10. Luminis version 4.2.2.34. After running for an hour to hour half it becomes unstable and stops responding. Banner channels are unable to be rendered. At the end of the slow response users trying to get logged in get the "too many simultaneous logins" message. By that point the system is gone. Just before it becomes unstable we notice ping packets are lost to the luminis server. No memory errors in log files. No error messages in system logs.