Technical data

Configuring JMS
Administration Guide 17-15
n <prefix>JMSStore
n <prefix>JMSState
The prefix name uniquely identifies JMS tables in the persistent store. Specifying
unique prefixes allows multiple stores to exist in the same database. You configure the
prefix via the Administration Console when configuring the JDBC store. A prefix is
prepended to table names when the DBMS requires fully qualified names, or when you
must differentiate between JMS tables for two WebLogic Servers, enabling multiple
tables to be stored on a single DBMS.
Warning: No two JMS stores should be allowed to use the same database tables, as
this will result in data corruption.
Specify the prefix using the following format, which will result in a valid table name
when prepended to the JMS table name:
[[[catalog.]schema.]prefix]JMSStore
where catalog identifies the set of system tables being referenced by the DBMS and
schema translates to the ID of the table owner. For example, in a production database
the JMS administrator could maintain a unique table for the Sales department, as
follows:
[[[Production.]JMSAdmin.]Sales]JMSStore
Note: For some DBMS vendors, such as Oracle, there is no catalog to set or choose,
so this format simplifies to
[[schema.]prefix]. For more information, refer
to your DBMS documentation for instructions on how to write and use a
fully-qualified table name.
Recommended JDBC Connection Pool Settings for JMS Stores
WebLogic Server provides robust JDBC connection pools that can automatically
reconnect to failed databases after they come back online, without requiring you to
restart WebLogic Server. To take advantage of this capability, and make your use of
JMS JDBC stores more robust, configure the following attributes on the JDBC
connection pool associated with the JMS JDBC store:
TestConnectionsOnReserve=”true”
TestTableName=”[[[catalog.]schema.]prefix]JMSState”