XmlBlaster Logo



XmlBlaster Logo

Type NEW
Priority MIDDLE
Topic XmlBlaster has an advanced queuing facility. Among others one tested persistence layer is offered by communicating with an oracle database.

The generic plugin for jdbc based queues has been tested against Oracle 8.1.6, Oracle 9.20 i and 10g ( on Linux and on HP-UX (11.0). 8.1.6 has been tested with the jdbc Driver of 10g with jdk1.4 on Linux and HP-UX and with jdk1.5 on Linux.

Oracle is available on http://www.oracle.com where you can find all necessary information and instructions on how to make Oracle run.

Once you have a running oracle database you can configure xmlBlaster to make it run against it. Before you need to download the jdbc driver (you need two files for jdk1.3 : the classes12.zip nls_charset12.zip and for jdk1.4 and higher you need ojdbc14.jar files which you can download them from http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html. You must put these files in the CLASSPATH (for example you can put them into $XMLBLASTER_HOME/lib and add them to the CLASSPATH.

These are example QoS of subscribe() invocations:
   <queue maxEntriesCache='1000' maxBytesCache='4000'  maxEntries='10000' maxBytes='1000000000' onOverflow='deadMessage'/>

These parameters allow to configure a cache queue running with postgres

Property Default Description Hot Impl
QueuePlugin[CACHE][1.0] org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin specifies the cache implementing class to be used yes yes
queue/maxEntries 1000 specifies the maximum number of entries allowed in this queue yes yes
queue/maxBytes 10485760 (10MB) specifies the maximum total size allowed in this queue yes yes
queue/persistent/url jdbc:oracle:thin:@develop:1521:TEST the url which specifies where to find the DB. yes yes
queue/persistent/user xmlblaster The db user under which to run yes yes
queue/persistent/password secret The password used together with the user 'xmlblaster' yes yes
Additionally the configuration parameters for the ram queue and the jdbc queue must be defined.

NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details.
Columns named Impl tells you if the feature is implemented.
Columns named Hot tells you if the configuration is changeable in hot operation.

See API org.xmlBlaster.util.queue.I_Queue
See API org.xmlBlaster.util.queue.jdbc.CacheQueuePlugin
See API org.xmlBlaster.util.queue.QueuePluginManager
See API org.xmlBlaster.util.queue.I_QueueEntry
See API org.xmlBlaster.util.qos.storage.QueuePropertyBase
See API org.xmlBlaster.util.I_Plugin
See API org.xmlBlaster.util.Global
See REQ queue
See TEST org.xmlBlaster.test.classtest.queue.I_QueueTest
See TEST org.xmlBlaster.test.classtest.queue.JdbcQueueTest
See TEST org.xmlBlaster.test.classtest.queue.CacheQueueTest

This page is generated from the requirement XML file xmlBlaster/doc/requirements/queue.jdbc.oracle.xml

Back to overview