Luminis IV on Solaris installed successfully
Fri, 2007-05-25 13:32 — clewis
Yesterday, our team successfully installed Luminis IV on our first try!
We did a baseline install and we still have a few open items, but overall, we were very happy to get it running. Because this is a test instance, we chose to install the application on a single Sun server with 3 zones: one for the calendar, portal and resource tiers, one for the mail tier, and one for the database tier. Our plan is to repeat the installation process on another server (with 3 zones), but turn on EAS to AD.
Our primary open items are:
- configure Banner and get the Banner channels running
- configure Banner and import users from Banner
- resolve Calendar issue (when you click Calendar as a test student, mail comes up; when you click Calendar as an admin user, the comexp login window pops up) -- I've asked Sungard for help with this.
Now the fun begins!
-Chris
- clewis's blog
- Login or register to post comments
Hack Your Knowledge
Recent blog posts
- Luminis IV GCF Single Sign On with OSX=Failure PC=Working
- Cisco 4710 - Load Balancer
- First CPIP - ERROR
- Luminis Developer Job Available w/ Stable Organization
- Luminus Developer Job
- SSO to SSB mixed content error in IE
- Avoid email sending when add or delete user from group
- Luminis components
- Luminis 4 & Groupwise 7
- Luminis Developer Needed for Position w/ Stable Organization
Developer Links
Poll
What version of Lumins / OS are you running in production?
Luminis 4.x - Linux
20%
Luminis 4.x - Windows
8%
Luminis 4.x - Solaris
31%
Luminis 3.x - Windows
18%
Luminis 3.x - Solaris
20%
Luminis 3.x - Linux (if so - we need to talk) <G>
4%
We gave up on Luminis - I just like this site !
0%
Total votes: 51
- Login or register to post comments
- Older polls
Syndicate
Comments
Build number?
What build did you use? We were sort of successful with the February build and then decided to try again with the most recent build 3591 and have had all sorts of problems getting the messaging (mail) system installed in a two box configuration on Solaris 10.
pkginfo
We are also still having trouble. Luminis build number, and a pkginfo list for your zone would be awesome if you could provide it.
About your zones: Did you just create simple whole root zones, or were there any tricks involved? Our whole root zone on one server installed the resource tier and ldap just fine, but another whole root zone on another server will not install calendar. Frustrating.
which build?
We used build 3591.
We created 3 whole root zones on a single server. No tricks.
Our UNIX system administrator did "Full + OEM" installs of Solaris 10 (11/06), so we got pretty much every package in the world installed. The full dump of packages is too long to post -- I'll send it too you separately via email.
which build?
I was wondering if I could get the package dump as well, your posting is from May but we're having problems here as well, probably at a different rev of the OS and we need to track down whatever info we can that will help to point us at a solution.
Don
Concerning Build number and mail setups with two boxes
I am responding to gjjones1 entry posted on 05/25/2007. We are using build 3591 and while the install worked to have a quasi-working mail setup, it is not kosher. Our mail server does not have an instance directory such as "msg-devmail" which we would expect for the mail host "devmail". We cannot click on the server group window on the window side to create certificates for the mail side. Something is not in sync quite for the LDAP(DS) and messenger.
A case has been opened weeks ago to SGHE. We have not received any help yet. We are running the Solaris Sparc platform.
We also opened a case with Sun. While they collected materials and asked questions about our setups, they never got in touch with us. We do not pay Sun enough in support to get alternate consultant help.
Problem with comexp and luminis mail
I believe comexp is installed by default. There are tailoring instructions in the install guide to make LuminisIV use the Luminis email client instead of comexp. The non-admin user will see the Luminis mail by default because of the permission not being granted to the channel.
You have to add both of the permissions to allow users who do not have admin to use the channel (comexp). Permissions are:
CommExpress
CommExpress_SSO
Look at 3.16 of the Luminis Platform System Admin guide. This tells how to assign the permission for MOWA - CommExpress also has to be done similarly.
Hope this helps.
T. Combs
could you find out about cpu for solaris 10
Chris, could you report on whether the cpu was SPARC or x86?
test spects specs
Our test server is a Sun T2000 Server with 8 core 1.2 GHz UltraSPARC T1 processors with 16GB RAM. All three zones are on this server.