BEA Logo BEA eLink Adapter for R/3 ALE Release 1.6

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   eLink Adapter for R/3 ALE Doc Home   |   BEA eLink Adapter for R/3 ALE User Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

About This Document

 

This document provides instructions for installing and configuring the BEA eLink Adapter for R/3 ALE product on a UNIX or Windows NT system.

The BEA eLink Adapter for R/3 ALE User Guide is organized as follows:

 


What You Need to Know

This document is intended for system managers who are responsible for installing products in the UNIX or Windows NT environments and for configuring layered products. Portions of this guide are intended for experienced R/3 users with knowledge of ALE configuration.

 


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 BEA eLink Adapter for R/3 ALE 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 BEA eLink Adapter for R/3 ALE documentation Home page, click the PDF files button and select the document you want to print.

If you do not have Adobe Acrobat Reader, you can get it for free from the Adobe Web site at http://www.adobe.com/.

 


Contact Us!

Your feedback on the BEA eLink Adapter for R/3 ALE 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 BEA eLink Adapter for R/3 ALE documentation.

In your e-mail message, please indicate that you are using the documentation for the BEA eLink Adapter for R/3 ALE 1.6 release.

If you have any questions about this version of BEA eLink Adapter for R/3 ALE, or if you have problems installing and running BEA eLink Adapter for R/3 ALE, 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:

 


Documentation Conventions

The following documentation conventions are used throughout this document.

Convention

Item

boldface text

Terms defined in the glossary.

Ctrl+Tab

You must press two or more keys simultaneously.

italics

Emphasis or book titles.

monospace text

Code samples, commands and their options, data structures and their members, data types, directories, and file names and their extensions. Monospace text also indicates text that you must enter from the keyboard.

Examples:

#include <iostream.h> void main ( ) the pointer psz

chmod u+w *

\tux\data\ap

.doc

tux.doc

BITMAP

float

monospace boldface text

Significant words in code.

Example:

void commit ( )

monospace italic text

Variables in code.

Example:

String expr

UPPERCASE TEXT

Device names, environment variables, and logical operators.

Examples:

LPT1

SIGNON

OR

{ }

A set of choices in a syntax line. The braces themselves should never be typed.

[ ]

Optional items in a syntax line. The brackets themselves should never be typed.

Example:

buildobjclient [-v] [-o name ] [-f file-list]... [-l file-list]...

|

Separates mutually exclusive choices in a syntax line. The symbol itself should never be typed.

...

One of the following in a command line:

  • That an argument can be repeated several times in a command line.

  • That the statement omits additional optional arguments.

  • That you can enter additional parameters, values, or other information.

    The ellipsis itself should never be typed.

    Example:

    buildobjclient [-v] [-o name ] [-f file-list]... [-l file-list]...

.
.
.

Omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.