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

Using or converting legacy resources into message maps

You can compile and deploy legacy message maps and legacy message flow nodes in WebSphere® Message Broker Version 8 and later versions. However, if you need to modify any of these resources, you must convert them into message maps that the new Mapping node consumes.

A legacy message map is a message map created as a .msgmap file in earlier versions of WebSphere Message Broker, for example in WebSphere Message Broker Version 7.

Note: From WebSphere Message Broker Version 8 onwards, legacy message maps are accessible in read-only mode and cannot be modified by using the IBM® Integration Toolkit.

The functions provided by the following legacy message flow nodes in WebSphere Message Broker Version 7 are replaced with the new Mapping node in WebSphere Message Broker Version 8 and later versions:
  • DataDelete node
  • DataInsert node
  • DataUpdate node
  • Extract node
  • Mapping node
  • Warehouse node

Follow these guidelines when you use legacy message maps and legacy message flow nodes in your integration solutions:

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:26


Task topicTask topic | Version 8.0.0.7 | br35001_