Installing WebLogic Platform
BEA WebLogic Platform 8.1 includes application infrastructure technology from proven BEA products that are used by thousands of customers worldwide, including BEA WebLogic Server®, BEA WebLogic WorkshopTM, BEA WebLogic PortalTM, BEA WebLogic IntegrationTM, and BEA JRockit® 1.4.2 SDK.
You can install WebLogic Server using a separate WebLogic Server installation program, or as a component selection using the WebLogic Platform installation program. The information provided in this document describes both methods of installation.
Two installation programs are available: a WebLogic Platform installer for all components of WebLogic Platform, and a WebLogic Server installer, which includes WebLogic Server and WebLogic Workshop only. Both programs provide the same functionality; all installation procedures described in this document apply to both installers.
You can use the WebLogic Server or WebLogic Platform installation program to install BEA WebLogic ExpressTM. WebLogic Express is a cost-effective entry point to the WebLogic Product Family creating a productive ramp for customers to begin using BEA's market-leading application server technology. From WebLogic Express, customers can easily upgrade to BEA WebLogic Platform, where they can take advantage of a wide variety of enterprise-level functionality.
To install WebLogic Express, you install WebLogic Server and then install a WebLogic Express license. The WebLogic Express license activates WebLogic Express features. For additional information about WebLogic Express, see the WebLogic Express documentation at the following URL:
You must use the WebLogic Platform installation program to install WebLogic Server Process EditionTM. WebLogic Server Process Edition provides you with the technologies and tools you need to effectively service-enable your existing resources, create composite services using process-driven development, and extend these composite services to interact with other applications and technologies. Each of these phases allows you to take distinct measurable steps that are effective for both project and enterprise level architectures.
To use WebLogic Server Process Edition, you must install WebLogic Integration using the WebLogic Platform installation program. You can install WebLogic Integration (using any of the installation methods described in this document) as part of a complete WebLogic Platform installation, or individually by performing a custom installation, and selecting WebLogic Integration.
The development license installed on your system when you install WebLogic Integration enables full WebLogic Integration functionality for use in a development environment. To use WebLogic Server Process Edition in a production environment, you must install a WebLogic Server Process Edition license.
WebLogic Server Process Edition enables a subset of the WebLogic Integration functionality. To avoid building applications that are not supported by the WebLogic Server Process Edition license, you should change the development mode in the WebLogic Workshop IDE to WebLogic Server Process Edition. For more information, refer to the section "WebLogic Server Process Edition Mode" in the WebLogic Server Process Edition Overview at the following URL:
Note: WebLogic Integration and WebLogic Platform licenses include support for WebLogic Server Process Edition functionality, and may also be used for WebLogic Server Process Edition applications. For more information about WebLogic Platform licenses, see the Licensing page at
Instructions for installing a license with WebLogic Server Process Edition support are provided in Installing and Updating WebLogic Platform License Files.
You must use the WebLogic Platform installation program to install WebLogic Platform ISV Edition. WebLogic Platform ISV Edition is a special software package tailored for ISVs who have a current agreement with BEA to build value-added solutions on WebLogic. WebLogic Platform ISV Edition comprises a set of WebLogic Platform components specifically packaged to help ISVs jumpstart their service-oriented architecture (SOA) initiatives.
To use WebLogic Platform ISV Edition, you must install all the WebLogic Platform product components using the WebLogic Platform installation program. You can do so using any of the installation methods described in this document.
The development license installed on your system when you install WebLogic Platform enables full WebLogic Platform functionality for use in a development environment. To use WebLogic Platform ISV Edition in a production environment, you must install a WebLogic Platform ISV Edition license.
WebLogic Platform ISV Edition enables a subset of the WebLogic Platform functionality. It provides full WebLogic Server, WebLogic Workshop, and BEA JRockit SDK functionality, and a subset of WebLogic Integration and WebLogic Portal functionality. The WebLogic Integration features included with WebLogic Platform ISV Edition are the same as those included with WebLogic Server Process Edition.
Instructions for installing a license with WebLogic Platform ISV Edition support are provided in Installing and Updating WebLogic Platform License Files.
For more information about WebLogic Platform ISV Edition, see the WebLogic Platform ISV Partners' Guide at the following URL:
Graphical-mode installation is an interactive, GUI-based method for installing WebLogic Platform. It can be run on both Windows and UNIX systems. For installation procedures, see Installing WebLogic Platform Using Graphical-Mode Installation.
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 installation is an interactive, text-based method for installing WebLogic Platform, from the command line, on either a UNIX system or a Windows system. For instructions for using this method, see Installing WebLogic Platform Using Console-Mode Installation.
Silent-mode installation is a noninteractive method of installing WebLogic Platform 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 Installing WebLogic Platform Using Silent-Mode Installation.
WebLogic Server is the foundation of the WebLogic Platform product: it provides the core services that ensure a reliable, available, scalable, and high performing execution environment for your application. If you select the entire WebLogic Server component, the installation program installs the WebLogic Server program files and the server examples.
WebLogic Workshop is a unified, visual development environment and run-time framework that lets all application developers—not only J2EE experts—rapidly create, test, and deploy enterprise-class Web applications, Web services, and custom controls for WebLogic Server, WebLogic Integration, and WebLogic Portal. If you select the entire WebLogic Workshop component, the installation program installs the run-time framework, the visual development environment, and the Workshop samples.
Note: The BPEL Import and Export Tools and the TIBCO RendezvousTM Control and Event Generator subcomponents are not installed by default. To install them you need to choose Custom installation and select the check box for each subcomponent. Alternatively, you can clear the checkbox for the WebLogic Integration component, and then select it again. All the subcomponents are then selected and will be installed on your system.
Note: You must install WebLogic Integration to have access to the WebLogic Server Process Edition controls. For more information about WebLogic Server Process Edition, see the WebLogic Server Process Edition documentation at
Note: Use of the TIBCO RendezvousTM Control and Event Generator with BEA WebLogic Integration in no manner confers or grants the right to use TIBCO RendezvousTM including "dynamic libraries." In order to use such TIBCO products, the user of the TIBCO RendezvousTM Control and Event Generator must obtain a valid license from TIBCO.
If you plan to install the TIBCO Rendezvous Control and Event Generator subcomponent of WebLogic Integration 8.1 SP5, you must install and configure TIBCO Rendezvous on your machine before you install WebLogic Integration.
By simply following the installation instructions provided by TIBCO for this product, you can make sure that TIBCO Rendezvous is installed correctly, ready to be used later with WebLogic Integration. For more information, see the TIBCO Rendezvous Control and Event Generator User Guide at the following URL:
WebLogic Portal simplifies the production and management of custom-fit portals. WebLogic Portal simplifies, personalizes, and lowers the cost of access to information, applications, and business processes, whether the person who needs such access is an employee, a partner, or a customer. If you select the entire WebLogic Portal component, the installation program installs the server program files, the WebLogic Workshop extension, and the samples.
Platform Samples and Utilities apply to all components of WebLogic Platform; they cannot be used unless all WebLogic Platform components (WebLogic Server, WebLogic Workshop, WebLogic Integration, and WebLogic Portal) are installed.
The BEA JRockit SDK provides tools, utilities, and a complete run-time environment for developing and running applications using the Java programming language. The BEA JRockit SDK includes the BEA JRockit Java Virtual Machine (JVM), the first commercial server-side JVM for Intel architectures. The BEA JRockit SDK is fully integrated into the WebLogic Platform package, and is supported by all WebLogic Platform components. In addition, it is available as a standalone SDK.
The BEA JRockit 1.4.2 SDK is installed automatically when you install WebLogic Server or WebLogic Platform on Windows and Linux platforms. On Windows platforms only, two Java 2 SDKs are installed on your system: the BEA JRockit SDK, optimized for server-side applications, and the Sun Java 2 SDK, provided for optional use by both client-side and server-side applications.
For more information about BEA JRockit, see the BEA JRockit 1.4.2 SDK documentation at
For more information about operating systems, hardware, and SDKs supported by WebLogic Platform and WebLogic Server, see Supported Configurations for WebLogic Platform 8.1 at
The installation program performs dependency checking to ensure that all components that provide functionality on which other components depend for proper operation are installed. These dependencies are visible during graphical and console mode installations. When you select or deselect components to be installed, the installation program checks for dependencies between components and automatically modifies the list of selected components accordingly.
You can download the WebLogic Platform software from the BEA Web site at
The net installer supports standard resume processing in the case of interrupted downloads. If the download is interrupted for any reason, either manually or by an unplanned network interruption, you can resume the download from the point at which it was interrupted. When the download is complete, the installation program performs an integrity check on the archive files that were downloaded to your system to verify that the files downloaded correctly.
Any service packs and rolling patches are included in the latest distribution of WebLogic Platform 8.1, which you can download as described in Web Distribution. If you do not have WebLogic Platform 8.1 installed, you should install this distribution.
http://support.bea.com, without downloading the entire WebLogic Platform distribution.
Details about installing WebLogic Platform service packs and rolling patches are provided in Installing Service Packs and Rolling Patches.
If you do not have a BEA eSupport account, go to the following URL to get one:
A configuration of hardware, operating system, SDK, and database that is supported by WebLogic Platform is required. See WebLogic Platform Supported Configurations at
The WebLogic Platform 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
For other UNIX platforms, the WebLogic Platform installation program does not install a Java 2 SDK. Filenames for these installation programs end in
The BEA installation program uses a temporary directory in which it extracts the files necessary to install WebLogic Platform 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.
During a custom installation, you are presented with the option to install the WebLogic Server Node Manager as a Windows service. Also, if you choose to run the Configuration Wizard to create user domains, you can configure the Administration Server as a Windows service. When the Node Manager or a server is installed as a Windows service, it starts automatically each time you boot your Windows system. You must have Administrator privileges to install the Node Manager or a server as a Windows service.
For additional information, see "Setting Up a WebLogic Server Instance as a Windows Service" in Configuring and Managing WebLogic Server at
The WebLogic Platform software cannot be used without a valid license. When you install 8.1 SP3 or higher, the installation program installs two non-expiring licenses: a license to use for development (
license.bea) and a license to use for limited scale production deployments (
To use WebLogic Platform 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
For more information about development, scale-limited, and production licenses, see About WebLogic Platform Licenses.
Development and production licenses for pre-8.1 versions of WebLogic Platform do not work with WebLogic Platform 8.1; any such license must be upgraded to 8.1. Procedures for upgrading a license file and installing permanent licenses are provided in Installing and Updating WebLogic Platform License Files.
Secure sockets layer (SSL) encryption software is available with two levels of encryption: 56-bit and 128-bit. In 8.1 SP3 and higher, the license files installed with WebLogic Platform enable both 56-bit and 128-bit encryption by default.
For instructions about enabling 128-bit encryption for earlier releases of WebLogic Platform, see "Enabling 128-bit encryption in SP2 or Earlier" at
On Windows platforms, two SDKs are installed: the Sun Java 2 SDK 1.4.2 and the BEA JRockit 1.4.2 SDK. For more information, see BEA JRockit SDK.
In a custom installation, you can optionally install the Node Manager as a Windows Service. In a production environment, you usually install the Node Manager only on server machines that host managed server instances of WebLogic Server. The WebLogic Server Node Manager is not installed as a Windows service in a complete installation. In a development environment, you may want to install the Node Manager on a server machine that hosts both the administration server and managed server instances of WebLogic Platform.
Notes: By default, the WebLogic Server Node Manager uses port 5555. If the Node Manager for a previous version of WebLogic Server is installed on the machine, the new version does not start when Windows starts because of port contention. To make sure that the new version starts when Windows starts, reconfigure the Node Manager to use a different port.
The BEA Node Manager service is linked to a BEA Home directory. If you have multiple BEA Home directories on your machine and you uninstall WebLogic Platform in the BEA Home directory linked to the Node Manager service, the uninstaller removes the service. If you have other instances of WebLogic Server that rely on the Node Manager, you must manually start the Node Manager or reinstall the Node Manager service.
When you install WebLogic Platform, 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 the BEA products installed on your system.
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
weblogic81. Although the default location for the product installation directory is within the BEA Home directory, you can select a different location outside the BEA Home directory.
During installation of WebLogic Platform, 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 WebLogic Platform installation program automatically creates the directory for you.
Note: For a BEA Home directory, you are allowed to install only one instance of each version of a BEA product that uses the BEA Home directory convention. For example, you can install only one instance of WebLogic Platform 8.1 in a BEA Home directory, but that BEA Home directory may also contain an instance of WebLogic Platform 7.0.
Java controls are server-side components that encapsulate external resources and business logic for use in Workshop applications. This directory contains two types of controls files supported by WebLogic Platform: full control implementation files (ready to be used) and control stub files (utilities that download the specified control implementations when needed). Both types of control files are integrated with the Workshop IDE and managed by the Workshop run-time framework.
The full control implementation files delivered in
For ISVs and other software developers who want more information about creating custom controls, see "Creating and Packaging WebLogic Workshop Java Controls" in the WebLogic Platform ISV Partners' Guide at
Contains the software for the Java 2 SDK installed with WebLogic Platform. The SDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. The SDK directories include:
Licenses are release specific. You cannot use a license from a previous release with WebLogic Platform 8.1. To convert a pre-8.1
To update your
Note: Do not edit
An XML file that contains license keys to enable you to run a single server instance with a server capacity limited to approximately 3 percent of the full capacity of a production server. For instructions on installing this license file, see Replacing Your license.bea 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 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 installing future BEA products or maintenance upgrades.
A command file (Windows) or a shell script (UNIX) that updates the current
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.
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 the initial installation of WebLogic Platform, to choose a product installation directory. If you accept the default, the WebLogic Platform software is installed in the following directory:
C:\bea is the BEA Home directory and
weblogic81 is the product installation directory for the WebLogic Platform 8.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
weblogic81 or create it under the BEA Home directory.
The installation program installs the software components in a product installation directory represented by the
WL_HOME variable. If, on your initial installation, you choose to install individual components of WebLogic Platform and not the full complement of products, and later decide to install additional components (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
WL_HOME directory and installs the additional components under in it.
A description of the WebLogic Platform directory structure is provided in Understanding the WebLogic Platform Product Directory Structure.
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.
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 installing service packs, see Installing Service Packs and Rolling Patches.
For information about upgrading WebLogic Platform components from previous releases, see the Upgrade Planning Guide at
For information about migrating from a previous release of WebLogic Server to WebLogic Server 8.1, see the WebLogic Server 8.1 Upgrade Guide at
When you start Smart Update, either from the Windows start menu or from the command line, it checks the version numbers of the products installed (associated with the current BEA Home directory), and then connects to the BEA Web site to check for available updates. For details about using Smart Update, see Installing Service Packs and Rolling Patches.
You can also use Smart Update to revert your system installation to an earlier version of the release. For additional information, see Uninstalling Maintenance Upgrades Using Smart Update.