WebSphere Application Server Version 6.1.x Feature Pack for Web Services
Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS
Learning about service integration buses
Use these topics to understand how you can use service integration
buses to allow applications to exchange messages:
About this task
Subtopics
Service integration buses
A service integration bus is a group of one or more
application servers or server clusters in
a WebSphere Application
Server cell that cooperate to provide asynchronous messaging services. The
application servers or server clusters in
a bus are known as bus members. WebSphere MQ servers
can also be bus members so that messages can be written to, and read from,
WebSphere MQ queues.
Bus members The
members of a service integration bus can be application servers, WebSphere MQ
servers, or server clusters. Bus members that are application servers or server clusters contain messaging engines,
which are the application server components that provide asynchronous messaging
services.
Messaging engines
A messaging engine is
a server component that provides the core messaging function of a service
integration bus. A messaging engine manages
bus resources and allows applications to communicate with the bus.
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 you can use to
specify how reliable message delivery will be. When you configure reliability
levels, you need to consider the requirements of your system. For example,
if you want messages to be delivered under any circumstances, you can set
assured delivery, and you can specify how the system will handle a large amount
of transactions.
Message ordering
Messages produced by a single producer to a single destination
will be seen by a consumer in that destination in the same order as they were
produced. However, certain events, such as system failures, can disrupt this
order. Message ordering allows you to prevent this order being changed.
Bus topologies
You can connect buses in different ways depending on your requirements.
For example, you can link messaging engines to distribute message workload,
and to provide system availability in the event of system failure.
Security considerations for service integration buses
There are a number of considerations that apply to service integration
buses. Messaging security ensures that users are authenticated, resources
are protected by security checks and messages are secure when they are in
transit.
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.