Sun Java System Access Manager 7.1 Developer's Guide

Compiling Logging Programs

Included with the sample log programs is a gmake Makefile which compiles both and, as well as the utilities module The item of most interest is the CLASSPATH setting.

Executing Logging Programs

The sample standalone log programs include ksh scripts. There are considerations for running on Solaris or Linux handled by the scripts, but a few less obvious settings concern whether there is local or remote logging, if database logging is configured, and if Access Manager is configured for SSL. The LOCAL_LOGGING shell variable is set to true by default. If the logging program is executing on a remote system, using the Access Manager client APIs, then the LOCAL_LOGGING shell variable this must be set to false. The LOCAL_LOGGING setting later determines the setting of the CONFIGOPTION variable. When the logging program is running on the same system as the Access Manager server, and logging to a database is configured, then the database JDBC driver must also be included in the CLASSPATH. If the Access Manager server is configured for SSL, and the logging program is executing on a remote system using the Access Manager client APIs, be sure that the following parameter is set in the script:


The certificate database conforming to the Access Manager server container must be provided, and the property in the file must point to the Access Manager server container. For example, for non-production testing to an Access Manager server running in a Application Server 8.1 container, you can copy (assuming default installation of AS 8.1) /var/opt/SUNWappserver/domains/domain1/config to the remote system, and set to that location. You must also set the following:

The .wtpass file needs to be created. More detailed information about certificates, see the file AccessManager-base/SUNWam/samples/authentication/api/Readme_setup.html .