Creating a message flow

Create a message flow to specify how to process messages in the broker. You can create any number of message flows and deploy them to one or more brokers.

Before you start:

The message flow and its resources are stored in a file system or in a shared repository. If you are using a file system, this can be the local drive or a shared drive. If you store files in a repository, you can use any of the available repositories that are supported by Eclipse, for example CVS.

Use this process to create a complete message flow that you can deploy, or a subflow that provides a subset of function (for example, a reusable error processing routine) that you cannot deploy on its own.

To create a message flow:

  1. Switch to the Broker Application Development perspective.
  2. Check that you have already created the message flow project in which you want to create the message flow. You can only create a message flow in an existing project. The project can be empty, or can already have message flows defined in it.
  3. Click File > New > Message Flow or right-click any resource in the Navigator view and click New > Message Flow.

    You can also press Ctrl+N. This displays a dialog that allows you to select the wizard to create a new object. Click Message Brokers in the left view. The right view displays a list of objects that you can create for WebSphere Event Broker. Click Message Flow in the right view, then click Next. The New Message Flow wizard displays.

  4. Identify the project in which you want to define the message flow. If you have a resource selected in the Navigator view, the name of the corresponding project is displayed in the first entry field, Project.

    If you do not have a resource selected, the first field is blank. Click Browse to select the appropriate project for this message flow. A dialog containing a list of valid projects is displayed. Select the correct project and click OK.

    You can type the project name in, but you must enter a valid name. The dialog displays a red cross and the error message The specified project does not exist if your entry is not a valid project.

  5. Complete the Schema and Name fields when the project is correct:
    1. In Schema, enter the identifier of the broker schema in which the message flow is defined. When you create a message flow project, a default schema is created within it, and this default value is always assumed if you do not enter a value in this field, or do not select a value using the Browse button.

      You can create and use different schemas within a single project to organize message flow resources, and to provide the scope of resource names to ensure uniqueness.

    2. In Name, enter the name of the message flow. You can use any valid character for the name; choose a name that reflects its function, for example OrderProcessing.
  6. Click Finish.
The new message flow (<message_flow_name>.msgflow) is displayed within its project in the Navigator view. The editor view is empty and ready to receive your input.
Next: save the message flow or define message flow content.
Related concepts
Development repository
Message flows overview
Broker schemas
Deployment overview
Related tasks
Defining message flow content
Developing message flows
Deciding which nodes to use
Creating a message flow project
Related reference
Broker Application Development perspective
Rules for naming workspace objects
Built-in nodes