While the New in Version 5.0 topic introduces you to the
main new function in WebSphere Business Integration Message Broker Version 5.0, this topic
introduces you to some of the other new function 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.

Some features added in Fix Pack 8:

Some features added in Fix Pack 5:
- On Linux (x86 platform),
you now use the DataDirect Driver Manager to connect to DB2 databases. For
more information, see Defining an ODBC connection to a 32-bit database on Linux and UNIX.
- The MRM domain TDS physical format can now recognize
and interpret HL7 service strings, and a new TDS messaging standard called
'HL7' has been added. For more information, see HL7 messaging standard.
- The broker now supports the 'Z' character
to mean a zero time difference from Coordinated Universal Time (UTC) when
it appears as a time zone in a dateTime field in a message. It is possible
to accept dateTimes containing 'Z' on input, and to generate them on output.
For more information, see DateTime as string data.
- The new mqsimigratequeues command makes
it easier to migrate a Version 2.1 broker to Version
5.0 by creating any new queues that are needed
by the updated broker.
- The mqsimigratemsgsets command
includes a new option -pl that you can
use to specify that elements that have prefixed identifiers and are referenced
more than once are to be created as local rather than global. For more information,
see Prefixed identifiers.
Some features added in Fix Pack 4:
- If you have existing Java code, you can now invoke it
directly from ESQL. For more information, see Java routines.
- The MRM Tagged/Delimited String format can now parse and write raw TLOG
messages. For more information, see TLOG messaging standard.
- The MRM Encoding Null mechanism
has been extended for the COBOL initialization of 01 structures. For more
information, see Importing from COBOL: supported features.
Some features added in Fix Pack 3:
- When an XML Schema is imported, the following constructs are now accepted:
Key, Keyref, and Unique. However, XML Schemas with such constructs are not
supported and are ignored by the broker. For more information, see Importing from XML Schema: unsupported features.
- The COBOL importer now supports the ASCII Sign
EBCDIC Custom External Decimal representation within the CWF component.
For more information, see Importing from COBOL: supported features.