To Configure the Client SDK

1. In Makefile.clientsdk, edit the following parameters:

   JAVA_HOME

   Use the following path: /usr/jdk/entsys-j2se

   SERVER_HOSTNAME

   The fully-qualified domain name of the Access Manager server.

   SERVER_PROTOCOL

   If the Access Manager server is SSL-enabled, change this value to HTTPS.

   SERVER_PORT

   The port number on which the Access Manager server is running.

   ENCRYPTION_KEY

   This value must be the same value used for the Access Manager server. You can obtain the value by running one of the following commands on the Access Manager server:

   On Solaris

   grep pwd /etc/opt/SUNWam/config/AMConfig.properties

   On Linux

   grep pwd /etc/opt/sun/identity/config/AMConfig.properties

   DEBUG_DIR

   (Optional) If you don't want the debug logs stored in the tmp directory, then change this value to the directory where you want debug logs to be created.

2. Run the make or gmake command:

   make -f Makefile.clientsdk

   This step generates a sample properties file in the directory temp, standalone samples in the directory clientsdk-samples and a deployable war file, amclientwebapps.war.The following table summarizes the items included in the WAR file.

   File	Description
   index.html	Instructions for installing and using the Client SDK packages
   WEB-INF/web.xml	Client SDK for stand-alone applications
   WEB-INF/classes/AMClient.properties	Archive of Access Manager samples, web applications, and Javadoc
   WEB-INF/classes/*.classes	File for building stand-alone samples and web applications
   WEB-INF/docs	Javadoc (Public Client SDK APIs)
   WEB-INF/samples	Sample stand-alone programs
   WEB-INF/webapps	Sample web applications