Use IBM Integration Bus patterns to accelerate the development of your integration solutions.
Use the Patterns Explorer and pattern generator to expose an asynchronous WebSphere MQ backend application as a web service, including logging and error handling, in minutes. Use the built-in test client to deploy, generate sample data, and test the running integration solution.
Try it yourself: Download the Demo Customer WSDL file used in the video
Length: 10:55 min | Size: 27.1 MB
Download the .mp4 file
You can read the pattern documentation and create a pattern instance to explore the pattern functionality.
Note: From the Patterns Explorer you also have access to the Experimental OT4I GitHub Pattern Repository. The Experimental OT4I GitHub Pattern Repository contains patterns that are available for testing but are not fully-supported.
For more information, see the Getting patterns from the GitHub repository in IBM Knowledge Center.
01 December 2015:
The current set of IIB V10 patterns are now live for use in the “Experimental GitHub Pattern Repository” while they undergo final review for publishing to the main “OT4I GitHub Pattern Repository” rather than “Experimental GitHub Pattern Repository”.
If you refresh your IIB V10 Integration Toolkit (you may need to restart the toolkit, because it typically caches content) then you should now see more in the categories of patterns:
30 November 2015:
IBM Developers have been migrating and testing patterns from IIB V9, and are expecting to publish the patterns to the ot4i repository this week.
I’ve provided a list (below) of the current set of patterns to be made available. You can read more about the patterns in the IIB V9 documentation in IBM Knowledge Center (See http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac68260_.htm).
File Processing patterns
– Record Distribution to WebSphere MQ: one-way
Message-based Integration patterns
– Message Correlator for WebSphere MQ: request-response with persistence
– Message Correlator for WebSphere MQ: request-response without persistence
– Message Splitter for WebSphere MQ: one-way (for XML)
– IBM MessageSight: Inbound event filter
Service Enablement patterns
– Service Facade to WebSphere MQ: one-way with acknowledgment
– Service Facade to WebSphere MQ: request-response
Service Virtualization patterns
– Service Proxy: static endpoint
If you are interested in any specific patterns, please let us know.
The scenarios included in this section require the following zip file to be unzipped into a location called c:\student.
Pattern Authoring scenario files
- Pattern Authoring – Lab 1: Basic introduction
- Take a simple message flow (an exemplar) and create a pattern based on that flow.
- Pattern Authoring – Lab 2: Using XPath
- Configure pattern parameters using the XPath expression tools in the pattern builder. When a pattern instance is generated, the value of the pattern parameters will be concatenated using an XPath expression.
- Pattern Authoring – Lab 3: Setting parser properties
- Configure the parser properties on an MQInput node. Configuring the message domain, message model, message and physical format properties on input nodes is a very common requirement in pattern authoring.
- Pattern Authoring – Lab 4: Using PHP and Java
- Create a pattern that includes a new Compute node and associated ESQL, which are be added to the generated message flow if the pattern selects the â€śdatabase loggingâ€ť option. This enables a pattern user to dynamically change the message flow logic, based on the value of pattern parameters.
- Pattern Authoring – Lab 5: Customisation
- As a Pattern Author you create a main message flow that includes customisation subflows, which are held in a separate project or Library. This enables the Pattern User to customise those subflows without overwriting the changes every time the pattern instance is re-generated.
- Pattern Authoring – Lab 6: Groups and table parameters
- Create a routing pattern that allows you to generate a dynamic-routing message flow. The pattern takes the number of routing destinations (MQOutput nodes) and the routing table as parameters.