Steffo's Echolot

Nevada, Parallels and Java Enterprise 5

What was annoying about the old Parallels/Solaris combo was that the clock did not work properly (very, very bad if you run into timeouts). I cannot say what the delay factor exactly was, but believe me I went for lunch rather than for a coffee break when I had the impression that I ran into a timeout.

With the new combo Parallels 2.5 (Beta) and Nevada (Beta) this problem is almost gone. However, it's not a good idea to put the virtual machine to sleep. It gets confused about the time delay when it wakes up again. Anyway, an OS (yes even Solaris) is more fun when it has some apps installed. So I decided to give the Java Enterprise System a try. For those not being familiar with the Sun products: the Java Enterprise System is a suite (or better: a set of suites) of different applications (LDAP Directory Server, Web Server, Cluster -- all the stuff you need).

Since the Parallels version I'm running on is beta and also the Nevada version is beta, I went for Java Enterprise 5 (should be available soonish). The graphical installer showed up shortly with a splash screen and the normal installer screen but disappeared (shy graphics). So I used installer -nodisplay and I got

Installation Summary Report
Install Summary
Java Enterprise System 5 : Installed
Sun Java(TM) System Web Server 7.0 : Installed, Configured
Sun Java(TM) System Directory Preparation Tool : Installed
Sun Java(TM) System Directory Server Enterprise Edition 6.0 : Installed



So far, so good. Next challenge: Access Manager. The installer installed the packages but for some reason was not able to deploy them to the Sun Webserver. I had no problems doing a manual deployment. Simply copy the config file /opt/etc/bin/amsamplesilent to amsilent-sun, edit it (I had to use the HTTPS port 8989 as the deployment port for Sun Webserver) and ./amconfig -s amsilent-sun . Before you restart your webserver, remember to to a chown -R webservd:webservd (or whatever user your webserver runs under) on /etc/opt/SUNWam to insure the deployed application can read the necessary config files (otherwise you'll get those nasty exceptions LoginLogoutMapping.java:74).

After 40 minutes, I have a brand new Access Manager deployment on my MacBook.

Posted at 05:08PM Feb 16, 2007 by steffo in Identity Systems  |  Comments[0]