		BEA eLink Data Integration Option 1.2 Information Center
		HOME \| SEARCH \| CONTACT \| PDF FILES \| WHAT'S NEW
		TABLE OF CONTENTS \| PREVIOUS TOPIC \| NEXT TOPIC

Preface

BEA eLink Mercator Integrator for DIO (hereafter referenced as eLink Integrator) is a component of the eLink Data Integration Option (eLink DIO) that runs with the BEA TUXEDO product as well as other BEA products.

Purpose of This Document

This document describes the BEA eLink Integrator component and gives instructions for using the tool for data mapping. This guide explains how to install and use the eLink Integrator component and how this component fits into the BEA TUXEDO environment.

Who Should Read This Document

This document is intended for system administrators who will configure and administer eLink Integrator as well as programmers who will map FML buffers to non-FML buffer types. This guide assumes knowledge of BEA TUXEDO, BEA eLink for Mainframe, TSI Mercator, and SAP R/3 products. This guide also assumes knowledge of the C programming language. In addition, programmers will find useful pointers for developing client programs and service routines that send data through eLink Integrator.

How This Document Is Organized

The BEA eLink Mercator Integrator for DIO User Guide is organized as follows:

Understanding the Data Integration Option introduces the eLink Integrator component and explains how eLink Integrator fits into the BEA TUXEDO environment.
Installing BEA eLink Integrator explains how to install the eLink Integrator component.
Configuring the Environment for eLink Integrator provides information for configuring BEA TUXEDO and BEA eLink for Mainframe to run with the eLink Integrator component to handle service requests for data mapping.
Data Mapping Conversion provides information about using the eLink Integrator component to define the rules for data mapping. It includes information for developing the rules for data mapping and executing a TUXEDO service request for data mapping.
Transaction Support describes support for TUXEDO transactions integrated with the existing Mercator rollback functionality.
Error and Informational Messages describes error and informational messages as well as actions to resolve the errors.
Data Mapping Worksheet is a planning worksheet for the data mapping installations, configurations and tasks.

How to Use This Document

The BEA eLink Mercator Integrator for DIO User Guide is designed primarily as a printed document; however, a PDF version of the document is available on the product CD.

Opening the Document in a Web Browser

To access the online version of this document if it is installed on a Web server, open the following HTML file:

http://(directory path to eLink Integrator documentation)/index.htm

Note: The online documentation requires a Web browser that supports HTML 3.0. Netscape Navigator 4.0 or higher or Microsoft Internet Explorer 4.0 or higher are recommended.

Document Conventions

The following documentation conventions are used throughout this document:

Item Examples

Variable names

Variable names represent information you must supply or output information that can change; they are intended to be replaced by actual names. Variable names are displayed in italics and can include hyphens but not underscores. The following are examples of variable names in text:
error-file-name
The when-return value...

User input and screen output

For screen displays and other examples of input and output, user input appears as in the first of the following lines; system output appears as in the second through fourth lines:
dir c:\accounting\data

Volume in drive C is WIN_NT_1 Volume Serial Number is 1234-5678 Directory of C:\BEADIR\DATA

Syntax

Code samples can include the following elements:

Variable names can include hyphens but not underscores (e.g., error-file-name)

Optional items are enclosed in square brackets: [ ]. If you include an optional item, do not code the square brackets.

A required element for which alternatives exist is enclosed in braces {}. The alternatives are separated by the pipe (vertical bar) character: |. You must include only one of the alternatives for that element. Do not code the braces or pipe character.

An ellipsis ( ... ) indicates that the preceding element can be repeated as necessary.

Omitted code

An ellipsis ( ... ) is used in examples to indicate that code that is not pertinent to the discussion is omitted. The ellipsis can be horizontal or vertical.

Environment variables

Environment variables are formatted in an uppercase font.
ENVFILE=${APPDIR}

Key names

Key names are presented in boldface type.
Press Enter to continue.

Literals

Literals are formatted in a monospace font.
class extendSample

Window items

Window items are presented in boldface type. Window items can be window titles, button labels, text edit box names or other parts of the window.
Type your password in the Logon window.
Select Export to make the service available to the client.

Item	Examples
Variable names	Variable names represent information you must supply or output information that can change; they are intended to be replaced by actual names. Variable names are displayed in italics and can include hyphens but not underscores. The following are examples of variable names in text: error-file-name The when-return value...
User input and screen output	For screen displays and other examples of input and output, user input appears as in the first of the following lines; system output appears as in the second through fourth lines: `dir c:\accounting\data` `Volume in drive C is WIN_NT_1 Volume Serial Number is 1234-5678 Directory of C:\BEADIR\DATA`
Syntax	Code samples can include the following elements: Variable names can include hyphens but not underscores (e.g., error-file-name) Optional items are enclosed in square brackets: [ ]. If you include an optional item, do not code the square brackets. A required element for which alternatives exist is enclosed in braces {}. The alternatives are separated by the pipe (vertical bar) character: \|. You must include only one of the alternatives for that element. Do not code the braces or pipe character. An ellipsis ( ... ) indicates that the preceding element can be repeated as necessary.
Omitted code	An ellipsis ( ... ) is used in examples to indicate that code that is not pertinent to the discussion is omitted. The ellipsis can be horizontal or vertical.
Environment variables	Environment variables are formatted in an uppercase font. ENVFILE=${APPDIR}
Key names	Key names are presented in boldface type. Press Enter to continue.
Literals	Literals are formatted in a monospace font. `class extendSample`
Window items	Window items are presented in boldface type. Window items can be window titles, button labels, text edit box names or other parts of the window. Type your password in the Logon window. Select Export to make the service available to the client.

Contact Information

The following sections provide information about how to obtain support for the documentation and software.

Documentation Support

If you have questions or comments on the documentation, you can contact the BEA Information Engineering Group by e-mail at docsupport@beasys.com (For information about how to contact Customer Support, refer to the following section.)

Customer Support

If you have any questions about this version of BEA eLink Integrator, or if you have problems installing and running BEA eLink Integrator, contact BEA Customer Support through BEA WebSupport at www.beasys.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

Your name, e-mail address, phone number, and fax number
Your company name and company address
Your machine type and authorization codes
The name and version of the product you are using
A description of the problem and the content of pertinent error messages

TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC