Data Transformation Engine Services Guide

Chapter 1 – Tuxedo Transformation Server
13
3 List these maps in the configuration file mercserv.cfg.
4 Modify an existing ubb file to add mercserv as a server.
5 Execute tmloadcf to process this ubb file.
6 Boot up Tuxedo (tmboot).
7 Send data to a service that has the name of one of the maps created and registered in
steps 2 and 3.
8 The response message will be the data returned from the output card specified in the
configuration file in step 3.
Using the Importer Wizard to Generate BEA Tuxedo Type
Trees
The BEA Tuxedo type trees can be generated using the Importer Wizard in the Type Designer. The
Importer Wizard uses FML field description files and View files to generate the type trees. See the
Type Designer Reference Guide.
FML Importer Type Tree Generation
The importer reads the FML file and the field names found in the FML field description file. The
selected list of data fields is used to produce a type tree. The type tree contains a partitioned group
which contains all of the selected fields from the FML file. This type tree contains the field names as
initiators, not the numeric field IDs.
View Importer Type Tree Generation
The importer generates a tree from a View Description file, a View Object file, or a View Disassembly
file. If the input is a View Description file, the file is compiled and then disassembled automatically.
If the input is a View Object File, the file is disassembled automatically. The importer then reads the
specified or generated view disassembly file and produces the type tree. The disassembly file contains
the names of the fields, the field types and the offsets into the structure. The offsets are critical, as the
same view may have different offsets on different platforms.
The importer creates padding bytes to ensure that the type tree generated represents the view
corresponding to the disassembly file specified.