• Navigate to JMS resources in system modules
• Navigate to JMS resources in an application module

1. To manage messages at destnation startup, select:

   Pause Message Production At Startup -- Specifies whether new message production is paused on a destination at startup..

   Pause Message Consumption At Startup -- Specifies whether consumption is paused on a destination at startup.

   Pause Message Insertion At Startup -- Specifies whether new message insertion is paused on a destination at startup.

2. If you are using the Unit-of-Order feature:

   In Auto-generate Unit-of-Order Name, specify whether you want the system to create a system-generated unit- of-order name that is statistically unique for this distributed queue. Any message landing on this distributed queue that does not already belong to a unit-of-order is automatically assigned with this default unit-of-order name.

   In Unit-of-Order Routing, specify how the distributed queue members are selected as the destination for a message. If set to Hash, the producer computes the queue member. If set to Path Service, the configured Path Service determines the queue member.

3. In Attach Sender Credential, specify whether messages landing on this distributed queue member should attach the credential of the sending user by selecting either: Supports, which sets the JMSXUserID property with the security principal of the sending user if requested; Never, which never sets the JMSXUserID property with the security principal of the sending user; Always, which always sets the JMSXUserID property with the security principal of the sending user.
4. In Create Destination Identifier, specify a reference name for a member of a distributed destination that provides a way to lookup that destination using createQueue. See How to Lookup a Destination.
5. In SAF Export Policy, specify whether a user can send messages to this distributed queue using the Store-and-Forward service.
6. In Messaging Performance Preference, specify how long the distributed queue member should wait (if at all) before creating full batches of available messages for delivery to consumers. The maximum message count of a full batch is controlled by the JMS connection factory's Message Maximum per Session setting.

   Do Not Batch Messages -- Available messages are promptly delivered to consumers.

   Batch Messages Without Waiting -- (default) Less-than-full batches are immediately delivered with available messages.

   Low Waiting Threshold for Message Batching -- Wait briefly before less-than-full batches are delivered with available messages.

   Medium Waiting Threshold for Message Batching -- Wait longer before less-than-full batches are delivered with available messages.

   High Waiting Threshold for Message Batching -- Wait even longer before less-than-full batches are delivered with available messages.

7. If you are using the Unit-of-Work feature:

   In Unit-of-Work (UOW) Message Handling Policy, specify whether the UOW feature is enabled for this distributed queue member. A UOW is a set of messages that are processed as a single unit. Pass-Through - by default, this distributed queue member does not treat messages as part of a UOW. Single Message Delivery - this setting should only be selected if UOW consumers are receiving messages on this distributed queue member. When selected, UOW messages are formed into a list and are consumed as an ObjectMessage containing the list.

   In Expiration Time for Incomplete UOW Messages, specify the maximum amount of time before undelivered messages in an incomplete UOW are expired. Such messages will then follow the distributed queue member's expiration policy defined for undeliverable messages.

   Note: An error destination for UOW messages cannot be configured to use the Single Message Delivery value. See Uniform distributed queues - configure delivery failure parameters.

For more information about these fields, see Configuration Options.

• Save changes to JMS resources in system modules
• Save changes to JMS resources in an application module