Advanced Queuing - Oracle

General Features of JMS
((AQjmsDestination)topic).schedulePropagation(t_sess, "dba", null,
null, null, null);
/*
some processing done here
*/
/* Unschedule propagation */
((AQjmsDestination)topic).unschedulePropagation(t_sess, "dba");
/* stop the topic */
((AQjmsDestination)topic).stop(t_sess, true, true, true);
/* drop topic */
((AQjmsDestination)topic).drop(t_sess);
/* drop queue table */
q_table.drop(true);
/* close session */
t_sess.close();
/* close connection */
t_conn.close();
}
catch(Exception ex)
{
System.out.println("Exception: " + ex);
}
}
System-Level Access Control in JMS
Oracle8i supports system-level access control for all queuing operations. This
feature allows an application designer or DBA to create users as queue
administrators. A queue/topic administrator can invoke all JMS interface (both
administration and operation) on any queue in the database. This simplifies the
administrative work since all administrative scripts for the queues in a database can
be managed under one schema. For more information, see "Oracle Enterprise
Manager Support" on page 4-8.
Example Scenario and Code
In the BooksOnLine (BOL) application, the DBA creates BOLADM, the BooksOnLine
Administrator account, as the queue administrator of the database. This allows
BOLADM to create, drop, manage, and monitor any queues in the database.If you
decide to create PL/SQL packages in the BOLADM schema that can be used by any
applications to enqueue or dequeue, then you should also grant BOLADM the
ENQUEUE_ANY and DEQUEUE_ANY system privilege.
12-16 Oracle9i Application Developer’s Guide - Advanced Queuing