Unregister a Queue/Topic Connection Factory in LDAP through LDAP

Figure 13-9 Use Case Diagram: Unregister a Queue/Topic Connection Factory in LDAP through LDAP

Text description of the illustration adq13jad33.gif

Purpose

Register a queue/topic connection factory in LDAP.

Usage Notes

unregisterConnectionFactory is a static method. To successfully unregister the connection factory, the hashtable passed to unregisterConnectionFactory 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).

Syntax

See Java (JDBC): Oracle9i Supplied Java Packages Reference, oracle.jms, AQjmsFactory.unregisterConnectionFactory.

Example

String               url;
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");
env.put(Context.SECURITY_CREDENTIALS, "welcome");
url = "jdbc:oracle:thin:@sun-123:1521:db1";
AQjmsFactory.unregisterConnectionFactory(env, "queue_conn1");