WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Topic space settings

A topic space is a location for publish/subscribe messaging.

In the administrative console page, to view this page click Service integration > Buses > [Content Pane] bus_name > [Destination resources] Destinations > [Content Pane] topicspace_name.

Related tasks
Creating a topic space for publish/subscribe messaging
Configuring bus destination properties
Related reference
Destinations administrative commands

Configuration tab

Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.

General properties

Identifier

The identifier by which this destination is known for administrative purposes.

Required No
Data type Text

UUID

The universal unique identifier assigned by the system to this destination for administrative purposes.

Required No
Data type Text

Type

Whether this bus destination is for a queue, topic space, or some other type of destination.

A topic space for publish/subscribe messaging.
Required No
Data type Text

Description

An optional description for the bus destination, for administrative purposes.

Required No
Data type Text area

Mediation

The name of the mediation that mediates this destination.

Required No
Data type Text

Default reliability

The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.

Required No
Data type Selection list
Range
Best effort nonpersistent
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.

For non-transactional JMS message-driven beans and MessageListeners that use a JMS destination configured on the default messaging provider, best-effort nonpersistent messages are not recoverable. In this case, if a message is unlocked because the message-driven bean or MessageListener threw an exception, then the message is not redelivered or sent to the exception destination because it was deleted from the message store when it was passed to the listener. If you require higher message reliability for non-transactional JMS message-driven beans and MessageListeners, configure a different option for the Maximum reliability property of the bus destination.

Express nonpersistent
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.

Reliable nonpersistent
Messages are discarded when a messaging engine stops or fails.

Reliable persistent
Messages may be discarded when a messaging engine fails.

Assured persistent
Messages are not discarded.

Maximum reliability

The maximum reliability of messages accepted by this destination.

Required No
Data type Selection list
Range
Best effort nonpersistent
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.

Express nonpersistent
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.

Reliable nonpersistent
Messages are discarded when a messaging engine stops or fails.

Reliable persistent
Messages may be discarded when a messaging engine fails.

Assured persistent
Messages are not discarded.

Enable producers to override default reliability

Select this option to enable producers to override the default reliability that is set on the destination.

Required No
Data type Check box

Default priority

The default priority assigned to messages sent to this destination when a priority has not been set by the producer.

Required No
Data type Integer
Range 0 (lowest) through 9 (high)

Maximum failed deliveries

The maximum number of failed attempts to process a message before the message is forwarded to the exception destination for the destination.

Required No
Data type Integer
Range 0 through 2147483647

Exception destination

The destination to which a message is forwarded by the system when it cannot be delivered to this destination.

Use this property to define what happens to any messages that cannot be delivered to this destination. By default, such messages are routed to the system default exception destination of the messaging engine that discovers the problem; _SYSTEM.Exception.Destination.engine_name.

If you want to messages to be sent to another exception destination, select Specify then type its name on this property. The exception destination must be a queue, on the same bus or a foreign bus, and must exist when the destination is created.

If you do not want undeliverable messages to be routed to an exception destination, select None.

Required No
Data type Text and Check box
Default System
Range
System
Default system exception destination
None
No exception destination is configured
Specify
Specify a named destination

Send allowed

Clear this option (setting it to false) to stop producers from being able to send messages to this destination.

Required No
Data type Check box
Range
Selected
Producers can send messages to this destination.

Cleared
Producers cannot send messages to this destination.

For a publication point, clearing this Send allowed property stops applications attached locally to the topic space from publishing messages. The send calls receive an exception, and the producer remains open.

Receive allowed

Clear this option (setting it to false) to prevent consumers from being able to receive messages from this destination.

Required No
Data type Check box
Range
Selected
Consumers can get messages from this destination.

Cleared
Consumers cannot get messages from this destination.

Any messages that have been published to the messaging engine for a publication point are stopped from proceeding either to local consumers or onwards to other messaging engines. Local consumers get the same exception as for a queue point.

Topic access check required

Whether or not authorization checks are required for access to topics.

When security is on, authorization checks are always performed at the topic space level. To add additional control, you can select this property to enable authorization checks at the topic level.
Required No
Data type Check box

Reply destination

The name of a destination to be appended to any non-empty reverse routing path of messages sent to this destination.

Required No
Data type Text

Reply destination bus

The bus on which the reply destination exists.

Required No
Data type Text

Additional properties

Context properties
Context information passed to the mediation.

Message points

Publication points
A publication point is created on each messaging engine in the bus when a publish/subscribe destination is created. The publication point on a messaging engine is used to hold messages published by applications connected to that messaging engine until they are delivered to subscribers.
Mediation points
The mediation points for the topic space. The locations in the messaging engine at which messages on the topic space are mediated.

Reference topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\sibresources\SIBTopicSpace_DetailForm.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)