78 Patterns: Implementing Self-Service in an SOA Environment
Clients can connect into any messaging engine in the bus and send
messages to it. If the destination is assigned to a different messaging engine,
the messaging engine will route it to the correct messaging engine.
destination is an addressing point within a bus. A destination is assigned to
one bus member and, therefore, one or more messaging engines. Clients
send messages to a destination and the bus ensures that it is routed to the
correct localization on the bus. The following destination types are supported
by the service integration bus:
– Web service destinations
Web service destinations are a representation of an outbound Web service
in the bus. They are used as a placeholder for a port selection mediation.
– Port destinations
Port destinations are a representation of an outbound Web service port.
Sending a Web service request to a port destination will result in the target
Web service being invoked.
– Queue destinations
Queue destinations are destinations that are configured for point-to-point
– Topic space destinations
Topic space destinations are destinations that are configured for
– Alias destinations
Alias destinations are destinations that are configured to refer to another
destination. They provide an extra level of indirection for messaging
applications. An alias destination can also be used to override some of the
values specified on the target destination, such as default reliability and
maximum reliability. An alias destination can also refer to a destination on
a foreign bus. Foreign buses are discussed in “Foreign bus link” on
– Foreign destinations
Foreign destinations are not actual destinations within a service
integration bus, but they can be used override the default reliability and
maximum reliability properties of a destination that exists on a foreign bus.
Foreign buses are discussed in “Foreign bus link” on page 79.
Destinations can be mediated to provide advanced message formatting and