Access Manager 7.1 supports both the Liberty Alliance Identity Web Services Framework 1.0 Specifications and the Liberty Alliance Identity Services Interface Specifications 1.0. The web services samples are located in /AccessManager-base/SUNWam/samples/phase2. To demonstrate the different Liberty-based web services protocols featured in Access Manager, four sample applications are included. They are located in the following sub-directories:
The wsc directory contains a collection of files to deploy and run a web service consumer (WSC).
Before implementing this sample, you must have two instances of Access Manager installed, and running, and Liberty-enabled. Completing the procedure in sample1 Directory will accomplish this.
In addition, this sample illustrates how to use the Discovery Service and Data Services Template client APIs to allow the WSC to communicate with a web service provider (WSP). This sample describes the flow of the Liberty-based Web Service Framework (ID-WSF) and how the security mechanisms and interaction service are integrated. The Readme.html file in the wsc directory provides detailed steps on how to deploy and configure this sample. For more information, see also Chapter 7, Data Services and Chapter 8, Discovery Service.
The sis-ep directory contains a collection of files to develop, deploy, and invoke a new Liberty-based web service to Access Manager. The sample implements the Liberty Employee Profile Service.
Before implementing this sample, you must have two instances of Access Manager installed, and running, and Liberty-enabled. Completing the procedure in sample1 Directory will accomplish this.
The Liberty Employee Profile Service is a deployment of the Liberty ID-SIS Employee Profile Service Specification (ID-SIS-EP), which is one of the Liberty Alliance ID-SIS 1.0 Specifications. The Readme.html file in the sample directory provides detailed steps on how to deploy and configure this sample. For more information, see also Chapter 7, Data Services
The paos directory contains
a collection of files that demonstrate how to set up and invoke a
PAOS Service interaction between a client and server. The sample is
based on the following scenario: a cell phone user subscribes to a
news service offered by the cell phone’s manufacturer. The news
service automatically provides stocks and weather information to the
user’s cell phone at regular intervals. In this scenario, the
manufacturer is the news service provider, and the individual cell
phone user is the consumer. After running the sample, you will see
the output from the PAOSServer
program.
You can also see the output from PAOSClientServlet
program in the log file of the Web Server. For example, when
using Sun Java System Web Server, look in the log subdirectory
for the errors file.
The Readme.html file in the sample directory provides detailed steps on how to deploy and configure this sample. In addition, see PAOS Binding Sample.
In an actual deployment, the server-side code would be developed by a service provider.
The authnsvc directory contains a collection of files to illustrate the use of the Access Manager Authentication Web Service. This sample program authenticates against the service and extracts the resource offering of a discovery bootstrap. The Readme.html file in the sample directory provides detailed steps on how to deploy and configure this sample. In addition, see Chapter 6, Authentication Web Service