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 and other resource files that you
need to start developing applications, you can use a Quick Start wizard.
To create only a message flow project, perform the following
actions:
- Switch to the Broker Application Development perspective.
- Click or right-click any
resource in the Broker Development view and click .
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® Message
Broker.
Click Message Flow Project in the right view, then click Next.
The New Message Flow Project wizard displays.
- Enter a name for the project. Choose a project name
that reflects the message flows that it contains. For example, if you want
to use this project for financial processing message flows, you might give
it the name Finance_Flows.
- Leave the Use default check
box checked (it is checked when the dialog opens) This applies
if you want to use the default location for the new message project directory,
that is, in the \workspace subdirectory of your current
installation. You cannot edit the Directory entry
field.
- Alternatively, clear the Use
default check box and specify a location for the new message
flow project files in the Directory entry
field. This applies if you do not want to use the default location.
- Use the Browse button to find the desired
location or type the location in.
- Click Next if you want to specify that this
message flow project depends on other message flow projects, or on message
set projects,
You are presented
with a list of current projects. Select one or more message flow projects, or one or more message set projects, or both, from the list
to indicate this new message flow project's dependencies. Message flow projects
and message set projects are filtered to only show artifacts in the active
working set.
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:
- ESQL subroutines (defined in broker schemas)
- Mappings
- Message sets
- Subflows
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 Broker Development view and clicking Properties.
Click References and select the dependent message flow
or message set project from the list of projects displayed.
- Click Finish to complete the task.
The project file is created within a directory
that has the same name as your message flow project in the specified location.
All other files that you create (or cause to be created) related to this message
flow project are created in this same directory.
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.