Advanced Queuing - Oracle

. Map the AQ agent to a database user as follows:
Customizing the AQ Servlet
dbms_aqadm.enable_db_access(agent_name =>'John', db_username =>'CBADM')'
7. Start propagation at the source site by calling:
dbms_aqdm.schedule_propagation.
dbms_aqadm.schedule_propagation('src_queue', 'dba');
Using SMTP to Access the AQ Servlet
The general procedure for an AQ client to make a request to the AQ servlet using
SMTP is as follows:
1. The client creates a message with the AQ XML client request. The client signs
the message with its private key using the Oracle S/MIME toolkit.
2. The client names the message with a substring, IDAP_MESSAGE, and sends it as
a binary attachment to the database e-mail address.
3. The e-mail server receives the message.
4. The e-mail server triggers the rule registered for the database e-mail address,
which does the following:
a. Connects to the LDAP server and retrieves the certificate of the sending AQ
agent
b. Verifies the signature of the message
c. Connects to the Web server as user ORACLE_SMTP_AGENT if authentication
succeeds, and sends an HTTP POST message containing the client request
The procedure for the AQ servlet to process a request is described in "AQ Servlet
Processes a Request Using HTTP" on page 17-60. When the servlet sends a response,
the e-mail server sends an e-mail message containing the XML response to the
address specified in the reply-to field of the original e-mail message.
Customizing the AQ Servlet
The oracle.AQ.xml.AQxmlServlet provides the API to set the connection pool size,
session timeout, style sheet, and callbacks before and after AQ operations.
Internet Access to Advanced Queuing 17-65