Technical data

17 Managing JMS
17-14 Administration Guide
Note: The JMS samples provided with your WebLogic Server distribution are set up
to work with the Cloudscape Java database. An evaluation version of
Cloudscape is included with WebLogic Server and a demoPool database is
provided.
If your existing JMS JDBC stores somehow become corrupted, you can regenerate
them using the
utils.Schema utility. For more information see, “JDBC Database
Utility” in Programming WebLogic JMS.
JMS JDBC Transactions
You cannot configure a transaction (XA) JDBC connection pool to be used with a JMS
JDBC store. JMS must use a JDBC connection pool that uses a non-
XAResource
driver (you cannot use an XA driver or a JTS driver). JMS does the XA support above
the JDBC driver.
This is because WebLogic JMS is its own resource manager. That is, JMS itself
implements the
XAResource and handles the transactions without depending on the
database (even when the messages are stored in the database). This means that
whenever you are using JMS and a database (even if it is the same database where the
JMS messages are stored), then it is two-phase commit transaction. For more
information about using transactions with WebLogic JMS, see “Using Transactions
with WebLogic JMS” in Programming WebLogic JMS.
From a performance perspective, you may boost your performance if the JDBC
connection pool used for the database work exists on the same WebLogic Server as the
JMS queue—the transaction will still be two-phase, but it will be handled with less
network overhead. Another performance boost might be achieved by using JMS file
stores rather than JMS JDBC stores.
JMS JDBC Security
Optionally, you can restrict the access control list (ACL) for the JDBC connection
pool. If you restrict this ACL, you still must include the WebLogic Server system user
and any user who sends JMS messages in the list. For more information on managing
WebLogic Server security, see “Managing Security” on page 14-1.
About JMS Store Table Prefixes
The JMS database contains two system tables that are generated automatically and are
used internally by JMS: