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
See information about the latest product version
Message Broker projects and files
You develop message flows in the Broker Application Development perspective. Message flow resources are maintained within Message Broker projects. A Message Broker project compiles to one or more deployable flows.
Message Broker projects contain the following resource files:
- .msgflow files
- A message flow file is a graphical representation of a message
flow, containing message nodes and connections. It also contains property
values and overrides to define, implement and control the behavior
of the message flow nodes. The New Message Flow Wizard automatically
creates this file.
Default editor: Message Flow editor
- .esql file
- (Optional) ESQL modules containing compute, filter, and database
ESQL functions and procedures. If none of the message flows defined
in the project include any nodes that require ESQL, you do not need
to create an ESQL file.
Default editor: ESQL editor
- .msgmap file
- (Optional) Mapping transformation descriptions for messages and
databases. If none of the message flows defined in the project include
any nodes that require mappings, you do not need to create a mapping
file.
Default editor: Graphical Data Mapping editor
You can define more than one message flow, each in a separate .msgflow file, in the same message project.