# Installing WebLogic Real Time, Core Edition

# Preparing for Your Installation

The following sections provide information that you need to know before installing your BEA WebLogic® Real Time, Core Edition software:

- Installation Overview
- Installable Product Components
- Product Distribution Methods
- Installation Prerequisites
- Selecting Directories for Your Installation
- Generating a Verbose Installation Log
- Generating a Verbose Installation Log

## Installation Overview

The BEA Products installation program provides a complete framework for the installation and uninstallation of WebLogic Real Time, Core Edition or individual components, as desired.

### Installation Modes

The BEA Products installation program can be used in the following modes:

- Graphical mode

Graphical-mode installation is an interactive, GUI-based method for installing your software. It can be run on both Windows and Unix systems. For installation procedures, see Running the Installation Program in Graphical Mode.

Note: | If you want to run graphical-mode installation, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for Unix systems do. If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.

- Console mode

Console-mode installation is an interactive, text-based method for installing your software from the command line, on either a Unix system or a Windows system. For instructions for using this method, see Running the Installation Program in Console Mode.

- Silent mode

Silent-mode installation is a noninteractive method of installing your software that requires the use of an XML properties file for selecting installation options. You can run silent-mode installation in either of two ways: as part of a script or from the command line. Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. For instructions, see Running the Installation Program in Silent Mode.

## Installable Product Components

WebLogic Real Time, Core Edition supports Java applications running in WebLogic Server 8.1 (SP2 and later) and WebLogic Server 9.1 (and later) environments, as well as supporting standalone Java applications or Spring-Framework based applications running on J2SE 1.4.2 or 5.0 runtime environments.

Using the BEA Products installation program, you can install the following WebLogic Real Time, Core Edition 1.1 (MP01) software on your system:

- BEA JRockit 1.4.2 R27.1 JDK for WebLogic Server 8.1 (SP2 and later) — Includes the Deterministic Garbage Collector (GC) and the JRockit Runtime Analyzer (JRA) tool, as well as a WebLogic domain configuration template (`wl-realtime.jar`) for creating an 8.1 SP2 or later domain with Deterministic GC enabled. The installer also includes sample startup scripts, `startRealTime` (`.cmd/.sh`), that demonstrate how to start BEA JRockit with Deterministic GC enabled, which may be useful for Spring-based applications that are using some WebLogic Server facilities.
- BEA JRockit 5.0 R27.1 JDK for WebLogic Server 9.1 (and later) — Includes the Deterministic Garbage GC and the JRA tool, as well as a WebLogic domain configuration template (`wl-realtime.jar`) for creating a 9.1 or later domain with Deterministic GC enabled. The installer also includes sample startup scripts, `startRealTime` (`.cmd/.sh`), that demonstrate how to start BEA JRockit with Deterministic GC enabled, which may be useful for Spring-based applications that are using some WebLogic Server facilities.
- Standalone JRockit 1.4.2 or 5.0 R27.1 JDK for J2SE Runtime Environments — For standalone Java applications or Spring Framework-based applications, both the 1.4.2 and 5.0 JDK versions of the installers can install WebLogic Real Time, Core Edition in standalone mode if the target WebLogic Server instance is not found in the specified BEA Home directory. When run in standalone mode, the installer includes the JRockit Deterministic GC and the JRA tool, and also provides the sample startup scripts. However, in standalone mode, the WebLogic domain template is not installed.

For additional information about:

- The features and capabilities of WebLogic Real Time, Core Edition, see the Introduction to WebLogic Real Time, Core Edition at`http://download.oracle.com/docs/cd/E13221_01/wlrt/docs11/intro_wlrt/index.html`
- Operating systems and hardware supported by your software, see "WebLogic Real Time, Core Edition 1.1 Supported Configurations" at `http://download.oracle.com/docs/cd/E13221_01/wlrt/docs11/intro_wlrt/intro.html#wlrt_supported_configs`
- The features and capabilities of BEA JRockit, see Introduction to JRockit JDK at `http://download.oracle.com/docs/cd/E13188_01/jrockit/geninfo/genintro/index.html`
- The features and capabilities of WebLogic Server, see Introduction to WebLogic Server and WebLogic Express at:

