OpenAM SSOAdminTools, problems with Windows 2008

OpenAM's SSO Admin Tools are packaged in SSOAdminTools.zip.  The first step before using the sso admin tools is to run setup command within the sso admin tools.  The command requires openam configuration directory, and locations for debug, and log files.  Along with other tools, the setup creates the sso admin tool, openam/bin/ssoadm.bat.  ssoadm is the tool used for OpenAM command line administration.

The batch file contains check for JAVA_HOME, and under Windows 2008 it is:

IF NOT EXISTS JAVA_HOME (
  JAVA_HOME=C:\Program Files (x86)\.....
)

The left paranthesis after JAVA_HOME closes with matching right closing parenthesis ..x86), resulting in parsing errors, and makes the ssoadm unusable in Windows 2008.

This problem seems to be specific to Windows 2008.

OpenAM Java SDK debugging using eclipse

Finally OpenAM made some good documentation available to the developers, http://openam.forgerock.org/doc/dev-guide/index.html.  the document provides examples using OpenAM's Java SDK.  Ant scripts were provided for the build process, and batch files were provided running the examples.  Out of box, the build files, and batch files ran without any issues.

The first step in running the examples is to run scripts\setup.bat.  This is an interactive batch file, and collects basic information about the openam host name, port number, realm, userid,  password etc.  As soon as all relevant information is provided, setup.bat creates resources\AMConfig.properties which would be used while running the examples.


Copy resources\AMConfig.properties to the root of the Java source directory, and Eclipse's debugging features can be used to debug Java clients secured by OpenAM.