Introduction to JRockit JDK
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
BEA JRockit JDK is very similar, in the file layout, to the Sun JDK, except that it includes a new JRE with the BEA JRockit JVM and some changes to the Java class libraries (however, all of the class libraries have the same behavior in BEA JRockit as in the Sun JDK). For a more detailed description of the differences between the two JDKs, please refer to File Differences Between BEA JRockit JDK and Sun HotSpot JDK.
This section describes the contents of the BEA JRockit JDK and compares a BEA JRockit JDK installation to a comparable Sun JDK installation. It includes information on the following subjects:
This section describes the various components that make up the BEA JRockit JDK. It also identifies the folder in which these components reside.
Development tools and utilities help you develop, execute, debug, and document programs written in the Java programming language. The BEA JRockit JDK includes the standard tools commonly distributed with the typical Java JDKs. While most of these are standard JDK tools and are proven to work well with Java development projects, you are free to use any other third party tools, compilers, debuggers, IDEs, and so on that might work best in your situation. The tools included with BEA JRockit JDK are:
Javac
compiler Jdb
debuggerJavadoc
, which is used to create an HTML documentation site for the JVM APIFor more information on these tools, please refer to Sun Microsystem's JavaTM 2 JDK at:
http://java.sun.com/j2se/1.5.0/index.jsp
Additional class libraries and support files required by the development tools.
Header files that support native-code programming using the Java Native Interface and the Java Virtual Machine Tools Interface and other functionality of the Java 2 Platform.
The BEA JRockit Management Console is used to monitor and control running instances of the JRockit JVM. It provides real-time information about the running application's characteristics, which can be used both during development-for example, to find where in an application's life cycle it consumes more memory-and in a deployed environment-for example, to monitor the system health of a running application server.
The BEA JRockit implementation of the Java 2 runtime environment for use by the JDK. The runtime environment includes the BEA JRockit JVM, class libraries, and other files that support the execution of programs written in Java.
By definition, the JVM is BEA JRockit JVM, as described in this documentation set.
In addition to JRE components specific to BEA JRockit JDK, the JRE also contains components found in the Sun implementation of the JRE. For a complete list of the standard J2SE JRE features, see the Sun documentation:
http://java.sun.com/j2se/1.5.0/docs/index.html
Table 3-1 and Table 3-2 list the differences between BEA JRockit JDK and Sun Microsystems' HotSpot JDK. The tables list, by component and operating system (OS/arch), files that either exist in HotSpot or BEA JRockit
Note: $ARCH
= i386 on Linux IA32, but $ARCH
= x86_64
on Linux Itanium and mydir[/*]
means mydir
and mydir/*
BEA JRockit configuration and tuning parameters are set by using specific command line options, which you can enter either along with the start-up command or include in a start-up script. These options are discussed in the relevant sections of the BEA JRockit documentation set; that is:
http://download.oracle.com/docs/cd/E13188_01/jrockit/docs50/userguide/start.html#1015884
http://download.oracle.com/docs/cd/E13188_01/jrockit/docs50/userguide/memman.html#1013105
http://download.oracle.com/docs/cd/E13188_01/jrockit/docs50/tuning/index.html
You can also find an alphabetical list of all BEA JRockit command line options at:
![]() ![]() |
![]() |
![]() |