page, click the Advanced button.
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 queue. Any message landing on this
queue that does not already belong to a unit-of-order is
automatically assigned this default unit-of-order name.
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
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 queue can
have both a local and global JNDI name.
Create Destination Identifier, enter a
unique queue identifier name when using the
QueueSession.createQueue API defined in the JMS
Specification. This name must be unique within the scope of the
JMS server to which this queue is targeted; however, it does not
need to be unique within the scope of a JMS module. Therefore, two
queues in the same module can have the same destination identifier
as long as those queues are targeted to different JMS
SAF Export Policy, specify whether a user
can send messages to this queue using the Store-and-Forward
Messaging Performance Preference, specify
how you want this queue to perform in regards to emphasizing
message latency or message throughput.