- `http://download.oracle.com/docs/cd/E13222_01/wls/docs81/intro/index.html`
- `http://download.oracle.com/docs/cd/E13222_01/wls/docs91/intro/index.html`
- `http://download.oracle.com/docs/cd/E13222_01/wls/docs92/intro/index.html`

### WebLogic Real Time, Core Edition

WebLogic Real Time, Core Edition includes the BEA JRockit® R27.1 JVM, with deterministic garbage collection and the JRockit Runtime Analyzer (JRA) tool.

#### BEA JRockit JVM With Deterministic Garbage Collection

Memory management relies on effective garbage collection (GC), which is the process of clearing dead objects from the heap, thus releasing that space for new objects. The BEA JRockit R27.1 JVM included with WebLogic Real Time, Core Edition features deterministic garbage collection (DGC), a dynamic garbage collection priority that ensures extremely short pause times and limits the total number of those pauses within a prescribed window.

For more information on the Deterministic GC, see " Minimal Transaction Latency (The Deterministic Garbage Collector)" in the BEA JRockit Memory Management Guide.

#### BEA JRockit Runtime Analyzer (JRA)

The JRockit Runtime Analyzer (JRA) tool is an application that helps you profile your application and the Java runtime. It provides a wealth of useful metrics that are useful when using BEA JRockit as your runtime VM.

The JRocking Runtime Analyzer is packaged as part of the BEA JRockit Mission Control 2.0 tools suite. Documentation for Mission Control 2.0 is bundled with the tools as online documentation. For general information about Mission Control 2.0, see Introduction to BEA JRockit Mission Control.

## Product Distribution Methods

Your BEA software is distributed on both the BEA Web site and CD-ROM.

### Web Distribution

You can download your software from the BEA Web site at `http://commerce.bea.com`.

This includes the BEA Products installation program for WebLogic Real Time, Core Edition and WebLogic Server, which includes all of the software described in Installable Product Components.

### CD-ROM Distribution

If you purchased your software from your local sales representative, you will find the following items in the product box:

- CD-ROMs containing the product software for Windows, Solaris, and Linux
- BEA Software License and Limited Warranty pamphlet

## Installation Prerequisites

The following sections specify the installation prerequisites:

- System Requirements
- Temporary Disk Space Requirements
- Administrator Privileges
- Licensing

### System Requirements

The system requirements for your installation are given in the following table.

Table 1-1 System Requirements
Component | Requirement
--- | ---
Platform configuration | A supported configuration of hardware and operating system is required. See "WebLogic Real Time, Core Edition 1.1 Supported Configurations" at `http://download.oracle.com/docs/cd/E13221_01/wlrt/docs11/intro_wlrt/intro.html#wlrt_supported_configs`
Processor | 1-GHz CPU recommended
Hard disk drive | A complete installation requires approximately 150 MB of disk space.
Memory | 2 GB of RAM minimum
Color bit depth display and size | For graphical user interface (GUI) mode installation, 8-bit color depth (256 colors) is required. For console-mode and silent-mode installation, there is no color bit depth requirement.
JDK | The BEA Products installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program and in some Unix installation programs (those with filenames ending in `.bin`). For other Unix platforms, the installation program does not install a JDK. Filenames for these installation programs end in `.jar`. To run the `.jar` installation programs, you must have the appropriate version of the JDK installed on your system, and include the `bin` directory of the JDK at the beginning of the `PATH` variable definition. It is important that you use a JDK because the installation process assigns values to `JAVA_HOME` and related variables to point to the JDK directory.

### Temporary Disk Space Requirements

The BEA installation program uses a temporary directory into which it extracts the files necessary to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java run-time environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory at the end of the installation process. As a general rule, installation programs require approximately 2.5 times the amount of temporary space that is ultimately required by the installed files.

By default, the installation program uses the following temporary directories:

- Windows platforms—directory referenced by the `TMP` system variable
- Unix platforms—system-dependent temporary directory

Note: | If you do not have enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program.

