Preface

Purpose of This Document

This document describes how to install and configure the BEA WebLogic Enterprise (sometimes referred to as WLE) software.

Note: Effective February 1999, the BEA M3 product is renamed. The new name of the product is BEA WebLogic Enterprise (WLE). Who Should Read This Document

This document is intended for the WLE software installers and system administrators. How This Document Is Organized

The Installation Guide is organized as follows:

Part 1, which includes Chapters 1 through 5, describes how to install the WebLogic Enterprise (C++) software, including the BEA Administration console. Separate chapters describe the installation procedure on the Microsoft Windows and UNIX platforms.
Part 2, which includes Chapters 6 through 8, describes how to install the WebLogic Enterprise (Java) software. Separate chapters describe the installation procedure for the Microsoft Windows NT and Solaris platforms.
Appendix A provides data sheets for the platforms that are supported for the WebLogic Enterprise (C++) software.
Appendix B provides data sheets for the platforms that are supported for the WebLogic Enterprise (Java) 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 firstfile-syntax]
[-l lastfile-syntax] -P

|

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:
genicf [options] idl-filename...

. . .

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 firstfile-syntax] [-l lastfile-syntax] -P
`\|`	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: `genicf [options] idl-filename...`
`. . .`	Indicates the omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.

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 the BEA WebLogic Enterprise product, or if you have problems installing and running the BEA WebLogic Enterprise software, 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

[Top] [Prev] [Next] [Bottom]

Preface

Purpose of This Document

Related Documentation

Contact Information