We met with the Parking office yesterday and are now finalizing the Draw-hold, Draw and Notify phases. In each phase, a user may either:
- see their draw process registration
- see their status, if they are on the waitlist
- be offered a chance to go on the waitlist
Some tweaking of the display is in process, and screen shots are going out to Parking once the changes are in place in development.
In regards to the migration it would appear that the belief Sungard had in regards to changing LDAP suffix causing the problem was incorrect. The problem was directly tied to attempting to move over a layout owner that did not exist in the list of users being loaded into Luminis IV. Once I removed this layout section from the dlm.xml file we were able to get farther. However we then stumbled on an issue with updating the LDAP with the layout owner information in the dlm.xml file.
This was due to there already existing layout information in the LDAP. The suggestion from Sungard for this was to reset the Luminis IV data and manually delete the layout information present so that the migration tool could insert the data from Luminis III.
This was done on Friday last week and we postponed the Luminis IV database recycle so that it could run through Saturday. We have now got even further then before. There is still an error in the output that I am having Sungard evaluate to determine if it is of a critical nature.
So in short the things that we have done to make the migration work:
1. Increase the error threshold to 2 as there is a known problem with the migration of the mb_topic table and UTF8
2. Migrate the mb_topic table manually as there is no translation being done on this table other then the dropping of one column
3. Ensure that there are no fragment entries in ou=site,o=Luminis Configuration, the cn pattern will look like org.jasig.portal.layout.dlm.fragments.data.?? where ?? is a number
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
Finished creating the new tables to store the RSS and User data. Still need to test the set up though, I plan to do that tomorrow.
Created the Class that will handle most of the capabilities of the RSS Reader application, such as fetching feeds, formating data correctly for use with the UI application, etc.
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.
Had a brief discussion with Brian in regards to where we are potentially going with handling RSS content in the future. I also began work installing the USask Drag and Drop into development. At this point it is there, but some aspects are throwing errors (i.e. add stuff). I hope to iron those out next week.
We also talked about the idea of switching back to the out of the box webmail client solution for JUMP as opposed to the link to Horde/IMP. Further talk will be needed.
The parking channel will have to behave a little differently once the student parking registration phase is over. Work is almost complete in development to support the draw, draw-hold and notify phases. These phases come after the registration is complete and then, after the lottery process is run. We are getting ready for another demo of these phases for the parking office in early June.
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.