ac68260_.htm |
Last updated Friday, 21 July 2017A built-in pattern is a pattern that covers a set of commonly encountered message flow scenarios and that is packaged and released with IBM® Integration Bus.
The built-in patterns that are supplied in IBM Integration Bus are shown in the following tables.
You can view patterns in the product documentation by using the links only when you use the product documentation that is integrated with the IBM Integration Toolkit, or when you use the online product documentation.
Message-based Integration patterns
| Pattern name | Description |
|---|---|
| Message Correlator for WebSphere® MQ: request-response with persistence | Use this pattern to accept requests from many client applications on a single queue, and to return responses to the correct client by using transactional flows and persistent WebSphere MQ messages. |
| Message Correlator for WebSphere MQ: request-response without persistence | Use this pattern to accept requests from many client applications on a single queue, and to return responses to the correct client by using non-transactional flows and non-persistent WebSphere MQ messages. |
| Message Splitter for WebSphere MQ: one-way (for XML) | Use this pattern to split a large XML message into smaller elements for processing by one or more targets by using transactional flows and persistent WebSphere MQ messages. |
Mobile patterns
| Pattern name | Description |
|---|---|
| Worklight® to Microsoft .NET: request-response | Use this pattern to integrate a mobile application written for the Worklight platform with Microsoft .NET applications that are running in IBM Integration Bus. |
| Worklight: mobile service | Use this pattern to integrate a mobile application written for the Worklight platform with a service that is running in IBM Integration Bus. |
| Worklight: push notification from WebSphere MQ | Use this pattern to send notifications to Worklight mobile applications from WebSphere MQ. |
| Worklight: resource handler | Use this pattern to provide services to mobile applications that use the Worklight APIs. The services are made available to mobile applications as Worklight adapter procedures that are started from JavaScript in the application. |
| IBM MessageSight: Inbound event filter | Use this pattern to configure IBM Integration Bus to receive events from mobile clients via IBM MessageSight, filter the events according to specified criteria, and then forward the events that match the criteria to a backend application. |
| IBM MessageSight: Outbound event notification | Use this pattern to configure IBM Integration Bus to receive events from a back-end system and dynamically publish those events to mobile clients via IBM MessageSight. |
Service Enablement patterns
| Pattern name | Description |
|---|---|
| Service Facade to WebSphere MQ: one-way with acknowledgment | Use this pattern to present a Web service interface to clients and to fulfill the service requests by using a WebSphere MQ enabled application. |
| Service Facade to WebSphere MQ: request-response | Use this pattern to provide a Web service facade to functions that are accessible only through WebSphere MQ. This pattern creates a bridge between the synchronous HTTP protocol, which is typically used with Web services, and existing applications with WebSphere MQ interfaces that cannot be easily upgraded. |
| Service Facade to Microsoft .NET: request-response | Use this pattern to integrate an application written for the Microsoft .NET platform with IBM Integration Bus. You can use the pattern to make a .NET class available as a web service by using IBM Integration Bus. |
| Service Access from WebSphere MQ: one-way | Use this pattern to process WebSphere MQ XML messages by using the data
that the pattern contains to call a Web service. Use this pattern
to bridge from the reliable WebSphere MQ messaging
protocols of client application with the synchronous requests, to
services to handle updates with an assurance that service failures,
including timeouts, are reliably reported. This pattern provides loose coupling between client applications and service providers in timing, protocols, and transport. It is appropriate for service interfaces to existing systems. |
Service Virtualization patterns
| Pattern name | Description |
|---|---|
| Service Proxy: static endpoint | Use this pattern to provide decoupling between Web service requesters and Web service providers by routing through a virtual service that is bound directly to the target service provider. |
| Service Proxy: static endpoint (web based) | This is an updated version of the Service Proxy: static endpoint pattern, which can be used in the IBM Integration Toolkit and in the web user interface. Use this pattern to provide decoupling between Web service requesters and Web service providers by routing through a virtual service that is bound directly to the target service provider. |
File Processing patterns
| Pattern name | Description |
|---|---|
| Record Distribution to WebSphere MQ: one-way | Use this pattern to bridge between two styles of integration, file based and transaction based. |
Application Integration patterns
| Pattern name | Description |
|---|---|
| Data distribution SAP to WebSphere MQ: one-way (for IDoc) | Use this pattern to process various types of IDocs that have a single program identifier without you being required to redeploy or rediscover existing message sets and adapters, even when you are adding different types of IDocs. |
| IBM BPM Integration Service | Use this pattern to integrate IBM Business Process Manager (BPM) Integration services with IBM Integration Bus services. Import a minimal BPM export .twx file into IBM Integration Bus, update the pattern to implement the requested services, and import it into BPM for final integration. |
Microsoft .NET Integration patterns
| Pattern name | Description |
|---|---|
| Microsoft Dynamics CRM Account Entity output: Static BAPI input | Use this pattern when you want to integrate Microsoft .NET, including Microsoft Dynamics CRM, with IBM Integration Bus. This pattern processes SAP BAPIs received by a synchronous RFC and maps them into Create, Retrieve Update, Delete operations on standard Microsoft™ Dynamics CRM Account entities. |
| Microsoft Dynamics CRM Account Entity output: Dynamic transport input | Use this pattern when you want to integrate Microsoft .NET, including Microsoft Dynamics CRM, with IBM Integration Bus. This pattern processes user-defined MQ, File or HTTP input messages and maps them into Create, Retrieve, Update and Delete operations on standard Microsoft™ Dynamics CRM Account Entities. |
Last updated Friday, 21 July 2017