A message flow project is a container for message flows; you must create a project before you can create a message flow.
The project 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 file system 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.
To create a message flow project:
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 Message Broker. Click Message Flow Project in the right view, then click Next. The New Message Flow Project wizard displays.
This message flow project depends on another message flow project if you intend to use common resources within it. Common resources that you can share between message flow projects are:
For example, you might want to reuse a subflow that provides standard error processing such as writing the message to a database, or recording a trace entry.
This message flow project depends on a message set project if you intend to refer to the message it defines within ESQL within the message flow nodes.
You can add dependencies after you have created the message flow project by right-clicking the project in the Resource Navigator and clicking Properties. Click References and select the dependent message flow or message set project from the list of projects displayed.
A default broker schema (default) is also created within the 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
Project references
Development repository
Message flows
Broker schema
Related tasks
Developing message flow applications
Deleting a message flow project
Creating a message flow
Related reference
Broker Application Development perspective
Rules for naming workspace objects
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac02180_ |