# About This Document This document describes the BEA eLink Adapter for MQSeries component and gives instructions for transferring data between MQSeries and the eLink Platform. This guide explains how to install and configure the eLink Adapter for MQSeries, and how to initiate data transfer requests. The BEA eLink Adapter for MQSeries User Guide is organized as follows: Understanding EAI and the Role of eLink Adapters introduces the eLink Adapter component and explains how eLink Adapter for MQSeries fits into the BEA TUXEDO environment. Installing BEA eLink Adapter for MQSeries explains how to install the eLink Adapter component. Configuring eLink Adapter for MQSeries provides information for configuring BEA TUXEDO servers and the MQSeries Queue Manager, and for mapping the MQI and ATMI API parameters. Running eLink Adapter for MQSeries provides information about booting the BEA TUXEDO server and initiating information transfer requests between a TUXEDO environment and MQSeries. Error Messages describes error and informational messages as well as actions to resolve the errors. ## What You Need to Know This document is intended for system administrators who will install the eLink Adapter on various platforms, as well as programmers who will configure the eLink Adapter and set up TUXEDO services to execute information transfers with MQSeries. This guide assumes knowledge of BEA TUXEDO and IBM MQSeries products. ## e-docs Web Site BEA product documentation is available on the BEA corporate Web site. From the BEA Home page, click on Product Documentation or go directly to the "e-docs" Product Documentation page at http://e-docs.beasys.com. ## How to Print the Document You can print a copy of this document from a Web browser, one file at a time, by using the File->Print option on your Web browser. A PDF version of this document is available on the eLink documentation Home page on the e-docs Web site (and also on the documentation CD). You can open the PDF in Adobe Acrobat Reader and print the entire document (or a portion of it) in book format. To access the PDFs, open the eLink documentation Home page, click the PDF files button and select the document you want to print. If you do not have the Adobe Acrobat Reader, you can get it for free from the Adobe Web site at http://www.adobe.com/. ## Related Information The following BEA publications are also available for more information: BEA TUXEDO Application Development Guide BEA TUXEDO Programmer's Guide BEA TUXEDO Reference Guide ## Contact Us Your feedback on the BEA eLink documentation is important to us. Send us e-mail at docsupport@beasys.com if you have questions or comments. Your comments will be reviewed directly by the BEA professionals who create and update the eLink documentation. In your e-mail message, please indicate that you are using the documentation for the BEA eLink Adapter for MQSeries 1.1 release. If you have any questions about this version of the eLink Adapter, or if you have problems installing and running the eLink Adapter, 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 ## 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 or 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 or 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.
[Table of Contents] [Prev] [Next]