Last week found out we were facing a new defect with the migration. In this case admin permissions for manipulating channels were missing after the migration. With suggestions from Sungard over the weekend I installed LP IV on romulus and performed another migration.
This time post migration we have access to these admin level functions. So prior to this post things were in good shape for Debbie and Brian to test, not so for Dave, Naramada, and Bill. But now everyone can take part on vulcan (lumnext.cc.umanitoba.ca) to fix up the custom channels. Perhaps on the weekend I will try and put in some of my new custom channels.
Today I continued my efforts at installing Luminis IV on brax. I had to ask Ed to reimage the box as the luminis isntalled may have messed things up quite bad. At this point I am back to the initial error that I had reported to Sungard. Hopefully tomorrow will bring better luck.
I also received permission to attempt a Luminis III to IV migration during day time hours. The migration did not complete successfully, however this time it appeared to be failing dealing with the layout fragments. This is different then the Apr 23rd attempt that caused Sungard to think it was a LDAP suffix issue. I have updated the Sungard ticket with this new information in case it adjsuts the troubleshooting.
Continued my attempts at installing Luminis IV on a RHEL 4 system. Ran into some issues that were sovled easily. Namely clearing the DISPLAY environment variable. However this still did not work in the end. Still in touch with the vendor on how to proceed.
I am also attempting another migration of Luminis III to Luminis IV. I have not heard back from the vendor but am going to try and remove the mention of a nonexistent user from one of the xml documents as the last attempt did complain about that user. I raised this with the vendor but they felt it was not the issue so I do not have high hopes, but despite that I figure it is worth a try.
Spent the day trying to install Luminis IV on brax. Brax is replacing our current Luminis IV test system apollo. Brax is also giving us an opportunity to install Luminis IV on a RHEL 4 system. However I ran into a number of issues throughout the day that caused the installation to fail requiring contact with the vendor.
At the end of the day the suggestion was to wipe the installation and try again. I was able to wipe the installation prior to heading for home so will attempt the install tomorrow.
I aslo found time to do a mockup of the earnings statement channel for a meeting that Kevin was going into tomorrow. This mockup can be viewed at the following location http://luminisd.cc.umanitoba.ca/flex/earnings.html
Dealt with some lingering JUMP Lite login issues for employees and parking. Began work on preparing brax to replace apollo as our Luminis IV test server. As part of the EBS system makes use of apollo spoke with Bill on what we will need to do in order to move that code from apollo to brax.
We now have the USask drag and drop working in Luminis III, including their ‘add stuff’ feature. There are some aspects of this we need to tweak prior to putting it into production. Also when time permits I will look at reworking the ‘add stuff’ feature to make use of AJAX/JSON as opposed to being a traditional channel embedded in the layout. I feel this will give a performance boast as we have noticed very little customisation to Luminis so no sense in pulling in a bunch of content that may never get used.
Responded to Sungard in regards to our recent LDAP migration issue and their desire for our export data. I have requested they get back to me with the break point sand variable monitoring the develoepr would like to do (assuming that was at the heart of the request for data) and said I can do this and share the results.
Today I continued work on building an application that will filter out old events from our calendar files. It appears to have been successful against my ical file. I am lacking the various proeprty settings at the top of an iCal file but that will be tomorrows task.
The plan is to use the same property data in the orignal file for the new one, minus any non America/Chicago timezone properties.
I had forgot to mention that yesterday I produced a list of JUMP users where the course population job was wishing to change the id the courses should be attached to according to the policy that was worked out between Brian and myself. A number of these were because the id initially chosen are technically no longer eligible for an account while the others are eligible for either just that the id selected is not the preferred one according to the policy. This has been forwarded off to Brian for his thoughts on how best to proceed.
As for today I worked with Sandy, Jennifer, and Lloyd to troubleshoot a recent problem where some employees are unable to sign into JUMP Lite to renew their parking. At this point there is a discussion that parking services will need to have with HR to potentially alter the rules for access. This will be transparent to the code that authenticates JUMP Lite users.
I have begun work on developing an application that will be used to migrate the calendar data from Luminis III to IV. Part of the cleanup will be to remove a custom timezone that we had added when we went live with JUMP, as well as a routine to clear out any calendar events that are older then two years. The hope will be that the calendar pruning will be able to be ran more regularly. At this point the code is in an early stage so there is not much to report here.
Today I spent some time looking into our recent migration attempt of Luminis III to Luminis IV. This was manily an exercise to try and find where in the migration code base it was picking up the old LDAP server’s base DN. Sadly more time will be needed here to track down this issue.
I also deal with bugzilla tickets 3422 and 3429. For Ticket 3429 I created a new Bugzilla component for JUMP called ‘Course: Duplicate PIDM’ as a means to track course population issues that are caused by the duplicate PIDM problem.
Worked with Lonnie on working out some of the aspects to this blog.