Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

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.

MBean Attribute:
WebLogicMBean.Name

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

Destination Keys

The list of potential destination keys for sorting messages that arrive on destinations that use this JMS template.

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
Pause Message Production At Startup

Specifies whether new message production on destinations that use this template is paused on at server startup.

  • false

    Paused message production at server startup is disabled on this template.

  • true

    Paused message production at server startup is enabled on this template.

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

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

Pause Message Consumption At Startup

Specifies whether message consumption is paused on destinations that use this template at server startup.

  • false

    Paused message consumption at server startup is disabled on this template.

  • true

    Paused message consumption at server startup is enabled on this template.

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

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

Pause Message Insertion At Startup

Specifies whether new message insertion is paused on destinations that use this template at server startup.

  • false

    Paused message insertion at server startup is disabled on this template.

  • true

    Paused message insertion at server startup is enabled on this template.

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

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

Auto-generate Unit-of-Order Name

Specifies whether WebLogic Server creates a system-generated unit-of-order name based on the domain, JMS server, and destination name. Any message arriving at this destination that does not already belong to a unit-of-order is assigned this default name.

This field is recommended for advanced use. Generally, it is recommended to set a message unit-of-order using application calls or connection factory configuration. When relying on a destination default unit order to enforce ordering with adistributed destination, the application must be aware that unit-of-order routing doesn't apply. Instead the application must specifically ensure that any particular set of messages that must be processed in order are all sent to the same specific member destination even in the event of process failures or service migration.

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

Attach Sender Credential

Specifies whether messages landing on destinations that use this template should attach the credential of the sending user.

  • Supports

    The JMSXUserID property is 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".

  • Never

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

  • Always

    The JMSXUserID property is always 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 destinations that use this template using Store-and-Forward.

  • All

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

  • None

    Remote users cannot send messages to destinations 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

Controls how long destinations that use this template are willing to wait to create full batches of available messages (if at all) for delivery to consumers. At the minimum value, batching is disabled; at the default value, less-than-full batches will not wait and are delivered immediately with currently available messages; tuning higher than the default value controls the maximum wait time for additional messages before less-than-full batches are delivered to consumers.

The maximum message count of a full batch is controlled by the JMS connection factory's MessagesMaximum setting.

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

Minimum value: 0

Maximum value: 100

Unit-of-Work (UOW) Message Handling Policy

Specifies whether the Unit-of-Work (UOW) feature is enabled for destinations that use this template. A UOW is a set of messages that are processed as a single unit.

  • Pass-Through

    By default, destinations that use this template do not treat messages as part of a UOW.

  • Single Message Delivery

    This value should only be selected if UOW consumers are receiving messages on destinations that use this template. When selected, UOW messages are formed into a list and are consumed as an ObjectMessage containing the list.

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

Expiration Time For Incomplete UOW Messages

Specifies the maximum amount of time, in milliseconds, before undelivered messages in an incomplete UOW are expired. Such messages will then follow the template's expiration policy defined for undeliverable messages.

Note: A template's error destination for UOW messages cannot be configured to use the Single Message Delivery value.

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

Related Tasks

Related Topics


Back to Top