JMS Template --> Configuration --> General

JMS Template --> Configuration --> General

Tasks Related Topics Attributes

Overview

This tab defines general configuration attributes for a JMS template, which provides an efficient means of defining multiple destinations with similar attribute settings:
The general configuration attributes are inherited by the destinations that use them. However, the Name attribute is not inherited by the destination; this name is valid for the JMS template only. You must explicitly define a unique name for all destinations.

Tasks

Creating a JMS Template

Related Topics

WebLogic JMS Fundamentals in Programming WebLogic JMS
Managing WebLogic JMS in Programming WebLogic JMS
Developing a WebLogic JMS Applicationin Programming WebLogic JMS

Attributes

Attribute Label

Description

Value Constraints
Name The name of this JMS template configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: Name

Destination Keys The sort ordering for messages that arrive on destinations based on this template.The keys are ordered from most significant to least significant. If more than one key is specified, a key based on the JMSMessageID property can only be the last key in the list. Note: If JMSMessageID is not defined in the key, it is implicitly assumed to be the last key and is set as "ascending" (first-in, first-out) for the sort order.MBean: weblogic.management.
configuration.
JMSTemplateMBeanAttribute: DestinationKey

Attribute Label	Description	Value Constraints
Name	The name of this JMS template configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: Name
Destination Keys	The sort ordering for messages that arrive on destinations based on this template.The keys are ordered from most significant to least significant. If more than one key is specified, a key based on the JMSMessageID property can only be the last key in the list. Note: If JMSMessageID is not defined in the key, it is implicitly assumed to be the last key and is set as "ascending" (first-in, first-out) for the sort order.MBean: weblogic.management. configuration. JMSTemplateMBeanAttribute: DestinationKey