Administration Console Online Help

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 topic resource that you want to configure:
   • Navigate to JMS Resources in System Modules
   • Navigate to JMS resources in an application module
3. On the Configuration: General page, click the Advanced button.
   1. If you are using the Unit-of-Order feature, in Unit-of-Order, specify whether you want the system to create a system-generated unit- of-order name that is statistically unique for this topic. Any message landing on this topic that does not already belong to a unit-of-order is automatically assigned this default unit-of-order name.
   2. In Attach Sender, specify whether messages landing on this destination 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 Local JNDI Name, enter a local JNDI name that will be bound on the local server instance, but which will not be globally propagated to the rest of the cluster. A topic can have both a local and global JNDI name.
   4. In Create Destination Identifier, enter a unique topic identifier name when using the topicSession.createtopic API defined in the JMS Specification. This name must be unique within the scope of the JMS server to which this topic is targeted; however, it does not need to be unique within the scope of a JMS module. Therefore, two topics in the same module can have the same destination identifier as long as those topics are targeted to different JMS servers.
   5. In SAF Export Policy, specify whether a user can send messages to this topic using the Store-and-Forward service.
   6. In Messaging Performance Preference, specify how you want this topic to perform in regards to emphasizing message latency or message throughput.

   For more information about these fields, see Configuration Options.

4. Save your changes:
   • Save Changes to JMS Resources in System Modules
   • Save changes to JMS resources in an application module
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).