Advanced Queuing - Oracle

Deploying the AQ XML Servlet
User Authorization
Using HTTP
In the context of the AQ servlet, the user name that is used to connect to the Web
server is known as the AQ HTTP agent or AQ Internet user.
Example: In Apache, the following can be used to restrict access (using basic
authentication) to servlets installed under aqserv/servlet. In this example, all
users sending POST requests to the servlet are authenticated using the users file in
/apache/htdocs/userdb.
AuthName "AQ restricted stuff"
AuthType Basic
AuthUserFile /apache/htdocs/userdb/users
require valid-user
After authenticating the users who connect to the AQ servlet, you establish which
operations the users are authorized to perform by doing the following:
1. Register the AQ agent for Internet access.
2. Map the AQ agent to one or more database users.
Registering the AQ Agent
To register the AQ agent for Internet access, use DBMS_AQADM.CREATE_AQ_AGENT.
The CREATE_AQ_AGENT procedure takes an agent_name. You specify which
protocols the user can use to access the servlet—HTTP, SMTP, or both. For agents
accessing the AQ servlet using SMTP, an LDAP certificate_location must
also be specified. See "Setup for Receiving AQ XML Requests Using SMTP (E-mail)"
on page 17-55 for more information.
Example
Create an AQ agent JOHN to access the AQ servlet using HTTP.
DBMS_AQADM.CREATE_AQ_AGENT(agent_name => ’JOHN’, enable_http => true);
The procedures ALTER_AQ_AGENT and DROP_AQ_AGENT for altering and dropping
AQ agents function similarly to CREATE_AQ_AGENT. These procedures are
documented in the Oracle9i Supplied PL/SQL Packages and Types Reference.
17-52 Oracle9i Application Developer’s Guide - Advanced Queuing