Introduction to JRockit SDK
BEA JRockit SDK is very similar 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 SDKs, please refer to File Differences Between BEA JRockit SDK and Sun HotSpot SDK.
This section describes the contents of the BEA JRockit 1.4.2 SDK and compares a BEA JRockit SDK installation to a comparable Sun SDK installation. It includes information on the following subjects:
This section describes the various components that make up the BEA JRockit 1.4.2 SDK. 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 1.4.2 SDK includes the standard tools commonly distributed with the typical Java SDKs. 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 1.4.2 SDK are:
Javac
compiler Jdb
debuggerFor more information on these tools, please refer to Sun Microsystem's JavaTM 2 SDK Tools and Utilities website at:
http://java.sun.com/j2se/1.4/docs/tooldocs/tools.html
Additional class libraries and support files required by the development tools.
Header files that support native-code programming using the Java Native Interface, the Java Virtual Machine Debugger Interface, the Java Virtual Machine Profiler Interface and other functionality of the Java 2 Platform.
The BEA JRockit Management Console is used to monitor and control running instances of BEA 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 SDK. 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 SDK (found in /jre
), the JRE also contains components found in the Sun implementation of the JRE. Table 3-1 lists these components.
APIs that facilitate software service and maintenance at customer sites by producing log reports suitable for analysis by end users, system administrators, field service engineers, and software development teams. |
||
An API that extends the Java platform's Write Once, Run AnywhereTM capability to reusable component development. |
||
APIs that enable application internationalization, the process of designing an application so that it can be adapted to various languages and regions without engineering changes. |
||
An API that provides a way for applications to store and retrieve user and system preference and configuration data. |
||
A unified architecture for representing and manipulating collections, allowing them to be manipulated independently of the details of their representation. |
||
The interface for writing Java native methods and embedding the JVM into native applications. |
||
APIs for program security, cryptography, signing, and so on. |
||
APIs providing fundamental classes for the designing the JavaTM programming language. |
The java.lang.* and java.util.* Packages Documentation Contents |
|
APIs providing support for the event model, collections framework, date and time facilities. |
The java.lang.* and java.util.* Packages Documentation Contents |
|
New I/O (NIO) APIs introduced in J2SE 1.4 to provide new features and improved performance in the areas of buffer management, scalable network and file I/O, character-set support, and regular-expression matching. |
||
APIs that provide support for sockets, URL authentication, and so on. |
||
Interfaces and classes responsible for specifying the remote behavior of the Remote Method Invocation (RMI) system, as defined in the |
||
An API that provides universal data access from the JavaTM programming language. Using the JDBC 3.0 API, you can access virtually any data source, from relational databases to spreadsheets and flat files. |
||
JNDI Toolkit (AWT) supports Graphical User Interface (GUI) programming. |
An interface that provides naming and directory functionality to applications written in Java. This API is independent of any naming or directory service implementation |
|
An Object Request Broker (ORB) and two CORBA programming models that use the Java CORBA ORB and Internet InterORB Protocol (IIOP). |
CORBA Technology and the JavaTM 2 Platform, Standard Edition |
|
One of the JavaTM Foundation Classes (JFC) that implements a set of GUI components with a pluggable look and feel. |
||
A toolkit that supports Graphical User Interface (GUI) programming. |
||
An API for capturing, processing, and playing back audio and MIDI (Musical Instrument Digital Interface) data. |
||
An input method framework that enables the collaboration between text editing components and input methods in entering text. |
||
An API comprised of classes for advanced 2D graphics and imaging. It encompasses line art, text, and images in a single comprehensive model. |
||
APIs, utilities, and other components for making applications accessible to disabled persons. |
||
A component that enables applets written to the Java 2 Platform 1.4 specification to be run in Netscape Navigator and Microsoft Internet Explorer web browsers. |
This section describes how BEA JRockit SDK differs from Sun Microsystems' HotSpot SDK. Each table below lists, by component and operating system (O/S), files that either exist in HotSpot SDK 1.4.2 or BEA JRockit SDK.
$ARCH
= i386 on linux32, but $ARCH
= ia64 on linux64mydir[/*]
means mydir and mydir/*
|
||