Data Transformation Engine Services Guide

Chapter 5 – CORBA Transformation Client

Chapter 5 – CORBA Transformation

Client

You can develop your own CORBA client to perform the transformation for your data. The CORBA

clients that need to invoke DTE CORBA Transformation Server have to import the server IDL. The

client has to invoke the transform(…) method on DTE CORBA Transformation Server with

appropriate arguments.

A sample CORBA Transformation Client (dteorbclnt) is included on the NonStop DTE CD. This client

application takes up to three command line arguments. Depending on the command line arguments, the

CORBA Transformation Client can invoke the CORBA Transformation Server with the appropriate

map name, supplying its own input data through reading a file, and requesting output data back as a

response.

The command line arguments for dteorbclnt are ordered as follows:

The arguments’ meanings are positional. The client application is dteorbclnt. The first argument is the

compiled map name with the .nsk file extension. The map files must be in the same directory as the

dteorbserv executable. The next argument is the file name of the client-supplied input data or “”

(empty string if there is no input card override). The next argument is the output card number that will

be used for output override. If this number is 0, no output card is overridden and no output data is sent

back. If this is a valid output card number, the output data is sent back to the client. Whenever the

output data is sent back to the client, the returned data is printed to the console.

For example, to call a map called ContactToLabel.nsk, which produces a mail label from contact

information, and pass input data in a myContact.txt file without receiving output data, you would

execute the command dteorbclnt ContactToLabel.nsk myContact.txt 0. Detailed command lines for

each usage scenario are provided in the next section.

dteorbclnt ma

name.mmc in

utFilename out

utCardNumber