WebSphere topic settings

Use this panel to view or change the configuration properties of the selected topic destination for use with the embedded WebSphere JMS provider.

A topic destination is used to configure the properties of a JMS topic for the associated JMS provider. Connections to the topic are created by the associated topic connection factory. A topic for use with the embedded WebSphere JMS provider has the following properties.

To view this administrative console page, click Resources-> WebSphere JMS Provider-> (In content pane, under Additional Properties) WebSphere Topic destinations-> destination_name

 

Configuration tab

Scope Level to which this resource definition is visible -- the cell, node, or server level.

Resources such as JMS Providers, Namespace bindings, or shared libraries can be defined at multiple scopes, with resources defined at more specific scopes overriding duplicates which are defined at more general scopes.

Note that no matter what the scope of a defined resource, the resource's properties only apply at an individual server level. For example, if you define the scope of a data source at the Cell level, all users in that Cell can look up and use that data source, which is unique within that Cell. However, resource property settings are local to each server in the Cell. For example, if you set Max Connections to 10, then each server in that Cell can have 10 connections.

Cell The most general scope. Resources defined at the Cell scope are visible from all Nodes and servers, unless they are overridden. To view resources defined in the cell scope, do not specify a server or a node name in the scope selection form.

Node The default scope for most resource types. Resources defined at the Node scope override any duplicates defined at the Cell scope and are visible to all servers on the same node, unless they are overridden at a server scope on that node. To view resources defined in a node scope, do not specify a server, but select a node name in the scope selection form.

Server The most specific scope for defining resources. Resources defined at the Server scope override any duplicate resource definitions defined at the Cell scope or parent Node scope and are visible only to a specific server. To view resources defined in a server scope, specify a server name as well as a node name in the scope selection form.

When resources are created, they are always created into the current scope selected in the panel. To view resources in other scopes, specify a different node or server in the scope selection form.

Data type String

Name The name by which the topic is known for administrative purposes within IBM WAS.

Data type String

JNDI name The JNDI name that is used to bind the topic into the application server's name space.

As a convention, use the fully qualified JNDI name; for example, in the form jms/Name, where Name is the logical name of the resource.

This name is used to link the platform binding information. The binding associates the resources defined by the deployment descriptor of the module to the actual (physical) resources bound into JNDI by the platform.

Data type String

Description A description of the topic, for administrative purposes within IBM WAS.

Data type String
Default Null

Category A category used to classify or group this topic, for your IBM WebSphere Application Server administrative records.

Data type String

Topic The name of the topic as defined to the JMS provider.

Data type String
Default Null
Range The topic value can be dot notation and include wildcard characters.

Persistence Whether all messages sent to the destination are persistent, non-persistent, or have their persistence defined by the application

Data type Enum
Default APPLICATION DEFINED
Range

APPLICATION DEFINED Messages on the destination have their persistence defined by the application that put them onto the queue.

NON-PERSISTENT Messages on the destination are not persistent.

PERSISTENT Messages on the destination are persistent.

QUEUE DEFINED [WebSphere MQ destination only] Messages on the destination have their persistence defined by the WebSphere MQ queue definition properties.

Priority Whether the message priority for this destination is defined by the application or the Specified priority property

Data type Enum
Units Not applicable
Default APPLICATION DEFINED
Range

APPLICATION DEFINED The priority of messages on this destination is defined by the application that put them onto the destination.

QUEUE DEFINED [WebSphere MQ destination only] Messages on the destination have their persistence defined by the WebSphere MQ queue definition properties.

SPECIFIED The priority of messages on this destination is defined by the Specified priority property.If you select this option, define a priority on the Specified priority property.

Specified priority If the Priority property is set to Specified, type here the message priority for this queue, in the range 0 (lowest) through 9 (highest)

If the Priority property is set to Specified, messages sent to this queue have the priority value specified by this property.

Data type Integer
Units Message priority level
Default 0
Range 0 (lowest priority) through 9 (highest priority)

Expiry Whether the expiry timeout for this queue is defined by the application or the Specified expiry property, or messages on the queue never expire (have an unlimited expiry timeout)

Data type Enum
Units Not applicable
Default APPLICATION DEFINED
Range

APPLICATION DEFINED The expiry timeout for messages on this queue is defined by the application that put them onto the queue.

UNLIMITED Messages on this queue have no expiry timeout, so those messages never expire.

SPECIFIED The expiry timeout for messages on this queue is defined by the Specified expiry property.If you select this option, define a timeout on the Specified expiry property.

Specified expiry If the Expiry timeout property is set to Specified, type here the number of milliseconds (greater than 0) after which messages on this queue expire

Data type Integer
Units Milliseconds
Default 0
Range Greater than or equal to 0

  • 0 indicates that messages never timeout

  • Other values are an integer number of milliseconds