Scribd
Upload
22 views2 pages

SI Bus

The document discusses different messaging providers that can be used with an application server, including the default provider using a service integration bus, an IBM MQ provider, and a generic JMS provider. It also describes the service integration bus and its components.

Uploaded by

pmmanick
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
22 views2 pages

SI Bus

The document discusses different messaging providers that can be used with an application server, including the default provider using a service integration bus, an IBM MQ provider, and a generic JMS provider. It also describes the service integration bus and its components.

Uploaded by

pmmanick
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Default messaging provider (service integration bus)

The default messaging provider uses the service integration bus for transport. The
default message provider provides point-to-point functions, as well as publish and
subscribe functions. Within this provider, you define JMS connection factories and
destinations that correspond to service integration bus destinations.
IBM MQ provider
You can use IBM MQ as the external JMS provider. The application server provides
the JMS client classes and administration interface, while IBM MQ provides the
queue-based messaging system.
Generic JMS provider
You can use another messaging provider as long as it implements the ASF component
of the JMS 1.0.2 specification. JMS resources for this provider cannot be configured
using the administrative console.
For transitioning users: Version 6 replaces the Version 5 concept of a JMS server
with a messaging engine built into the application server, offering the various kinds of
providers mentioned previously. The Version 5 messaging provider is offered for
configuring resources for use with Version 5 embedded messaging. You also can use
the Version 5 default messaging provider with a service integration bus.

EJB 2.1 introduces an ActivationSpec for connecting message-driven beans to


destinations. For compatibility with Version 5, you still can configure JMS message-
driven beans (EJB 2.0) against a listener port. For those message-driven beans, the
message listener service provides a listener manager that controls and monitors one or
more JMS listeners, each of which monitors a JMS destination on behalf of a
deployed message-driven bean.

Service integration bus

The service integration bus provides a unified communication infrastructure for


messaging and service-oriented applications. The service integration bus is a JMS
provider that provides reliable message transport and uses intermediary logic to adapt
message flow intelligently into the network. It supports the attachment of web
services requestors and providers. Its capabilities are fully integrated into product
architecture, including the security, system administration, monitoring, and problem
determination subsystems.

The service integration bus is often referred to as just a bus. When used to host JMS
applications, it is often referred to as a messaging bus. It consists of the following
parts (not shown at this level of detail in the diagram).
Bus members
Application servers added to the bus.
Messaging engine
The component that manages bus resources. It provides a connection point for clients
to produce or from where to consume messages.
Destinations
The place within the bus to which applications attach to exchange messages.
Destinations can represent web services endpoints, messaging point-to-point queues,
or messaging publish and subscribe topics. Destinations are created on a bus and
hosted on a messaging engine.
Message store
Each messaging engine uses a set of tables in a supported data store (such as a JDBC
database) to hold information such as messages, subscription information, and
transaction states.
Through the service integration bus web services enablement, you can:
 Make an internal service that is already available at a service destination
available as a web service.
 Make an external web service available at a service destination.
 Use the web services gateway to map an existing service, either an internal
service or an external web service, to a new web service that appears to be
provided by the gateway.
Concurr

You might also like