Data Transformation Engine Services Guide

Chapter 6 – Service Usage Scenarios

There are four scenarios in which the CORBA Transformation service can be used to transform data.

They are examined in this chapter.

In the following diagrams, this arrow ( ) represents the code flow (invoke, request or reply) and

this arrow ( ) represents the data flow (input or output).

A Client Requests to Execute a Map

In this scenario, the CORBA Client makes a request to the CORBA Server. The CORBA Server

executes a map and transforms the input data according to the map settings but does not return the

transformed data back to the client.

The CORBA request contains the name of the compiled map file. The CORBA Transformation Server

invokes the RunMap function of the Platform API and executes the specified map. The DTE reads the

input data according to the map input settings, transforms the data, and writes out the transformed data

as per the map output settings.

The following line shows the command at the prompt to run the CORBA Client (

dteorbclnt):

The first argument ContactToLabel.nsk is the name of the compiled map to be executed.

In the NonStop DTE sample client C++ code, the CORBA Transformation Client makes the CORBA

transform() API call similarly to the following statements:

The first parameter argv[1] contains the name of the map (ContactToLabel.nsk) from the command

line. The third parameter 0 indicates that no transformed data will be sent back and the return value

outData will be an empty string.

The command string that dteorbserv forms and assigns to the lpszDataToApp field of the

EXITPARM structure is ContactToLabel.nsk

CORBA

Client

CORBA

Server

DTEORBServ_var lp_DTEORBServ_obj; …

char *outData = lp_DTEORBServ_obj ->transform(argv[1], “”, 0);

: dteorbclnt ContactToLabel.nsk