Luminis 4.2.x
Hi
We have been running Luminis 4.1.0.15 since June 2008 and after the initial pain of migration it has mostly met our needs until now. We need to leverage portlet deployment, CAS on PD and some permissions fixes provided by Luminis 4.2.x. So before we decide what to do, I wanted to get some feedback from users on various flavours of 4.2.x and if there are any particular builds we should stay away from, we are using solaris and parallel deployment.
Thanks
David
4.2.1.77
We are on 4.2.1.77, Solaris and PD. It's a pretty good build, some small known issues (which you can get by asking Sungard for the fixes from 77 to current) but nothing too painful so far.
Todd
4.2.0.67 is stable for us.
4.2.0.67 is stable for us. ~2000 concurrent connections. PD environment.
4.2.2.14
Thank you for your replies. I have tried the latest available build on my development box, the install went well, my only issue with it so far is that the Request/Create a Group functionality is broken, Sungard have opened a critical defect on this. I will update this with any further findings.
David
4.2.2.14 patch notes
Are there patch notes available for 4.2.2.14? I was not able to find them.
4.2.1.96
We are on 4.2.1.96 Solaris PD. This fixes a serious security issue from earlier releases of Luminis 4.2 (maybe 4.1 and 4.0 as well but not sure). Our portal is not completely on SSL. Login is https but SSL terminates at the load balancer and once you are logged in, the content is http. Not sure if this security flaw is there in SSL. We will be moving to SSL late this year. Anyways to see if you are experiencing the issue, log in to luminis, then logout and wait till the login page reloads. Do Not close the Browser window. Thereafter, from your browser history, locate the page "Login Succesful" (loginok.html) and click on the page in the history just before the loginok page. That page is cp/home/login. It will ask you to refresh and once you do that you will be logged in to the previous session. We could reproduce this on every single browser except Firefox (as it does not cache intermediate pages like cp/home/login).
4.2.1.96 fixes it. Recently tried to upgrade to 4.2.2.14 on our two Development environments (single-server, not PD) and the experience was horrible. The webserver won't start. stopcp won't stop jsvc processes and manually killing processes would make some reload. Not to mention some code (like in newChannel.xsl and the groupstudio javascripts) are pretty badly written. Add to this the irritating newlines in every jsp, html. We have Identity Management (Banner IdM) enabled however I don't think that has anything to do with this problem. Unpatching did not work either and I had to revert to 4.2.1.96 using backups. I would stay away from 4.2.2 for now.
cp/home/login
I just tried that with IE8, cpver 4.2.0.67 and was not able to reproduce that security flaw.
4.2.0.67
We have 4.2.0.67. Group studio email and targeted announcement email is not working. SunGard has recommened we upgrade to 4.2.0.79 or later.
group studio email
Thats odd. We have the same version and our group studio email and TA's are working fine.
Same
Same version with no issues on production or test boxes.
Odd, yes
Our Dev environment is the same version and it works, but not Prod.
4.2.1.78 defects?
Anyone else notice these issues with 4.2.1.78?