Introduction to BEA WebLogic JRockit

Welcome to BEA WebLogic JRockit 8.1 Beta, the first commercial server-side Java Virtual Machine. JRockit was developed uniquely for server-side applications and optimized for Intel architectures to ensure reliability, scalability, manageability, and flexibility for Java applications. This user guide provides instructions for using JRockit on the Window and Linux platforms.

This section contains information on the following subjects:

• What is JRockit?
• Why Should I Use JRockit?
• What Platforms Does JRockit Support?
• How to Print JRockit Documents
• Documentation Conventions
• JRockit Support

 

---

What is JRockit?

BEA WebLogic JRockit 8.1 Beta is the only credible high performance Java Virtual Machine (JVM) developed uniquely for server-side applications and optimized for Intel architectures. JRockit is designed to ensure reliability, scalability, manageability, and flexibility for Java applications. A crucial component of the BEA WebLogic Platform, WebLogic JRockit delivers a new level of performance for Java applications deployed on any kind of hardware architecture at significantly lower costs to the enterprise. Furthermore, it is the only enterprise-class JVM optimized for Intel Architecture, providing seamless interoperability across multiple hardware and operating system configurations.

 

---

Why Should I Use JRockit?

There are two critical reasons for using BEA WebLogic JRockit:

• JRockit is designed for server-side applications.

If you are running server-side applications, JRockit is the most effective VM you can use. A server-side VM is designed with server applications in mind. Server-side applications have very different requirements than client-side applications and demand different behavior from a VM. These applications generally do not use graphical user interfaces, run for longer periods of time, and are usually parallel and thread intensive. To fully exploit server-side applications and ensure optimal performance, you VM should employ a server-specific design policy.

• JRockit employs adaptive optimization to significantly improve runtime performance.

Adaptive optimization is a JRockit feature that detects and removes bottlenecks in a running program, significantly improving program performance. Adaptive optimization can result in code with better performance than statically compiled code because it has access to more information regarding the running program. Another advantage is that the code does not lose any of the dynamic characteristics of interpreted languages.

 

---

What Platforms Does JRockit Support?

BEA WebLogic JRockit 8.1 Beta, running with JS2E version 1.4.1, supports the following platforms:

• Microsoft Windows 2000 SP2 (Intel Pentium / Xeon and compatible servers)
• Microsoft Windows .NET ES RC1 (Intel Itanium 2 servers)
• Red Hat Linux Advanced Server 2.1 (Intel Pentium / Xeon and compatible servers)
• Red Hat Linux Advanced Server 2.1 IPF (Intel Itanium 2 servers)

How to Print JRockit Documents

You can print a copy of this user guide from a Web browser, one file at a time, by using the File—>Print option on the browser.

A PDF version of this user guide is available on the JRockit 8.1 Beta 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:

1. Open the web page for the JRockit 8.1 Beta 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.

2. Click the print button on the Adobe Acrobat Reader toolbar.

   The Print dialog box appears.

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

 

---

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

 

 

---

JRockit Support

Should you experience any problems or find any bugs, please send us an e-mail at [e-mail]. We would appreciate if you could provide as much information as possible about the problem, for example:

• Hardware
• Version
• The program you ran
• Stack dumps (if any)
• A small code example that will reproduce the error.