Advanced Queuing - Oracle

Using HTTP to Access the AQ XML Servlet
users has privileges to access the queue/topic specified in the request, the
AQ servlet super-user creates a session on behalf of this db_user.
For example, where the agent JOHN is mapped to the database user OE
using the DBMS_AQADM.ENABLE_DB_ACCESS call, the servlet will create a
session for the agent JOHN with the privileges of database user OE. (See
"Mapping the AQ Agent to Database Users" for information on ENABLE_
DB_ACCESS.)
A new database transaction is started if no transaction is active in the HTTP
session. Subsequent requests in the session will be part of the same
transaction until an explicit COMMIT or ROLLBACK request is made.
The requested operation
(SEND/PUBLISH/RECEIVE/REGISTER/COMMIT/ROLLBACK) is
performed.
The response is formatted as an XML message and sent back the client.
For example, the response for the preceding request may be as follows:
0
OE.OE_NEW_ORDERS_QUE
12341234123412341234123412341234
The response also includes the session id in the HTTP headers as a cookie.
For example, Tomcat sends back session IDs as JSESSIONID=239454ds2343.
If the operation does not commit the transaction, the transaction will
remain active until an explicit commit/rollback call is received. The effects
of the transaction are visible only after it is committed. If the transaction
remains inactive for 120 seconds, it is automatically aborted.
Internet Access to Advanced Queuing 17-61