Type	NEW
Priority	MIDDLE
Status	CLOSED

Topic	XmlBlaster has an advanced queuing facility. As the default persistence layer HSQLDB is used as an embedded java database.
Des cription	As default xmlBlaster comes with persistence switched on. The default database is HSQLDB which can be used in embedded mode. This means that there is no need to have an external database running. It runs in the same virtual machine as xmlBlaster. Configuration of the DB is therefore kept to an absolute minimum for default behaviour. If you want to deactivate persistence, or if you want to choose another database please look at the comments in the xmlBlaster.properties file (which normally resides in your home directory). Setup hsqldb Setup xmlBlaster.properties as described in the example section below
Example Java	This is a configuration example from xmlBlaster.properties: JdbcStorage[HSQLDatabaseEngine]=org.xmlBlaster.util.queue.jdbc.JdbcQueueCommonTablePlugin,\ url=jdbc:hsqldb:xmlblaster,\ user=sa,\ password=,\ connectionPoolSize=1,\ connectionBusyTimeout=90000,\ maxWaitingThreads=300,\ tableNamePrefix=XB_,\ entriesTableName=ENTRIES,\ dbAdmin=true StoragePlugin[JDBC][1.0]=${JdbcStorage[HSQLDatabaseEngine]} QueuePlugin[JDBC][1.0]=${JdbcStorage[HSQLDatabaseEngine]} JdbcDriver.mapping[HSQLDatabaseEngine]=\ string=VARCHAR,longint=BIGINT,int=INTEGER,blob=BINARY,\ boolean=CHAR
Configure	These parameters allow to configure a cache queue running with hsqldb Property Default Description Hot Impl QueuePlugin[CACHE][1.0] org.xmlBlaster.util.queue.cache.CacheQueueInterceptorPlugin specifies the cache implementing class to be used queue/maxEntries 1000 specifies the maximum number of entries allowed in this queue queue/maxBytes 10485760 (10MB) specifies the maximum total size allowed in this queue queue/persistent/url jdbc:hsqldb:xmlblaster the url which specifies where to find the DB. queue/persistent/user sa The db user under which to run queue/persistent/password The password used together with the user 'sa' 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	http://hsqldb.sourceforge.net/
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.hsqldb.xml

Back to overview