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
To complete this task, you must have completed the following task:
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:
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 Business Integration Event Broker. Click Message Flow in the right view, then click Next. The New Message Flow wizard displays.
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.
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.
Related concepts
Development repository
Message flows
Broker schema
Message flow application deployment
Related tasks
Developing message flow applications
Deciding which nodes to use
Creating a message flow project
Related reference
Broker Application Development perspective
Rules for naming workspace objects
Built-in nodes
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac02200_ |