Advanced Queuing - Oracle

Using HTTP to Access the AQ XML Servlet
'welcome', -- email user password
'acme.com', -- email user domain
'aqdb1@acme.com', -- complete email address
'aqdb1', -- name of destination database
'http://aq-sun:8000/aqserv/servlet/AQTestServlet', -- URL to access
the destination database servlet
'welcome', -- password of ORACLE_SMTP_AGENT
'ldaphost', -- LDAP host for lookup client certificates
'389', -- LDAP port for LDAP lookup
'cn=aqdb1,cn=oraclecontext,cn=acme,cn=com', -- base DN of LDAP lookup
NULL, NULL -- anonymous bind
);
dbms_output.put_line('register DB status: ' || status);
end;
5. Make sure the operation returns status 0.
After the setup is complete, an AQ agent can send e-mail messages to the database
e-mail address to perform AQ operations. The AQ operations should be constructed
according to IDAP, signed using the Oracle e-mail S/MIME toolkit, and sent as a
binary attachment with the name including IDAP_MESSAGE.
Using HTTP to Access the AQ XML Servlet
The procedures for an AQ client to make a request to the AQ servlet using HTTP
and for the AQ servlet to process the request are as follows:
AQ Client Request to the AQ Servlet Using HTTP
1. The client opens an HTTP(S) connection to the server.
For example,
https://aq.us.oracle.com:8000/aqserv/servlet/AQTestServlet
This opens a connection to port 8000 on aq.us.oracle.com.
2. The client logs in to the server by either:
HTTP basic authentication (with or without SSL)
SSL certificate-based client authentication
3. The client constructs the XML message representing the Send, Publish, Receive
or Register request.
Example:
17-58 Oracle9i Application Developer’s Guide - Advanced Queuing