Configuring alias destination properties

Use this task to browse or change the configuration properties of an alias destination on a service integration bus. An alias destination maps a bus name and destination name (identifier) to a target where the bus name, or the destination name, or both, are different. Any alias destination properties that you set override the destination defaults.

1. In the navigation pane, click Service integration -> Buses.
2. In the content pane, click the name of the bus on which the alias destination was created.
3. In the content pane, under Destination resources, click Destinations.
   A list of existing bus destinations is displayed.
4. Select the alias destination that you want to configure.
5. You can view or change the following alias destination properties.

   Description

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

   Target identifier

   The name of the destination for which this is an alias.

   Target bus

   The name of the bus on which the destination for which this is an alias exists.

   Use all target queue points

   This property is displayed only if the destination that the Target identifier and Target bus properties identifies has multiple queue points configured (that is, the destination is on a cluster bus member with multiple messaging engines) and the Target bus is the local bus.Whether to use all target queue points indicates whether all the queue points of the target queue can be used, including any queue points created after the alias is configured. When selected, the Target queue points menu is disabled.

   Unselected queue points

   A list of the queue points that are not addressable by the alias definition. The list is generated from the complete list of queue points for this queue. This list is enabled only when Use all target queue points is unchecked.

   Selected queue points

   A list of the queue points that are addressable by the alias definition. This list is enabled only when Use all target queue points is unchecked.

6. You can change the following alias destination properties to suit your needs. These values will override the destination defaults.

   Enable producers to override default reliability

   Controls the quality of service for message flows between producers and the destination. Select this option to use the quality of service specified by producers instead of the quality defined for the destination.

   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 might also be discarded if a connection used to send them becomes unavailable or as a result of constrained system resources.

   Express nonpersistent

   Messages are discarded when a messaging engine stops or fails. Messages might 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 might be discarded when a messaging engine fails.

   Assured persistent

   Messages are not discarded.

   Note: Higher levels of reliability have higher impacts on performance.

   For more information about service integration reliability levels, see Message reliability levels - JMS delivery mode and service integration quality of service.

   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

   Express nonpersistent

   Reliable nonpersistent

   Reliable persistent

   Assured persistent

   For more information about service integration reliability levels, see Message reliability levels - JMS delivery mode and service integration quality of service.

   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.

   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.

   Reply destination

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

   Reply destination bus

   The bus on which the reply destination exists.

   Default forward routing path

   The value to which a message's forward routing path will be set if the message contains no forward routing path. This identifies a sequential list of intermediary bus destinations that messages must pass through to reach a target bus destination. The format of the field is a list of line-delimited bus destinations specified as bus:name.

   Delegate authorization check to target destination

   Indicates which destination access role is checked when a user accesses the alias destination. When this option is selected, the destination access role of the target destination is checked. When this option is not selected, the destination access role of the alias destination is checked.

   Include an RFH2 message header when sending messages to WebSphere MQ

   Indicates whether messages sent to IBM MQ include an RFH2 header. The RFH2 header stores additional information to that which is stored in theIBM MQ message header. This property applies when the target bus is an IBM MQ queue manager.

7. Click OK.
8. Save your changes to the master configuration.