Skip navigation.
Downloads | Product Documentation | Support

Installation Guide

# Starting the Installation Program

The following sections describe how to start the installation program on Windows and UNIX platforms:

- Before You Start
- Starting the Installation Program on Windows Platforms
- Starting the Installation Program on UNIX Platforms
- What's Next?

# Before You Start

Before you start installing the software, please review the following information:

- Make sure that you are installing your software on a hardware/software configuration that is supported by your BEA Products software. A complete list of documents that describe the configurations supported by BEA can be found at `http://e-docs.bea.com/platform/suppconfigs/index.html`.
- Read Preparing for Your Installation
- You cannot reinstall any BEA product on top of a previously installed version of the same product—in the same BEA Home directory or in the same file location. You can, however, add products and product components to an existing installation. For example, you can install WebLogic Server during one installation, and AquaLogic Service Bus during a separate installation. However, to reinstall the same version of one of the products, you must first uninstall the previous installation, as described in Uninstalling the Software.
- If you are adding components to an existing installation of WebLogic Server, you should shut down any running servers before starting the installation.

# Starting the Installation Program on Windows Platforms

The following sections describe how to start the installation program on a Windows platform:

- Starting in Graphical Mode
- Starting in Console Mode
- Starting in Silent Mode

Notes: If you are installing the software on a Windows system that supports more than one monitor, you must disable all but one monitor before starting the installation program.

If you want to install Node Manager as a Windows service, you must have Administrator privileges. For more information, see About Installing Node Manager as a Windows Service.

## Starting in Graphical Mode

To start the graphical-mode installation process on a Windows platform, follow these steps:

1. Log in to the Windows system.
2. Go to the directory where you downloaded the installation program.
3. Complete the appropriate procedure in the following table.

If you are installing from . . . | Perform the following action . . .
--- | ---
Web download | Go to the directory where you downloaded the installation program.
CD-ROM | 1. Insert the software CD into the CD-ROM drive. 2. If the installation program does not start automatically, open Windows Explorer and double-click the CD-ROM icon. 3. Navigate to the folder for the Windows installation.

4. Double-click the installation file:

- `alsb200_wls900_win32.exe` (BEA Products installation program for AquaLogic Service Bus and WebLogic Server)
- `server900_win32.exe` (BEA Products installation program for WebLogic Server)

The installation program begins to install the software.

5. Proceed to Running the Installation Program in Graphical Mode.

## Starting in Console Mode

To start the console-mode installation process on a Windows platform, follow these steps:

1. Log in to the target Windows system.
2. Complete the appropriate procedure in the following table:

If you are installing from . . . | Perform the following action . . .
--- | ---
Web download | 1. Open an MS-DOS command prompt window. 2. Go to the directory where you downloaded the installation program.
CD-ROM | 1. Insert the software CD into the CD-ROM drive. Note: If autorun is enabled, the installation program may start automatically in graphical mode. You must exit the installation program to use console-mode installation. 2. Open an MS-DOS command prompt window. 3. Go to the CD-ROM directory and navigate to the folder for the Windows installation program.

3. Launch the installation by entering one of the following commands:

- `alsb200_wls900_win32.exe -mode=console` (BEA Products installation program for AquaLogic Service Bus and WebLogic Server)
- `server900_win32.exe -mode=console` (BEA Products installation program for WebLogic Server)

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`alsb200_wls900_win32 -mode=console -log=C:\logs\server_install.log`

For more information, see Generating a Verbose Installation Log.

After a few moments, a BEA Installer window opens and the installation program begins to install the software.

4. Proceed to Running the Installation Program in Console Mode.

## Starting in Silent Mode

For details about silent-mode installation, see What Is Silent-Mode Installation?.

To start the silent-mode installation process on a Windows platform, follow these steps:

1. Log in to the Windows system.
2. Create a `silent.xml` file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating a `silent.xml` file, see Creating a silent.xml File for Silent-Mode Installation.

Note: Incorrect entries in the `silent.xml` file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.

3. Complete the appropriate procedure in the following table.

