While the
What's new in Version 6.0? topic introduces you to the
main new function in
WebSphere Message Broker Version 6.0,
New function added in Version 6.0 fix packs summarizes
new function in its fix packs, and this topic introduces you to additional
function that has been added in
Message Broker Toolkit Version
6.0.2.0. This version is compatible with any runtime component level.
You might also find useful the developerWorks article that
describes some of the additional function in Version 6.0.2.0.
- Start here topics in the information center
- A Start here category has been added to the Contents pane of the information
center. The Start here category contains
topics that provide an introduction for users who are new to WebSphere Message Broker Version 6.0.
Use the Start here topics to get overview information and links to relevant
topics in the information center on getting started, developing applications,
broker administration, and troubleshooting tasks.
- New Quick Start wizards
- You can use the three new "quick start" wizards to help you to create
your applications using the Message Broker Toolkit.
For more details, see Getting started with Quick Start wizards.
- New Message Set wizard redesigned
- The New Message Set wizard has been redesigned, therefore you do not need
to create a message set project when you create a new message set. A more
logical tree structure is used by the Message Set editor to organize the physical
formats of message sets. See Creating a message set for more details
about the New Message Set wizard.
- New Message Flow wizard redesigned
- The New Message Flow wizard has been redesigned to allow you to either
select an existing message flow project for a new message flow, or to create
a new message flow project for the new message flow. See Creating a message flow for
more information.
- New XML Schema wizard renamed
- The New XML Schema wizard is now called the Generate XML Schema wizard.
To start the wizard, click . For more information, see Generating an XML schema.
- RDB Definition Files wizard renamed
- The RDB Definition Files wizard is now called the New Database Definition
Files wizard. To start the wizard, click .
- New Message Definition File wizard redesigned
- The New Message Definition File wizard has been redesigned. Click to
create a new message definition file from scratch, or click to create a new message definition file from existing resources.
In the latter case, you then choose from a list of existing resources (XML
Schema file, IBM-supplied message, XML DTD file, C header file, COBOL file,
or WSDL file). See Creating a message definition file from scratch and Creating a message definition file from an existing resource for
more details about the new message definition wizards.
When you create
a new message definition file from an existing resource such as an XML Schema
file, you can now select a file from outside the current workspace (previously,
the file had to exist in the current workspace).
The steps to create
a new message definition file from a WSDL file have been simplified.
- New WSDL Definition wizard renamed
- The New WSDL Definition wizard is now called the Generate WSDL Definition
wizard. To launch the wizard, click . For more details, see Generate WSDL wizard.
- Option to generate XML Schemas and WSDL to an external
folder
- You can now choose an external folder as the destination for generated
XML Schemas and WSDL definitions.
- Creation of a message definition file based on a
C header, a COBOL copybook , or an XML DTD file
- The wizards that you use to create a message definition file that is based
on a C header file, a COBOL copybook, or an XML DTD file, have all been simplified.
- Support for mapping MIME messages
- You can create message mappings for messages in the MIME message domain.
Select the MIME message domain for your message set, and create the message
mappings that you require. If you plan to create message mappings for messages
in the MIME domain, your messages must comply with the rules stated in the
following topics:
- Broker Development view (formerly the Resource Navigator
view)
- The Resource Navigator view in the Broker Application Development perspective has
been renamed and is now called the Broker Development view. The ways in which
resources can be displayed in the Broker Development view have also changed.
For example, you can choose whether to display or hide namespaces, categories,
or categorized file extensions. When you create resources, they are grouped
together by file type in logical categories, and placed in virtual folders.
You can choose whether to display the resources in the logical categories,
or to hide them. You can also filter closed projects in the View menu. See Resources and Broker Application Development perspective for more
information.
- Displaying projects in working sets
- A working set is a logical collection of application projects, which you
can use to limit the number of resources that are displayed in the Broker
Development view. For more information, see Resources and Displaying selected projects in working sets.
- Global toolbar in the Broker Application Development
perspective
- The icons that are displayed by default in the toolbar of the Broker Application
Development perspective have changed. See Broker Application Development perspective for
more information.
- Add a node by dragging from the Broker Development view
(formerly Resource Navigator view)
- You can add a message flow node to the canvas by dragging it from the
Broker Development view, as described in Dragging a resource from the Broker Development view.
- New categories for nodes on the node palette
- The nodes on the node palette have been organized into categories, as
shown in Message flow node palette. You can add the nodes that you
use most often into the Favorites category, either by dragging them, or using
the menu, as described in Adding nodes to the Favorites category on the palette.
- Editing node properties
- You can rename a node in the Message Flow editor when you add it to the
canvas, or you can rename it on the Description tab of the Properties view.
- When you double-click a node in the Message Flow editor, you
open the resource that is associated with that node; for example, if you double-click
a Mapping node, you open the New Message Map dialog box. When you double-click
a node that does not have a resource associated with it, you open the
Properties view for that node.
- You can choose to view and edit a node's properties either in the tabbed
Properties view beneath the Message Flow editor, or in the Properties dialog
box.
For more details, see Configuring a message flow node.
- Mapping enhancements
- The New Message Map wizard has been changed. Select
the type of message map that you want to create, then select the sources and
targets for the message map. The options available in the New Message
Map wizard depend on the node that you have selected, or whether
you are creating a message map from the Broker Development view (formerly
Resource Navigator view). For more details see the following topics:
- You can no longer select to map headers in your message map from the New
Message Map wizard. Instead, you can now select to add the following
message headers and folders to your message map using the Add or
Remove Headers and Folders dialog box:
- LocalEnvironment
- Properties
- MQ Headers
- HTTP Headers
- JMS Transport Header
Properties are included with the message body in a message map by default.
If you do not select to add the LocalEnvironment or any extra message headers
to your message map, the corresponding values are copied from the source message
to the target message automatically. For more details see Mapping headers and folders.
You can also convert between a message map and a submap using the Add
or Remove Headers and Folders dialog box as described in Converting a message map to a submap.
- Enhancements have been made to mappings involving databases:
- Two new dialog boxes have been added to the Message Mapping editor.
These dialog boxes, in addition to the Add Sources and Targets dialog
box, can be used to add sources and targets to your message map. You can use
the Add Sources dialog box to add Messages, Message Components,
and Data Sources to your message map as sources. You can use the Add
Targets dialog box to add Messages, Message Components, and Data
Targets to your message map as targets. See the following topics for more
information:
- You can drag sources and targets from the Broker Development view (formerly
Resource Navigator view) onto the Source and Target panes in your message
map. See the following topics for more information:
- Refreshing the contents of a broker archive
- You can now refresh the contents of a broker
archive in the Broker Archive editor.
This single task combines the actions of removing, updating, and replacing
resources that were previously required. You can also now view, and clear,
the user and service logs from the Broker Archive editor.
- Test Client
- Test messages during message flow development using the Test Client in
the Message Broker Toolkit. Click Test Message
Flow or Test Client on the menu that is
displayed when you right-click a message flow file in the Broker Development
view, or click Test when you right-click either an
MQInput node or an HTTInput node in the Message Flow editor to generate the
Test Client editor.
You can use the Test Client editor to:
- Configure a Message Broker test environment
- Compose and edit test messages
- Start and send test messages
- Monitor test execution events
- Save the test configurations for reuse and analysis
- Save and review message test execution traces
For more details, see Testing message flows using the Test Client