Skip navigation.

eDocs Home > BEA WebLogic Integration 8.5 Documentation > Installing WebLogic Integration > Preparing to Install WebLogic Integration

Installing WebLogic Integration

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

Preparing to Install WebLogic Integration

The following sections provide information that you need to know before installing the BEA WebLogic IntegrationTM 8.5 software and the BEA WebLogic PlatformTM 8.1 components required for that installation:

 

About WebLogic Integration Installation

WebLogic Integration 8.5 is distributed and installed using the BEA Installation and Distribution System, which provides a complete framework for the following:

The installation program installs the following:

Optionally, the installation program also installs the following products. These products are provided as a convenience to WebLogic Integration users who may incorporate one or more of them into their applications and domains:

The installation program also enables support for the following products:

WebLogic Express Support

You can use the WebLogic Integration installation program to install WebLogic Express 8.1. 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.

Note: WebLogic Express does not support applications developed in the WebLogic Workshop IDE.

Licensing

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:

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/wlx.html

WebLogic Server Process Edition Support

You can use the WebLogic Integration 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.

Installation

When you install WebLogic Integration using any of the installation procedures described in this document, all the components required for WebLogic Server Process Edition—namely, WebLogic Integration, WebLogic Server, and WebLogic Workshop—are installed by default.

For installation procedures, refer to the following chapters:

Licensing

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 "The WebLogic Server Process Edition Mode" in the WebLogic Server Process Edition Overview at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs85/peoverview/introduction.html#process_edition_mode

Note: WebLogic Integration and WebLogic Platform licenses include support for WebLogic Server Process Edition functionality, and can also be used for WebLogic Server Process Edition applications. For more information about WebLogic Platform licenses, see the Licensing page at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/interm/license.html

Instructions for installing a license with WebLogic Server Process Edition support are provided in Installing and Updating WebLogic Integration 8.5 License Files.

For more information about WebLogic Server Process Edition, see the WebLogic Server Process Edition documentation at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs85/wlspe.html

WebLogic Platform ISV Edition Support

You can use the WebLogic Integration installation program to install WebLogic Platform ISV Edition. WebLogic Platform ISV Edition is a special software package tailored for Independent Software Vendors (ISVs) who have a current agreement with BEA to build value-added solutions on WebLogic Platformor one of its components. WebLogic Platform ISV Edition comprises a set of WebLogic Platform components specifically packaged to help ISVs jumpstart their service-oriented architecture (SOA) initiatives.

Installation

To use WebLogic Platform ISV Edition, you must install the following WebLogic Platform product components using the WebLogic Integration installation program:

You can do so using any of the installation methods described in this document. For standard installation procedures, refer to the following chapters:

Licensing

The development license installed on your system when you install WebLogic Integration 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 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" in Installing WebLogic Platform at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/license.html

For more information about WebLogic Platform ISV Edition, see the WebLogic Platform ISV Partners' Guide at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/isv/index.html

Installation Methods

The BEA installation program supports the following methods for installing the BEA WebLogic Integration software:

 

About the WebLogic Integration Software

WebLogic Integration provides a development and run-time framework for joining business process management and application integration capabilities into a single, flexible environment. If you select the entire WebLogic Integration component, the installation program installs the program files for the WebLogic Integration server, the WebLogic Workshop Integration Extension, and the examples.

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 the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs85/wlspe.html

WebLogic Integration consists of the following subcomponents:

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.

Installing the TIBCO Rendezvous Control and Event Generator Subcomponent

If you plan to install the TIBCO Rendezvous Control and Event Generator subcomponent of WebLogic Integration 8.5, you must install and configure TIBCO Rendezvous on your machine before you install WebLogic Integration.

Information about obtaining and installing a licensed copy of TIBCO Rendezvous is available at the following URL:

http://www.tibco.com

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:

http://download.oracle.com/docs/cd/E13214_01/wli/docs85/tibcorv/index.html

 

WebLogic Platform Software Components

WebLogic Platform, which is available from the WebLogic Integration installation program, consists of the following software, in addition to WebLogic Integration:

For additional information about:

WebLogic Server

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 Server consists of the following subcomponents:

WebLogic Workshop

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.

WebLogic Workshop consists of the following subcomponents:

WebLogic Portal

WebLogic Portal, provided as a convenience with this installation program, 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.

WebLogic Portal consists of the following subcomponents:

WebLogic Platform Samples and Utilities

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 sample application is the Platform Tour: a fully integrated application that demonstrates key features of WebLogic Platform.

BEA JRockit SDK

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 Integration 8.5 package, and is supported by WebLogic Integration and 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 Integration 8.5 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.

Note: The BEA JRockit 1.4.2 SDK is certified to be compatible with Sun Java 2 Standard Edition (J2SE), version 1.4.2.

For more information about BEA JRockit, see the BEA JRockit 1.4.2 SDK documentation at http://download.oracle.com/docs/cd/E13188_01/jrockit/docs142/index.html.

