Sun Java System Access Manager 7 2005Q4 Developer's Guide

Initializing the Client SDK

Before Access Manager Client SDK can communicate with Access Manager Server, you must initialize some properties in the client SDK. You can set these properties in one of three ways:

Using a Properties File

You can set properties in a properties file and then provide a path to it at runtime. The properties files must be in the CLASSPATH. The default properties file name is and is always read at start-up.

ProcedureTo Set ClientSDK Properties in a Properties File

  1. Generate a sample by running the following command:

    make -f Makefile.clientsdk properties

    The will be present in the temp directory.

  2. Edit properties to suit your environment.

  3. At runtime if the file name is different from AMConfig, provide the edited properties filename (without the .properties extension, and also with the path. The path should be in the CLASSPATH) by declaring the JVM option:


Using the Java API

The ClientSDK properties can also be set programmatically using the class: See Using the Java API.

Example 1–1 Setting ClientSDK Properties

import java.util.Properties;
public static void main(String[] args) {
        // To initialize a set of properties
        Properties props = new Properties();
        props.setProperty(”’, ”amAdmin’);
        props.setProperty(”’, ”11111111’);
        SystemProperties.initializeProperties(props) ;

        // To initialize a single property
    // Application specific code ...


Setting Individual Properties

You can set properties one at a time. For example, you can declare the following JVM option at run time to assign a value to a particular property:


The following sections describe the properties expected by Access Manager Client SDK. A client application deployed within a servlet container can register for changes to session, user attributes and policy decisions. These properties must be set to receive such notifications.

Naming URL Properties This is a required property. The value of this property represents the URL where the Client SDK would retrieve the URLs of Access Manager internal services. This is the URI for the Naming Service. Example:
		port/ amserver/namingservice This property can be used by any remote SDK application that wants failover in, for example, session validation or getting the service URLs. Example: http:// 
		AcceessManager-HostName.domain_name:port/		amserver/failover

Debug Properties

Specifies the debug level. Possible values are levels are: off, error , warning, or message.

The value of this property is the output directory for the debug information. This directory should be writable by the server process. Example:


Notification URL Properties

The value of this property is the URI of the Notification Service running on the host machine where you installed the Client SDK. Example: http://clientSDK_host.domain_name:

This property enables or disables notifications for remote policy API. Example:



This property defines the notification URL for remote policy API.