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
Converting a legacy message map that includes calls to message map functions
The conversion process converts a number of supported calls to predefined legacy message map functions (msgmap:functionName) to an XPath expression, or a Custom XPath transform.
If there is no XPath equivalent of a message map function, the conversion process creates a Task transform instead.
The following legacy message map functions have no
XPath equivalent:
- msgmap:element-from-bitstream
- msgmap:cdata-element
- msgmap:db-path
Complete the following steps to convert a transformation that includes a call to a message map function that is not converted automatically:
- Select a Task transform.
- In the Task transform Properties view, check out the information provided in the Documentation tab.
- Replace the Task transforms with any of the available transforms. Consider using a Custom XPath transform, a Custom Java transform, or a Custom ESQL transform.
- Manually re-create the equivalent transformation logic of the message map function.
Continue converting your legacy message map. For more information, see Converting a message map from a .msgmap file to a .map file.