A number of pattern categories are available in IBM® Integration Bus, from which you can choose
the pattern that you want to use.
IBM Integration Bus includes the following
categories for built-in patterns. You can also use these pattern categories
for your user-defined patterns, or you can create your own categories.
- Message-based Integration
- An Enterprise Service Bus can extend an existing messaging infrastructure
by providing an environment for building and deploying infrastructure
level message-based applications. Examples of these applications include
routing and transformation services, and logging services. This environment
can extend a single underlying messaging infrastructure or provide
a bridge between different products and technologies.
- Mobile
- Mobile is a category of patterns in which mobile applications
are integrated with enterprise applications. The mobile pattern category
encapsulates functionality where new or existing services are made
available to mobile applications through a service-oriented interface
(typically JSON/HTTP). These patterns allow existing assets to be
reused in new contexts without requiring large changes.
- Service Enablement
- These patterns encapsulate functionality that does not have a
service interface, and present this functionality through a service-oriented
interface. These patterns represent the move from traditional enterprise
application integration into service-oriented architectures, allowing
existing assets to be reused in the new style without requiring radical
change.
- Service Virtualization
- These patterns provide loose coupling between services by providing
additional levels of direction through an Enterprise Service Bus.
These patterns also address the requirements of mediation (for example,
routing, protocol conversion, data transformation, and logging) between
services, when addressing connectivity requirements in a service-oriented
architecture.
- Gateway
- A Gateway is a part of a message or service bus that provides
boundary functions that apply to all incoming messages, and are not
format-dependent. Boundary functions typically use data from standard
headers (at transport, SOAP, or data level) to determine what action
to take, but are not required to understand the complete format of
the message data or body. A Gateway pattern can then call a service
directly, or call another pattern.
- Conversion
- Conversion patterns convert resources from other applications
so that they can be used in IBM Integration Bus projects.
- File Processing
- An Enterprise Service Bus can provide a managed runtime environment
for processing files locally or by using an FTP protocol. Typically
this processing involves activities including the transformation or
translation of data held in the files, the shredding of files into
multiple individual transaction records, the routing of records, the
accumulation of records into target files, and the routing of files
or records to specified locations.
- Event-driven Integration
- Event-driven architecture covers different application scenarios
in which an Enterprise Service Bus plays a key role. These scenarios
include integration with complex event processing engines that include
the ability to filter information or event streams, distribute events
in real time, and process events from physical devices, for example,
detectors and sensors.
- Application Integration
- Application Integration is a collection of technologies
and services that form a middleware to enable the integration of systems
and applications across the enterprise.
For more information about individual built-in patterns, see Built-in patterns.
Last updated Friday, 21 July 2017