The following sections provide information that you need to know before installing your BEA software:
The BEA Products installation program provides a complete framework for the installation and uninstallation of your entire BEA software product, or individual components, as desired. You can install AquaLogic Service Bus using one of the following options:
|Note:||Both programs provide the same functionality; all installation procedures described in this document apply to both versions of the installation program.|
The following sections provide an overview on:
You can use either of the two BEA Products installation programs to install BEA WebLogic Express™. WebLogic Express is a cost-effective entry point to the WebLogic product family, creating a productive ramp for you to begin using BEA’s market-leading application server technology. From WebLogic Express, you can easily upgrade to other products in the WebLogic family, which allows you to take advantage of a wide variety of enterprise-level functionality.
For additional information about WebLogic Express, see the WebLogic Express documentation at the following URL:
You can use the BEA Products installation program in one of the following modes:
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.
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.
|Note:||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 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 in the Console 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 information on running the installation program in the silent mode, see Running the Installation in the Silent Mode.
Using the BEA Products installation program, you can install the following components on your system:
If you are using the BEA Products installation program for BEA WebLogic Server, only the WebLogic Server components are available for installation.
For additional information about:
Operating systems and hardware supported by your software, see BEA Products Supported Configurations at
BEA WebLogic Server® provides the core services that ensure reliability, high availability, scalability, and high-performing execution environment for your application. It includes Apache Beehive, a cross-container framework that provides a consistent, abstract, and easily toolable programming model, providing a way for developers to build applications more productively.
WebLogic Server consists of the following subcomponents that can be installed on your system:
|Note:||You must choose Custom installation to install the Web Server plug-ins. They are not installed by default in a complete installation.|
BEA Workshop for WebLogic Platform™ provides a unified development environment that enables you to develop web applications and Web services regardless of your experience in developing applications using J2EE. It includes a suite of tools for developing, debugging, and deploying sophisticated enterprise applications.
Workshop for WebLogic Platform is an integrated development environment for building enterprise-class J2EE applications on the WebLogic Platform. WebLogic Workshop provides an intuitive programming model that enables you to focus on building the business logic of your application rather than on complex implementation details. Whether you are an application developer with a business problem to solve or a J2EE expert building business infrastructure, Workshop for WebLogic Platform makes it easy to design, test, and deploy enterprise-class applications.
Workshop for WebLogic Platform consists of two parts: an Integrated Development Environment (IDE) and a standards-based run-time environment. The purpose of the IDE is to remove the complexity in building applications for the entire WebLogic platform. Applications you build in the IDE are constructed from high-level components rather than low-level API calls. Best practices and productivity are built into both the IDE and run time. Workshop for WebLogic Platform also includes the workshop examples to help you to get acquainted with the product.
You can use Workshop for WebLogic Platform to:
BEA AquaLogic Service Bus™ combines intelligent message brokering with service monitoring and administration to provide a unified software product for implementing and deploying your Service-Oriented Architecture (SOA). This converged approach adds a scalable, dynamic routing and transformation layer to your enterprise infrastructure, with service lifecycle management capabilities for service registration, service usage, and Service Level Agreement (SLA) enforcement.
AquaLogic Service Bus relies on WebLogic Server run-time facilities. It leverages WebLogic Server capabilities to deliver functionality that is highly available, scalable, and reliable.
AquaLogic Service Bus consists of the following subcomponents that can be installed on your system:
The BEA JRockit® JDK provides tools, utilities, and a complete run-time environment for developing and running applications using the Java programming language. The BEA JRockit JDK includes the BEA JRockit Java Virtual Machine (JVM) and BEA JRockit Mission Control. The BEA JRockit JVM is developed uniquely for server-side applications and optimized for Intel architectures to ensure reliability, scalability, and manageability for Java applications. BEA JRockit Mission Control is a tool set developed to monitor, manage, profile, and eliminate memory leaks in your Java applications.
The BEA JRockit JDK is fully integrated with the BEA Products installation kit for Windows and Linux 32-bit platforms. It is also available as a standalone JDK. Although BEA JRockit JDK is optimized for server-side applications, you may use it for client-side as well. The Sun JDK is also supported as an alternative for both client side and server side applications.
For more information about the BEA JRockit JDK, see the JRockit documentation at
The BEA JRockit 5. 0 JDK is certified to be compatible with Sun Java 2 Standard Edition (J2SE) version 5. 0.
BEA JRockit Mission Control
The BEA JRockit Mission Control tools suite consists of the following components:
Mercury Profiling Tools
The Mercury profiling tools, which are provided as part of this JRockit installation, can be used by Java and J2EE developers in a development environment to profile application performance. During the installation process, you are presented with the option to install the Mercury profiling tools. For more information about these tools, see
Your BEA software is distributed on both the BEA Web site and DVD.
You can download your software from the BEA Web site at
In the left panel click on BEA AquaLogic to go to the download page of BEA AquaLogic Product Family. Click on BEA AquaLogic Service Bus from the list of AquaLogic products. From the drop down list choose the appropriate operating system and click
|Note:||You are to register before you can download the installer.|
If you purchased your software from your local sales representative, you will find the following items in the product box:
The following sections specify the installation prerequisites:
The system requirements for your installation are given in the following table.
A supported configuration of hardware, operating system, JDK, and database is required. See Supported Configurations at
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
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:
|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.
On Windows systems, Administrator privileges are required to do the following:
You must have Administrator privileges to install the Node Manager as a Windows service. When the Node Manager is installed as a Windows service, it starts at the completion of the installation process, and again, automatically, each time you boot your Windows system.
For more information, see About Installing Node Manager as a Windows Service.
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.
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 required.
If a user without Administrator privileges installs the software, the Start menu entries are created in the user’s local Start menu folder.
During the installation process, you need to specify locations for the following directories:
During the installation of the BEA software, you are prompted to specify a BEA Home directory. This directory serves as a repository for common files that are used by various 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. These files:
The following illustration shows the structure of a sample BEA Home directory, on a Windows platform, which includes both the Sun and BEA JRockit JDKs.
This illustration depicts only the files and directories required in the BEA Home directory. If you choose the default product installation directory, however, you will see additional directories in the BEA Home directory, such as
workshop92. 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.
CLASSPATHmay not be resolved properly. You can install only one instance of each version of a BEA product in a single BEA Home directory. For example, you can install only one instance of WebLogic Server 9.2 in a BEA Home directory, but that BEA Home directory may also contain an instance of WebLogic Server 9. 0.
registry.xml, or if any of the other installation directories are not empty, the following messages will be displayed. You will then be prompted to continue installation, or return to the directory selection task with the one of the error message as shown in Listing 1-1:
For BEA Home directory selection task: BEA_HOME directory is not empty. Proceed with installation?
For product installation directories selection task:One or more installation directories are not empty. Proceed with installation?
|Note:||You must obtain the compatible installer or perform maintenance in order to achieve compatibility.|
The files and directories in the BEA Home directory are described in the following table.
Contains the software for the Sun JDK if it is installed with your software. The JDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. In this directory name,
Contains the software for the BEA JRockit JDK installed with your software. The JDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. In this directory name,
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.
For more information about the BEA registry file, see “Using the BEA Registry API” in ISV Partners’ Guide at the following URL:
Although it is possible to create more than one BEA Home directory, BEA recommends 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.
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 is the BEA Home directory and
weblogic92 is the product installation directory for the WebLogic Server 9.2 software. However, you can specify any name and location on your system for your product installation directory; you need not name the directory
weblogic92 or create it under the BEA Home directory. You must also create a product installation directory for workshop for weblogic. The default location for the workshop is
The installation program installs the software components in a product installation directory represented by the
WL_HOME variable. You are not prompted for a product installation directory during the installation, if you are adding a component to the existing installation. The installation program detects the
WL_HOME directory and installs the additional products under it.
A description of the BEA Products directory structure is provided in Understanding the Product Directory Structure
The BEA Products installation program provides two types of installation:
If you choose a
Complete installation type, following components are installed:
The following components are not installed if you choose the
Complete installation type:
Custom installation type, you have the following options:
You can choose whether to install the WebLogic Server Node Manager as a Windows Service. See About Installing Node Manager as a Windows Service.
On Windows systems only, two JDKs are installed: the BEA JRockit 5. 0 JDK and the Sun JDK 5. 0. For more information, see BEA JRockit JDK.
When installing your software on a Windows platform, you can optionally install WebLogic Server Node Manager as a Windows service. The WebLogic Server Node Manager is used to:
In a multi-machine environment, you must install Node Manager on each machine that hosts Managed Server and Administration Server instances of WebLogic Server.
To install Node Manager as a Windows service in silent mode, you need to specify the appropriate values in the silent.xml file. For more information, see Creating a silent.xml File for Silent-Mode Installation.
You can also install and uninstall Node Manager as a Windows service using the following scripts that are provided when you install WebLogic Server:
In these pathnames,
WL_HOME is the product installation directory in which you installed WebLogic Server, typically
Following are some additional considerations for installing the node manager as a Windows service:
C:\bea\weblogic92. Node Manager can be used to manage communication with all domains associated with that installation directory.
If you install additional instances of WebLogic Server 9.2 on a machine, in different BEA Home directories, you can install a Node Manager instance as a Windows service for each installation. Each Node Manager instance will manage the domains associated with the relevant installation.
|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. Changing the Node Manager listen port value in the registry.xml does not change the port for the installed service.|
For more information about Node Manager, including instructions for installing it on a UNIX system, see “Using Node Manager to Control Servers” in Managing Server Startup and Shutdown at
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.|
To create a verbose log file during installation, include the -
log=full_path_to_log_file option in the command line. For example:
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.
For information about upgrading your software with maintenance patches and service packs, if available, see Installing Maintenance Updates and Service Packs at
For information about upgrading your application environments from a previous release, see Roadmap for Upgrading WebLogic and AquaLogic Application Environments at
If you are installing WebLogic Server 9.2 into an existing BEA Home directory that contains an installation of WebLogic Server 7.0 or 8.1 or 9.2, all custom security providers that reside in the default location,
WL_HOME specifies the root directory of the pre-9.2 installation, are upgraded automatically. If all of your custom security providers reside in the default location, then the security provider upgrade step is complete, and you do not have to perform any of the additional steps in “Upgrading a Security Provider” in Upgrading WebLogic Application Environments at
You can verify that a custom security provider has been upgraded by locating the upgraded security provider,
security_provider_name_Upgraded, in the
WL_HOME\server\lib\mbeantypes directory, where
WL_HOME specifies the root directory of the 9.2 installation and
security_provider_name specifies the name of the security provider.