Use this task to create a new topic space for
publish/subscribe messaging.
Why and when to perform this task
To create a topic space,
you need to specify only a minimum set of required properties; you can change
these and other properties after you have completed this task.
To create
a topic space, use the administrative console to complete the following steps.
Steps for this task
- In the navigation pane, click
- In the content pane, click the name of the bus that is to provide
the publication points for
the topic space.
- In the content pane, under Additional Properties, click Destinations. This displays any existing destinations in the content pane.
- To create a topic space,
click New in the content pane.
- On the Create New Destination page, select the Topic
space option.
- Click Next.
- In the Identifier field, type the name
that you want to give the topic space for
administrative purposes.
- Optional: Specify the following properties for the topic space:
- Description
- An optional description of the topic space,
for administrative purposes.
- Maximum reliability
- The maximum reliability of messages accepted by this destination.
- 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.
- Click Next.
- On the Confirm Topic space creation page, review the summary of
actions.
- To create the topic space,
click Finish.
- If you want to change any of the properties that you have specified,
click Previous, then change the properties on the preceding
pages.
- Save your changes to the master configuration.
If you want to change properties of the
topic space,
see
Configuring bus destination properties.
By default,
messages that cannot be delivered to the topic space are
sent the default exception destination for the messaging engine that is publishing
the message. If you want to use a non-default exception destination for messages
that cannot be delivered to this topic space,
you must have already defined that exception destination. For more information
about configuring exception destinations, see Configuring an exception bus destination.
If the topic space is
to be used for JMS publish/subscribe messaging, specify the topic space identifier
on a JMS topic as described in Configuring a JMS topic, default messaging provider.