To make sure that you have adequate temporary space, you may want to allocate an alternate directory for this purpose. To do so, follow the instructions provided in the following table.

Table 1-2 Setting Temporary Disk Space
On this platform . . . | Perform this step . . .
--- | ---
Windows | Do one of the following: Set the `TMP` system variable to a directory of your choice. If starting the installation program from the command line, include the `-Djava.io.tmpdir=``tmpdirpath` option, replacing `tmpdirpath` with the full path of the directory that you want to designate as a temporary storage area for the BEA Products installation program. For example, on Windows with the BEA JRockit 5.0 JDK-based installer: `realtime11_jdk1.5.0_win32.exe` `-mode=console -Djava.io.tmpdir=D:\Temp`
Unix | Enter the following option on the command line when you start the installation program: `-Djava.io.tmpdir=``tmpdirpath` Here, `tmpdirpath` is the full path of the directory that you want to designate as a temporary storage area for the BEA Products installation program.

### Administrator Privileges

On Windows systems, Administrator privileges are required to create Start menu shortcuts in the All Users folder.

When you are installing the software as a user with Administrator privileges, you are presented with the option to create the Start menu shortcuts in the All Users folder, or in the Local user's Start menu folder. The following table describes the options available.

Table 1-3 Creating Start Menu Shortcuts
If you select . . . | The following occurs . . .
--- | ---
All Users | All users registered on the machine are provided with access to the installed software. Subsequently, if users without Administrator privileges use the Configuration Wizard from this installation to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired.
Local user | Other users registered on this machine will not have access to the Start menu entries for this installation.

If a user without Administrator privileges installs the software, the Start menu entries are created in the user's local Start menu folder.

### Licensing

Your WebLogic Real Time, Core Edition software cannot be used without a valid license. When you install your software, the installation program installs a 30-day evaluation development license (`license.bea`) into the BEA_HOME/jrockit-realtime11_XXX/jre/ directory, to allow you to start using the product immediately.

To use your software in a full-scale production environment, you must purchase a production license. To find out how to do so, contact your sales representative or visit the BEA corporate Web site at `http://www.bea.com`.

For more information about development and production licenses, see About BEA Product Licenses.

## Selecting Directories for Your Installation

During the installation process, you need to specify locations for the following directories:

- BEA Home directory
- Product installation directory

### Choosing a BEA Home Directory

When you install your BEA software, you are prompted to specify a BEA Home directory. This directory serves as a repository for common files that are used by multiple BEA products installed on the same machine. For this reason, the BEA Home directory can be considered a central support directory for all the BEA products installed on your system.

The files in the BEA Home directory are essential to ensuring that BEA software operates correctly on your system. They perform the following types of functions:

- Ensure that licensing works correctly for the installed BEA products
- Facilitate checking of cross-product dependencies during installation
- Facilitate Service Pack installation

The following illustration shows the structure of a sample BEA Home directory, on a Windows platform, created by the WebLogic Real Time, Core Edition installation program when run in standalone mode, which includes the BEA JRockit JVM for WebLogic Real Time, Core Edition.

This illustration depicts only the files and directories required in a new BEA Home directory for WebLogic Real Time, Core Edition. If you choose an existing product installation directory, however, you will see additional directories in the BEA Home directory, such as `weblogic81` and/or `weblogic91` (and later), and the WebLogic Server license and license update utility. Although the default location for the product installation directory is within the BEA Home, you can select a different location outside the BEA Home directory.

During installation of your BEA software, you are prompted to choose an existing BEA Home directory or specify a path to create a new BEA Home directory. If you choose to create a new directory, the installation program automatically creates it for you.

Notes: | BEA recommends that you do not exceed a maximum of 12 characters when naming your BEA Home directory. If the name of this directory has more than 12 characters, the `CLASSPATH` may not be resolved properly.

Note: | If WebLogic Real Time, Core Edition is installed into a BEA Home directory where multiple WebLogic Server 9.0 and later instances exist (e.g., release 9.0 and 9.1), the WebLogic Real Time, Core Edition domain creation template and sample scripts are installed into latest WebLogic Server instance.

