Advanced Queuing - Oracle

General Features of JMS
To connect directly to LDAP, the parameters for the
registerConnectionFactory method include the LDAP context, the name of
the Queue/Topic ConnectionFactory, hostname, database SID, port
number, JDBC driver (thin or oci8) and factory type (queue or topic).
Connect to LDAP through the database server - the user can log on to the
Oracle9i database first and then have the database update the LDAP entry.
The user that logs on to the database must have the AQ_ADMINISTRATOR_
ROLE to perform this operation.
To connect directly to LDAP through the database server, the parameters
for the registerConnectionFactory method include a JDBC connection (to a
user having AQ_ADMINISTRATOR_ROLE), the name of the Queue/Topic
ConnectionFactory, hostname, database SID, port number, JDBC driver
(thin or oci8) and factory type (queue or topic).
After the Connection Factory objects have been registered in LDAP by a JMS
administrator, they can be looked up by using JNDI
Example
Lets say the JMS administrator wants to register a order entry queue connection
factory, oe_queue_factory. In LDAP, it can be registered as follows:
public static void register_Factory_in_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");
/* register queue connection factory for database "aqdb", host "sun-123",
port 5521, driver "thin" */
AQjmsFactory.registerConnectionFactory(env, "oe_queue_factory", "sun-123",
"aqdb", 5521, "thin", "queue");
}
Creating Applications Using JMS 12-7