Skip navigation.

Administration Console Online Help

PreviousNextvertical dots separating previous/next from contents/index/pdfContents

JMS Templates: Configuration: General

Configuration Options     Advanced Configuration Options     Related Tasks     Related Topics

Use this page to define the general configuration of this JMS template, such as selecting a destination sort key for sorting messages as they arrive on destinations. .

The JMS template attributes are inherited by the JMS destinations that use them, with the exception of the Name attribute, which is valid for the JMS template only. You must explicitly define a unique name for all JMS destinations created from this JMS template.

Configuration Options

Name Description
Name

The name of this JMS template.

Destination Keys

The list of potential destination keys for sorting messages that arrive on the JMS template or destination.

The keys are ordered from most significant to least significant. If more than one key is specified, a key based on the JMSMessageID 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" (FIFO) for the sort order.

MBean Attribute (Does not apply to application modules):
TemplateBean.DestinationKeys

Changes take effect after you redeploy the module or restart the server.

Advanced Configuration Options

Name Description
Production Paused At Startup

Specifies whether new message production is paused on a destination at startup.

  • default

    If a JMS template is specified, then this value inherits the template's Production Paused At Startup value. If no JMS template is configured for the destination, then the Default value is equivalent to false.

  • false

    Production Paused is explicitly disabled for this destination.

  • true

    Production Paused is explicitly turned on for this destination.

MBean Attribute (Does not apply to application modules):
TemplateBean.ProductionPausedAtStartup

Changes take effect after you redeploy the module or restart the server.

Consumption Paused At Startup

Specifies whether consumption is paused on a destination at startup.

  • default

    - If a JMS template is specified, then this value inherits the template's Consumption Paused At Startup value. If no JMS template is configured for the destination, then the Default value is equivalent to false .

  • false

    - Consumption Paused is explicitly disabled for this destination.

  • true

    - Consumption Paused is explicitly turned on for this destination

MBean Attribute (Does not apply to application modules):
TemplateBean.ConsumptionPausedAtStartup

Changes take effect after you redeploy the module or restart the server.

Insertion Paused At Startup

Specifies whether new message insertion is paused on a destination at startup.

  • default

    - If a JMS template is specified, then this value inherits the template's Insertion Paused At Startup value. If no JMS template is configured for the destination, then the Default value is equivalent to false .

  • false

    - Insertion Paused is explicitly disabled for this destination.

  • true

    - Insertion Paused is explicitly turned on for this destination

MBean Attribute (Does not apply to application modules):
TemplateBean.InsertionPausedAtStartup

Changes take effect after you redeploy the module or restart the server.

Unit of Order

Specifies whether WebLogic Server creates a system-generated Unit- of-Order name that is statistically unique for a destination. Any message arriving at this destination that does not already belong to a unit-of-order is assigned this default unit-of-order name.

The initial use case is to replace the deprecated "ordered redelivery" feature.

MBean Attribute (Does not apply to application modules):
TemplateBean.DefaultUnitOfOrder

Attach Sender

Specifies whether messages landing on this destination should attach the credential of the sending user.

  • Supports

    - The JMSXUserID property will be set with the security principal of the sending user if requested. The sender can request its identity to be attached to its messages by using a ConnectionFactory with AttachJMSXUserID="true".

  • Always

    - The JMSXUserID property will always be set with the security principal of the sending user.

  • Never

    - The JMSXUserID property will never be set with the security principal of the sending user.

This property is dynamically configurable. A dynamic change will only affect messages received after the update has been made.

MBean Attribute (Does not apply to application modules):
TemplateBean.AttachSender

SAF Export Policy

Specifies whether a user can send messages to a destination using Store-and-Forward.

  • All

    All users can send messages to this destination using Store-and-Forward.

  • None

    Remote users can not send messages to a destination using Store-and-Forward.

This property is dynamically configurable. A dynamic change will only affect messages sent after the update has been made.

MBean Attribute (Does not apply to application modules):
TemplateBean.SafExportPolicy

Changes take effect after you redeploy the module or restart the server.

Messaging Performance Preference

Specifies the destination's peformance preference in regards to message latency or throughput. The lower the value, the more the destination will emphasize latency over throughput. Conversely, the higher the value, the more the destination will emphasize throughput over latency.

MBean Attribute (Does not apply to application modules):
TemplateBean.MessagingPerformancePreference

Minimum value: 0

Maximum value: 100

Related Tasks

Related Topics

 

Skip navigation bar   Back to Top