T3270 Transport Project User Guide

The T3270 connector allows data to read and written to a 3270 (Telnet) session. The connector is based on FreeHost3270.

CONFIGURATION

All configuration for the connector is made on the endpoint. The connector supports both inbound and outbound endpoints. The address is configured using T3270 as protocol.

<endpoint address="T3270://host.company.com:23"/>

The main part of the configuration is defining a sequence of commands that will be performed during the session. This is done using a map, named "commands", within the endpoint properties.

<endpoint address="T3270://host.company.com:23">
    <properties>
        <map name="commands">{color}
          <!-- MORE ON THIS FURTHER DOWN -->
        </map>
    </properties>
</endpoint>

 There are three different types of commands availabe:

• SEND
• SENDKEY
• GET

To achieve flexibility these commands can be combined into a sequence of commands that the connector should execute during the session. Each command has different syntax.

SEND SYNTAX

The SEND command is used for sending values into different fields. The syntax looks like this:

SEND(startPos-endPos=value) where startPos is the position where the field start and endPos is the position where it ends. These values are numeric.

It's also possible to send multiple values to the same screen. This can be done using ; as separator:

SEND(startPos-endPos=value;startPos2-endPos2=value2)

The connector allows parameter placeholders like {$property}. The placeholder can be the payload, bean fields and message properties.

SEND(startPos-endPos={$property};startPos2-endPos2={$payload})

This applies for all command types.

SENDKEY SYNTAX

The SENDKEY command is used for sending key strokes to the terminal screen. For the moment only F1-F12 is supported but it's very easy to increase.

SENDKEY(F8)

GET SYNTAX

The GET command is user for retrieving field values. When using GET it has to be the last command in a sequence. GET syntax:

GET(startPos-endPos) where startPos is the position where the field start and endPos is the position where it ends. These values are numeric.

As with the SEND command it's possible to configure multiple fields to retrieve.

GET(startPos-endPos;startPos2-endPos2)

The connector will return a java.util.List

CONFIGURE A SEQUENCE

Since it's most common that fields you want to get, or functions you want to execute, requires that you go through different screens before they are available, the connector can be configured to perform a sequence of commands. This means that multiple SEND commands can be executed before a GET command is executed and so on. A sequence is configured using a map, named "commands", containing properties (commands). Every single property (command) is named using a sequence number that tells the connector in which order to perform the commands.

<endpoint address="T3270://host.company.com:23">
    <properties>
        <map name="commands">
           <property name="0" value="SEND(240-1920={$action})"/>
           <property name="1" value="SEND(254-266={$user};414-422={$password})"/> 
           <property name="3" value="SENDKEY(F8)"/>
           <property name="4" value="GET(754-794;914-954)"/>
        </map>
    </properties>
</endpoint>

POLLING

When using T3270 transport as inbound endpoint, it's possible to configure polling. This is done using the pollingFrequency property, used by other transports. This is configured on the endpoint:

<endpoint address="T3270://host.company.com:23">
    <properties>
        <!-- how many milliseconds between each poll -->
        <property name="pollingFrequency" value="5000"/>
        <map name="commands">
            <property name="0" value="SEND(240-1920={$action})"/>
            <property name="1" value="SEND(254-266={$user};414-422={$password})"/>
            <property name="3" value="SENDKEY(F8)"/>
            <property name="4" value="GET(754-794;914-954)"/>
        </map>
    </properties>
</endpoint>