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

What do I need to know to start developing applications?

New users: Before you start developing your applications, use the links in this topic to get information about concepts that you must understand.

Basic application development concepts

What types of resources can I develop?

You can develop the following kinds of resources:
  • Message flows

    A message flow is a sequence of processing steps that run in the broker when an input message is received. You define a message flow by including a number of message flow nodes, each of which represents a set of actions that define a processing step. For more information about message flow nodes, see message flow nodes.

  • Message models

    You can define the structure of messages for use with your message flows.

What is WebSphere Message Broker typically used for?

Use the links in this section to find out about the tasks that WebSphere Message Broker is commonly used for. You can also find out about the alternative ways to implement message flows for these tasks.
  • How can I use WebSphere Message Broker to route messages?

    You can select from a number of ways of routing messages using message flows:

    • Using a Filter node

      You can route messages through a message flow based on the content of the message using a Filter node. The nodes that are connected to the different terminals of the Filter node can be used to apply different processing and routing to messages based on their content.

    • Using a Route node

      You can route messages through different paths in a message flow, based on the content of the message using a Route node. The Route node uses XPath expressions to control processing.

    • Using the destination list to route messages

      You can create a destination list to define the recipients of output messages using a Compute, Mapping, PHPCompute, or JavaCompute node. This list can then be used to route messages using RouteToLabel and Label nodes. Alternatively, a single message can be sent to many locations using a destination list for the destination mode, on some output nodes.

    You can see examples of how message flows can be used for routing in the following samples. You can view information about samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit or the online information center. You can run samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit.
  • How can I use WebSphere Message Broker to transform and enrich messages?

    You can select from a number of different ways of transforming and enriching messages using different nodes in message flows. Messages can be enriched with content from databases, applications, and files. The following methods of programming nodes in your message flows can be used to transform messages:
    • Databases

      WebSphere Message Broker supports various database managers so that you con configure your brokers to interact with databases on behalf of your message flows. Follow this link to get instructions on how to create and configure databases and connections.

    • ESQL

      Extended Structured Query Language (ESQL) is a programming language based on Structured Query Language (SQL) that is typically used to work with databases. ESQL is extended to access and manipulate data in messages and databases. You can code ESQL to transform and enrich messages using the Compute node.

    • Java™

      Use the JavaCompute node to add valid Java code to your message flow. You can access, create, and transform messages in your message flows by using Java.

    • Message mappings

      Message mappings use a drag-and-drop interface to transform messages. You can use conditional logic, ESQL functions, Java functions, and XPath functions to create complex mappings and transformations. You can also use message mapping to select and manipulate data in database tables. You can create message mappings to transform and enrich messages using the Mapping node.

    • PHP

      Use the PHPCompute node to add valid PHP code to your message flow. You can access, create, and transform messages in your message flows by using PHP.

    • XML transformation

      You can use the XSLTransform node to transform from one type of XML message to another, based on rules provided by an Extensible Stylesheet Language (XSL) style sheet.

    The Airline Reservations demonstrates message enrichment, and the following samples demonstrate message transformation. You can view information about samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit or the online information center. You can run samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit.
  • How can I use WebSphere Message Broker with Web services?

    WebSphere Message Broker provides a number of ways to work with Web services:

How can I connect my applications?

Use the links in this section to find out how you can connect your applications to WebSphere Message Broker.

What is a logical message tree?

Use the links in this section to find out about the logical message tree and the internal representation of messages within message flows. When a message is received by a message flow, a logical structure is created, known as the logical message tree or the message assembly. The message assembly contains a message tree, which is the internal representation of the physical message, and a number of other trees that are used to store information during the processing of the message in the message flow.

What are physical message formats?

Use the links in this section to get information about the physical messages received by message flows, and to find out how the different structures and formats are handled by your applications.

Advanced application development concepts

What other resources can I develop?

  • Developing message flows that use WebSphere Adapters

    You can develop applications that connect to an Enterprise Information System (EIS) using WebSphere Adapters.

  • User-defined extensions overview

    A user-defined extension is an optional component that is designed by the user to extend the functions provided by WebSphere Message Broker. A user-defined extension can be either a node or a parser.

  • Message Broker API applications

    The Message Broker API (also known as the CMP API) is an application programming interface (API) that you can program to control brokers by using a remote interface to the appropriate broker.

Notices | Trademarks | Downloads | Library | Support | Feedback

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

        
        Last updated:
        
        Last updated: 2016-05-23 14:45:56


General topicGeneral topic | Version 8.0.0.7 | aa40070_