#### Understanding the Functions of the BEA Home Directory

The files and directories in the BEA Home directory when WebLogic Real Time, Core Edition is installed in standalone mode are described in the following table.

Table 1-4 BEA Home Directory Description
Component | Description
--- | ---
`jrockit-realtime11``_xxx` directory | Contains the software for the BEA JRockit JDK for WebLogic Real Time, Core Edition. The JDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications running in either J2SE 1.4.2 (standalone or WebLogic 8.1 SP2 and later) or J2SE 5.0 (standalone or WebLogic 9.1 and later) environments. In this directory name, `xxx` indicates the version of the JRockit JDK installed on your system, such as `jrockit-realtime11_150_08` or `jrockit-realtime11_142_12`. It also contains the JRockit R27.1 license (`license.bea`) with the necessary Deterministic GC and JRockit Runtime Analyzer tool keys in the `/jre` directory. For more information, see Licensing.
`logs` directory | Contains a history file of installation and uninstallation for the BEA Home directory.
`realtime111` directory | Contains the sample startup scripts, `startRealTime` (`.cmd/.sh`), in the `common/bin` directory, which demonstrate how to start BEA JRockit with Deterministic GC enabled.
`utils` directory | Contains utilities that are used to support the installation of all BEA products installed in this BEA Home directory. The `utils.jar` file contains code that supports the `UpdateLicense` utility.
`registry.xml` file | A registry file that contains a persistent record of all BEA products installed on the target system. This registry contains product-related information, such as version number, service pack number, and location of the installation directory.
Note: | Do not edit this file manually. Doing so may cause operating problems for the currently installed BEA products, or result in installation problems when future BEA products or maintenance upgrades are installed.
For more information about the BEA registry file, see "Using the BEA Registry API" in ISV Partners' Guide at the following URL: `http://download.oracle.com/docs/cd/E13179_01/common/docs91/isv/detect.html`

#### Creating Multiple BEA Home Directories

Although it is possible to create more than one BEA Home directory, we recommend that you avoid doing so. In almost all situations, a single BEA Home directory is sufficient. There may be circumstances, however, in which you prefer to maintain separate development and production environments, with a separate product stack for each. With two directories, you can update your development environment (in a BEA Home directory) without modifying the production environment until you are ready to do so.

### Choosing a Product Installation Directory

The product installation directory contains all the software components that you choose to install on your system, including program files and examples. You are prompted during your initial installation to choose a product installation directory. If you accept the default on a Windows system, for example, your software is installed in the following directory:

    C:\bea\realtime111

Here, `C:\bea` is the BEA Home directory and `realtime111` is the product installation directory for the WebLogic Real Time, Core Edition 1.1 software. However, you can specify any name and location on your system for your product installation directory; there is no requirement that you name the directory realtime111 or create it under the BEA Home directory.

The installation program installs the software components in a product installation directory represented by the `WLRT_HOME` variable. If, during your initial installation, you choose to install WebLogic Server only, and not all of the products available for installation, and you later decide to install additional products, such as AquaLogic Service Bus (using the same BEA Home directory), you are not prompted, during the subsequent installations, to specify a product installation directory. The installation program detects the `WLRT_HOME` directory and installs the additional products under it.

A description of the WebLogic Real Time, Core Edition directory structure is provided in Understanding the Product Directory Structure.

## Generating a Verbose Installation Log

If you launch the installation from the command line or from a script, you can specify the `-log` option to generate a verbose installation log. The installation log stores messages about events that occur during the installation process, including informational, warning, error, and fatal messages. This type of file can be especially useful for silent installations.

Note: | You may see some warning messages in the installation log. However, unless a fatal error occurs, the installation program completes the installation successfully. The installation user interface indicates the success or failure of each installation attempt, and the installation log file includes an entry indicating that the installation was successful.

### Syntax

To create a verbose log file during installation, include the `-log=``full_path_to_log_file` option in the command line. For example, on Windows using the BEA JRockit 5.0 JDK-based installer:

    realtime11_jdk1.5.0_win32.exe -log=C:\logs\server_install.log

The path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file.