Preface

This reference describes features of application development and integration using Oracle Advanced Queuing. This information applies to versions of the Oracle Server that run on all platforms, unless otherwise specified.

This preface discusses the following:

Audience

The Oracle9i Application Developer's Guide - Advanced Queuing is intended for programmers developing new applications that use Oracle Advanced Queuing, as well as those who have already implemented this technology and now wish to take advantage of new features.

Organization

The Oracle9i Application Developer's Guide - Advanced Queuing contains the following chapters and appendices:

Chapter 1, "Introduction to Oracle Advanced Queuing"

This chapter describes the requirements for optimal messaging systems. Although Oracle AQ is a relatively new technology, and not all these goals have been realized, you can get an overview of the design and a clear idea of the intended direction.

Chapter 2, "Basic Components"

This chapter describes features already present in Oracle AQ under three headings: General Features, Enqueue Features, and Dequeue Features.

Chapter 3, "AQ Programmatic Environments"

This chapter describes the elements you need to work with and issues you will want to take into consideration in preparing your AQ application environment.

Chapter 4, "Managing AQ"

This chapter discusses issues related to managing Advanced Queuing such as migrating queue tables (import-export), security, enterprise manager support, protocols, sample dba actions as preparation for working with AQ, and current restrictions.

Chapter 5, "Performance and Scalability"

This chapter discusses performance and scalability issues.

Chapter 6, "Frequently Asked Questions"

Frequently asked questions are answered here.

Chapter 7, "Modeling and Design"

This chapter covers the fundamentals of Advanced Queueing modeling anddesign.

Chapter 8, "A Sample Application Using AQ"

This chapter considers the features of Oracle Advanced Queuing in the context of a sample application.

Chapter 9, "Administrative Interface"

This chapter describes the administrative interface to Oracle Advanced Queuing.

Chapter 10, "Administrative Interface: Views"

In this chapter we describe the administrative interface with respect to views in terms of a hybrid of use cases and state diagrams.

Chapter 11, "Operational Interface: Basic Operations"

In this chapter we describe the operational interface to Oracle Advanced Queuing in terms of use cases.

Chapter 12, "Creating Applications Using JMS"

In this chapter we consider the features of the Oracle JMS interface to AQ in the context of a sample application based on that scenario.

Chapter 13, "JMS Administrative Interface: Basic Operations"

In this chapter we describe the administrative interface to Oracle Advanced Queuing in terms of use cases.

Chapter 14, "JMS Operational Interface: Basic Operations (Point-to-Point)"

In this chapter we describe point-to-point operations.

Chapter 15, "JMS Operational Interface: Basic Operations (Publish-Subscribe)"

In this chapter we describe publish-subscribe operations.

Chapter 16, "JMS Operational Interface: Basic Operations (Shared Interfaces)"

In this chapter we describe shared interface operations.

Chapter 17, "Internet Access to Advanced Queuing"

In this chapter we describe how to perform AQ operations over the Internet by using the Internet Data Access Presentation (IDAP) and transmitting the message over the Internet using transport protocols such as HTTP or SMTP.

Appendix A, "Oracle Advanced Queuing by Example"

This appendix provides examples of operations using different programmatic environments.

Appendix B, "Oracle JMS Interfaces, Classes and Exceptions"

This appendix provides a list of Oracle JMS interfaces, classes, and exceptions.

Appendix C, "Scripts for Implementing 'BooksOnLine'"

This appendix contains scripts used in the BooksOnLine example.

Appendix D, "JMS and AQ XML Servlet Error Messages"

This appendix listserror messages.

Appendix E, "Interpreting Unified Modeling Language Diagrams"

This appendix provides a brief explanation of use case diagrams and UML notation.

Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention	Meaning	Example
Bold	Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both.	The C datatypes such as ub4, sword, or OCINumber are valid. When you specify this clause, you create an index-organized table.
Italics	Italic typeface indicates book titles, emphasis, syntax clauses, or placeholders.	Oracle9i Database Concepts You can specify the parallel_clause. Run `U``old_release``.SQL` where old_release refers to the release you installed prior to upgrading.
UPPERCASE monospace (fixed-width font)	Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, user names, and roles.	You can specify this clause only for a `NUMBER` column. You can back up the database using the `BACKUP` command. Query the `TABLE_NAME` column in the `USER_TABLES` data dictionary view. Specify the `ROLLBACK_SEGMENTS` parameter. Use the `DBMS_STATS`.`GENERATE_STATS` procedure.
lowercase monospace (fixed-width font)	Lowercase monospace typeface indicates executables and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, user names and roles, program units, and parameter values.	Enter `sqlplus` to open SQL*Plus. The `department_id`, `department_name`, and `location_id` columns are in the `hr.departments` table. Set the `QUERY_REWRITE_ENABLED` initialization parameter to `true.` Connect as `oe` user.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention	Meaning	Example
[ ]	Brackets enclose one or more optional items. Do not enter the brackets.	`DECIMAL (digits [ , precision ])`
{ }	Braces enclose two or more items, one of which is required. Do not enter the braces.	`{ENABLE \| DISABLE}`
\|	A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar.	`{ENABLE \| DISABLE}` `[COMPRESS \| NOCOMPRESS]`
`...`	Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code	`CREATE TABLE ... AS subquery;` `SELECT col1, col2, ... , col``n` `FROM employees;`
. . .	Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example.
Other notation	You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as it is shown.	`acctbal NUMBER(11,2);` `acct CONSTANT NUMBER(4) := 3;`
`Italics`	Italicized text indicates variables for which you must supply particular values.	`CONNECT SYSTEM/``system_password`
`UPPERCASE`	Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase.	`SELECT last_name, employee_id FROM employees;` `SELECT * FROM USER_TABLES;` `DROP TABLE hr.employees;`
`lowercase`	Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files.	`SELECT last_name, employee_id FROM employees;` `sqlplus hr/hr`

Documentation Accessibility

Oracle's goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.