While the What's new in Version 6.0? topic introduces you to the
main new function in WebSphere Message Broker Version 6.0, this topic
introduces you to additional function that has been added in fix packs.
For detailed information about the content of fix packs, go to the WebSphere Message Broker support
Web page and select your product to display the recommended
fix pack or to list all available fix packs. Each fix pack includes a memo,
called memo.ptf, that includes details of its content.
Fix Pack V6.0.0.2 enhancements:

- Extended database support
- Support is added for the following databases on Solaris (x86 platform):
See Supported databases for details of available database
support by operating environment.
See Configuring component databases for
instructions to configure these databases on this platform.
- Mapping enhancements
- You can select WebSphere
MQ constants as
target element values. See Setting the value of a target element to a WebSphere MQ constant.
- Several changes have been made to the wizards in the Mapping node:
- The new Map by Name wizard performs automatic mapping of sources and targets
that have the same or similar names. See Mapping from source: by name.
- Add Instance and Add Group Instances have been replaced by the Insert
Before and Insert After wizards that allow mapping statements to be added
at specific locations in a map.
- The Substitute Element wizard has been replaced with the Replace wizard
that allows mapping statements on elements, attributes, and database columns
to be substituted by similar statements.
- IPv6 support
- Internet Protocol Version 6 is now supported. You can enter or refer to
an IPv6 address in all situations in which an IPv4 address is valid, for example
in the mqsichangeproperties command.
- Overview of creating z/OS components
- The information that describes the mandatory and optional tasks that create
components on z/OS has been enhanced. No new function is provided, but the
topics have been changed and extended to improve the order and description
of how you achieve the results you want in your broker domain. See Creating WebSphere Message Broker components on z/OS.

- Fix Pack V6.0.0.1 enhancements:
- Updated Rational support for Message Brokers Toolkit
- Message Brokers Toolkit is now based
on Rational Application Developer (RAD) Version 6.0.1.1 and is compatible
with that release and later Version 6.0.1 updates. It cannot coexist with
RAD products that are based on different versions, so such products cannot
be below Version 6.0.1.1, and must be below Version 6.0.2. Other Rational
products must also be at the latest available level. For detailed guidance
about ensuring you have a compatible Rational framework, see the Installation Guide.
- Support for 64-bit execution groups
- The addition of support for 64-bit execution groups allows the use of
very large messages, and also enables WebSphere Message Broker Version 6.0 to
run applications in fastpath (trusted) mode when using the 64-bit Queue Manager
provided in WebSphere
MQ Version 6.0.
- Extended platform and operating system support for runtime environments
- Support is now provided for the following runtime environments:
- Solaris (x86-64 platform), running Solaris 10.
- Linux (POWER platform) on iSeries and pSeries hardware,
running either of the following operating systems:
- Linux PowerPC Red Hat Enterprise Advanced Server V4
- Linux PowerPC SUSE Linux Enterprise Server (SLES) 9
- Linux Red Hat Enterprise Advanced Server V4 to Linux (x86 platform) and Linux (zSeries
platform).
- Solaris 10 on Solaris
(SPARC platform) and Solaris (x86-64 platform).
See Operating system requirements for more detailed information
about supported environments.
- Extended database support
- Support is added for the following databases:
- Remote access to Microsoft SQL Server 2000, from the following
platforms:
- AIX
- HP-UX
- Linux (x86 platform)
- Solaris
(SPARC platform)
- Informix Dynamic Server V9.4, on the following platforms:
- AIX
- HP-UX
- Linux (x86 platform)
- Solaris
(SPARC platform)
- Windows.
- IBM DB2 V8 on Solaris (x86-64 platform) and Linux (POWER platform).
See Supported databases for details of available database
support by operating environment.
- Backward recovery extended to Version 2.1
- It is now possible to restore components and resources that you have migrated
to Version 6.0 from Version 2.1 products
back to their original state. For details of how to do this, see Restoring components and resources to Version 2.1
- User exit for tracing message flows
- Support is provided for user exits, which enable user-provided custom
software to track data passing through message flows in WebSphere Message
Brokers. The user-provided functions can be invoked at specific points during
the lifecycle of a message as it passes through the message flow, and can
invoke utility functions to query information about the point in the flow,
and the contents of the message assembly. For more information about user
exits see Developing user exits