Message Queue supports both file-based and JDBC-based persistence modules. The broker property imq.persist.store (Table 17–4) specifies which module to use. The following sections describe the broker configuration properties for the two modules.
Table 17–4 Global Broker Persistence Property
Table 17–5 lists the broker properties related to file-based persistence.
Table 17–5 Broker Properties for File-Based Persistence
Table 17–6 lists the file-based persistence properties for the transaction logging mechanism introduced in Message Queue 4.4 Update 1.
Table 17–6 Broker Properties for File-Based Persistence Using the Transaction Logging Mechanism
Property |
Type |
Default Value |
Description |
---|---|---|---|
Boolean |
false |
Enables the transaction logging mechanism introduced in Message Queue 4.4 Update 1. For information about this mechanism, see Optimizing File-Based Transaction Persistence. |
|
Boolean |
false |
This property is applicable only if imq.persist.file.newTxnLog.enabled is true. Can improve performance if imq.persist.file.sync.enabled is true and the number of concurrent transactions being processed is high:
|
|
Boolean |
false |
This property is applicable only if imq.persist.file.newTxnLog.enabled is true. Overrides the behavior for persisting non-transacted messages (as defined by the imq.persist.file.sync.enabled property):
|
|
Boolean |
false |
This property is applicable only if imq.persist.file.newTxnLog.enabled is true. Overrides the behavior for persisting non-transacted message acknowledgements (as defined by the imq.persist.file.sync.enabled property):
|
Table 17–7 lists the broker properties related to JDBC-based persistence. The first of these properties, imq.persist.jdbc.dbVendor, identifies the database vendor being used for the broker’s persistent data store; all of the remaining properties are qualified by this vendor name.
Table 17–7 Broker Properties for JDBC-Based Persistence