Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Default messaging provider topic [Settings]
A JMS topic is used as a destination for publish/subscribe messaging. Use topic destination administrative objects to manage JMS topics for the default messaging provider.
To view this page in the console, click one of the following paths:
- Resources -> JMS -> Topics -> topic_name
- Resources -> JMS -> JMS providers -> a_messaging_provider -> [Additional Properties] Topics > topic_name
Configuration tab
These property values are preserved even if the runtime environment is stopped then restarted.
General Properties
Scope
Highest topological level at which application servers can use this resource object.
Required No Data type String
Provider
Specifies a JMS provider, which enables asynchronous messaging based on the JMS. It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. JMS provider administrative objects are used to manage JMS resources for the associated JMS provider.
Required No Data type String
Name
The required display name for the resource.
Required Yes Data type String
JNDI name
The JNDI name for the resource.
As a convention, use a JNDI name of the form jms/Name, where Name is the logical name of the resource. For more information about the use of JNDI and its syntax, see the topic JNDI support in WAS.
Required Yes Data type String
Description
An optional description for the resource.
Required No Data type Text area
Topic name
The name of the topic that this JMS topic is assigned to, in the topic space defined by the Topic space property.
To specify a multi-level topic name, separate each level by a forward slash character (/); for example:
schools/eton/subjects/maths
Required No Data type String
Bus name
Name of bus hosting topic.
Required No Data type Custom
Topic space
The name of the topic space that contains the topic, on the service integration bus defined by the Bus name property
Type the name of a topic space that has been created on the service integration bus.
Required Yes Data type Custom
JMS delivery mode
The delivery mode for messages sent to this destination. This controls the persistence of messages on this destination.
Required No Data type drop-down list Range
Application
The persistence of messages on this topic is defined by the producing application.
Nonpersistent
All messages sent to this topic are treated as nonpersistent.
Persistent
All messages sent to this topic are treated as persistent.
Time to live
The default length of time in milliseconds from its dispatch time that a message sent to this destination should be kept by the system.
Messages are deleted after the specified time. If a value is not specified for this property, the time limit set by the producing application is used.
Required No Data type Long Range 0 through 574476389546486783 A value of 0 (zero) means that messages are kept indefinitely. The default for this property is null, which allows the application to determine the time to keep messages.
Message priority
The relative priority for messages sent to this destination, in the range 0 to 9, with 0 as the lowest priority and 9 as the highest priority.
If a value is not specified for this property, the message priority set by the producing application is used.
Required No Data type Integer Range 0 through 9 The message priority range is from 0 (lowest) through 9 (highest).
Read ahead
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Messages that are assigned to a consumer are locked on the server and cannot be consumed by any other consumers for that destination. Messages that are assigned to a consumer, but not consumed before that consumer is closed, are subsequently unlocked on the server and then available for receipt by other consumers.
This property overrides the value set by the Read ahead property on the JMS connection factory.
Required No Data type drop-down list Range
Enabled
The messaging provider preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests for this destination.
Disabled
The messaging provider does not preemptively assign messages to consumers for this destination.
Inherit from connection factory
Read ahead optimization is defined on the connection.
Related Items
Buses
A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
JMS topic resources and service integration
Configure a topic for the default messaging provider
Administrative console buttons
Administrative console preferences