bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JMS Server --> Configuration --> General

Tasks Additional Documentation Attributes

Overview

This tab defines general configuration attributes for an instance of a JMS server. A JMS server manages connections and message requests on behalf of clients. You must first configure a JMS server before you can configure any destinations or consumers.

Tasks

Create a JMS Server

Clone a JMS Server

Delete a JMS Server

Assign a JMS Server

Additional Documentation

(Requires an Internet connection.)

"Managing JMS"in the Administration Guide

"Managing WebLogic JMS" in Programming WebLogic JMS

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Name | The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. MBean: weblogic.management. configuration. JMSServerMBean Attribute: Name | Configurable: yes Readable: yes Writable: yes
Store | The persistent store (either a disk-based file or a JDBC-accessible database) for this JMS server, which will be used as a physical repository for storing persistent message data. This store must not be the same as the paging store, or the same as the store for any other JMS server. MBean: weblogic.management. configuration. JMSServerMBean Attribute: Store |
Paging Store | The name of the paging store for this JMS server, which is a dedicated JMS file store where message bodies can be temporarily paged out when the JMS server's message load reaches a specified threshold--if paging is enabled on the Thresholds & Quotas tab. The paging store must not be the same as the non-paging store, or the same as the store for any other JMS server. MBean: weblogic.management. configuration. JMSServerMBean Attribute: PagingStore |
Temporary Template | The temporary template for the JMS server. The name of an existing JMS template used by JMS applications to create all temporary destinations (queues and topcis). The attribute values for a temporary destination are derived from this JMS template. If provided as part of the template, the Store attribute values are ignored because temporary destinations do not support persistent messaging. Note:If this attribute is set to none, attempts to create a temporary destination will fail. MBean: weblogic.management. configuration. JMSServerMBean Attribute: TemporaryTemplate | Default: null Configurable: yes Readable: yes Writable: yes