Introduction to JRockit SDK

Using the Documentation

This section provides hints for using the BEA JRockit SDK documentation set. It includes information on the following subjects:

• BEA JRockit SDK Documentation Set
• Printing These Documents
• Understanding Documentation Conventions

 

---

BEA JRockit SDK Documentation Set

The documentation set is comprised of these documents:

• Release Notes and assorted web documents
• Introduction to BEA JRockit 1.4.2 SDK

This document serves as an overview of BEA JRockit. It allows anyone, from managers to any personnel down through the organization to gather all essential background about the product without having to read through procedural information normally included in a user guide or development guide.

• Installing BEA JRockit 1.4.2 SDK

This web document contains information for installing BEA JRockit SDK as a standalone application.

• Using BEA JRockit 1.4.2 SDK

This is the BEA JRockit SDK user guide. It describes such functions as selecting and running a memory management system, configuring the JVM, and using the BEA JRockit Management Console.

• Tuning BEA JRockit 1.4.2 JVM

This is the BEA JRockit JVM tuning guide. It includes tuning guidelines for heap and thread management along with tips and techniques for tuning BEA JRockit JVM to ensure optimal performance with your Java applications.

• Developing Applications

The guide contains tips and techniques for developing applications to run successfully on a JVM, particularly BEA JRockit. It includes a detailed troubleshooting guide, information on implementing profiling and debugging interfaces, and instructions for migrating applications developed on a third-party JVM (for example, Sun Microsystem's HotSpot JVM) to BEA JRockit JVM.

These documents can be found at:

http://download.oracle.com/docs/cd/E13188_01/jrockit/docs142/index.html

 

---

Printing These Documents

You can print a copy of any BEA JRockit SDK document from a Web browser, one file at a time, by using the File—>Print option on the browser.

PDF versions of all BEA JRockit documents are available on the BEA JRockit documentation pages on the e-docs Web site. You can open the PDF in Adobe Acrobat Reader and print the entire document (or a portion of it) in book format. To access and print the PDFs, do the following:

Open the web page for the BEA JRockit document you want to print and click the view as PDF icon.

A new browser launches, running the Adobe Acrobat Reader, which contains the PDF version of the document you selected.

Click the print button on the Adobe Acrobat Reader toolbar.

The Print dialog box appears.

Select the Print range (All, Current page, or Pages from) and click OK to print the document.

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

 

---

Understanding Documentation Conventions

The following documentation conventions are used throughout this document.

Convention	Item
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 filenames 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	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.