Use this panel to browse or change the configuration properties of the selected JMS topic destination for publish/subscribe messaging with WebSphere MQ as a messaging provider.
A WebSphere MQ topic destination is used to configure the properties of a JMS topic for WebSphere MQ as a messaging provider. Connections to the topic are created by the associated topic connection factory. To view this page, use the administrative console to complete the following steps:
Note:
The name by which the topic is known for administrative purposes within IBM WebSphere Application Server.
Data type | String |
The JNDI name that is used to bind the topic into the 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 |
A description of the topic, for administrative purposes within IBM WebSphere Application Server.
Data type | String |
Default | Null |
A category used to classify or group this topic, for your IBM WebSphere Application Server administrative records.
Data type | String |
Whether all messages sent to the destination are persistent, non-persistent, or have their persistence defined by the application
Whether the message priority for this destination is defined by the application or the Specified Priority property
Data type | Enum |
Default | APPLICATION DEFINED |
Range |
|
If the Priority property is set to Specified, type here the message priority for this destination, in the range 0 (lowest) through 9 (highest)
Data type | Integer |
Units | Message priority level |
Default | 0 |
Range | 0 (lowest priority) through 9 (highest priority) |
Whether the expiry timeout for this destination 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 |
Default | APPLICATION DEFINED |
Range |
|
If the Expiry Timeout property is set to Specified, type here the number of milliseconds (greater than 0) after which messages on this destination expire.
Data type | Integer |
Units | Milliseconds |
Default | 0 |
Range | Greater than or equal to 0
|
The name of the WebSphere MQ topic to which messages are sent.
Data type | String |
Range | Depends on the broker used. For details, see the documentation for your broker; for example the WebSphere MQ Event Broker library at http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/wsmqebv21.html. |
The coded character set identifier for use with WebSphere MQ.
This coded character set identifier (CCSID) must be one of the CCSIDs supported by WebSphere MQ.
Data type | String |
Units | Integer |
Default | Null |
Range | 1 through 65535 |
For more information about supported CCSIDs, and about converting between message data from one coded character set to another, see the WebSphere MQ System Administration and the WebSphere MQ Application Programming Reference books. These are available from the WebSphere MQ messaging multiplatform and platform-specific books Web pages; for example, at http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html, the IBM Publications Center, or from the WebSphere MQ collection kit, SK2T-0730.
Whether or not the destination should use native encoding (appropriate encoding values for the Java platform).
Data type | Check box |
Units | Not applicable |
Default | Cleared |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
If native encoding is not enabled, select whether integer encoding is normal or reversed.
Data type | Enum |
Default | NORMAL |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
If native encoding is not enabled, select whether decimal encoding is normal or reversed.
Data type | Enum |
Default | NORMAL |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
If native encoding is not enabled, select the type of floating point encoding.
Data type | Enum |
Default | IEEENORMAL |
Range |
For more information about encoding properties, see the WebSphere MQ Using Java document. |
Whether the receiving application is JMS-compliant or is a traditional WebSphere MQ application
Data type | Enum |
Default | JMS |
Range |
The name of the broker's queue from which durable subscription messages are retrieved
The subscriber specifies the name of the queue when it registers a subscription.
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
The name of the broker's queue from which durable subscription messages are retrieved for a ConnectionConsumer. This property applies only for use of the Web container.
Data type | String |
Default | Null |
Range | 1 through 48 ASCII characters |
Whether or not this topic destination uses multicast transport.
With multicast, messages are delivered to all consumers. This is useful in environments where there are a large number of clients that all want to receive the same messages, because with multicast only one copy of each message is sent. Multicast reduces the total amount of network traffic. Reliable multicast is standard multicast with a reliability layer added.
Data type | Enum |
Default | NOTUSED |
Range |
|
Configuration tab
The level to which this resource definition is visible to applications.
Resources such as messaging 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.
The scope displayed is for information only, and cannot be changed on this panel. If you want to browse or change this resource (or other resources) at a different scope, change the scope on the messaging provider settings panel, then click Apply , before clicking the link for the type of resource.
Data type | String |
Related tasks
Configuring a JMS topic connection factory, for WebSphere MQ