The server and bus environment of WebSphere ESB is
built on the service integration technologies of the underlying WebSphere Application Server.
Why and when to perform this task
The service integration functionality within WebSphere Application Server provides
a highly-flexible messaging system that supports a service-oriented architecture
(SOA) with a wide spectrum of quality of service options, supported protocols,
and messaging patterns. It supports both message-oriented and service-oriented
applications.
This messaging system is based on the concept of a
service
integration bus, which combines the messaging fabric and service-oriented
capabilities:
- A service-oriented infrastructure to support application description,
deployment, and invocation using the service-oriented architecture.
- Reliable message transport capability
- Both tightly and loosely coupled communications options
- Intermediary logic (mediations) to intelligently adapt message
flow in the network
- Implementation of relevant Web Services standards
You can configure service integration in a variety of different
ways; for example, to tailor the functionality to meet specific messaging
needs without needing specialized messaging point products.
Within WebSphere
Application Server, service integration provides:
- The default messaging provider as a J2EE 1.4 compliant JMS provider, fully
integrated with Application Server, supporting multi-server configurations,
and inter-operating with WebSphere MQ.
- The Service Integration Bus, which provides the first-class infrastructure
for Web Services integration of applications by leveraging the service-oriented
architecture based on Web Services standardization.
- Support for the Web services gateway, which provides you with a single
point of control, access and validation of Web service requests, and allows
you to control which Web services are available to different groups of Web
service users.
- The messaging infrastructure for On Demand Computing.
For more information about what is provided by service integration
technologies, see the following WebSphere Application Server topics:
Alternatives for this task
- Service
integration buses
These topics provide information about service
integration buses, which support applications using message-based and
service-oriented architectures, including those using the Java Message Service
(JMS) interfaces of the default messaging provider.
- Messaging
engines
These topics provide information about messaging
engines, which provide the processing function on a service integration
bus.
- Data
stores
Use this task to obtain information about data
stores.
- Bus
destinations
This topic is the entry-point into a set
of topics about bus destinations within a service integration
bus, to which applications can attach as producers, consumers, or both to
exchange messages.
- Mediations
These topics provide information about mediations, which are used
for applications deployed on to
change how messages are handled at destinations on a service integration bus.
- Using
the default messaging provider
This topic is the entry-point
into a set of topics about enabling WebSphere applications to use messaging
resources provided by the default messaging provider.
- Interoperating
with WebSphere MQ
These topics introduce how to exchange
messages with a WebSphere MQ network using the WebSphere MQ link
- Security
These topics provide information about security in service integration
technologies.
- High
availability of service integration technologies
These
topics provide information about high availability of service integration
technologies.
- Enabling
Web services through service integration technologies
- Service
integration topologies
This topic provides information
about the service integration topologies that you can configure. A service
integration topology can range from a single host running two connected applications
to a globally-dispersed set of hundreds or thousands of communicating applications
running over the bus.