Use this task to create a new alias destination on a service
integration bus. The alias destination can be used to route messages
to a target destination in the same bus, or another (foreign) bus
(including across a WebSphere® MQ
link to a WebSphere MQ
queue). You can set its own destination properties which will override
the destination defaults.
About this task
To define a new alias destination, use the administrative
console to complete the following steps.
Procedure
- In the navigation pane, click .
- In the content pane, click the name of the bus on which
the alias destination is to be created.
- In the content pane, under Destination resources,
click Destinations. This displays
any existing destinations in the content pane.
- To create a new destination, click New in
the content pane.
- On the Create New Destination page, select Alias Destination.
- Click Next.
- In the Identifier field, type
the name that you want to give the alias destination for administrative
purposes.
- Specify the following properties for the destination:
- Bus
- The name of the bus used by applications when referring to the
alias destination. If you leave this field empty, the alias destination
is created on the local bus.
- Target identifier
- The identifier of the target destination that this alias destination
should route messages to.
If the alias destination is targeting
a queue provided by WebSphere MQ,
type the value as a concatenation of the queue name and the queue
manager name, queue_name@qmanager_name;
for example: Queue1@Qmgr2.
- Target bus
- The name of the service integration bus (or foreign bus) that
hosts the target destination. This can be the name of a foreign bus
that represents a WebSphere MQ
network. The default is the name specified for the Bus property.
- Optional: Specify the following properties
for the destination. These will override the destination defaults.
- Description
- An optional description of the destination, for administrative
purposes.
- Default reliability
- The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
- INHERIT
- Use the reliability configured on the target 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.
- Maximum reliability
- The maximum reliability of messages accepted by this destination.
Producers
cannot send messages to this destination with a reliability higher
than the value specified for this property.
- INHERIT
- Use the reliability configured on the target 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.
- Enable producers to override default reliability
- Select this option to enable producers to override the default reliability that is set on the destination.
- Send allowed
- Clear this option (setting it to false) to stop producers from being able to send messages to this destination..
- INHERIT
- Use the value configured on the target destination.
- TRUE
- Producers can send messages to this destination.
- FALSE
- Producers cannot send messages to this destination.
- Receive allowed
- Clear this option (setting it to false) to prevent consumers from being able to receive messages from this destination.
- INHERIT
- Use the value configured on the target destination.
- TRUE
- Consumers can receive messages from this destination.
- FALSE
- Consumers cannot receive messages from this destination.
- Default priority
- The default priority for messages sent to the target destination,
in the range 0 (lowest) through 9 (highest), or -1. The value -1 indicates
that messages should use the default priority defined on the target
destination. The default priority is used only if a message does not
specify its own priority.
- Click Next.
- On the Confirm Destination Creation page, review the summary
of actions.
- To create the alias destination , click Finish.
- If you want to change any of the destination properties, click Previous,
then change the properties on the preceding pages.
- Save your changes to the master configuration.