Skip Headers
Oracle® Access Manager Developer Guide
10g (

Part Number B25346-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

E SOAP and HTTP Client

Several components, such as IdentityXML and AccessXML, allow you to gain access to Oracle Access Manager by using SOAP (Simple Object Access Protocol). To do this, you build a properly formatted SOAP request, with the Oracle Access Manager-related information contained within it.

SOAP provides a way to exchange information in a decentralized, distributed environment. It uses XML as a basis for its protocol, which consists of three parts:

A full discussion of the protocol can be found at:

Though SOAP provides the means to communicate with Oracle Access Manager, it is still necessary to transport the message content using the Web to the Identity or Access System Server that will process it. This requires the use of an HTTPClient.The HTTPClient is an application that simulates the HTTP communication capabilities of a browser, without an HTML presentation.

Though such a client could be written from scratch, toolkits are available that provide the necessary components. One such toolkit is available from Innovation:

The toolkit is free and internally documented. It includes support for the request methods HEAD, GET, POST and PUT, and contains modules that support automatic handling of authorization, redirection requests, and cookies.

You use the toolkit to provide the HTTP communication modules that will be the back end of an HTTPClient that you write. The front end of your client will have these features:

A sample of such a client is provided in the following directory:

Identity_install_dir /unsupported/integsvcs

in the file You need to compile this file into a class version, within the HTTPClient build environment.

The resulting example enables you to send a selected request file to a selected port of a selected host. The command line arguments are:

java ObSoapClient -h hostname -p port -f file

where hostname is the URL you want to communicate with, por t is the port number, and file is the name of the request file you want to send. The response is displayed to the screen. You will probably want to pipe this to a file, or modify the example to print to a file you name on the command line.

The file provides a similar example for use with PERL.

Several example request files are provided for you, also in the location:

Identity_install_dir /unsupported/integsvcs

You will not be able to use these files as is. You will need to change at least the login and password information in each one to information matching a valid user on the system you are trying to access. And, you will probably need to change the uid information in each file to match your directory structure and content.