NonStop Server Guide for BEA WebLogic Server 8.1

HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001

7-1

Configuring JDBC Stores for JMS

The WebLogic Java Messaging Service (JMS) Server can be configured to use a JMS

JDBC store when the underlying JDBC connection pool uses NonStop SQL/MX 2.0

with ANSI tables as the database.

The JMS database contains two system tables (generically called JMSState and

JMSStore) that are generated automatically and are used internally by each JMS

server. Because the JMSStore table has a column defined with a BLOB data type, a

special table is used by the JDBC/MX driver to store the BLOB data. Be aware of the

following situations regarding this special table:

•

When using a JMS Server in a WebLogic Server domain, you must pre-create this

table before you start WebLogic Server. To pre-create the table, use the

JdbcMxLobAdmin utility supplied with the JDBC/MX driver. The JDBC Driver for

SQL/MX Programmer’s Reference Manual describes how to do this.

•

You must identify the name of the BLOB table to the JDBC/MX driver by specifying

the following in the JAVA_OPTIONS environment variable:

-Djdbcmx.blobTableName=catalog.schema.table-name

where catalog is your catalog, schema is your schema, and table-name is the

name you gave the table.

•

If your application runs in a cluster, you must specify the prefix name for

JMSDBStore to uniquely identify the tables used by a particular JMS Server. The

prefix should contain the catalog name, the schema name, and a unique identifier.

JMS prepends the prefix to the generic table name to form a valid table name.

Specifying the prefix using the following format results in a valid table name:

[catalog.] [schema.] unique-identifier

where catalog is the catalog used by the application, schema is the schema

used by the application, and unique-identifier is any value you choose.

For example, specifying a prefix such as mycat.myschema.s1 causes JMS to

create tables named mycat.myschema.s1JMState and

mycat.myschema.s1JMStore.

•

Because JDBC/MX stores BLOB data for the JMSStore table in the special BLOB

table, you must create TRIGGERs to delete the BLOB data from the BLOB table

when the BLOB data is deleted or changed in the base JMSStore table. Use the

Note. If you specify -Djdbcmx.catalog=catalog and -Djdbcmx.schema=schema in

the JAVA_OPTIONS environment variable, you do not need to specify the catalog or

schema.