Create an alias destination on a bus
We can create an alias destination on a service integration bus. An alias destination maps an alternative name for a queue destination or a topic space destination. Any alias destination properties set override the destination defaults.
An alias destination maps an alias bus name and destination name (identifier) to a target bus name and destination name where the bus name, or the destination name, or both, are different.
To define a new alias destination, use the console to complete the following steps.
- In the navigation pane, click Service integration -> Buses.
- 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. A list of any existing bus destinations is displayed.
- To create a destination, click New.
- On the Create new destination page, select Alias.
- Click Next.
- In the Identifier field, type the name of the destination for applications to use to refer to the alias destination.
- Specify the following properties for the destination:
- Bus
- The name of the bus for applications to use to refer to the alias destination. If we leave this field empty, the name of the local bus is used.
- Target identifier
- The identifier of the target destination that this alias destination represents.
If the alias destination targets 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 bus that hosts the target destination. This can be the local bus, a foreign service integration bus, or 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.
- 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.
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.
- 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 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.
If we do not want to override the security of the target destination, select this option.
- Click Next.
- On the Confirm alias destination creation page, review the summary of actions.
- To create the alias destination, click Finish.
- To change any of the destination properties, click Previous, then change the properties on the preceding pages.
- Save the changes to the master configuration.
What to do next
We can change properties or configure further properties of the alias destination. See Configure alias destination properties.To override security settings for the destination, see Administer destination roles.
Related concepts
Foreign destinations and alias destinations Interconnected bus configurations Use a scoped service integration bus alias destination to restrict messages to a single queue point
Related tasks
Configure exception destination processing for a bus destination Configure alias destination properties
Mapping destinations to and from WebSphere MQ queues, topics, and destinations WebSphere MQ naming restrictions
Related information:
Alias destination [Settings]