LDN - Luminis Developer Network

This information provided here for archival and documentation purposes

The answer as to whether Luminis IV could recover from a database restart was 'sort-of', with conflicting responses. It ended up as defect #1-3J67MJ, now resolved. The resolution appears in the documentation for the IV.1.0 upgrade.

Here's a summary of what I found out myself and from the RC:

I'd like to change our failed login experience to be something other than what's in failedlogin.thtml. I'd actually like to go to a completely different page.

I realize I will lose the number of attempts counters and all that, but that's ok.

I tried the easiest method, a refresh as in:

 meta http-equiv="refresh" content="0:mywebpage..." 

This works fine in Firefox, but not in IE. Just sits and spins.
Any ideas?
Thanks, Bob.

We have developed a number of custom channels for Luminis III that get the users' uPortal, and Banner, ID and get personalized information from Banner for display to the user. Cool.

To do this, we use the IPerson object, something along the lines of:
IPerson person = staticData.getPerson();
String username = (String) person.getAttribute("username");

However, with Luminis IV, the 'username' attribute is no longer giving us what we want. It returns the immutable id, not the Banner or userid. Hmmm.

All, After waiting for 2 months for Response Centre to solve this, I did it myself. Of course, not sure if this the 'proper fix', but at least it works and I can move onto the next problem....

Issue: Migration of Address Book does not work for root-level (main) entries.

After migrating platform data from Luminis III to Luminis IV the root level address book entries do not appear in the Communications Express client. Address book entries that are in an address book group appear as they should.

More reports from looking at the Luminis III to IV migration.

It turns out that Message Board Topic descriptions are no longer gathered or displayed in Luminis IV. This change in functionality is not documented anywhere, as far as I can tell.

I didn't realize this until it was pointed out to me by the response centre after my query to them as to why the Topic descriptions weren't appearing. I guess they figure they don't collect descriptions anymore, why display them. Well here's a reason: migrated data!

I've just got a Luminis IV migrated instance up and am looking at the integrated web mail and calendar client: Communications Express.
Is anyone else using this? If so, what are your issues?

So far, I've found that:
- The Email and Calendar icons both take you to the email tab in CommExp.
- Resizing the CommExp browser when in the Calendar takes you back to the Mail tab.
- Clicking the Calendar link in the Group Tools opens the CommExp client to the Mail tab(are you sensing a pattern here?) and doesn't auto select the Group Calendar.

I've been spending a fair bit of time with Luminis migrations. Here's some notes:

Migrate to a development box.
I've managed to get a migration of production data to a development box. This meant that the ldap entries needed to be fiddled first. This isn't as onerous as it seems but it did take a few passes. In fact, I think this is what the migrator script is doing in the 'Transform PDS' section.

With migration to Luminis IV pending, one of my issues is:
What hostname do I give the new server?

I know many of us have given our Luminis III servers the name of 'my' or 'usource' (hi Dave), or whatever the campus name for the portal is.

I don't want to deal with an old 'my' and new 'my' during installation. It's possible but way too confusing and would require special networking.

So what am I to call the Luminis IV server?

I finally did get a (possibly) successful migration. Some accounts can login and others can't. Don't know why. I probably won't try to fix it, but will re-install and migrate again. Notes from this attempt:

Read 1-21BG0A and 1-2AG4ZG and used the new migrator script, installed a_mig-1.8.jar and migration-config.properties in the appropriate places.

Problems:
1 New migrator script did not work on unix.
Script contained CR and LF which does no work in unix. Fixed: removed CR.

2 Database inconsistencies.
ERROR The source and target table names are UP_CARS and UP_CARS.

I'm trying out my first pass at a migration from III.3.3 to IV (a good Friday afternoon project). Mirgrating from our III.3.3 Luminis development to a throw-away instance of IV.