Preface

Purpose of This Document

This document describes how to install and configure the BEA M3 (hereafter referred to as M3) software.

Who Should Read This Document

This document is intended for the M3 software installers and system administrators.

How This Document Is Organized

Chapter 1, "Preparing to Install the M3 Software," describes how to prepare to install the M3 software.
Chapter 2, "Installation on Microsoft Windows NT, 95, and 98 Systems," describes how to install the M3 software on Microsoft Windows NT, 95, and 98 systems.
Chapter 3, "Installation on UNIX Systems," describes how to install the M3 software on UNIX systems.
Chapter 4, "BEA Administration Console Startup," describes how to start the BEA Administration Console.
Chapter 5, "Postinstallation Considerations," discusses postinstallation issues.
Appendix A, "Platform Data Sheets," provides data sheets for each Microsoft Windows and UNIX platform that can be used to run the M3 software.

Documentation Conventions

The following documentation conventions are used throughout this document.

Convention Item

boldface text

Indicates terms defined in the glossary.

Ctrl+Tab

Indicates that you must press two or more keys simultaneously.

italics

Indicates emphasis or book titles.

monospace text

Indicates 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 * .doc
BITMAP
float

monospace boldface text

Identifies significant words in code.
Example:
void commit ( )

monospace italic text

Identifies variables in code.
Example:
String expr

UPPERCASE TEXT

Indicates device names, environment variables, and logical operators.
Examples:
LPT1
SIGNON
OR

{ }

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

[ ]

Indicates 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.

...

Indicates 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]...

. . .

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

Convention	Item
boldface text	Indicates terms defined in the glossary.
Ctrl+Tab	Indicates that you must press two or more keys simultaneously.
italics	Indicates emphasis or book titles.
`monospace text`	Indicates 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 * .doc` `BITMAP` `float`
`monospace boldface text`	Identifies significant words in code. Example: `void` `commit` `( )`
`monospace italic text`	Identifies variables in code. Example: `String` `expr`
UPPERCASE TEXT	Indicates device names, environment variables, and logical operators. Examples: LPT1 SIGNON OR
`{ }`	Indicates a set of choices in a syntax line. The braces themselves should never be typed.
`[ ]`	Indicates 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.
`...`	Indicates 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``]...`
`. . .`	Indicates the omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.