For more information about operating systems, hardware, and SDKs supported by WebLogic Integration 8.5, see Supported Configurations for WebLogic Platform 8.5 at http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs85/85_over/index.html.

 

Dependencies Between Installable Components

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.

Note: The same dependencies are enforced during silent installation: components on which other components depend are installed even if they are not explicitly referenced in a silent script.

Some examples of component dependencies are as follows:

Dependency checking is also performed when you uninstall WebLogic Integration, to ensure that you do not uninstall a component that is required by another component.

 

WebLogic Integration Distribution Methods

WebLogic Integration 8.5 is distributed on both the BEA Web site and CD-ROM.

Web Distribution

You can download the WebLogic Integration 8.5 software, including the WebLogic Platform 8.1 components it requires, from the BEA Web site at http://commerce.bea.com.

Two methods are available for download:

CD-ROM Distribution

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

Web Distribution of Service Packs and Rolling Patches

Any service packs and rolling patches are included in the latest distribution of WebLogic Integration 8.5, which you can download as described in Web Distribution. If you do not have WebLogic Integration 8.5 installed, you should install this distribution.

If you already have WebLogic Integration 8.5 installed, and if you have a BEA eSupport account, you can upgrade your software in one of the following ways:

Details about installing WebLogic Integration 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: http://support.bea.com

 

Installation Prerequisites

The following sections specify the installation prerequisites for a WebLogic Integration installation:

System Requirements

The system requirements for WebLogic Integration are given in the following table.

Table 1-1 System Requirements 

Component

Requirement

Platform configuration

A configuration of hardware, operating system, SDK, and database that is supported by WebLogic Integration is required. See Supported Configurations for WebLogic Integration 8.5 at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs85/85_over/overview.html

This document also specifies other prerequisites and recommendations, such as recommended versions of the Java 2 SDK.

Processor

For a full WebLogic Platform installation, a 1-GHz CPU is recommended.

Hard disk drive

A full WebLogic Platform installation requires approximately 1 GB of disk space.

Memory

Full WebLogic Platform installation—512 MB of RAM minimum, 1 GB recommended

WebLogic Server (with Sun Java 2 SDK)—256 MB of RAM minimum, 512 MB or more recommended (without WebLogic Workshop)

WebLogic Server (with BEA JRockit SDK)—512 MB of RAM minimum

WebLogic Integration—512 MB RAM minimum, 1 GB recommended

WebLogic Portal—512 MB of RAM minimum, 1 GB recommended

WebLogic Workshop—512 MB RAM minimum, 1 GB recommended

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.

Java 2 SDK

The WebLogic Integration 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 WebLogic Integration installation program does not install a Java 2 SDK. Filenames for these installation programs end in .jar. To run the .jar installation programs, you must have the appropriate version of the Java 2 SDK installed on your system, and include the bin directory of the SDK at the beginning of the PATH variable definition. It is important that you use an SDK because the installation process sets the JAVA_HOME and related variables to point to this directory. For procedures, see one of the following:


 

Temporary Disk Space Requirements

The BEA installation program uses a temporary directory in which it extracts the files necessary to install WebLogic Integration 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 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.

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 WebLogic Integration installation program. For example:

platformXXX_win32.exe -mode=console -Djava.io.tmpdir=D:\Temp

In the filename used in this example, XXX represents the version number of the software you are installing.

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 WebLogic Integration installation program.


 

Administrator Privileges

Administrator privileges are required in the following circumstances:

Licensing and Encryption

The WebLogic Integration software cannot be used without a valid license. When you install WebLogic Integration 8.5, 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 (license_scale_limited.bea).

To use WebLogic Integration, and the WebLogic Platform components it requires, 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, scale-limited, and production licenses, see "Installing and Updating WebLogic Platform License Files" in Installing WebLogic Platform at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/license.html

Development and production licenses for version 8.1 of WebLogic Platform will continue to work with WebLogic Integration 8.5.

About 128-Bit Encryption

Secure sockets layer (SSL) encryption software is available with two levels of encryption: 56-bit and 128-bit. In WebLogic Integration 8.5 and higher, the license files installed with WebLogic Integration 8.5 enable both 56-bit and 128-bit encryption by default.

 

Choosing a Type of Installation

The WebLogic Integration installation program provides two types of installation: Complete and Custom.

Complete Installation

In a complete installation, the following components are automatically installed:

The WebLogic Server Node Manager is not installed as a Windows service.

Custom Installation

In a custom installation, you have the following options:

Two SDKs are installed on Windows platforms only: the Sun Java 2 SDK 1.4.2 and the BEA JRockit 1.4.2 SDK. For more information, see BEA JRockit SDK.

 

Installing the Node Manager as a Windows Service

When installing WebLogic Integration on a Windows platform, you can optionally install the WebLogic Server Node Manager as a Windows service. The WebLogic Server Node Manager is used to:

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 the managed server instances of WebLogic Integration.

The Node Manager is installed as a Windows service only under the following conditions:

