WebSphere Application Server Network Deployment, Version 6.0.x
Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
Learning about service integration buses
Use these topics to learn about service integration buses:
Service integration buses
A service integration bus supports
applications using message-based and service-oriented architectures. A bus
is a group of one or more interconnected servers or server
clusters that have been added as members of the bus. Applications connect
to a bus at one of the messaging engines associated with its bus members.
Bus members
The members of a service integration bus are the application servers and server clusters within which messaging
engines for that bus can run.
Messaging engines
A messaging engine is
a server component that provides the core messaging functionality of a service
integration bus. A messaging engine manages
bus resources and provides a connection point for applications.
Bus destinations
A bus destination is a virtual location within a service integration bus, to
which applications attach as producers, consumers, or both to exchange messages.
Message reliability levels
Messages have a quality of service attribute that specifies the
reliability of message delivery. You can select a reliability to suit your
requirements for assured delivery, and system performance.
Message ordering
In general, messages produced by a single producer to a single
destination will be seen by a consumer to that destination in the same order
as they were produced. However there are certain events, such as system failures,
that can change the order of messages.
Bus topologies
Different service integration bus topologies can be used depending
on your requirements.
Foreign buses
A foreign bus is a representation of another service integration
bus, or a WebSphere MQ queue manager, with which an existing service integration
bus, or a WebSphere MQ queue manger, can exchange messages. The purpose of
a foreign bus is to extend the network of buses that can exchange messages.
Custom properties
Custom properties are used to set internal system configuration
properties.
Dynamic reloading of configuration files
With dynamic reloading of configuration files, any updates to the
configuration information are dynamically passed to the server, and therefore
made available to messaging engines whether or not they are started.