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

Developing message flows

Develop message flows to process your business messages and data.

WebSphere® Message Broker provides several ways in which you can develop the message flows that you need to support your business processes. Your client applications can use many different techniques to interact with a broker, and the message flows that you have deployed to it.

The following steps provide a typical route that you might take through this section of the information center to understand the concepts associated with message flows, develop your own, and establish the ways in which your client applications can use message flows. When you are familiar with the basic concepts and behavior, you can progress to more complex options by adding further resources for your message flows to use.

  1. If you are not familiar with WebSphere Message Broker, read Message processing overview. This section defines the concepts associated with message flows, and is essential reading whatever your planned use of the broker. It also covers the general processing performed by a broker on all messages, regardless of origin. For example, it explains how a broker handles errors in your message flows, and how you can set up coordinated transactions.
  2. When you have reached an understanding of what a message flow is, and how it can process your messages and data, you can review the different ways in which you can create your own message flows. Choose from the following options:
    • Learning about WebSphere Message Broker features by using samples. The supplied samples provide tested message flows that focus on a particular feature or function supported by WebSphere Message Broker. They are more limited in scope than patterns, but provide comprehensive examples of typical message processing in particular scenarios. They are stand-alone applications; you can use them without having to create and configure additional resources.

      Because they are created to demonstrate a particular facet of the product, the samples are not always designed to use the preferred techniques for a particular task. Therefore, use them as examples to learn how particular functions work, not as complete production-level solutions. You might find them helpful as a starting point to developing your own message flows, or as part of a larger solution.

    • Developing message flows by using patterns. The supplied patterns provide reusable solutions that encapsulate a tested approach to solving a common architecture, design, or deployment task in a particular context. Much of the work of design and development has been done for you when you use a pattern.

      You can use these patterns unchanged, or modify them to meet your own requirements. You must create additional resources to complement the pattern and complete the solution.

    • Developing message flow applications from a wizard. You can run one of several Quick Start wizards in the WebSphere Message Broker Toolkit. These wizards create message flows and associated resources that are dependent on particular requirements; for example, adapter connections. You can use the messages flows created by these wizards as the basis for other message flows that change or add to the original result.
    • Developing message flow applications from scratch. If you prefer, you can create a message flow by using the basic building blocks available in the Message Flow editor. You decide which nodes are appropriate, and how to connect them together, to provide the processing that your messages require.
    • Developing a service. You can develop a service to contain a web services solution. A service contains subflows to implement the specified service operations.
    • Developing message flow applications by using the Message Broker Java API. You can create a message flow by running Java code that uses the Message Broker Java API. You can write code to load an existing message flow, modify it, and save it as a new message flow, or you can write code that creates a message flow from scratch. You do not need to install the WebSphere Message Broker Toolkit to run your code.
  3. Connect your business process applications and data to your message flows. You can use a number of different protocols to communicate with the broker. You can also interact from your message flows with other products and services. Find out what options are available in Connecting client applications.
  4. You can design your message flows to handle your messages and data in different ways. You can choose from a range of nodes that support:
  5. Message flows can process self-defining messages, predefined messages, or both. Predefined messages might provide extra value in your environment, and offer additional processing options within your message flows, Learn about these benefits, and how you can define your own message models, in Constructing message models.
  6. Your message processing environment might need some special processing that is not provided by WebSphere Message Broker. You can explore further options in Developing user-defined extensions, and learn about how to customize your broker in additional ways.
When you develop your message flows, and when you run them in the broker, you can tune the way the message flows work to improve message flow performance. For further information, see Tuning message flow performance.

When you create a project, it is recommended to avoid using spaces in the project name. Although using spaces in the name is valid, you might encounter problems. For example: A scenario where an XML schema file located in project X references an XML schema file project Y, either through import or include statements. If the referenced schema in the project contain spaces in project name, the name does not resolve, and you receive errors

Notices | Trademarks | Downloads | Library | Support | Feedback

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

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:01


Task topicTask topic | Version 8.0.0.7 | bc88710_