After you install the Node Manager as a Windows service, the service is started the next time you reboot the system. You can also manually start the service from the Windows Services control panel.

When you uninstall WebLogic Integration, the service is also uninstalled.

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 Integration and all other WebLogic Platform components 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.

If you uninstall an instance of WebLogic Server that is not in the BEA Home directory linked to the Node Manager service, the uninstallation program does not uninstall the Node Manager service.

For more information about the Node Manager, including instructions for installing it on a UNIX server, see the following topics in Configuring and Managing WebLogic Server:

 

Selecting Directories for the WebLogic Integration Installation

During installation of WebLogic Integration, you need to specify locations for the following directories:

Choosing a BEA Home Directory

When you install WebLogic Integration, 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.

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:

The following illustration shows the structure of a sample BEA Home directory, created by the WebLogic Integration installation program, that includes a bundled SDK.

BEA Home directory structure


 

This illustration depicts only the files and directories required in the BEA Home directory. However, if you choose the default product installation directory, you will see additional directories in the BEA Home directory, such as weblogic81_wli85. 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.

Note: For some UNIX platforms, the WebLogic Integration installation program does not install an SDK.

During installation of WebLogic Integration, 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 Integration 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 Integration 8.5 in a BEA Home directory, but that BEA Home directory may also contain an instance of WebLogic Platform 7.0.

Understanding the Functions of the BEA Home Directory

The files and directories in the BEA Home directory are described in the following table.

Table 1-2 BEA Home Directory Description 

Component

Description

ext_components directory

Contains controls for third-party components and the TIBCO Rendezvous Control, if the latter is selected during the installation of WebLogic Integration 8.5.

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 ext_components are automatically installed with WebLogic Integration. When you are ready to start using them, however, you must integrate them, manually, with your application. For instructions, see "How Do I: Start Using a Packaged Control?" in the WebLogic Workshop Help at the following URL:

http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en
/workshop/guide/howdoi/howStartUsingPackagedControl.html

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 the following URL: http://download.oracle.com/docs/cd/E13196_01/platform/docs81/isv/controls.html

sdk directories

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:

  • jdk142_XX—the 1.4.2 version of the Sun Java 2 SDK. In this directory name, XX indicates the version of the Sun SDK installed on your system, for example jdk142_08.

  • jrockitXXX—the 1.4.2 version of the BEA JRockit SDK. In this directory name, XXX indicates the version of the JRockit SDK installed on your system, such as jrockit81sp5_142_08. SDK options vary by hardware platform. BEA JRockit is installed on Windows and Linux platforms. On Windows platforms only, both the Sun and BEA JRockit SDKs are installed.

Note: For some UNIX platforms, the WebLogic Integration installation program does not include an SDK.

logs directory

Contains a history file of installation and uninstallation for the BEA Home directory.

utils directory

Contains utilities that are used to support the installation of all BEA WebLogic Platform products. The utils.jar file contains code that supports the UpdateLicense utility.

license.bea file

An XML file that contains the license keys for all the BEA WebLogic products installed in the BEA Home directory.

Licenses are generally release-specific. You cannot use a license from a release of WebLogic Platform prior to 8.1. To upgrade a pre-8.1 license.bea file to enable use of, or additional functionality in, WebLogic Integration 8.5, see "Installing and Updating WebLogic Platform License Files" in Installing WebLogic Platform at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/license.html

Note: Do not edit license.bea file manually. Doing so may cause operational problems for the currently installed BEA products, or result in problems later when BEA products are installed for maintenance upgrades.

license_scale_limited.bea file

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 "Installing and Updating WebLogic Platform License Files" in Installing WebLogic Platform at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/license.html

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 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.

UpdateLicense (.cmd/.sh)

A command file (Windows) or a shell script (UNIX) that updates the current license.bea file with new license sections. The result is a merged license that contains both the existing and new license sections. For details about using the UpdateLicense utility, see "Installing and Updating WebLogic Platform License Files" in Installing WebLogic Platform at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/license.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 can 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 the initial installation of WebLogic Integration, to choose a product installation directory. If you accept the default, the WebLogic Integration software, and the WebLogic Platform components it requires, are installed in the following directory:

C:\bea\weblogic81_wli85

Here, C:\bea is the BEA Home directory and weblogic81_wli85 is the product installation directory for the WebLogic Integration 8.5 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_wli85 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 Integration 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:

platformXXX_win32.exe -log=C:\logs\platform_install.log

In this filename, XXX represents the version number of the software you are installing.

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.

 

Where to Find Upgrade Information

For information about installing service packs, see Installing Service Packs and Rolling Patches.

For information about upgrading WebLogic Integration components from previous releases, see BEA WebLogic Integration Upgrade Guide at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs85/upgrade/index.html

 

About Smart Update

The Smart Update feature enables you to upgrade your software quickly and easily with service packs and rolling patches.

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.

 

Skip navigation bar  Back to Top Previous Next