JMSJDBCStore

 

 

---

Create a JMS JDBC Store

1. Click to expand the JMS node.

2. Click the JMS Stores node. The JMS Stores table displays in the right pane showing all the JMS JDBC stores.

3. Click the Create a new JMS JDBC Store text link. A dialog displays in the right pane showing the tabs associated with configuring a new JDBC store.

4. Enter values in the attribute fields.

5. Click Create to create a JDBC store instance with the name you specified in the Name field. The new instance is added under the JMS Stores node in the left pane.

 

---

Clone a JMS JDBC Store

1. Click to expand the JMS node.

2. Click the JMS Stores node. The JMS Stores table displays in the right pane showing all the JMS JDBC stores.

3. Click the Clone icon in the row of the JDBC store you want to clone. A dialog displays in the right pane showing the tabs associated with cloning a JDBC store.

4. Enter values in the attribute fields.

5. Click Create to create a JDBC store instance with the name you specified in the Name field. The new instance is added under the JMS Stores node in the left pane.

 

---

Delete a JMS JDBC Store

1. Click to expand the JMS node.

2. Click the JMS Stores node. The JMS Stores table displays in the right pane showing all the JMS file stores.

3. Click the Delete icon in the row of the JDBC store you want to delete. A dialog displays in the right pane prompting you to confirm your deletion request.

4. Click Yes to delete the JDBC store. The JDBC store icon under the JMS Stores node is deleted.

 

---

Configuration

General

Attribute	Description	Range of Values	Default Value
Name	Name of the JMS JDBC store. This attribute is not dynamically configurable.	Java identifier, unique within the JMSServer	MyJMSJDBC Store[-n]
Connection Pool	Name of the JDBC Connection Pool for this backing store. This attribute is not dynamically configurable.	Existing JDBC ConnectionPool name or none	none
Prefix Name	The prefix name of JMS tables in the backing store. Specifying unique prefixes allows multiple stores to exist in the same database. The prefix is prepended to table names when: The DBMS requires fully qualified names. You must differentiate between JMS tables for two WebLogic servers, enabling multiple tables to be stored on a single DBMS. The prefix should be specified using the following format and will result in a valid table name when prepended to the JMS table name: [[catalog.]schema.]prefix Note: No two JMS stores should be allowed to use the same database tables, as this will result in data corruption.	Valid table prefix for JMS tables	N/A

Notes

Attribute	Description	Range of Values	Default Value
Notes	This attribute provides a space for user-supplied information.	The value must be an alphanumeric string.	Null