Advanced Queuing - Oracle

General Features of JMS
Using JNDI to Look Up Destination Objects
As described in "Connection Factory" on page 12-5, the database can be configured
to register schema objects with an LDAP server. If a database has been configured to
use LDAP and the GLOBAL_TOPIC_ENABLED parameter has been set to TRUE,
then all JMS queues and topics are automatically registered with the LDAP server
when they are created.
The administrator can also create aliases to the queues and topics registered in
LDAP using the DBMS_AQAQDM.add_alias_to_ldap PL/SQL procedure.
Queues and topics that are registered in LDAP can be looked up through JNDI
using the queue/topic name or one of their aliases.
Example Code
Lets say we have a new orders queue OE.OE_neworders_que stored in LDAP, it
can be looked up as follows:
public static void get_Factory_from_LDAP() throws Exception
{
Hashtable env = new Hashtable(5, 0.75f);
env.put(Context.INITIAL_CONTEXT_FACTORY, AQjmsConstants.INIT_CTX_FACTORY);
}
// aqldapserv is your LDAP host and 389 is your port
env.put(Context.PROVIDER_URL, "ldap://aqldapserv:389);
// now authentication info
// username/password scheme, user is OE, password is OE
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, "cn=oe,cn=users,cn=acme,cn=com");
env.put(Context.SECURITY_CREDENTIALS, "oe");
DirContext inictx = new InitialDirContext(env);
// initialize context with the distinguished name of the database server
inictx=(DirContext)inictx.lookup("cn=db1,cn=OracleContext,cn=acme,cn=com");
// go to the destination holder
DirContext destctx = (DirContext)inictx.lookup("cn=OracleDBQueues");
// get the destination OE.OE_new_orders queue
Queue myqueue = (Queue)destctx.lookup("cn=OE.OE_new_orders_que");
Methods on the Destination Object include:
12-14 Oracle9i Application Developer’s Guide - Advanced Queuing