LDN - Luminis Developer Network

During summit I was reading up on Subversion (http://subversion.tigris.org/). I came across a blog post that said "the blog you are reading now, is a checkout from a subversion repository.

It got me thinking about how I maintain my test and production systems. In particular, the challenge of keeping track of all the changes across the systems. Several times I've had the installation of a patch on our test systems act differently than the same patch installed on our production systems.

Competing with iGoogle and MyYahoo
April 14th, 2008 7:49 am

Drag and drop channels and tabs made easy:) Very cool. Was developed in Luminis IV, so for you Luminis III folks out there, I'm not sure if it will work.
The downside is two system calls per login. 95% of the code is in the theme folder, but nested-tables.xsl and util.js are touched also.
BONUS:: edit $CP_WEBINF/uPortal/properties/portal.properties (big perf. hit)
set_caching=off, root_caching=off, url_caching=off (will allow instant changes on dev box).
channel fname= to add a channel anywhere.

Having been through 2 registration days (winter and spring) with Luminis IV, I thought I'd share what I've learned about the hardware requirements for the system.

On our winter registration in November, we entered that day with the following hardware:

Resource/Ldap/Message Broker: Sun V490, 4x sparc IV+ cpus, 16 gigs of ram.
Oracle Database: Sun V245, 2x sparc IIIi, 8 gigs of ram.
Web Server: T2000, 1x 8 core 1.0ghz cpu, 8 gigs of ram
Identical second web server was not online for PD deployment due to load balancer problem.
Calendar: Sun V245, 2x sparc IIIi, 8 gigs of ram.

In Luminis III, we created a single JSP page that would pass combinations of user LDAP information to external systems in order to provide single sign-on and more (http://www.lumdev.net/node/220). This was accomplished using the API's that the uPortal provides. Namely the PersonDirectory and IPerson architectures.

Some of the external systems were not traditional web sites with login pages. If I had been more familiar with GCF, I might have been able to accomplish the same thing, however, I preferred to build in a more well known language.

The downside to this approach:

Well, its been nearly 3 weeks of attempting migrations, and I think we nearly have all the bugs worked out. We are moving from HP-UX to Solaris, and from LPIII to LPIV, so it is not always cut and dry. We also wanted to move from Oracle 9i to 10g.

The first error we got was:
ERROR The error code is 17041
ERROR The Sql Error Code is 17041
ERROR Error encountered while executing Sql Statement INSERT INTO gt_user(USER_ID,DATE_CREATED,USER_ROLE,GT_STATUS,DISPLAY_NAME,EMAIL_ADDRESS)VALUES(?,?,?,?,?,?)
java.sql.SQLException: Missing IN or OUT parameter at index:: 6

Luminis IV success!

Well, at least the resource tier and calendar. After finding the known issue list on the support site, and removing the conflicting packages, as well as disabling the admin console, the resource tier installed just fine.

However, our calendar would not install on a separate box. No amount of package management seemed to help. Friday I decided to install the calendar on a different box, different zone. Theoretically, all our zones are equal. We used the exact same very basic procedure to create all zones. So I wasn't expecting success, but... it worked.

We recently ugpraded from Banner 6 to 7, and it went smoothly.

Imported the following files:

sso_oclass_sunone.ldif
sso_root_sunone.ldif
sso_parms.ldif
sso_parms_sserv.ldif

Which created o=SCTSSOapplications, and some containers and values underneath.

Changed the following to match our self-service server and paths:

cn=SSBServerName,o=sserv,o=config,o=Banner,o=SCTSSOapplications
cn=DADNormal,o=sserv,o=config,o=Banner,o=SCTSSOapplications
cn=HTTPPrefixServer,o=sserv,o=config,o=Banner,o=SCTSSOapplications
cn=CSSURL,o=sserv,o=config,o=Banner,o=SCTSSOapplications

Everything else I left default. We didn't choose to do SSO to INB at this time, so I left all that alone.