WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Built-in patterns

A built-in pattern is a pattern that covers a set of commonly encountered message flow scenarios and that is packaged and released with WebSphere® Message Broker.

The built-in patterns that are supplied in WebSphere Message Broker are shown in the following tables.

You can view patterns in the information center by using the links only when you use the information center that is integrated with the WebSphere Message Broker Toolkit, or when you use the online information center.

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 WebSphere Message Broker.
Worklight: mobile service Use this pattern to integrate a mobile application written for the Worklight platform with a service that is running in WebSphere Message Broker.
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.

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 WebSphere Message Broker. You can use the pattern to make a .NET class available as a web service by using WebSphere Message Broker.
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 WebSphere Message Broker 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.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:33


Concept topicConcept topic | Version 8.0.0.7 | ac68260_