Data Transformation Engine Resource Adapter Reference Guide

Chapter 1 - Resource Adapters Encoding and Decoding Data

Resource Adapters Reference Guide

Encoding and Decoding Data

There are a number of adapters which only manipulate data (for example, Base64,

SOAP), while others provide transport (for example, HTTP). Chaining these

adapters together provides greatly enhanced functionality.

Using the

-ENCODE and -DECODE commands in combination with the -TRANSPORT

command allows you to effectively combine the encoding/decoding capabilities of

one adapter with the getting or sending of data of another adapter.

Supported Adapters

Almost any adapter can be used as a transport adapter (although it must be used

in its supported contexts). The only adapter that cannot be a transport adapter is

the File adapter because it is the only adapter that is not invoked from the

Resource Manager.

The following adapters can be used as encoding/decoding adapters:

♦ Base64

♦ Quoted-Printable

♦ SOAP

Limitations

The following limitations exist, either by design or due to applied constraints:

♦ There can be only ONE transport adapter in a card. Since the transport

generally represents the end point or start point in a process, it does not make

sense to permit more than one transport adapter.

♦ Encode/decode adapters can be nested. However, the total length of the

command line cannot exceed 260 bytes.