Preface

This manual describes the different options available for publishing reports with Oracle Reports Services as well as how to configure the Oracle Reports Services software for publishing reports.

Oracle Reports Services New Features

New Feature	See
Oracle Internet Applications Server. Provides a middle-tier application server.	Chapter 1, "Introduction" and Chapter 3, "Installing Oracle Internet Application Server Oracle on the Sun SPARC Solaris"
Oracle HTTP Server for JSDK. Configuration for running the Reports Servlet with JSDK through the Oracle HTTP Server (powered by Apache).	Section 4.2.1, "Configuring the Oracle HTTP Server to Run the Reports Services Servlet with JSDK"
Oracle HTTP Server for JServ. Configuration for running the Reports Servlet through the Oracle HTTP Server (powered by Apache).	Section 4.2.2, "Configuring the Oracle HTTP Server to Run Reports Services Servlet with JServ"
Oracle HTTP Server Listener. Configuration for Oracle HTTP Server Listener to run the Reports CGI.	Section 4.3, "Configuring Oracle HTTP Server Listener to Run Reports Services CGI"
Control user access to report. Restrict user access to reports that are run with Oracle Reports Services. Oracle Reports uses Oracle WebDB to check that users have the necessary access privileges to run the report with restricted Oracle Reports Services.	Chapter 6, "Controlling User Access to Reports"
Clustering. Improve performance and loading balancing by clustering your Oracle Reports Services.	Chapter 7, "Configuring Oracle Reports Services Clusters"
Report Customization. Apply customizations to reports at runtime without changing the original report and generate different output depending upon the audience.	Chapter 8, "Customizing Reports at Runtime"

Intended Audience

This manual is intended for anyone who is interested in publishing reports with Oracle Reports Services. It could be that you have built reports yourself and now want to publish them to a wider audience in your organization. It could also be that someone else built the reports for you and you now want to deploy them for other users to access. To configure Oracle Reports Services software for publishing reports, you should have a thorough understanding of the operating system (for example, Windows NT or Solaris) as well as Net8. If you are planning to deploy reports dynamically on the Web, then you should also be knowledgeable about your Web server configuration.

Structure

This manual contains the following chapters:

Chapter 1	Introduces you to the Oracle Reports Services.
Chapter 2	Introduces the architecture of the Oracle Reports Services and choices that you need to make before you configure the report.
Chapter 3	Provides information about installing.
Chapter 4	Describes how to configure the Oracle Reports Services.
Chapter 5	Describes the various methods for running reports to the Oracle Reports Services.
Chapter 6	Describes how the Oracle Reports Services can be integrated with Oracle WebDB to control user access to reports.
Chapter 7	Describes how to configure the Oracle Reports Services with clustering to enhance performance and reliability.
Chapter 8	Describes how to use XML to apply customizations to reports at runtime.

Related Documents

For more information on building reports, Oracle WebDB, or the Oracle Report Services, refer to the following manuals:

• Oracle Reports Developer Building Reports, A73172-01

• Oracle Reports Developer Getting Started for Windows, A73156-01

• Oracle WebDB Getting Started-Installation and Tutorial, A70070-01

• Deploying Forms to the Web with Oracle Internet Application Server, A83591-01

Notational Conventions

The following conventions are used in this book:

Convention	Meaning
boldface text	Used for emphasis. Also used for menu items, button names, labels, and other user interface elements.
italicized text	Used to introduce new terms.
courier font	Used for path and file names, and for code and text that you type.
COURIER CAPS	Used for file extensions (.PLL or .FMX) and SQL commands
CAPS	Used for environment variables, built-ins and package names, and executable names