| Oracle® Streams Advanced Queuing User's Guide and Reference Release 10.1 Part Number B10785-01 |
|
|
View PDF |
| Oracle® Streams Advanced Queuing User's Guide and Reference Release 10.1 Part Number B10785-01 |
|
|
View PDF |
This reference describes features of application development and integration using Oracle Streams Advanced Queuing (AQ). This information applies to versions of the Oracle Database server that run on all platforms, unless otherwise specified.
The Preface contains these topics:
Oracle Streams Advanced Queuing User's Guide and Reference is intended for programmers who develop applications that use Oracle Streams AQ.
This chapter introduces you to Oracle Streams AQ and describes the requirements for optimal messaging systems.
This chapter describes the prerequisites for Oracle Streams AQ. It also provides examples of operations using different programmatic environments and answers to several frequently asked questions about Oracle Streams AQ in general.
This chapter describes Oracle Streams AQ features including general, enqueue, and dequeue features.
This chapter describes the elements you must work with and issues to consider in preparing your Oracle Streams AQ application environment for different languages.
This chapter discusses issues related to managing Oracle Streams AQ, such as migrating queue tables (import-export), security, Oracle Enterprise Manager support, protocols, sample DBA actions to prepare for working with Oracle Streams AQ, and current restrictions.
This chapter discusses performance and scalability issues. It included frequently asked questions.
This chapter describes the administrative interface to Oracle Streams AQ.
This chapter describes how to use Oracle Streams AQ views administrative interface. It includes syntax and examples.
This chapter describes how to use the Oracle Streams AQ operational interface. It includes syntax and examples.
This chapter describes how to create application using Oracle JMS interface with Oracle Streams AQ.
This chapter describes how to use the Oracle Streams AQ administrative interface for JMS.
This chapter describes how to use Oracle JMS interface with Oracle Streams AQ for point-to-point operations.
This chapter describes how to use Oracle JMS interface with Oracle Streams AQ for publish/subscribe operations.
This chapter describes how to use Oracle JMS interface with Oracle Streams AQ for shared interface operations.
This chapter provides JMS type enqueuing and dequeuing examples for bytes, streams, and map message types. The examples illustrate how you can use JMS and DBMS_AQ for enqueuing and dequeuing.
This chapter describes how to perform Oracle Streams AQ operations over the Internet using its Internet Data Access Presentation (IDAP) and Simple Object Access Protocol (SOAP). It also shows how to transmit messages over the Internet using HTTP.
This chapter introduces Messaging Gateway's features, functions, and architecture. It describes how applications based on Oracle Streams AQ can communicate with non-Oracle messaging systems using Messaging Gateway.
This chapter describes the prerequisites for running Messaging Gateway, how to load and unload Messaging Gateway, and how to set it up for use.
This chapter describes how to use Messaging Gateway: how to configure, start, and stop it, and how to configure Messaging Gateway Agent.
This chapter shows how to transform messages between Oracle Streams AQ formats and those used by supported third-party messaging systems.
This chapter discusses abnormal situations you may experience, several sources of information about Messaging Gateway errors and exceptions, and suggested remedies.
This chapter describes how to use Oracle Streams for staging and propagation of queues and SYS_AnyData.
This chapter includes a detailed example that illustrates how to use Oracle Streams for messaging.
This chapter describes ways you can troubleshoot Oracle Streams AQ.
This appendix provides scripts for implementing the BooksOnLine example.
For more information, see these Oracle resources:
For Oracle APIs for JMS see:
http://otn.oracle.com/docs/products/aq/doc_library/ojms/index.html
Many examples in the documentation set use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.
Printed documentation is available for sale in the Oracle Store at
http://oraclestore.oracle.com/
To download free release notes, installation documentation, white papers, or other collateral, visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at
http://otn.oracle.com/membership/
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://otn.oracle.com/documentation/
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.
| Convention | Meaning | Example |
|---|---|---|
| Bold | Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both. | When you specify this clause, you create an index-organized table. |
| Italics | Italic typeface indicates book titles or emphasis. | Oracle Database Concepts
Ensure that the recovery catalog and target database do not reside on the same disk. |
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, usernames, and roles. | You can specify this clause only for a NUMBER column.
You can back up the database by using the Query the Use the |
lowercase monospace (fixed-width) font |
Lowercase monospace typeface indicates executables, filenames, directory names, 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, usernames and roles, program units, and parameter values.
Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. |
Enter sqlplus to open SQL*Plus.
The password is specified in the Back up the datafiles and control files in the The Set the Connect as The |
lowercase italic monospace (fixed-width) font |
Lowercase italic monospace font represents placeholders or variables. | You can specify the parallel_clause.
Run |
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:
|
CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln FROM employees; |
. . . |
Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example. |
SQL> SELECT NAME FROM V$DATAFILE; NAME ------------------------------------ /fsl/dbs/tbs_01.dbf /fs1/dbs/tbs_02.dbf . . . /fsl/dbs/tbs_09.dbf 9 rows selected. |
| Other notation | You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown. |
acctbal NUMBER(11,2); acct CONSTANT NUMBER(4) := 3; |
Italics |
Italicized text indicates placeholders or variables for which you must supply particular values. |
CONNECT SYSTEM/system_password DB_NAME = database_name |
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.
Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. |
SELECT last_name, employee_id FROM employees; sqlplus hr/hr CREATE USER mjones IDENTIFIED BY ty3MU9; |
The following table describes conventions for Windows operating systems and provides examples of their use.
| Convention | Meaning | Example |
|---|---|---|
| Choose Start > | How to start a program. | To start the Database Configuration Assistant, choose Start > Programs > Oracle - HOME_NAME > Configuration and Migration Tools > Database Configuration Assistant. |
| File and directory names | File and directory names are not case sensitive. The following special characters are not allowed: left angle bracket (<), right angle bracket (>), colon (:), double quotation marks ("), slash (/), pipe (|), and dash (-). The special character backslash (\) is treated as an element separator, even when it appears in quotes. If the file name begins with \\, then Windows assumes it uses the Universal Naming Convention. |
c:\winnt"\"system32 is the same as C:\WINNT\SYSTEM32 |
C:\> |
Represents the Windows command prompt of the current hard disk drive. The escape character in a command prompt is the caret (^). Your prompt reflects the subdirectory in which you are working. Referred to as the command prompt in this manual. |
C:\oracle\oradata> |
| Special characters | The backslash (\) special character is sometimes required as an escape character for the double quotation mark (") special character at the Windows command prompt. Parentheses and the single quotation mark (') do not require an escape character. Refer to your Windows operating system documentation for more information on escape and special characters. |
C:\>exp scott/tiger TABLES=emp QUERY=\"WHERE job='SALESMAN' and sal<1600\" C:\>imp SYSTEM/password FROMUSER=scott TABLES=(emp, dept) |
HOME_NAME |
Represents the Oracle home name. The home name can be up to 16 alphanumeric characters. The only special character allowed in the home name is the underscore. |
C:\> net start OracleHOME_NAMETNSListener |
ORACLE_HOME and ORACLE_BASE |
In releases prior to Oracle8i release 8.1.3, when you installed Oracle components, all subdirectories were located under a top level ORACLE_HOME directory that by default used one of the following names:
This release complies with Optimal Flexible Architecture (OFA) guidelines. All subdirectories are not under a top level All directory path examples in this guide follow OFA conventions. Refer to Oracle Database Platform Guide for Windows for additional information about OFA compliances and for information about installing Oracle products in non-OFA compliant directories. |
Go to the ORACLE_BASE\ORACLE_HOME\rdbms\admin directory. |
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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.
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
|
 Copyright © 1996, 2003 Oracle Corporation All Rights Reserved. |
|
