So Oracle have moved away from Sun Access Manager towards the Oracle Access Manager roadmap. However, ForgeRock have taken over the product (only possible because of the Opensource nature of the product).
Anyways, let’s push on with installing OpenAM Release 9 onto Tomcat 6.0.26 on Windows 7.
Update – Check out:
for an install video.
To set up Tomcat, extract it to a folder. I picked C:\tomcat. We’ll need to edit C:\tomcat\bin\startup.bat and change the amount of memory available for Tomcat. Add the line set CATALINA_OPTS=”-Xmx1024m” above the set “CURRENT_DIR=%cd%” line. This sets the maximum memory available to Tomcat as 1024MB. You’ll probably have to tell Tomcat where to find the Java Runtime Environment.
Click Start and right click on the Computer button and select properties. Then click Advanced System Settings. Finally click Environment Variables. Click the button for a new System Variable. The variable is called JRE_HOME and the value in my case is c:\Program Files\Java\jre6\.
We’ll need to add an administration user. Edit C:\tomcat\conf\tomcat-users.xml.
Add the following lines:
<role rolename=”manager” />
<user username=”admin” password=”admin” roles=”manager” />
Awesome. Now edit c:\windows\system32\drivers\etc\hosts in Notepad as a privileged user. Add a domain and your computer’s IP address. I added:
Now open up the command line and navigate to C:\tomcat\bin. Type startup and Tomcat should start. If things are going well, you should see this window. The last line should mention the server startup in X ms.
In your web browser, head to http://sso.kenningcorp.com:8080, obvious replacing my domain with your domain. You should see the Tomcat page if things are going well. Now navigate to http://sso.kenningcorp.com:8080/manager/html, with the login being admin and the password admin.
Under WAR file to deploy navigate to openam_release9_20100207\opensso\deployable-war and select opensso.war. Then hit the Deploy button. It’ll take a while as the war file is uploaded through your browser into Tomcat. Tomcat has an auto-deploy function, Google it if you’re interested.
Eventually the application will be deployed. Navigate to http://sso.kenningcorp.com:8080/opensso.
If things are going well, you should see the OpenSSO configuration options page.
Click Custom Configuration. Here are the settings I use:
- Default user password – password
- Server settings – I leave the default entries in there
- Configuration store – First instance, OpenSSO
- User data store – OpenSSO
- Site configuration – No (not being a load balancer)
- Default policy agent password – password2
Now click Create Configuration. Fingers crossed. I’ve had problems installing this, in the following order:
- Don’t use the version of Tomcat that comes with XAMPP. Didn’t work for me.
- Don’t use the nightly version of OpenAM. Didn’t work for me.
- Don’t use 127.0.0.1 as the IP address of your domain. Didn’t work for me.
I had weird errors such as cookie domains not being valid host names, and other weird errors.
If things go well it should install. I get an error about a log file being NULL, but I don’t worry about it. Head to http://sso.kenningcorp.com:8080/opensso, which should now redirect you to http://sso.kenningcorp.com:8080/opensso/UI/Login. Type amAdmin as the username, and password as the password, and you should be authenticated against your OpenAM install, and shown the Administration page. Congratulations!