With reference to my earlier post
some people asked me why not use Glassfish as the servlet container
instead of Tomcat. I think they made sense to me. When I tried the
glassfish to my surprise the configuration of glassfish
was as simple as Tomcat. Few simple well documented steps got me a
working Application server in place. I have documented those simple
steps to save few minutes of yours.

Installing the Glassfish

1. Get the glassfish http://www.java.net/download/javaee5/promoted/SunOS/glassfish-installer-v2-b26.jar

2. java -Xmx256m -jar

3. cd glassfish;ant -f setup.xml

4. ./asadmin start-domain domain1

Build the OpenSSO

1. You can download or build the opensso by visting this page

2. Build the opensso
amserver.war if you have checked out the cvs source
3. Deploy the opensso
web application.

      [auduin]:/export1/glassfish/glassfish/bin>./asadmin deploy --user admin
--host auduin.example.com --port 4848 --contextroot opensso --name
Please enter the admin password>
Command deploy executed successfully.

[Glassfish default admin user is: admin with password: adminadmin ]

you can also leverage the autodeploy option in glassfish to deploy the
opensso web application.

Install and Configure OpenDS

1. Download the OpenDS binaries

wget https://opends.dev.java.net/files/documents/4926/44276/OpenDS-0.1-build017.zip

2. Unzip and configure the OpenDS

[auduin]:/export1/glassfish/OpenDS-0.1-build017> ./setup --cli
OpenDS Directory Server 0.1-build017
Please wait while the setup program initializes....
On which port would you like the Directory Server to accept connections from
LDAP clients?
[389]: 8389
What would you like to use as the initial root user DN for the Directory
[cn=Directory Manager]: cn=opends manager
Please provide the password to use for the initial root user:
Please re-enter the password for confirmation:
What do you wish to use as the base DN for the directory data?
[dc=example,dc=com]: dc=example,dc=com
Options for populating the database:
1.  Only create the base entry
2.  Leave the database empty
3.  Import data from an LDIF file
4.  Load automatically-generated sample data
Database population selection:
Applying the requested configuration to the Directory Server....
Successfully wrote the updated Directory Server configuration.
Creating a temporary LDIF file with the initial base entry contents....
Importing the LDIF data into the Directory Server database....
Import complete.
The OpenDS setup process has completed successfully.
[auduin]:/export1/glassfish/OpenDS-0.1-build017>cd config/schema
[auduin]:/export1/glassfish/OpenDS-0.1-build017/config/schema>wget http://blogs.sun.com/indira/resource/99-am_sm_ds_schema.ldif
16:48:10 (18.88 MB/s) - `99-am_sm_ds_schema.ldif' saved [2692/2692]
00-core.ldif              03-rfc2926.ldif
01-pwpolicy.ldif          03-rfc3112.ldif
02-config.ldif            03-rfc3712.ldif
03-changelog.ldif         03-uddiv3.ldif
03-rfc2713.ldif           04-rfc2307bis.ldif
03-rfc2714.ldif           99-am_sm_ds_schema.ldif
[auduin]:/export1/glassfish/OpenDS-0.1-build017>cd bin
[30/Nov/2006:17:00:05 -0800] category=CORE severity=NOTICE id=458886 msg="OpenDS Directory Server 0.1-build017 starting up."
[30/Nov/2006:17:00:12 -0800] category=BACKEND severity=NOTICE id=8847402 msg="A database backend containing 1 entries has started."
[30/Nov/2006:17:00:12 -0800] category=CONFIG severity=SEVERE_WARNING id=3277325 msg="Access control has been disabled."
[30/Nov/2006:17:00:13 -0800] category=CORE severity=NOTICE id=458887 msg="The Directory Server has started successfully."
[30/Nov/2006:17:00:13 -0800] category=CORE severity=NOTICE id=458891 msg="The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887):  The Directory Server has started successfully.."
[auduin]:/export1/glassfish/OpenDS-0.1-build017/bin>ldapsearch -p 8389 -D"cn=opends manager" -w secret12 -b"dc=example,dc=com" "objectclass=\*"
dn: dc=example,dc=com
objectClass: domain
objectClass: top
dc: example

Configure OpenSSO with OpenDS as configuration repository

After the opensso web application is deployed successfully, you can
access the opensso application by entering the
http://slapd.example.com:8080/opensso this page will bring up the
opensso configurator.

Enter the appropriate data that fits your local deployment. For instance
the configuration data for this particular scenario would be some thing
like this


once you hit the configure, the configurator will start configuring the
OpenSSO. After the successfull configuration you would see a
configuration succeeded message in the browser, after a few second
browser will redirect to the opensso login page.

If you notice any failure at this point consult the debug directory for further details on why the configurator failed.


The login screen of the OpenSSO should look like this


enter your opensso administrator user ID ‘amadmin’, hit enter