Sample Scenarios for the Data Integration Option

The BEA eLink Data Integration Option uses the eLink Platform product for processing service requests for data mapping and data conversion.

A TUXEDO translation service takes an input buffer, performs a data translation on the buffer, and returns the translated data in an output buffer, exposing the Mercator wrapper for TUXEDO as a service. It also can write output data to queues or files.

For example, to call a map called TOEDI.MMC that produces EDI data in an FML format, the service name would be TOEDI.

Each map has at least one input card and one output card. The service passes the input data to input card 1 and returns data back to the service-requester via output card 1. There may be any number of additional input or output cards (to read from a file or create a file, for example). Output card 1 has a "header" with control information set in the map. This card determines the destination and format of the output buffer. This header is required. See the section entitled "Control Information for TUXEDO /Q" in this document for more details.

This document will describe the following topics:

• Using Data Mapping with a Mainframe Environment

• Using Data Mapping with Multiple Destinations

• Using Data Mapping with Other eLink Adapters

Using Data Mapping with a Mainframe Environment

Figure 2-1 shows how the products and components work together to convert buffers between an FML and a non-FML format and transfer the buffers between a UNIX or Windows NT environment and a mainframe environment.

The BEA eLink for Mainframe gateway asynchronously calls external TUXEDO services, a feature which will be used to call the ELINKDIO server. The ELINKDIO server is a standard TUXEDO MSSQ server that receives a TUXEDO buffer as input, invokes the Mercator data mapping engine, and returns a TUXEDO buffer as output.

Figure 2-1 Data Mapping Scenario of FML to COBOL Copybook to FML

The following description explains the process flow in Figure 2-1 of a TUXEDO client making a request to send an FML buffer from a UNIX environment to a CICS region on a mainframe and return an FML buffer to the TUXEDO client.

1. A TUXEDO client issues a request to send an FML buffer to the mainframe.

2. The request passes the FML buffer to the BEA eLink for Mainframe gateway. The service name in the request causes the gateway to pass the FML buffer to the eLink DIO component to convert the FML buffer to a COBOL copybook format.

3. The eLink DIO component converts the FML buffer to a COBOL copybook and passes it back to the BEA eLink for Mainframe gateway.

   Note: For conversions to COBOL copybook, the COBOL type tree does not contain the eLink DIO header, so you must edit the type tree using the Type Editor. You must add the eLink DIO control header from the FML type tree to output COBOL copybooks.

4. The BEA eLink for Mainframe gateway passes the converted COBOL copybook to the CICS or IMS region on the mainframe.

5. After the requested transaction is complete, the mainframe returns a response by sending the COBOL copybook back to the BEA eLink for Mainframe gateway.

6. The BEA eLink for Mainframe gateway passes the copybook to the eLink DIO for conversion back to an FML buffer.

7. After the copybook is converted to an FML buffer, it is passed back to the BEA eLink for Mainframe gateway.

8. The BEA eLink for Mainframe gateway then passes the FML buffer response to the TUXEDO client.

The data mapping process uses a TUXEDO environment that includes the eLink Platform and the BEA eLink Data Integration Option products. Figure 2-2 shows how the products work together to convert buffers between an FML and a non-FML format.

The ELINKDIO server is a standard TUXEDO MSSQ server that receives a TUXEDO buffer as input, invokes the Mercator data mapping engine, converts the buffer to another format and then passes it to multiple destinations.

Figure 2-2 Converting FML to New Format and Passing to Multiple Destinations

The following description explains the process flow in Figure 2-2 of a TUXEDO client making a request to send an FML buffer to multiple applications.

1. A TUXEDO client issues a request to send an FML buffer to multiple applications.

2. The request passes the FML buffer to the eLink Data Integration Option to convert the FML buffer to another buffer format.

3. The eLink Data Integration Option converts the FML buffer to the new format and passes it to the appropriate applications.

   Note: The mapping to multiple destinations is done through Mercator input and output cards. For information on defining input and output cards, refer to the Mercator documentation.

A particular use of the eLink Data Integration Option component allows for processing of FML32 Value buffers. Figure 2-3 shows how to map a Mercator tag to an FML32 field that then points to the actual data buffer. Once the actual data buffer is located, only it is passed to the eLink Data Integration Option application for conversion.

Figure 2-3 Passing an FML32 Value Buffer

1. The FML32 name contains the actual data buffer to be passed to the eLink DIO component.

   Note: The FML32_VAL_FLD specifies the name of the FML32 field in the input buffer which contains data for processing. This parameter replaces the MERCATOR_FV_IN field used in previous releases of eLink DIO.

2. The data is extracted from the FML32 field and sent directly to Mercator for mapping.

The data mapping process uses an eLink Platform environment that includes the eLink Platform and the BEA eLink Data Integration Option products as well as other eLink Adapters. For example, Figure 2-4 shows how the products and components work together to convert buffers between an FML and a non-FML format and then pass a request to an eLink Adapter.

Figure 2-4 Data Mapping Scenario of FML with eLink DIOs

The following description explains the process flow for invoking eLink DIO directly from the client to transform data prior to sending it to an eLink Adapter. The same process could be used after receiving data from an eLink Adapter to transform it back to an eLink Platform format.

1. An eLink Platform client calls eLink DIO to transform data to a format usable by an eLink Adapter.

2. The eLink DIO software sends the transformed data back to eLink Platform.

3. BEA eLink Platform calls the eLink Adapter to process the data.

4. After the eLink Adapter processes the data, it passes the response back to eLink Platform.

5. The resulting data from the eLink Adapter is passed to the eLink DIO to be transformed into an eLink Platform-compatible format, such as FML.

6. The eLink DIO transforms the data to an eLink Platform-compatible format, such as FML, and passes it back to eLink Platform.