Advanced Queuing - Oracle

General Features of JMS
After order entry, queue connection factory oe_queue_factory has been
registered 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 connection factory holder cn=OraclDBConnections
DirContext connctx = (DirContext)inictx.lookup("cn=OracleDBConnections");
// get connection factory "oe_queue_factory"
QueueConnectionFactory qc_fact =
(QueueConnectionFactory)connctx.lookup("cn=oe_queue_factory");
Connection
A JMS Connection is a client’s active connection to its JMS provider. A Connection
performs several critical services:
Encapsulates either an open connection or a pool of connections with a JMS
provider
Typically represents an open TCP/IP socket (or a set of open sockets) between a
client and a provider’s service daemon
Provides a structure for authenticating clients at the time of its creation
Creates Sessions
Provides Connection metadata
Supports an optional ExceptionListener
12-8 Oracle9i Application Developer’s Guide - Advanced Queuing