IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Bindings > Export and import binding configuration > Data format transformation in imports and exports

Data handlers

Data handlers are configured against export and import bindings to transform data from one format to another in a protocol-neutral fashion. Several data handlers are provided as part of the product, but you can also create your own data handler, if necessary. You can associate a data handler with an export or import binding at one of two levels:


Predefined data handlers

You use IBM Integration Designer to specify the data handler that you want to use.

The data handlers that are predefined for your use are listed in the following table, which also describes how each data handler transforms inbound and outbound data.

Except where noted, these data handlers can be used with JMS, Generic JMS, MQ JMS, WebSphere MQ, and HTTP bindings.

Predefined data handlers
Data handler Native data to business object Business object to native data
ATOM Parses ATOM feeds into an ATOM feed business object. Serializes an ATOM feed business object to ATOM feeds.
Delimited Parses delimited data into a business object. Serializes a business object to delimited data, including CSV.
Fixed Width Parses fixed-width data into a business object. Serializes a business object to fixed-width data.
Handled by WTX Delegates data format transformation to the WebSphere Transformation Extender (WTX). The WTX map name is derived by the data handler. Delegates data format transformation to the WebSphere Transformation Extender (WTX). The WTX map name is derived by the data handler.
Handled by WTX Invoker Delegates the data format transformation to the WebSphere Transformation Extender (WTX). The WTX map name is supplied by the user. Delegates the data format transformation to the WebSphere Transformation Extender (WTX). The WTX map name is supplied by the user.
JAXB Serializes Java beans to a business object using the mapping rules defined by the JAXB specification. Deserializes a business object to Java beans using the mapping rules defined by the JAXB specification.
JAXWS

The JAXWS data handler can be used only with the EJB binding.

Used by an EJB binding to transform a response Java object or exception Java object to a response business object using the mapping rules defined by the JAX-WS specification. Used by an EJB binding to transform a business object to the outgoing Java method parameters using the mapping rules defined by the JAX-WS specification.
JSON Parses JSON data into a business object. Serializes a business object to JSON data.
Native body Parses the native bytes, text, map, stream, or object into one of five base business objects (text, bytes, map, stream, or object). Transforms the five base business objects into byte, text, map, stream, or object.
SOAP Parses the SOAP message (and the header) into a business object. Serializes a business object to a SOAP message.
XML Parses XML data into a business object. Serializes a business object to XML data.
UTF8XMLDataHandler Parses UTF-8 encoded XML data into a business object. Serializes a business object into UTF-8 encoded XML data when sending a message.


Create a data handler

Detailed information about creating a data handler can be found in the "Developing data handlers" topic in the Integration Designer information center.

Data format transformation in imports and exports


Related information:
Developing data handlers