If you are installing from . . . | Perform the following action . . .
--- | ---
Web download | 1. Open an MS-DOS command prompt window. 2. Go to the directory where you downloaded the installation program.
CD-ROM | 1. Insert the software CD into the CD-ROM drive. 2. Open an MS-DOS command prompt window. 3. Go to the CD-ROM directory and navigate to the folder for the Windows installation program.

4. Launch the installation by entering the following command:

`filename``.exe -mode=silent -silent_xml=``path_to_silent.xml`

Here, `filename.exe` is the name of the BEA software installation file, and `path_to_silent.xml` is the full pathname of the `silent.xml` file.

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`alsb200_wls900_win32.exe -mode=silent -silent_xml=C:\silent.xml -log=C:\logs\server_install.log`

For more information, see Generating a Verbose Installation Log.

A BEA Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.

For more information, see Running the Installation Program in Silent Mode.

# Starting the Installation Program on UNIX Platforms

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 include a JRE. Filenames for these installation programs end in `.jar`. To run the `.jar` installation programs, you must have an appropriate version of a Java 2 JDK installed on your system, and include the `bin` directory of the Java 2 JDK at the beginning of your `PATH` system variable.

Notes: It is important that you use a JDK because the installation process assigns values to `JAVA_HOME` and related variables to point to this directory. All scripts installed by your installation program use this JDK by default, including scripts to start sample applications, the Configuration Wizard, and other development tools.

To run graphical-mode installation, your console must support a Java-based GUI. If the installation program determines that your system cannot support a Java-based GUI, it automatically starts running in console mode. For details, see Running the Installation Program in Console Mode.

## Using Installers with Filenames Ending in .bin

The following sections describe how to start the installation program on UNIX platforms using filenames that end in `.bin`:

- Starting Graphical-Mode Installation
- Starting Console-Mode Installation
- Starting Silent-Mode Installation

### Starting Graphical-Mode Installation

To start the graphical-mode installation process for installation files with names ending in `.bin`, follow these steps:

1. Log in to the target UNIX system.
2. Complete the appropriate procedure in the following table.

If you are installing from . . . | Perform the following action . . .
--- | ---
Web download | Go to the directory where you downloaded the installation program.
CD-ROM | 1. Insert the software CD into the CD-ROM drive and go to the CD-ROM directory. 2. Navigate to the directory that contains the installation program for your platform.

3. Launch the installation by entering the following commands:

`chmod a+x` `filename``.bin
./``filename``.bin`

In these commands, `filename``.bin` is the name of the installation program specific to your platform, for example, `alsb200_wls900_solaris32.bin`.

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`alsb200_wls900_solaris32.bin -log=/home/logs/BEA_install.log`

For more information, see Generating a Verbose Installation Log.

The installation program begins to install the software.

4. Proceed to Running the Installation Program in Graphical Mode.

### Starting Console-Mode Installation

To start the console-mode installation process for installation files with names ending in `.bin`, follow these steps:

1. Log in to the target UNIX system.
2. Complete the appropriate procedure in the following table.

If you are installing from . . . | Perform the following action . . .
--- | ---
Web download | Go to the directory where you downloaded the installation program.
CD-ROM | 1. Insert the software CD into the CD-ROM drive and go to the CD-ROM directory. 2. Navigate to the directory that contains the installation program for your platform.

3. Launch the installation by entering the following commands:

`chmod a+x` `filename``.bin
./``filename``.bin -mode=console`

Here `filename``.bin` is the name of the installation program specific to your platform, for example, `alsb200_wls900_solaris32.bin`.

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`alsb200_wls900_solaris32.bin -mode=console -log=/home/logs/BEA_install.log`

For more information, see Generating a Verbose Installation Log.

4. Proceed to Running the Installation Program in Console Mode.

### Starting Silent-Mode Installation

For details about silent-mode installation, see What Is Silent-Mode Installation?.

To start the silent-mode installation process for installation files with names ending in `.bin`, follow these steps:

1. Log in to the target UNIX system.
2. Create a `silent.xml` file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating a `silent.xml` file, see Creating a silent.xml File for Silent-Mode Installation.

Note: Incorrect entries in the `silent.xml` file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.

3. Complete the appropriate procedure in the following table.

