The Access Manager server which will be used by the client SDK must be up and running, and you must know the URL for accessing this server.
The machine where the client SDK will be installed must have an Access Manager supported web container installed. Examples of Access Manager supported web containers are Sun Java System Web Server 6.1 sp5, Sun Java System Application Server 8.1, BEA WebLogic Server 8.1 sp4, and IBM Websphere Application Server 5.1.1.5.
The web container instance on which the client SDK will be deployed must be up and running.
The client SDK machine must have access to the Access Manager client SDK package SUNWamclnt through the Java Enterprise System 4 bits or through some other means.
Create a package administration file. .
Using a text editor, add the following contents to this file.
mail= instance=unique partial=nocheck runlevel=nocheck idepend=nocheck rdepend=nocheck space=nocheck setuid=nocheck conflict=nocheck action=nocheck basedir=ClientSDK-base-directory
In this example, the package administration file is named /usr/tmp/pkgadmin.
The value for basediris the directory in which you want to install the Access Manager client SDK.
Create a package response file named /usr/tmp/pkgresp.
Using a text editor, place the following three lines (a single y on each line) in this file.
y y y
In the Access Manager package directory, use the pkgadd utility to install the SUNWamclnt package:
cd JES2005Q4-Image-root/OperatingSystem-Architecture/Product/identity_svr/Packages
pkgadd -n -a /usr/tmp/pkgadmin -d . -r /usr/tmp/pkgresp -R / SUNWamclnt
In the directory in which you installed the Access Manager client SDK package, make a copy of the file Makefile.clientsdk.
The directory in which you installed the Access Manager client SDK package should be the same as the value you used for basedir in the package administration file in step 1a.
cd ClientSDK-base-directory/SUNWam
cp Makefile.clientsdk Makefile.clientsdk.orig
cd ClientSDK-base-directory/identity
cp Makefile.clientsdk Makefile.clientsdk.orig