-->
edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Uniform distributed

Uniform distributed topics - configure advanced parameters


After you create a uniform distributed topic, you can define advanced property values, such as specifying unit-of-order parameters and attaching the credentials of message senders.

To configure advanced values for a distributed topic:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

  2. In the Administration Console, navigate to the uniform distributed topic resource that you want to configure:

  3. On the Configuration: General page, click the Advanced button.

    1. 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 topic. Any message landing on this distributed topic 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 topic members are selected as the destination for a message. If set to Hash, the producer computes the topic member. If set to Path Service, the configured Path Service determines the topic member.

    2. In Attach Sender Credential, specify whether messages landing on this uniform distributed topic 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.

    3. In SAF Export Policy, specify whether a user can send messages to this distributed topic using the Store-and-Forward service.

    4. In Messaging Performance Preference, specify how long the distributed topic 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.

    5. 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 topic member. A UOW is a set of messages that are processed as a single unit. Pass-Through - by default, this distributed topic 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 topic 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 topic 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 topics - configure delivery failure parameters.

    For more information about these fields, see Configuration Options.

  4. Save your changes:

  5. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).
} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i