Implementation considerations

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

1
Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

2
platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

3
developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

4
WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

5
build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

6
A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.

A mapper is a WebSphere Message Broker subflow that is started to perform the mapping.

The mapper subflow uses one or more nodes that are provided by WebSphere Message

Broker to perform the parsing and transformation of messages. For more information about

developing Mappers, see Chapter 5, “Using WebSphere Message Broker Toolkit to produce

build artifacts” on page 131.

In this section, we describe implementing mapping in Financial Transaction Manager by using

various options for mapping that is offered by the underlying WebSphere Message Broker

platform. Financial Transaction Manager also includes support for mapping by using

WebSphere Transformation Extender.