Advanced Queuing - Oracle

Notifications from the server to the client
The Internet Data Access Presentation (IDAP)
Note: AQ Internet Access is supported only for 8.1-style queues.
8.0-style queues cannot be accessed using IDAP.
Client Requests for Enqueue
Client requests for enqueue—SEND and PUBLISH requests—use the following
methods:
AQXmlSend—to enqueue to a single-consumer queue
AQXmlPublish—to enqueue to multiconsumer queues/topics
AQXmlSend and AQXmlPublish take the arguments and argument attributes
shown in Table 17–1. Required arguments are shown in bold.
Table 17–1 Client Requests for Enqueue—Arguments and Attributes for AQXmlSend and AQXmlPublish
Argument Attribute
producer_options destination—specify the queue/topic to which messages are to be sent. The
destination element has an attribute lookup_type which determines how the
destination element value is interpreted
DATABASE (default)—destination is interpreted as schema.queue_
name
LDAP—the LDAP server is used to resolve the destination
- visibility
ON_COMMIT—The enqueue is part of the current transaction. The operation is
complete when the transaction commits. This is the default case.
IMMEDIATE—effects of the enqueue are visible immediately after the request
is completed. The enqueue is not part of the current transaction. The
operation constitutes a transaction on its own.
- transformation—the PL/SQL transformation to be invoked before the
message is enqueued
message_set—contains
one or more messages.
Each message consists of a message_header and message_payload
message_header message_id—unique identifier of the message, supplied during dequeue
- correlation—correlation identifier of the message
Internet Access to Advanced Queuing 17-7