This preface describes what is in this Developer's Guide.

This preface contains the following sections:

• About This Guide

• What You Should Know

• How This Guide Is Organized

• Documentation Conventions

About This Guide

---

This guide describes iAS UIF concepts, how to configure and use the components provided with iAS adapter targets. It also describes how to write servlet or EJB to access an connector program on the target platform and documents the APIs.

What You Should Know

---

This guide assumes you are familiar with the following topics:

• iAS programming concepts

• Internet and World Wide Web

• Target platform programming concepts

• Target connector programming concepts

• Java programming language and Java servlets

• Enterprise JavaBeans

How This Guide Is Organized

---

This guide is organized into the following chapters:

Chapter 1 "Concepts" describes concepts you should be familiar with before you set up UIF or use the API in your servlets or EJBs.

Chapter 2 "The Repository Browser" describes how to use the repository browser to view and modify target information.

Chapter 3 "Pooling Concepts" describes pooling concepts you should be familiar with when you set up a repository for target.

Chapter 4 "Programming Concepts" describes concepts you should be familiar with before use the UIF API in your servlets or EJBs.

Chapter 5 "API Reference" describes the classes and methods you can use from your servlet or EJB to access and manipulate data stored on a target system.

Documentation Conventions

---

File and directory paths are given in Windows format (with backslashes separating directory names). For Unix versions, the directory paths are the same, except slashes are used instead of backslashes to separate directories.

This guide uses URLs of the form:

http://server.domain/path/file.html

In these URLs, server is the name of server on which you run your application; domain is your Internet domain name; path is the directory structure on the server; and file is an individual filename. Italics items in URLs are placeholders.

This guide uses the following font conventions:

The monospace font is used for sample code and code listings, API and language elements (such as function names and class names), file names, pathnames, directory names, and HTML tags.

Italic type is used for book titles, emphasis, variables and placeholders, and words used in the literal sense.