If you are installing from . . . | Perform the following action . . .
--- | ---
Web download | Go to the directory where you downloaded the installation program.
CD-ROM | 1. Insert the software CD into the CD-ROM drive and go to the CD-ROM directory. 2. Navigate to the directory that contains the installation program for your platform.

4. Launch the installation program by entering the following command:

`chmod a+x` `filename
`./`filename``.bin` `-mode=silent -silent_xml=/``path_to_silent.xml`

Here `filename``.bin` is the name of the installation file, for example, `alsb200_wls900_solaris32.bin`, and `path_to_silent.xml` is the full pathname of the `silent.xml` template file.

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`alsb200_wls900_solaris32.bin -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/BEA_install.log`

For more information, see Generating a Verbose Installation Log.

A BEA Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.

For more information, see Running the Installation Program in Silent Mode.

## Using Installers with Filenames Ending in .jar

The following sections describe how to start the installation program on UNIX platforms using filenames that end in .jar:

- Starting Graphical-Mode Installation
- Starting Console-Mode Installation
- Starting Silent-Mode Installation

### Starting Graphical-Mode Installation

To start the graphical-mode installation process for installation files with names ending in `.jar`, follow these steps:

1. Log in to the target UNIX system.
2. Add the `bin` directory of the appropriate JDK to the beginning of the `PATH` variable definition on the target system. For example:

`PATH=``JAVA_HOME``/bin:$PATH
export PATH`

Here `JAVA_HOME` represents the full path to the JDK directory.

3. Go to the directory where you downloaded the installation program.
4. Launch the installation program by entering the following command:

`java -jar server900_generic32.jar`

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`server900_generic32.jar -log=/home/logs/BEA_install.log`

For more information, see Generating a Verbose Installation Log.

The installation program begins to install the software.

5. Proceed to Running the Installation Program in Graphical Mode.

### Starting Console-Mode Installation

To start the console-mode installation process for installation files with names ending in `.jar`, follow these steps:

1. Log in to the target UNIX system.
2. Add the `bin` directory of the appropriate JDK to the beginning of the `PATH` variable definition on the target system. For example:

`PATH=``JAVA_HOME``/bin:$PATH
export PATH`

Here, `JAVA_HOME` represents the full path to the JDK directory.

3. Go to the directory where you downloaded the installation program.
4. Launch the installation by entering the following command:

`java -jar` `filename``.jar -mode=console`

Here, `filename``.jar` is the name of the BEA Products installation file, for example, `server900_generic.jar`.

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`java -jar` `server900_generic.jar``` `-mode=console
-log=/home/logs/BEA_install.log`

For more information, see Generating a Verbose Installation Log.

5. Proceed to Running the Installation Program in Console Mode.

### Starting Silent-Mode Installation

For details about silent-mode installation, see What Is Silent-Mode Installation?.

To start the silent-mode installation process for installation files with names ending in `.jar`, follow these steps:

1. Log in to the target UNIX system.
2. Create a `silent.xml` file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating a `silent.xml` file, see Creating a silent.xml File for Silent-Mode Installation.

Note: Incorrect entries in the `silent.xml` file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.

3. Add the `bin` directory of the appropriate JDK to the beginning of the `PATH` variable definition on the target system. For example:

`PATH=``JAVA_HOME``/bin:$PATH
export PATH`

Here, `JAVA_HOME` is the full path of the JDK directory.

4. Go to the directory that contains the installation file.
5. Launch the installation by entering the following command:

`java -jar` `filename``.jar -mode=silent
-silent_xml=/``path_to_silent``.xml`

Here, `filename``.jar` is the name of the BEA Products installation file (for example, `server` `XXX``_generic.jar`, where `XXX` represents the version number of the software you are installing) and `path_to_silent.xml` is the full path to the `silent.xml` file.

Note: You can also include the `-log=``full_path_to_log_file` option in the command line to create a verbose installation log. For example:

`server900_generic.jar -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/BEA_install.log`

For more information, see Generating a Verbose Installation Log.

A BEA Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.

For more information, see Running the Installation Program in Silent Mode.

# What's Next?

For details about running the installation program, see one of the following, depending on your selected installation mode:

- Running the Installation Program in Graphical Mode
- Running the Installation Program in Console Mode
- Running the Installation Program in Silent Mode