Oracle9i Application Developer's Guide - Advanced Queuing Release 1 (9.0.1) Part Number A88890-02 |
|
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:
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.
The Oracle9i Application Developer's Guide - Advanced Queuing contains the following chapters and appendices:
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.
This chapter describes features already present in Oracle AQ under three headings: General Features, Enqueue Features, and Dequeue Features.
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.
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.
This chapter discusses performance and scalability issues.
Frequently asked questions are answered here.
This chapter covers the fundamentals of Advanced Queueing modeling anddesign.
This chapter considers the features of Oracle Advanced Queuing in the context of a sample application.
This chapter describes the administrative interface to Oracle Advanced Queuing.
In this chapter we describe the administrative interface with respect to views in terms of a hybrid of use cases and state diagrams.
In this chapter we describe the operational interface to Oracle Advanced Queuing in terms of use cases.
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.
In this chapter we describe the administrative interface to Oracle Advanced Queuing in terms of use cases.
In this chapter we describe point-to-point operations.
In this chapter we describe publish-subscribe operations.
In this chapter we describe shared interface operations.
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.
This appendix provides examples of operations using different programmatic environments.
This appendix provides a list of Oracle JMS interfaces, classes, and exceptions.
This appendix contains scripts used in the BooksOnLine example.
This appendix listserror messages.
This appendix provides a brief explanation of use case diagrams and UML notation.
Use the PL/SQL User's Guide and Reference to learn PL/SQL and to get a complete description of this high-level programming language, which is Oracle Corporation's procedural extension to SQL.
The Oracle Call Interface (OCI) is described in:
You can use the OCI to build third-generation language (3GL) applications that access the Oracle Server.
Oracle Corporation also provides the Pro* series of precompilers, which allow you to embed SQL and PL/SQL in your application programs. If you write 3GL application programs in Ada, C, C++, COBOL, or FORTRAN that incorporate embedded SQL, refer to the corresponding precompiler manual. For example, if you program in C or C++, refer to the Pro*C/C++ Precompiler Programmer's Guide.
For SQL information, see the Oracle9i SQL Reference and Oracle9i Database Administrator's Guide. For basic Oracle concepts, see Oracle9i Database Concepts.
In North America, printed documentation is available for sale in the Oracle Store at
http://oraclestore.oracle.com/
Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from
http://www.oraclebookshop.com/
Other customers can contact their Oracle representative to purchase printed documentation.
To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at
http://technet.oracle.com/membership/index.htm
If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at
http://technet.oracle.com/docs/index.htm
This section describes the conventions used in the text and code examples of this documentation set. It describes:
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.
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.
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.
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|