Advanced Queuing - Oracle

Registering a Queue/Topic Connection Factory Through LDAP—with JDBC Connection Parameters
See Also:
Table 13–1 for a list of JMS administrative interface basic
operations
"Class - oracle.jms.AQjmsFactory" on page B-49
"Registering a Queue/Topic Connection Factory Through
LDAP—with a JDBC URL" on page 13-11
Purpose
Register a queue/topic connection factory through LDAP with JDBC connection
parameters to LDAP.
Usage Notes
registerConnectionFactory is a static method. To successfully register the
connection factory, the hashtable passed to registerConnectionFactory must
contain all the information to establish a valid connection to the LDAP server.
Furthermore, the connection must have write access to the connection factory
entries in the LDAP server (which requires the LDAP user to be either the database
itself or be granted global_aq_user_role). After registration, look up the
connection factory using JNDI.
Syntax
See Java (JDBC): Oracle9i Supplied Java Packages Reference oracle.jms,
AQjmsFactory.registerConnectionFactory.
Example
Hashtable env = new Hashtable(5, 0.75f);
/* the following statements set in hashtable env:
* service provider package
* the URL of the ldap server
* the distinguished name of the database server
* the authentication method (simple)
* the LDAP user name
* the LDAP user password
*/
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://sun-456:389");
env.put("searchbase", "cn=db1,cn=Oraclecontext,cn=acme,cn=com");
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, "cn=db1aqadmin,cn=acme,cn=com");
JMS Administrative Interface: Basic Operations 13-9