Skip navigation.
Downloads | Product Documentation | Support

Release Notes

# BEA WebLogic Platform 8.1 Release Notes

This document provides important information about all WebLogic Platform 8.1 releases up to and including Service Pack 6.

It includes the following topics:

- Revision History
- Terminology Used in This Document
- About BEA WebLogic Platform
- What Is New in BEA WebLogic Platform 8.1 Service Pack 5
- Tutorials and Samples
- Supported Configurations Information
- Customer Support
- Special Installation and Usage Instructions
- Installing the Java Plug-In for Online Help Search
- System Configuration Notes and Best Practices
- Known Limitations
- Problems Fixed

For updated release note information, see the BEA documentation Web site at the following URL:

`http://e-docs.bea.com`

Note: If you are using an earlier version of WebLogic Platform 8.1, such as Service Pack 4, and you need information specific to that service pack, see "Important Usage Notes for Previous Releases of WebLogic Platform 8.1" at:

http://e-docs.bea.com/platform/docs81/sp_notes/sp_notes.html

This document provides instructions for tasks such as enabling 128-bit encryption, configuring your WebLogic Platform domain for Oracle9i RAC, and downloading and installing the SDK1.4.2/Oracle10gdriver/Database patch.

For detailed information about any of the components of WebLogic Platform—WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal, or BEA JRockit—see the Release Notes document for the component in question.

For information about this component . . . | Choose the following Release Notes link . . .
--- | ---
WebLogic Server | http://e-docs.bea.com/wls/docs81/notes/index.html
WebLogic Workshop | http://e-docs.bea.com/workshop/docs81/relnotes/relnotes.html
WebLogic Integration | http://e-docs.bea.com/wli/docs81/relnotes/index.html
WebLogic Portal | http://e-docs.bea.com/wlp/docs81/relnotes/relnotes.html
BEA JRockit | http://e-docs.bea.com/wljrockit/docs142/relnotes/relnotes.html

# Revision History

This section describes the changes that have been made to this document since the release of BEA WebLogic Platform 8.1 Service Pack 5 (SP5).

Date | Description
12/02/05 | Added CR248707, which addresses the removal of the WebLogic Workshop IDE from a production environment, to Known Limitations.

# Terminology Used in This Document

The following two substitutable strings are used throughout this document, in pathnames:

- `BEA_HOME` represents the directory that serves as a repository for files used by multiple BEA products installed on the same machine, such as license files. A typical value for `BEA_HOME` is `c:\bea`, but you can designate any directory as `BEA_HOME`.
- `WL_HOME` represents the directory in which WebLogic Platform software is installed. By default, it is located under `BEA_HOME`. A typical default pathname is `c:\bea\weblogic81`, but you can situate `WL_HOME` in any directory.

# About BEA WebLogic Platform

BEA WebLogic Platform merges all the features of the existing BEA WebLogic products—application server, development, portal, and integration—into a highly integrated solution. This integrated solution combines the benefits of a common application infrastructure with an easy-to-use, robust framework.

# What Is New in BEA WebLogic Platform 8.1 Service Pack 5

BEA WebLogic Platform 8.1 Service Pack 5 (SP5) provides maintenance updates for all WebLogic Platform 8.1 components (WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal, and BEA JRockit). BEA WebLogic Platform 8.1 SP5 is the fourth full service pack for WebLogic Platform 8.1.

WebLogic Platform 8.1 SP5 can be used to update all WebLogic Platform 8.1 components.

Service Pack 5 includes the following enhancements and changes:

- Oracle9i RAC and 10g RAC Support
- Support Provided for WebLogic Scripting Tool (WLST)
- WebLogic Integration Enhancements
- WebLogic Portal Enhancements
- SDK Support Changes

For a complete list of the new features introduced in WebLogic Platform 8.1 GA, 8.1 SP2, 8.1 SP3, and 8.1 SP4, see the "What's New" page at the following URL:

`http://e-docs.bea.com/platform/docs81/interm/whatsnew.html`

## Oracle9i RAC and 10g RAC Support

Oracle Real Application Clusters (RAC) is a software option you can add to an Oracle 9i or 10g database to allow multiple database instances to access the same database (storage) simultaneously via cluster technology. In SP5, support for Oracle9i RAC and 10g RAC is extended to all component products in WebLogic Platform 8.1.

The benefits of using Oracle RAC include:

- High Availability—Because all instances access the same database, the failure of one instance does not cause the loss of access to the database.
- Load Balancing—Oracle RAC allows the server load to be distributed to different database nodes within the cluster.
- Scalability—Oracle RAC accommodates increasing numbers of users by allowing you to add database nodes to the cluster, increase storage, or both.

When you configure a domain with Oracle9i RAC and 10g RAC, the use of WebLogic JDBC MultiPools and global (XA) transactions with connection pool failover and load balancing is supported.

For information about configuring and using Oracle RAC with your WebLogic domain, see:

- "Using WebLogic Platform with Oracle RAC" in Managing WebLogic Platform Database Resources:

`http://e-docs/bea.com/platform/docs81/db_mgmt/oracle_rac.html`

- "Using WebLogic Server with Oracle RAC" in Programming WebLogic JDBC:

`http://e-docs.bea.com/wls/docs81/jdbc/oracle_rac.html`

## Support Provided for WebLogic Scripting Tool (WLST)

WLST is a command-line scripting interface that you use to configure WebLogic Server and WebLogic Platform domains. Using WLST, WebLogic Server administrators and operators can perform administrative tasks and initiate WebLogic Server configuration changes interactively or by using an executable script.

WLST supports both online and offline configuration:

- WLST online configuration

Enables you to perform administrative tasks and initiate WebLogic Server configuration changes while connected to a running server.

- WLST offline configuration

Enables you to create a new domain or update an existing domain without connecting to a running WebLogic Server instance—supporting the same functionality as the Configuration Wizard.

Prior to SP5, WLST was available only as an unsupported developer offering from dev2dev. As of SP5, WLST is available and supported by BEA as follows.

The following WLST component . . . | Is available as follows . . . | And is supported by BEA as follows . . .
--- | --- | ---
WLST Online | As a download from dev2dev. The software, including documentation that explains how to set up and use WLST Online, is available at the following Web site: `https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=13` | As of SP5, WLST Online is supported for use with all releases of WebLogic Platform 7.0 and 8.1.
WLST Offline | As a set of JAR files and scripts bundled with the WebLogic Platform 8.1 SP5 software. Instructions for setting up and using WLST Offline, as well as sample scripts for configuring domains, are available from dev2dev at the following Web site: `https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=97` | WLST Offline is now supported for use with WebLogic Platform 8.1 SP5 and later service packs only. WLST Offline is not supported in WebLogic Platform 7.0, or in releases of WebLogic Platform 8.1 prior to SP5.

## WebLogic Integration Enhancements

The WebLogic Integration 8.1 Service Pack 5 release includes the following new features:

- BPEL Import and Export Tools

BPEL Import and Export tools are provided to enable design-time interoperability with other tools that support the BPEL 1.1 specification. For more information, see BPEL Import and Export User Guide, available at the following URL:

`http://e-docs.bea.com/wli/docs81/bpel/index.html`

- TIBCO® RendezvousTM Control and Event Generator

The TIBCO Rendezvous (TIBCO RV) control enables seamless connection to, and transfer of data with, TIBCO RV version 7.2.16 using the Rendezvous daemon. TIBCO RV event generator listens for messages on a Rendezvous subject and raises events to the message broker on receiving the desired message. For more information, see TIBCO Rendezvous Control and Event Generator User Guide, available at the following URL:

`http://e-docs.bea.com/wli/docs81/tibcorv/index.html```

For more information about the 8.1 SP5 release of WebLogic Integration, see the WebLogic Integration Release Notes at the following URL:

`http://e-docs.bea.com/wli/docs81/relnotes/index.html`

## WebLogic Portal Enhancements

The WebLogic Portal 8.1 Service Pack 5 release includes the following new feature enhancements:

- Production Operations Tools

- The Propagation Utility allows you to propagate the configuration of one portal environment to another. Use this utility to propagate your portals from a staging to a production environment, or from production back to staging.
- The Export/Import Utility provides a round-trip feature that allows you to move books, pages, and desktops back and forth between development and staging environments. This utility lets you import `.portal` and `.pinc` files into the database, and also lets you export these files from the database. The exported files can be loaded back into WebLogic Workshop, or imported into another WebLogic Portal database.

- Enhanced Portlet Forking

With SP5 you now have the ability to thread the "pre-render" lifecycle as well as, or instead of, the "render" lifecycle. If your portlets communicate with external systems during this lifecycle, you might want to implement pre-render forking.

- New documentation

- Simplifying Portal URLs, available at `http://e-docs.bea/com/wlp/docs81/url/simplify.html`
- Portal Production Operations Guide, available at `http://e-docs.bea.com/wlp/docs81/prodOps/index.html`
- Getting Started with Autonomy Search, a guide that serves as an introduction to using Autonomy Search with WebLogic Portal, available at `http://e-docs.bea.com/wlp/docs81/autonomy/intro.html`
- BEA WebLogic Portlets for Groupware Integration documentation (formerly Compoze portlets), available from the WebLogic Portal documentation Web site at `http://e-docs.bea.com/wlp/docs81/index.html`

For more information about the 8.1 SP5 release of WebLogic Portal, see the WebLogic Portal Release Notes at the following URL:

`http://e-docs.bea.com/wlp/docs81/relnotes/relnotes.html`

## SDK Support Changes

The WebLogic Platform 8.1 SP5 software supports the following Java 2 SDKs:

- Sun Java 2 SDK 1.4.2_08
- BEA JRockit 1.4.2_08 SDK

If you are upgrading a domain from SP4 to SP5, the script in that domain that sets the `JAVA_HOME` variable needs to be modified to point to the new SDK that has been installed. This script is located in the domain's root directory. Depending on the type of domain you are upgrading, this variable is set in either the `setDomainEnv` or `startWebLogic` script.

To update the value of the `JAVA_HOME` variable, set it to the directory containing either the Sun or JRockit 1.4.2 directory as appropriate. For example:

>     set JAVA_HOME=C:\bea\jrockit81sp5_142_08

If you are installing SP5 as an upgrade to a previous 8.1 release, it is also recommended that you update your application startup scripts and silent configuration scripts to reference the new Sun or JRockit SDK directory.

For a complete list of Java SDKs for each hardware and operating system combination supported in WebLogic Platform 8.1 SP5, see "Summary of Supported Operating System Configurations, by Release Number" in "WebLogic Platform 8.1 Supported Configurations" in Supported Configurations for WebLogic Platform 8.1 at the following URL:

`http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/overview.html`

# Tutorials and Samples

To get hands-on experience with WebLogic Platform 8.1, we recommend that you try the following tutorials and samples:

- Tutorials and Samples for WebLogic Server
- Tutorials and Samples for WebLogic Workshop
- Tutorials and Samples for WebLogic Integration
- Tutorials and Samples for WebLogic Portal
- End-to-End WebLogic Platform Tour
- Configuration Wizard Tutorials

## Tutorials and Samples for WebLogic Server

WebLogic Server 8.1 provides the following tutorials and examples:

- Avitek Medical Records Tutorials:

`http://e-docs.bea.com/wls/docs81/medrec_tutorials/index.html`

- Pet Store 1.3.1_02
- Smart Ticket
- API Examples

Information about running the tutorials and examples is available at:

`http://e-docs.bea.com/wls/docs81/samples.html`

## Tutorials and Samples for WebLogic Workshop

WebLogic Workshop 8.1 provides the following tutorials:

- Getting Started tutorials, a series of short tutorials that offers a basic step-by-step introduction to the following core J2EE components:

- Web services
- Web applications
- Controls
- Enterprise JavaBeans
- Portal applications

- Tutorial: Java Control
- Tutorial: Web Service
- Tutorial: Page Flow
- Tutorial: Enterprise JavaBeans

Information about running the tutorials is available at:

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/navTutorials.html`

WebLogic Workshop includes numerous fully documented samples to help you become familiar with WebLogic Workshop Web service design patterns, page flows, features, and programming techniques. After completing the tutorials, we recommend that you also run the following WebLogic Workshop samples:

- The Getting Started Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/samples/navGSTutorialsSamples.html`

- Java Control Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/samples/navJavaControlSamples.html`

- Web Application Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/netui/samples/navPageFlowAndJSPSamples.html`

- Web Service Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/samples/navSampleWebServices.html`

- Web Service Client Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/samples/navWebServiceClientSamples.html`

- XMLBeans Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/samples/navXMLBeansSamples.html`

- XQuery Map Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/workshop/samples/navXQueryMapSamples.html`

- Enterprise JavaBean Samples

`http://e-docs.bea.com/workshop/docs81/doc/en/wls/samples/navEJBSamples.html`

## Tutorials and Samples for WebLogic Integration

WebLogic Integration 8.1 provides the following tutorials:

- Tutorial: Building Your First Business Process

`http://e-docs.bea.com/workshop/docs81/doc/en/integration/tutorial/tutWLIProcessIntro.html`

- Tutorial: Building Your First Data Transformation

`http://e-docs.bea.com/workshop/docs81/doc/en/integration/dttutorial/tutWLIDataTransIntro.html`

- Tutorial: Building a Worklist Application

`http://e-docs.bea.com/wli/docs81/wltutorial/index.html`

- Tutorials for Trading Partner Integration, which include:

- Tutorial: Building ebXML Solutions

`http://e-docs.bea.com/wli/docs81/tptutorial/ebxml.html`

- Tutorial: Building RosettaNet Solutions

`http://e-docs.bea.com/wli/docs81/tptutorial/rosettanet.html`

- WebLogic Integration—Business Connect Tutorial

`http://e-docs.bea.com/wlibc/docs81/install/tutorial.html`

Note: The code for the Trading Partner Integration tutorials is available for download from the dev2dev code samples Web site at the following URL:

`https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=75`

WebLogic Integration also provides the following samples:

- Example: ebXML Security Configuration

`http://e-docs.bea.com/wli/docs81/tpintro/ebXMLSec_appx.html`

- Example: RosettaNet Security Configuration

`http://e-docs.bea.com/wli/docs81/tpintro/RNSec_appx.html`

- Non-XML Data Mapping Sample

`http://e-docs.bea.com/workshop/docs81/doc/en/integration/samples/sampleMap.html`

- Using the Suppressible Attribute for a Static Subscription

`http://e-docs.bea.com/workshop/docs81/doc/en/integration/samples/sampleSuppressible.html`

The following samples are available on BEA's dev2dev site and can be accessed from the following URL:

`http://e-docs.bea.com/wli/docs81/sol_samples/index.html`

- Async Binary Update Sample
- Sync to Async Sample
- Large File Non-XML Sample
- Worklist Sample

## Tutorials and Samples for WebLogic Portal

WebLogic Portal 8.1 provides the following tutorials:

- Tutorial: Building Your First Portal

`http://e-docs.bea.com/workshop/docs81/doc/en/portal/tutorials/tutFirstPortalIntro.html`

- Tutorial: Changing a Portal's Look & Feel and Navigation

`http://e-docs.bea.com/workshop/docs81/doc/en/portal/tutorials/tutChangePortalLookFeelIntro.html`

- Tutorial: Showing Personalized Content in a Portlet

`http://e-docs.bea.com/workshop/docs81/doc/en/portal/tutorials/tutP13nPortletIntro.html`

- Tutorial: Creating a Login Control Page Flow Using the Wizard

`http://e-docs.bea.com/workshop/docs81/doc/en/portal/tutorials/tutLoginCtrlIntro.html`

- Tutorial: Using Page Flows Inside Portlets

`http://e-docs.bea.com/workshop/docs81/doc/en/portal/tutorials/tutPageFlowPortletIntro.html`

Information about running these tutorials is available at:

`http://e-docs.bea.com/workshop/docs81/doc/en/portal/tutorials/tutOV.html`

WebLogic Workshop 8.1 also provides sample portlets that you can use in the portals you create with WebLogic Workshop. Information about accessing these sample portlets is available at:

`http://e-docs.bea.com/workshop/docs81/doc/en/portal/samples/samples.html`

## End-to-End WebLogic Platform Tour

The WebLogic Platform Tour Guide provides a hands-on walk-through of a WebLogic Platform example developed with WebLogic Workshop. The example includes new portal, Web application, Java control, and business process functionality. To take the Tour, visit:

`http://e-docs.bea.com/platform/docs81/tour/index.html`

# Configuration Wizard Tutorials

WebLogic Platform 8.1 provides the following tutorials:

- Tutorial: Creating Your First Domain
- Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
- Tutorial: Extending an Existing Domain

Information about running these tutorials is available in "Tutorials: Using the Configuration Wizard" in Creating WebLogic Configurations Using the Configuration Wizard at the following URL:

`http://e-docs.bea.com/platform/docs81/confgwiz/tutorials.html`

# Supported Configurations Information

Information about configurations supported by WebLogic Platform, including hardware and software requirements, is provided in Supported Configurations for WebLogic Platform 8.1 at the following URL:

`http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/overview.html`

# Customer Support

If you have any questions about this version of WebLogic Platform, or if you have problems installing and running the product, contact BEA Customer Support through BEA eSupport at:

`http://support.bea.com`

You can also contact Customer Support by using the contact information provided on the BEA Customer Support card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

- Your name, e-mail address, phone number, and fax number
- Your company name and company address
- Your machine type and authorization codes
- The name and version of the product you are using
- A description of the problem and the content of pertinent error messages

# Special Installation and Usage Instructions

For WebLogic Platform 8.1, special installation and usage instructions are required for some operating systems, such as IBM AIX 5.1 and HP-UX 11i v2 on Itanium.

These installation instructions are now provided in Supported Configurations for WebLogic Platform 8.1 at the following URL:

`http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/install_info.html`

# Installing the Java Plug-In for Online Help Search

The online help for the following tools includes a search function that is provided by a Java applet:

- WebLogic Workshop IDE (when configured to use help files from the local disk)
- Configuration Wizard
- Configuration Template Builder

This applet requires a Java plug-in. If you do not have this plug-in installed on your system and you want to be able to search the online help for these tools, then you must install the plug-in.

Note: By default, the content for the Workshop IDE online help topics is hosted at BEA, and the search function is also performed at BEA. Unless you specifically configure the IDE to use help files that are installed on the local disk, the plug-in described in this section is never used for IDE help search.

If you are working on a Microsoft Windows platform, the first time you initiate a search in the online help for one of these tools, you are prompted to download and install the plug-in.

However, if you are working on the HP-UX, Red Hat Enterprise Linux, or Sun Solaris platform, you need to download and install the Java plug-in manually. Table 1 provides the Web site from which you can download the required Java plug-in for these platforms. The plug-in you download must be version 1.4 or later.

Table 1 Downloading the Java Plug-in Required for Help Search Applet

For the following platform . . . | Go to the following Web site to obtain the Java plug-in
--- | ---
HP-UX | For Itanium-based systems, download and install the latest Runtime plug-in version 1.4.2 from: http://www.hp.com/products1/unix/java/java2/jpi/downloads/ For PA-RISC-based systems, download and install the latest Runtime Environment for Java version 1.4.2 from: http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/index_pa-risc.html
Red Hat Enterprise Linux | Complete the following steps: 1. Go to the following URL and choose Download J2SE JRE: http://java.sun.com/j2se/1.4.2/download.html. 2. Accept the licence agreement that is displayed. 3. Choose either the RPM in self-extracting file, or the self-extracting file.
Sun Solaris | Complete the following steps: 1. Go to the following URL and choose Download J2SE JRE: http://java.sun.com/j2se/1.4.2/download.html. 2. Accept the licence agreement that is displayed. 3. Choose the JRE appropriate for your system.

# System Configuration Notes and Best Practices

This section provides tips, based on best practices, for configuring the environment in which you run WebLogic Platform 8.1:

- SDK Selection
- Important Database Setup Information
- Character Limit for the BEA Home Directory Name
- WebLogic Integration Domains with Administration and Managed Servers Require a Cluster
- Referencing Database Schemas
- Apache Web Server Support

## SDK Selection

This release provides the BEA JRockit SDK and JVM. BEA JRockit is designed specifically to address the needs of server-side applications. To use WebLogic Platform 8.1 client-side development tools and features, such as the WebLogic Workshop IDE, use of the Sun Java 2 SDK is recommended. Therefore, when using the WebLogic Workshop IDE to develop applications to run on the JRockit SDK, do not remove the Sun Java 2 SDK 1.4.2 from your machine because it is required by the IDE.

Notes: JRockit is available on Windows and Linux platforms only.

For some UNIX platforms, the WebLogic Platform installation program does not include an SDK.

For a list of JVMs supported for your operating system and hardware platform, see "Summary of Supported Operating System Configurations, by Release Number" in "WebLogic Platform 8.1 Supported Configurations" in Supported Configurations for WebLogic Platform 8.1 at the following URL:

`http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/overview.html`

### Steps to Switch JVMs

The following instructions are provided for users who have already installed WebLogic Platform 8.1 SP5 and want to switch to another JVM:

1. Examine the WebLogic Server start script. This script is located in your domain's root directory, and by default is named `startWebLogic.cmd` (Windows) or `startWebLogic`.`sh` (UNIX).
2. Locate the settings for the following two variables:

- `JAVA_VENDOR`
- `JAVA_HOME`

3. If these variables are set within the script, change them as appropriate.

The following `set JAVA_VENDOR` and `set JAVA_HOME` commands specify the BEA JRockit 1.4.2 SDK, where `c:\bea` is the BEA home directory:

`set JAVA_VENDOR=BEA
set JAVA_HOME=c:\bea\jrockit81sp5_142_08`

For Sun, the equivalent commands are as follows:

`set JAVA_VENDOR=Sun
set JAVA_HOME=c:\bea\`jdk142_08

4. If the `JAVA_VENDOR` variable is not set in the WebLogic Server start script, then you need to set the default JVM in the `setDomainEnv`.`cmd` (Windows) or `setDomainEnv.sh` (UNIX) script as described in this step. The `setDomainEnv` script is also located in the domain's root directory.

The following two code snippets show the switching of the default JVM from Sun Java 2 SDK 1.4.2 to BEA JRockit 1.4.2 SDK in `commEnv.cmd` on Windows. In these snippets, the BEA home directory is `c:\bea`.

The first code snippet shows the initial settings that establish Sun Java 2 SDK 1.4.2 as the default:

>     if "%JAVA_VENDOR%"=="BEA" (
>            set JAVA_HOME=C:\bea\jrockit81sp5_142_08
>     ) else (
>            if "%JAVA_VENDOR%"=="Sun" (
>                  set JAVA_HOME=C:\bea\jdk142_08
>            ) else (
>                  set JAVA_VENDOR=Sun
>                  set JAVA_HOME=C:\bea\jdk142_08
>            )
>     )

The second code snippet shows the changes, in bold, made to switch to JRockit as the default:

>     if "%JAVA_VENDOR%"=="BEA" (
>            set JAVA_HOME=C:\bea\jrockit81sp5_142_08
>     ) else (
>            if "%JAVA_VENDOR%"=="Sun" (
>                  set JAVA_HOME=C:\bea\jdk142_08
>            ) else (
>                  set JAVA_VENDOR=BEA
>                  set JAVA_HOME=C:\bea\jrockit81sp5_142_08

### Supported Configurations

For more information about WebLogic Platform 8.1 support for BEA JRockit and the Sun Java 2 SDK, see "Summary of Supported Operating System Configurations, by Release Number"

in "WebLogic Platform 8.1 Supported Configurations" in Supported Configurations at the following URL:

`http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/overview.html`

## Important Database Setup Information

If your domain includes the MS SQL Server, DB2, Oracle RAC, or Sybase database, see Managing WebLogic Platform Database Resources at the following URL for required database setup information:

`http://e-docs.bea.com/platform/docs81/db_mgmt/index.html`

This document also includes the following sections:

- Configuring Your Database Resources
- Preparing Your Database for Production
- Switching Databases

## Character Limit for the BEA Home Directory Name

It is recommended that you do not exceed a maximum of 12 characters when naming your BEA Home directory. If the name of this directory contains more than 12 characters, the `CLASSPATH` resolution may not be performed properly.

## WebLogic Integration Domains with Administration and Managed Servers Require a Cluster

A WebLogic Integration domain that includes an administration server and one or more managed servers must include a cluster. The Configuration Wizard enables you to create a WebLogic Integration domain that includes an administration server and one or more managed servers without a cluster, but this is an unsupported configuration.

## Referencing Database Schemas

When creating a domain for WebLogic Server, WebLogic Integration, WebLogic Portal, or WebLogic Workshop, the database schema used in that domain cannot be used or referenced by any other domain. For example, the database schema for the WebLogic Integration repository that is configured in one domain cannot be shared by the WebLogic Integration configuration in another domain.

## Apache Web Server Support

Note that WebLogic Platform supports only those users of the Apache multithreaded option who use 2.0.48 or a higher version of Apache. For complete details about Apache Web Server support in WebLogic Platform 8.1, see "Supported Web Servers, Browsers, and Firewalls" in Supported Configurations for WebLogic Platform 8.1 at the following URL:

`http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/add-ons.html`

# Known Limitations

This section describes problems that have been identified in this release. For each problem listed in the following table, a problem ID is specified. These IDs enable BEA and users to monitor the status of issues while solutions are being developed. Whenever possible, workarounds are provided.

Table 2 Known Limitations in WebLogic Platform 8.1

Problem ID | Description
--- | ---
CR097633 | Each script in WL_HOME/common/eval/pointbase/tools/startPointBaseConsole requires a PointBase Server to be started independently If a PointBase Server is not running when the PointBase Console is launched, the Connect to the Database option fails with an error message (SQL State 08004). Operating System: All Workaround: Before launching either a domain-based startPointBaseConsole script or the PointBase Console (from one of the Example links on the Start menu), start the WebLogic Server for the relevant domain. As it starts each domain, WebLogic Server also starts the PointBase Server associated with the domain. When you log in to the database console (by selecting Connect to the Database), enter `weblogic` as both your user ID and your password.
CR099617 | Restrict the addition of an application via extension template if the application already exists in the domain The Configuration Wizard allows you to extend a domain using an extension template that contains an application name that already exists in the target domain. As a result, two applications of the same name will end up in the `config.xml` file for the domain. Operating System: All Workaround: No workaround exists. Make sure that any extension template you plan to use does not contain an application with the same name as an application in your domain.
CR107937/ 34347 | Workshop Web service fails to invoke secure WebLogic Server Web service due to a missing timestamp header Interoperability between Workshop Web services and a secure WebLogic Server Web service is currently not supported. Operating System: All Workaround: N/A
CR108897/ 12823 | Windows-31J is not included in versions 1.4.0 through 1.4.1_03 of the Sun Java 2 SDK The WebLogic Workshop 8.1 IDE and compiler use a new API from Sun called java.nio.Charset (introduced in the Sun Java 2 SDK 1.4.0). The implementation of this API contains a bug: Windows-31J, the Japanese character set most commonly used in Windows, is not included in versions 1.4.0 through 1.4.1_03 of the Sun Java 2 SDK. For details, see: http://developer.java.sun.com/developer/bugParade/bugs/4626545.html The absence of Windows-31J does not mean that users cannot read and write their files using Japanese; other character sets are available. If, however, characters from a character set other than Windows-31J are included in an IDE file, the IDE fails silently: it allows the user to save the file, without issuing a warning that the file has been corrupted by the inclusion of non-Windows-31J characters. This problem will be solved in two future versions of the Sun Java 2 SDK: 1.4.1_05 and 1.4.2. These versions will include the Windows-31J (MS932) character set. Operating System: All Workaround: For types of files that may include encoding headers, including HTML, XML, and JSP files, specify UTF-8, instead of Windows -31J, for the file's encoding.
CR109961 | If you change the DBMS Name for PointBase on Configure JDBC Connection Pools, the database files are not renamed In the Configuration Wizard window labeled Configure JDBC Connection Pools, you can change the values of several PointBase parameters: DBMS Name, Dbms Host, Dbms Port, User Name, and User Password. Your changes, however, are reflected only in the `config.xml` file for your domain; your PointBase database files and startup scripts are not updated with the new values. Operating System: All Workaround: When using the Configuration Wizard and a PointBase database, always accept the default values for DBMS Name, DBMS Host, DBMS Port, User Name, and User Password.
CR110086 | The PointBase database must use port number 9093 The Configuration Wizard offers the option of changing the port number used by PointBase from the default. If you do change the PointBase port number, however, the test connection for the database fails and the server cannot start properly. Operating System: All Workaround: Always accept the default port number for PointBase: 9093.
CR110828 | When you try to stop the server by entering Ctrl+c, the PointBase process running in the background is not killed If you enter Ctrl+c to stop a server on a platform comprising Windows and PointBase, and then try to start a different server, you may get exceptions, but you will not get any obvious clues about the problem. Operating System: All Workaround: On Windows platforms, run the stopWeblogic script (`stopWebLogic.cmd` on Windows or `stopWebLogic.sh` on UNIX) to shut down the server and all related processes.
CR110893 | Generated stopWebLogic script cannot stop PointBase configured at a nondefault port The Configuration Wizard does not customize the stopWebLogic script (`stopWebLogic.cmd` on Windows or `stopWebLogic.sh` on UNIX) of a created domain with a user-specified PointBase port number. When the server is shut down from a WebLogic Server console, the PointBase server is left running. Operating System: All Workaround: You have a choice of two workarounds: Run the stopWebLogic script to force a shutdown of the WebLogic Server. Shut down the WebLogic Server from the WebLogic Server console and then run the stopWebLogic script again.
CR111126/ 36644 | Corrupted connections in connection pool using MS SQL Server and XA are used Shared use of a JDBC connection pool for global (XA) transactions by multiple Data Sources creates recovery problems in the event of a failure. Operating System: All Workaround: If you are using an MS SQL Server driver and corrupted connections have already occurred, adjust the JDBC Connection Pool configuration in the WebLogic Server Administration Console by doing the following: 1. With the Administration Server running, log in to your domain's Administration Console and navigate to domain_name—>Services—>JDBC—>Connection Pools—>pool_name. 2. Click Show to display the Advanced Options section. 3. Check Test Reserved Connections to enable your reserved connections. 4. In the Test Table Name field, enter `dbo.sysusers`. 5. Click Apply. The corrupted connections are no longer used.
CR125469 | A java.lang.IncompatibleClassChangeError exception is generated when the clientgen or autotype Ant task is executed to generate non-built-in data type components from an XML Schema file This problem happens only when the following two circumstances occur simultaneously: (a) the `wlxbean.jar` and `xbean.jar` files are specified in the `CLASSPATH` variable for your build or deployment environment; and (b) you are using the `clientgen` or `autotype` Ant task to generate non-built-in data type components from an XML Schema that references SOAP encoding data types. The two JAR files, used by the XMLBeans feature, are part of WebLogic Platform and Workshop; they are not part of WebLogic Server. The JAR files contain SOAP-encoding data type classes that conflict with those generated by the Ant tasks. This problem is discussed further in FAQs: Web Services in WebLogic Server Frequently Asked Questions. Operating System: All Workaround: Use any of the following three ways to work around this problem: 1. Use the `packageName` or `packageBase` attribute of the `autotype` Ant task (or the `typePackageName` or `typePackageBase` attribute of the `clientgen` Ant task) to force the Ant-task-generated SOAP-encoding data types into a user-specified package so that they do not conflict with the XMLBeans data types. For information about the attributes of the `autotype` and client Ant tasks, see Web Service Ant Tasks and Command-Line Utilities. 2. Remove the `xbean.jar` and `wlxbean.jar` files from your build and deployment environment. These files are installed in the `WL_HOME``\server\lib` directory by WebLogic Platform, where `WL_HOME` refers to the main WebLogic Platform installation directory, such as `c:\beahome\weblogic81`. If you need these JAR files (because some of your Web Services use XMLBeans), then do the following: (a) find all the EAR files that contain WebLogic Web Services that, in turn, use XMLBeans; and (b) put a copy of the two JAR files (`xbean.jar` and `wlxbean.jar`) in the `APP-INF/lib` directory of each such EAR file. 3. If you do not use WebLogic Workshop to create applications, or if you do not deploy any applications generated by WebLogic Workshop, then you can remove the conflicting SOAP-encoding classes from the `wlxbean.jar` and `xbean.jar` files.
CR126214 | When Smart Update is used to revert a Service Pack installation, the End-to-End sample application domain is not reverted After a WebLogic Platform installation is reverted from SP2 to a previous release, the End-to-End sample application does not start. Operating System: All Workaround: After you revert a WebLogic Platform installation, restart the server in the End-to-End sample application domain you are using.
CR126952/ CR126651/ CR127350 | Upgrade installer overwrites all user applications in the samples directory As part of the upgrade procedure, the WebLogic Platform 8.1 SP2 installation program automatically overwrites any files, including applications, that you have created in `WL_HOME`. Operating System: All Workaround: Before installing SP2, make backup copies of any files or applications that you have created in `WL_HOME`. As a general best practice, however, if you want to ensure that your application files are untouched by newer installations of WebLogic Platform, create new domains outside of the BEA product directory. For more detailed information regarding additional workarounds, please contact BEA Customer Support and reference CR126952.
CR128232/ 43254 | WebLogic Integration and End-to-End sample domains log MDB warnings during server startup When the server is started in either a Platform or End-to-end sample domain, the following messages are logged: <BEA-014006> <The message driven bean (MDB) named "ProcessTrackingEventErrorListener" has a dispatch policy "wli.internal.ProcessTracking" that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.> <BEA-014006> <The message driven bean (MDB) named "InstanceInfoEventListener" has a dispatch policy "wli.internal.ProcessTracking" that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.> <BEA-014006> <The message driven bean (MDB) named "ProcessTrackingEventListener" has a dispatch policy "wli.internal.ProcessTracking" that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.> Operating System: All Workaround: These messages are advisory; they can be ignored. It is possible, by using the WebLogic Server Administration Console, to create the execute queues listed in these logged messages in such a way that they contain the listed EJBs. If you create execute queues in this way, however, make sure that you specify a thread size that accommodates the relevant application and tracking level. For more information about creating execute queues, see "Execute Queue —> Configuration" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_executequeue_config.html
CR135846 | Use of org.apache.xalan.processor.TransformerFactoryImpl causes portability issues In the `weblogic.xml.jaxp.WebLogicTransformerFactory` API, the constructor is using `org.apache.xalan.processor.TransformerFactoryImpl` as the default. This behavior contradicts the specification in the WebLogic Server Administration Console Online Help document (http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_xmlregistry_config.html), which specifies `weblogic.apache.xalan.processor.TransformerFactoryImpl` as the default. Also, use of the Xalan transformer obtained directly from Apache causes portability issues, because this version is newer than the JAXP currently shipped with WebLogic Server. Operating System: All Workaround: Set the Transformer Factory to `weblogic.apache.xalan.processor.TransformerFactoryImpl`. For details, see: http://e-docs.bea.com/wls/docs81/ConsoleHelp/xml.html
CR137592 | Java error when running Workshop without Administrator privileges If you install WebLogic Workshop on a Windows system as a user with Administrator privileges, then all users must have Administrator privileges to use Workshop. Otherwise, users without Administrator privileges receive the following error when running a Workshop application: `java.lang.SecurityException: Could not open windows registry node Software\JavaSoft\prefs at root 0x80000002: Access Denied` Operating system: Windows Workaround: On Windows systems, install and use WebLogic Workshop as a user with Administrator privileges.
CR172412 | Distributed queues assigned to an additional cluster cannot be configured because they do not appear in the JMS Queue dropdown list in the Configuration Wizard When using the Configuration Wizard to create a multi-cluster domain, a problem exists in the Configure JMS Distributed Queue Members window. This problem occurs when adding a distributed queue member to a JMS distributed queue that has been assigned to a second cluster. When you click on the queue, and click the Add button, the JMS Queue dropdown list is empty. This prevents you from using the Configuration Wizard to assign distributed queue members to a JMS distributed queue not on the primary cluster. Operating system: All Workaround: After creating the domain, use the WebLogic Server Administration Console to configure JMS distributed queues as follows: 1. Start the Administration Server and the Administration Console. 2. In the Administration Console, select Services—> JMS—> Distributed Destinations. 3. Select the Distributed Destination to configure. 4. Select the AutoDeploy tab, and add the distributed queue members for the desired JMS distributed queue.
CR181310 | Anonymous login to Web application resources under certain circumstances can fail If your `config.xml` file contains the flag `FullyDelegateAuthorization=true`, anonymous access to resources in a Web application are denied when those resources have no security restraints specified in the application's `web.xml` file. This combination, namely, `flag FullyDelegateAuthorization=true`, along with the value of `CLIENT-CERT` in the <`login-config`> element of the `web.xml` file, causes anonymous access to any resource within the Web application to fail with the following error: `401 - Unauthorized`. Operating System: All Workarounds: (1) If you require these settings and the use of `CLIENT-CERT`, you need to create a descriptor constraint for each of the resource URLs used by the Web application. For more information about using CLIENT-CERT, see "Two-Way SSL" in the WebLogic Workshop Help at the following URL: http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/security/transport/conTwoWaySSL.html (2) If you are not using WebLogic Integration, you can change `FullyDelegateAuthorization` from true to false.
CR181772 | Domain administration port: error starting managed server on same machine as Administration Server When a cluster domain is configured with Managed Servers on multiple machines, including a machine that hosts both a Managed Server and the Administration Server, errors are generated in the log file for the Managed Server that is on the same machine as the Administration Server. Operating System: All Workaround: The administration port accepts only secure, SSL traffic, and all connections via the port require authentication. Enabling the administration port imposes the following restrictions on your domain: The Administration Server and all Managed Servers in your domain must be configured with support for the SSL protocol. Managed Servers that do not support SSL cannot connect with the Administration Server during startup—you will have to disable the administration port in order to configure them. Because all server instances in the domain must enable or disable the administration port at the same time, you configure the administration port at the domain level. You can change an individual Managed Server's administration port number, but you cannot enable or disable the administration port for an individual Managed Server. The ability to change the port number is useful if you have multiple server instances with the same Listen Address. After you enable the administration port, you must establish an SSL connection to the Administration Server in order to start any Managed Server in the domain. This applies whether you start Managed Servers manually, at the command line, or using Node Manager. For instructions to establish the SSL connection, see "Booting Managed Servers to Use Administration Port" in "Configuring Network Resources" in Configuring and Managing WebLogic Server at the following URL: http://e-docs.bea.com/wls/docs81/adminguide/network.html After enabling the administration port, all Administration Console traffic must connect via the administration port. If multiple server instances run on the same computer in a domain that uses a domain-wide administration port, you must either: host the server instances on a multi-homed machine and assign each server instance a unique listen address; or, override the domain-wide port on all but one of one of the servers instances on the machine. Override the port using the Local Administration Port Override option on the Advanced Attributes portion of the Server—> Connections—> SSL Ports page in the Administration Console.
CR182698 | Smart Update fails to complete on Red Hat Linux 64-bit systems When upgrading to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux 3.0 on Itanium systems, Smart Update hangs and does not complete the installation. (Smart Update works on Red Hat Enterprise Linux 2.1 on Itanium, but not 3.0.) Operating System: Red Hat Enterprise Linux AS, ES 3.0 on Itanium Workaround: Do not use Smart Update to upgrade to WebLogic Server 8.1 SP3 on Red Hat Enterprise Linux 3.0. Either use the upgrade installer, or perform a new installation of WebLogic Server 8.1 SP3. For more information about using the upgrade installer, see "Installing Service Packs and Rolling Patches Using a Downloadable Upgrade Installer" in "Installing Service Packs and Rolling Patches" in Installing BEA WebLogic Platform at the following URL: http://e-docs.bea.com/platform/docs81/install/update.html Note that if you are simultaneously upgrading WebLogic Server 8.1 and Red Hat Enterprise Linux (from 2.1 to 3.0), you can complete the following procedure to use Smart Update successfully to upgrade to SP3: 1. Upgrade WebLogic Server 8.1 to SP3. 2. Upgrade your machine from Red Hat Enterprise Linux 2.1 to 3.0.
> CR183569 | Sun JDK HotSpot compiler crashes when precompiling JSPs in production mode (-server) with debug enabled In domains configured with the Sun Java 2 SDK 1.4.2_04, the Sun JDK HotSpot compiler can crash while precompiling JSPs with a HotSpot Virtual Machine Error. A log similar to the following may be generated:
>     # HotSpot Virtual Machine Error, Internal Error
>     # Please report this error at
>     # http://java.sun.com/cgi-bin/bugreport.cgi
>     #
>     # Java VM: Java HotSpot(TM) Server VM (1.4.2_04-b05 mixed mode)
>     #
>     # Error ID: 53484152454432554E54494D450E435050018D
>     #
>     # Problematic Thread: prio=5 tid=0x2d48f578 nid=0xc10 runnable
>     #
This problem is most likely to occur with the following JVM command-line options: `-server -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -java.compiler=NONE -ea -da:com.bea... -da:javelin... -da:weblogic...` Operating System: All Workaround: Any of the following workarounds prevent this problem from occurring: Use the BEA JRockit SDK instead of the Sun Java 2 SDK. Edit the WebLogic Server start script to start using the `-client` (not `-server`) option when debugging with Sun Java 2 SDK 1.4.2_04. Disable debugging, either by editing the `setDomainEnv` script, or by manually removing the JVM debug arguments. Don't precompile when debugging. Update the domain configuration to use the Sun Java 2 SDK 1.4.2_05 or later.
CR192264 | EAR file component with pathname longer than 255 characters may not be accessible Before an EAR file is deployed on a domain, it is exploded to the`.applications` folder. When the combined length of (a) the full path of the domain that includes a particular component, and (b) the relative path of the component itself exceeds 255 characters, the component in question cannot be located. Operating System: Windows Workaround: Keep the domain path as short as possible.
CR203645 | When you add a Managed Server to a cluster in an existing domain, the domain fails to start If you add a Managed Server to a cluster in an existing domain, the updated domain fails to boot. This limitation exists if you attempt to add the Managed Server outside the scope of creating a new domain or modifying an existing domain via an extension template. Operating System: All Workaround: To add a Managed Server to a cluster, you must add the server via either a domain or a domain extension template. For example, you can add a Managed Server to an existing domain via the Configuration Wizard or WLST Offline in either of the following ways: You can extend the domain via an extension template. While applying the extension template, you can specify the additional Managed Server. You can create a template of the existing domain, then create a new domain based on that template in which you specify the additional Managed Server.
CR204361 | When creating an extension template, the JMSDistributedQueues in a cluster domain are lost When using the Template Builder to create an extension template of a clustered domain that includes JMS distributed queues, those queues are excluded from the resulting template. Operating System: All Workaround: At the time you use the resulting template to extend a domain, configure each JMS distributed queue as required.
CR204521 | Downgrading from SP5 to SP4 or SP3 may fail on HP-UX if maxdsiz is too small If you upgrade from 8.1 SP3 to 8.1 SP4, or from 8.1 SP4 to 8.1 SP5, by using Smart Update or the Upgrade Installer on an HP-UX 11.0 or 11i on PA-RISC configuration, and then try to use the same tool to downgrade from 8.1 SP5 to 8.1 SP4, or 8.1 SP4 to 8.1 SP3, the downgrade attempt may fail. Operating system: HP-UX 11.0, 11i on PA-RISC Workaround: When downgrading from 8.1 SP5 to SP4, set the `maxdsiz` kernel parameter to 1 GB or higher. When downgrading from 8.1 SP4 to SP3, set the `maxdsiz` kernel parameter to 2 GB or higher.
CR206782 | Error encountered while upgrading from SP2 to SP3 on AIX If you upgrade WebLogic Platform from 8.1 SP2 to 8.1 SP3 on AIX, the upgrade process might fail before completion with the following message: `Fatal error. Cannot move libmuxer.so which is in use.` This condition occurs due to improper system memory cleanup when WebLogic Server 8.1 SP2 shuts down. Operating system: IBM AIX 5.1 or 5.2 PowerPC, POWER3, POWER4, and POWER5 Workaround: Before upgrading to SP3, you must manually clean out any unused libraries on your machine by using the `slibclean` command, which you must execute as root. (Note that rebooting the machine after running this command is not necessary.)
CR208487 | Applications fail to launch from QuickStart if the installation directory name includes High-ASCII characters If the directory name for either the BEA Home or WebLogic Home directories contains characters from the High-ASCII character set, you cannot use QuickStart to launch applications, such as the Configuration Wizard. This is a limitation imposed by the Sun Java 2 J2SE. Operating system: Any system in which the Sun Java 2 J2SE is used Workaround: If you plan to use QuickStart to launch applications, during installation you should choose directories for BEA Home and WebLogic Server Home with names that include only the ASCII character set.
CR209566 | The 'ulimit -n' command to limit the number of open file descriptors is not provided in commEnv.sh on HP-UX platforms On many UNIX platforms, `WL_HOME``/common/bin/commEnv.sh` script invokes the `ulimit -n` command to set the upper limit of number of open file descriptors to 1024 before WebLogic Server is started. However the `-n` option of the `ulimit` command is not supported by HP-UX shells (except `ksh`). In WLS8.1SP5, the `commEnv.sh` script does not set the upper limit of open file descriptors for HP-UX. Operating system: HP-UX 11.0, 11i on PA-RISC Workaround: In your shell environment, you can manually limit the number of open file descriptors, which should be set to less than 1024.
CR212708 | Smart Update hangs during upgrade to SP4 on HP-UX If you use Smart Update to upgrade WebLogic Platform 8.1 on HP-UX 11i Itanium systems, the upgrade procedure hangs before running to completion. This problem occurs when you upgrade to any service pack of WebLogic Platform 8.1. Operating system: HP-UX 11i Itanium Workaround: Use the package upgrade installer instead of Smart Update for upgrading a WebLogic Platform 8.1 installation. For more information, see "Installing Service Packs and Rolling Patches Using a Downloadable Upgrade Installer" in "Installing Service Packs and Rolling Patches" in Installing BEA WebLogic Platform at the following URL: http://e-docs.bea.com/platform/docs81/install/update.html
CR226286 | WLST failures should cause WLST to exit with failure Currently if the execution of a WebLogic Server Scripting Tool (WLST) script fails, WLST terminates without sending a proper failure notification. As a result, calling components that depend on a successful WLST script execution are not aware of the failure, such as when WLST is employed via Ant, which is a common use case. Operating System: All Workaround: When invoking WLST from an Ant script, it is recommended that you fork a new JVM by specifying `fork="true"`. This will ensure a clean environment and prevent the WLST `exit` command, which calls `System.exit(0)`, from exiting the Ant script.
CR228706 | Cannot overwrite another user's wlst_module.py file If you use WLST as a module, you are unable to overwrite another user's `wlst_module.py` files. Operating System: UNIX Workaround: Make sure you have write permissions to the directory specified by the `java.io.tmpdir` Java system property.
CR231633 | Multibyte characters are garbled when WLST runs in interactive mode If you install WebLogic Platform on a machine that is configured with the multibyte character set, and launch WLST from a command window prompt, the output generated by WLST—in both the command window as well as any files into which WLST writes—is garbled. This problem occurs only when WLST is used offline in interactive mode; that is, when not connected to a running WebLogic Server instance. Operating System: All Workaround: On machines configured with the multibyte character set, use WLST offline in script mode.
CR232858 | WLST fails to launch when multibyte characters are used in the installation path If the names of the directories in which WebLogic Platform is installed contain multibyte characters, attempting to start WLST from a command window fails, and an error message similar to the following example is displayed: `>Initializing WebLogic Scripting Tool (WLST) ... >Problem invoking WLST - Traceback (innermost last): > File "<string>", line 7, in ? >ImportError: No module named plateng` Operating System: All Workaround: When installing WebLogic Platform, do not specify directories for BEA Home or WebLogic Home that have names containing the multibyte character set.
CR235573 | Failover with Oracle RAC takes longer than the time specified in Test Interval in RDBMSAuthenticator In a domain configured with Oracle RAC, the length of time required for failover to a secondary RAC node to complete is longer than the time specified in the Test Interval parameter in the RDBMSAuthenticator window. Operating System: All Workaround: The RDBMSAuthenticator will failover to a secondary RAC node only after detecting a database connection failure, either through failed user authentication attempts or through RDBMSAuthenticator connection tests. Connections that fail the tests are closed and reopened to re-establish a valid physical database connection, as determined by the Test Interval parameter specified while creating the RDBMSAuthenticator. The Test Interval setting should be based on a trade-off between system availability requirements and database performance impact. Lower settings will reduce the amount of time to detect RAC failures and reduce the likelihood of failed user authentication attempts, but will increase the database load. The default setting is 120 seconds. To minimize failed user authentication attempts due to RAC failures, set the Test Interval parameter to its minimum value of 5 seconds. With the Administration Server running, log in to your domain's Administration Console and navigate to Security—> Realms—> myrealm—> Providers—> Authentication—> RDBMSauthenticator. Select the Details tab—> Test Interval. The Test Interval parameter sets the amount of time for connections to be closed and re-established.
CR237216 CR241625 | Japanese characters are garbled in the graphical user interface to the installation program, Configuration Wizard, and Template Builder On Red Hat Enterprise Linux 4.0 systems configured with the Japanese character set, the graphical user interfaces to the installation program, Configuration Wizard, and Template Builder fail to display correctly. This problem is caused by a limitation in the Sun Java 2 J2SE 1.4.2_08 JDK, which does not have the `font.properties` files for the Japanese character set for Red Hat Enterprise Linux 4.0 systems. Operating System: Red Hat Enterprise Linux 4.0 Workaround: Use the console-mode interfaces to these applications. Note: This limitation does not exist on Red Hat Enterprise Linux 3.0 systems. However, for Red Hat Enterprise Linux 4.0 systems, Sun provides a workaround that is described at `http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6235633`.
CR248707 | Cannot install WebLogic Integration in a production environment without also installing the WebLogic Workshop IDE In WebLogic Platform 8.1 SP5, when you use a custom or silent-mode installation method to install the WebLogic Integration server component, both the WebLogic Workshop Runtime Framework and the IDE are installed. Only the WebLogic Workshop Runtime Framework should be installed with the WebLogic Integration server component. Operating System: All Workaround: To remove the WebLogic Workshop IDE from a production environment, manually delete the `BEA_HOME`\weblogic81\workshop directory and files.

# Problems Fixed

This section lists problems that have been fixed in WebLogic Platform 8.1 that were described as known limitations in earlier versions of this document.

This topic includes the following sections:

- Problems Fixed in Service Pack 4
- Problems Fixed in Service Pack 3
- Problems Fixed in Service Pack 2

## Problems Fixed in Service Pack 4

Table 3 lists and describes the problems fixed in WebLogic Platform 8.1 SP4.

Table 3 Problems Fixed in WebLogic Platform 8.1 Service Pack 4

Problem ID | Description
--- | ---
CR127141 | Exception occurs while the End-to-End server is being shut down If you boot the End-to-End server and then run the `stopWebLogic` script (`stopWebLogic` on Windows, `stopWebLogic.sh` on UNIX), the `stopWebLogic` script throws an exception on the server console. Operating System: All Workaround: N/A. Fix Information: In SP3, the exception occurred while applications were being undeployed. In SP4, this problem no longer occurs because multiple applications with the same LoadOrder are deployed and undeployed in alphabetical order of deployment name.
CR181354 | Application-scoped roles cause an error dialog to be displayed in the Workshop IDE After creating security roles in the Workshop IDE, an error dialog box is displayed with the following message: `Authentication failure when connecting to the server` This error does not prevent application deployment or role creation, but will occur with domains that are based on the Basic WebLogic Portal Domain template or Basic WebLogic Platform Domain template. The cause of this error is nominally the Identity Assertion security provider that is required for the Web Services for Remote Portals (WSRP) feature of WebLogic Portal, and occurs when the classloader of the JVM for the Workshop IDE is unable to locate the JAR file for that security provider. However, this error can occur with any custom security provider that cannot be located by the IDE JVM classloader. Operating System: All Workaround: The JAR file for the WSRP Identify Assertion provider, as well as any additional custom security provider configured for your domain, needs to be added to the classpath for the Workshop IDE. The IDE classpath is specified in the file `WL_HOME``/workshop/Workshop.cfg`. Fix Information: The `Manifest.mf` file for `wlw-ide.jar` has been changed such that `wsrp-security-providers.jar` is added to the `Shared-Class-Path` entry.
CR182859 | Domains created with the Configuration Wizard using non-XA compliant JDBC drivers are configured with EnableTwoPhaseCommit=true, which can result in data risks under certain failure conditions When the Configuration Wizard tool is used to configure a domain using non-XA JDBC drivers, the `EnableTwoPhaseCommit` setting on Tx Data Source(s) is set to `true` by default. In some cases, under failure conditions, this setting can result in data risks as described in "Limitations and Risks When Using a Non-XA Driver in Global Transactions" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_datasources.html Operating System: All Workaround: The `EnableTwoPhaseCommit=true` setting applies only when non-XA JDBC drivers are used. This setting is used to allow non-XA drivers to participate in XA transactions. If XA-compliant JDBC drivers are used (preferred), this issue does not apply. Depending on the resources involved in a distributed transaction, this setting may or may not be used. This setting is described in the following topics in the WebLogic Server Administration Console Online Help: "Configuring Non-XA JDBC Drivers for Distributed Transactions" in "Connection Pool and Data Source Configuration Guidelines" in "JDBC Connection Pools" at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_connection_pools.html "JDBC DataSources" at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_datasources.html To summarize the key information from the preceding topics: If the only resource involved in a distributed transaction is a non-XA connection pool resource, use the `EnableTwoPhaseCommit=false` setting on the Tx Data Source. In this case, the setting is ignored and one-phase commit is used. The data risks under failure are not present. If more than one resource is used in a distributed transaction, but only one non-XA connection pool resource is involved, it is necessary to set `EnableTwoPhaseCommit=true` on the Tx Data Source to avoid errors during XA prepare. In this case, the data risks described in the preceding link are present because two-phase commit is being simulated for this resource.
CR182859 (continued) | Note that you can set `EnableTwoPhaseCommit=false` to avoid data risks under failure. And if you see XA prepare errors occur, you can optionally set `EnableTwoPhaseCommit=true` to accept the data risks, if desired. If you need to use `EnableTwoPhaseCommit=true`, consider the data risks. And, if possible, design applications to tolerate heuristic conditions. Fix Information: To prevent the likelihood of data risks under failure, `EnableTwoPhaseCommit=true` is no longer the default setting for the portalFrameworkPool JDBC Tx Data Source. Other JDBC Tx Data Sources may still set `EnableTwoPhaseCommit=true` as necessary depending on the resources used by those data sources.
CR183230 | Exception thrown when the JRockit tab on the Monitoring page of the WebLogic Server Administration Console is selected The exception `com.bea.jvm.NotAvailableException` may be displayed when you select the JRockit tab on the Monitoring page of WebLogic Server Administration Console. Operating System: All Workaround: You may ignore this exception. This problem will be corrected in the next release. If you require a patch for this issue, please contact BEA Customer Support. Fix Information: When the JVM heap size is set to 1GB, JRockit uses the "Parallel" garbage collection (GC) strategy by default. When the Parallel GC strategy is used, Nursery Size should be 0 (zero). However, when JRockit uses the Parallel GC strategy in 8.1 SP3 and you use the console to monitor the server, the console tries to get the nursery size, and an exception is thrown, indicating a failure. In SP4, WebLogic Server handles the exception properly and returns 0 (zero), as expected.
CR184180 | WebLogic Workshop IDE fails to start on Linux for some locales On systems running Linux, WebLogic Workshop IDE fails to start for the following `LANG` settings: `ja_JP.eucjp` (Japanese) `ko_KR.euckr` (Korean) `zh_CN.gbk` (Chinese) The following error is thrown: `Error occurred during initialization of VM java.lang.Error: java.lang.IllegalStateException: recursive invocation` Operating system: Red Hat Enterprise Linux 2.1 and 3.0-1 Workaround: To correct this problem, complete the following steps: 1. Download and install the Sun Java 2 SDK 1.4.2_05 or a later version of 1.4.2. 2. Change to the `WL_HOME``/workshop` directory. 3. Edit the `Workshop.sh` script, changing the path `BEA_HOME``/jdk142_04/jre/bin/java` to point to the newly installed SDK. 4. Restart WebLogic Workshop. Fix Information: The problem was caused by a bug in the Sun SDK 1.4.2_04, which was bundled with WebLogic Platform 8.1 SP3. The problem is fixed in the Sun SDK 1.4.2_05, which is delivered with 8.1 SP4.
CR188133 | In a Chinese GB18030 locale environment, WebLogic Platform may not work intermittently because of a JVM I/O problem After the GB18030 Support Package is installed and the JVM default encoding is changed from `GBK` to `GB18030` in a Chinese locale environment, WebLogic Platform components may not work correctly. This problem may be due to an intermittent problem using GB18030 with either the Sun JVM 1.4.2_04 or the JRockit JVM 1.4.2_04. For example, the Workshop IDE with the Sun JVM 1.4.2_04 may fail to compile an application. For information about the JVM problem, see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4954023. Operating system: All Workaround: None Fix Information: Because the problem does not occur when the Sun SDK 1.4.2_05 is used, and the Sun SDK 1.4.2_05 is delivered with WebLogic Platform 8.1SP4, the problem does not occur with SP4.
CR202445 | WLI Admin EJBs are not targeted to a cluster For 8.1 and 8.1 SP2 configurations, the Configuration Wizard, by default, pins WLI Admin EJBs to a single managed server. As a result, users are required to perform two tasks manually: (a) configure the managed server as migratable, and (b) target the WLI Admin EJBs to the cluster. For 8.1 SP3 configurations created by using the Configuration Wizard, the managed servers in a cluster are migratable by default. However, the SP3 Configuration Wizard still pins WLI Admin EJBs to a single managed server, although this function is no longer required. As a result, users must still perform one task manually: they must target WLI Admin EJBs to the cluster. Operating System: All Workaround: N/A Fix Information: For 8.1 SP4 configurations created by using the Configuration Wizard, the managed servers are migratable and the WLI Admin EJBs are automatically targeted to the cluster by the Configuration Wizard.

## Problems Fixed in Service Pack 3

Table 4 lists and describes the problems fixed in WebLogic Platform 8.1 SP3.

Table 4 Problems Fixed in WebLogic Platform 8.1 Service Pack 3

Problem ID | Description
--- | ---
CR111006 | In the Platform domain, the stopWebLogic script fails; it does not stop WebLogic Server If you change the server listen address (from the default) when prompted to do so by the Configuration Wizard (in the "Configure the Administration Server" panel), then the `stopWebLogic` script does not connect to the server because the server listen address is not updated to reflect your change. Operating System: All Workaround: In the stopWebLogic script, change the setting of the server address, as shown in the following example (for a Windows platform): From: `set ADMIN_URL="t3://localhost:7001"` To: `set ADMIN_URL="t3://SERVER_NAME:7001"` Fix Information: The server and port information are now reflected correctly in the `config.xml` file when you modify them in the Configuration Wizard so that this problem does not occur.
CR111819 | Problems can occur when a JDBC connection pool, used by a JMS JDBC store, is inadvertently set up with an XA driver Connection pools between JMS JDBC stores and JMS servers require non-XA drivers. Problems may occur as a result of switching from a non-XA driver to an XA driver and not reconfiguring JMS-related resources completely. This situation may be encountered when using the Configuration Wizard to create a WebLogic Workshop, WebLogic Integration, WebLogic Portal, or WebLogic Platform domain and switching from the default non-XA driver used with PointBase to an XA driver for a different database. Operating System: All Workaround: The Basic WebLogic Workshop, WebLogic Integration, WebLogic Portal, and WebLogic Platform Domain templates are preconfigured to use the JDBC connection pool `cgPool` for the JMS JDBC store `cgJMSStore`. If `cgPool` is reconfigured to use an XA driver, then a new JDBC connection pool with a non-XA driver must be set up for `cgJMSStore`. For details, see http://e-docs.bea.com/platform/docs81/sp_notes/sp_notes.html#sp2_config. The following procedure illustrates the JDBC and JMS configuration steps required in the Configuration Wizard. 1. If you plan to configure one of the domains listed above with an XA driver, select an XA driver for `cgPool` in the Configure JDBC Connection Pools window in the Database (JDBC) Options section. 2. In the same Configure JDBC Connection Pools window, add a new JDBC connection pool and configure it for use with a non-XA driver. For example, add a new JDBC connection pool called `auxPool`, and set it up to use an Oracle Thin Driver (which is a non-XA driver). 3. In the Configure JMS JDBC Store window in the Messaging (JMS) Options section, change the connection pool assignment of an existing JMS JDBC store, or add a new JMS JDBC store, to use the non-XA JDBC connection pool set up in step 2. For example, for the existing JMS JDBC store `cgJMSStore`, specify `auxPool` as the connection pool. 4. In the Target Services to Servers or Clusters window in the Applications and Services Targeting Options section, make sure that all the JDBC connection pools target the appropriate servers. For example, make sure`auxPool` is targeted to `cgServer`. Note: For some domain-specific configurations, you may need to make additional adjustments to the JDBC setup through the Administration Console. Fix Information: In SP3, the templates used to create domains via the Configuration Wizard have been changed to simplify JDBC configuration. For details, see "JDBC Changes in Configuration Templates" in "What's New" for SP3 at: http://e-docs.bea.com/platform/docs81/interm/whatsnew.html#81sp3
CR125482 | WebLogic Integration applications fail after configuring a proxy When you configure a cluster, the Configuration Wizard gives you the option of configuring a Managed Server that can function as a proxy server. However, some properties required for WebLogic Integration applications in such a configuration cannot be set in the Configuration Wizard. Therefore, if you create a proxy server during the cluster configuration process, you cannot specify values for those properties. As a result, WebLogic Integration applications, which depend on settings for those properties, fail at run time. Operating System: All Workaround: After creating a domain configured for a WebLogic Integration application, use the WebLogic Server Administration Console to set the following properties for the Managed Server to function as a proxy server: `FrontendHTTPPort` Set to contain the proxy listen port `FrontendHTTPSPort` Set to contain the proxy SSL listen port `FrontendHost` Set to contain the host name of the proxy server Note: You can also configure these settings via a silent-mode Configuration Wizard script.
CR128781/ CR185278 | startManagedWebLogic.sh cannot find startWebLogic.sh in some domains With some domains configured on UNIX systems, the `startManagedWebLogic.sh` script cannot invoke the `startWebLogic.sh` script. The problem is that the invocation to `startWebLogic.sh` does not specify the path to that script, which is needed even when that script is in the same directory. This problem affects domains based on the following templates: Basic WebLogic Workshop Domain Basic WebLogic Portal Domain Basic WebLogic Integration Domain Basic WebLogic Platform Domain Operating System: UNIX Workaround: You can fix this by adding the domain's root directory to the `$PATH` environment variable for your system. Or you can simply edit your domain's `startManagedWebLogic.sh` script and prepend the domain's root directory to the invocation to `startWebLogic.sh`. Fix Information: The affected domain templates have been fixed so that `startWebLogic.sh` can be invoked from `startManagedWebLogic.sh`.
CR130185/ CR178854/ CR181546 | Certificate expires on mm/dd/yyyy When starting WebLogic Server, you may see a warning message that begins with text similar to the following: `<Dec 20, 2003 8:40:03 PM EST> <Notice> <WebLogicServer> <BEA-000298> <Certificate expires in` 18`days:` If the Certificate Authority certificate for your server, or for a client connected to your server, has expired, you may be unable to create SSL connections. Operating System: Windows, Linux, and Solaris Workaround: This message is displayed when loading trusted certificate authority certificates from pem files or keystore files that are due to expire on the indicated date. (The JDK `cacerts` file and the WebLogic Server `cacerts` file are keystore files that contain out-of-the-box trusted Certificate Authority (CA) certificates. These trusted certificates are used in certificate chain verification when SSL is used.) If you use certificates from the affected CAs in your server certificate chain, you should obtain an updated certificate from your CA of choice (for example, Verisign or Certicom). Refer to your CA of choice for information about obtaining an updated certificate, if necessary. If the messages are warnings that the WebLogic Demo CAs will expire on May 14, 2004, refer to the following article on dev2dev for more information about these warnings and how to modify your system so the warning messages no longer appear: http://dev2dev.bea.com/products/wlserver81/wls_demo_cas.jsp For more information about certificates, keystores, and CAs, see "Configuring SSL" in Managing WebLogic Security at http://e-docs.bea.com/wls/docs81/secmanage/ssl.html. Fix Information: The expired certificates have been removed from the keystores. (Newer WebLogic Demo CA certificates, which are provided for demonstration and development purposes, are generated during installation. The expired demo certificates are no longer needed and should no longer be used.)
CR130361/ 43128 | The Tx Data Source WLAI_DataSource is part of the Basic WebLogic Platform Domain template Although this Tx Data Source is required only for the out-of-the-box WebLogic Integration samples domain, it is also included in the Basic WebLogic Platform Domain template. The inclusion of this Data Source does not present a problem for domains based on this template, as long as you are not using global (XA) transactions. However, if you use global transactions in such a domain, the inclusion of this Data Source may create a problem that requires a workaround. Operating System: All Workaround: If you do not use global (XA) transactions in your domain, no action is required. If you do use XA transactions, you must implement one of the workarounds listed here. Which one you implement depends on whether you require `WLAI_DataSource` in your domain: If you require `WLAI_DataSource`, you need to add a new JDBC connection pool, `aiPool`, to your domain, connect to a supported database using a Type 4/XA driver, and change `WLAI_DataSource` to use `aiPool`. You can do this when you create the domain via your Configuration Wizard. You can also modify an existing domain to use `WLAI_DataSource` for XA transactions via the WebLogic Server Administration Console. For information about configuring a JDBC Data Source, see "JDBC DataSources" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_datasources.html If you do not require `WLAI_DataSource`, you must remove it from your domain. You can do so while you are creating the domain via the Configuration Wizard, or from an existing domain via the WebLogic Server Administration Console. For information about deleting this Data Source from an existing domain, see "Deleting a Data Source" in "JDBC DataSources" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_datasources.html Fix Information: The `WLAI_DataSource` Tx Data Source has been removed from the Basic WebLogic Platform Domain template.
CR133495 | Domain upgrade fails with "The domain to be read must be a directory containing a valid domain of version 8.1.0.0 or up" When upgrading a domain from 8.1 to 8.1 SP2 using an upgrade script provided with a component of WebLogic Platform 8.1 SP2, the script fails. This underlying problem causing the upgrade failure is not related to an invalid domain, as the message indicates, but rather is due to a construct in the domain's `config.xml` file that does not conform to the schema that the Configuration Wizard uses. Operating System: All Workaround: If you enable the Configuration Wizard to run in debug mode before executing the upgrade script, you might be able to obtain information from the log file that provides information about the specific problem with the `config.xml` file. If you cannot determine the cause of the problem based on the log file information, contact support. To run the Configuration Wizard in debug mode, enter the following command, where`log-file.txt` represents the file name and path of the Configuration Wizard debug mode output. Windows: `config.cmd -log=``log-file.txt``-log_priority=debug` UNIX: `config.sh -log=``log-file.txt``-log_priority=debug` Fix Information: In SP3, the schema used by the Configuration Wizard to parse a domain's `config.xml` file is enhanced to prevent this problem from occurring. In addition, the Configuration Wizard's error logging is also improved to provide more precise details about potential domain update problems. If you are using SP2, a patch is available to BEA Support Contract users. Information about this patch is provided at the following URL: http://support.bea.com/application?namespace=browse&origin=browse_results.jsp&event=link.view_answer_page_clfydoc&extraParams=&answerpage=solution&page=wlplat/S-25807.htm BEA Support Contract users may access the patch by logging in at http://support.bea.com using their username/password with contract access privileges.
CR134025 | Cannot add cluster support to a single-server WebLogic Integration domain template If you use the Configuration Template Builder to add cluster support to a single-server WebLogic Integration domain template, the newly-extended domain template does not work. If you subsequently attempt to use the domain template with the Configuration Wizard, the following error message is displayed: `There is a problem with the template` Operating System: All Workaround: Do not use the Configuration Template Builder to add cluster support to a single-server WebLogic Integration domain template. Instead, after you have created a single-server WebLogic Integration domain template, you must subsequently use the Configuration Wizard to create the clustered domain based on that single-server domain template. Fix Information: The Configuration Template Builder has been fixed in SP3 so that this workaround is no longer required. That is, you can now use this tool to add cluster support to a single-server domain template.
CR134188 | Configuration credentials need to be converted during template build If you use the Configuration Template Builder to create a template that is based upon a domain that is currently booted, the `config.xml` file in the template contains incorrect credential values for the `SecurityConfiguration` and `EmbeddedLDAP` element attributes. Operating System: All Workaround: After creating a template from a booted domain, edit the `config.xml` file and specify the correct credential values. Fix Information: The Configuration Template Builder has been fixed in SP3 so that this workaround is no longer required.
CR137240 | Update F1 URL in WebLogic Workshop Properties for Java API The Sun J2SE 1.4.1 JVM and its associated Javadoc is no longer available on the Sun Microsystems Web site. You can no longer access this version of the Sun J2SE Javadoc using the context-sensitive (F1) help in WebLogic Workshop. Operating System: Windows and Linux Workaround: Update the WebLogic Workshop IDE properties to reference the location of the Sun J2SE 1.4.2 Javadoc, as described in the following steps: 1. Start WebLogic Workshop. 2. Select Tools—> IDE Properties. The IDE Properties window is displayed. 3. Click Help in the left-hand pane. 4. Set the J2SE Javadoc location to the following value: `http://java.sun.com/j2se/1.4.2/docs/api` 5. Click OK. Fix Information: The Sun J2SE 1.4.2 Javadoc is now available by default via context-sensitive help.

## Problems Fixed in Service Pack 2

Table 5 lists and describes the problems fixed in WebLogic Platform 8.1 SP2.

Table 5 Problems Fixed in WebLogic Platform 8.1 Service Pack 2

Problem ID | Description
--- | ---
36677/ CR111552/ CR122578/ CR129205/ CR139945 | stopManagedWebLogic scripts do not work When a stopManagedWebLogic script (`stopManagedWebLogic.cmd` on Windows or `stopManagedWebLogic.sh` on UNIX) is run to stop the managed servers in a domain, the following error message is displayed: "The system cannot find the path specified." Operating System: All Workaround: Fix the script manually by redefining three variables, `JAVA_HOME`, `PLATFORMHOME`, and `ADMIN_URL`, to reflect the correct values for your WebLogic Platform installation. Fix Information: The stopManagedWebLogic scripts have been fixed.
CR104436, CR108349, and CR122182 | The startPointBaseConsole.cmd script does not run if the value of BEA_HOME (a directory name) includes a space The startPointBaseConsole script (`startPointBaseConsole.cmd` on Windows and `startPointBaseConsole.sh` on UNIX) and other BEA scripts for Windows platforms cannot be run if the name of the `BEA_HOME` directory includes a space, such as `c:\Program Files\bea`. Operating System: All Workaround: Make sure that the name of the directory that you designate as `BEA_HOME` does not include any spaces. Fix Information: The Configuration Wizard has been fixed so that a value of `BEA_HOME` that contains a space is passed to the startPointBaseConsole script. (This fix works only for domains that have been created via the Configuration Wizard in Service Pack 2 or later.)
CR108899 | Cannot start PointBase Server in Configuration Wizard when creating a new domain When you use domain templates to create a new WebLogic Workshop, WebLogic Portal, WebLogic Integration, or WebLogic Platform domain with a PointBase database, the PointBase database is actually created as part of the domain creation process. It is, therefore, not possible to start the PointBase Server until the domain is created. As a result, the "Start PointBase Server," "Test Connection," and "Load Database" functions in the Test JDBC Connection Pools and Setup JDBC database window cannot be used during the process of domain creation. The PointBase database is populated automatically, as appropriate for these domains. Operating System: All Workaround: In the circumstances described above, skip the procedural step of testing and loading your connection to the PointBase database from the Test JDBC Connection Pools and Setup JDBC Database window. If you do try to test and/or load your connection, and see an error message displayed on your screen, you can safely ignore it. Fix Information: The Start Pointbase Server button has been removed from the Configuration Wizard.
CR109014 | PointBase Server is always started for a domain generated with Oracle When you start the server in a domain created from the Configuration Wizard with Oracle, a PointBase server is always started in the background. Operating System: All Workaround: Add `pointbaseFlag=false` to the startWebLogic script (`startWebLogic.cmd` on Windows or `startWebLogic.sh` on UNIX). Fix Information: The Configuration Wizard has been fixed so that startWebLogic scripts that contain the correct PointBase startup logic are generated for each domain.
CR109606 | If you try to load new data into the database without first removing any existing WebLogic Integration tables, an exception is thrown When you create a new Platform domain or WebLogic Integration domain with the Configuration Wizard, you are given an opportunity to load tables into your database. If you do so without first removing any existing WebLogic Integration tables from the database, the Configuration Wizard throws an exception. Operating System: All Workaround: When using the Configuration Wizard to create a Platform domain or a WebLogic Integration domain in production mode, you must do the following: 1. Using the Configuration Wizard in custom mode, configure the JDBC Connection Pools with your production DBMS. 2. Load the domain level tables if the following is true: (a) The tables do not already exist, or (b) You want the domain to be created with fresh data. 3. If you want the domain to be created with fresh data, you must clean up the existing tables before trying to load new data via the Configuration Wizard. To do so, complete the procedure available at the following URL: http://e-docs.bea.com/wli/docs81/manage/database.html Fix Information: The Configuration Wizard has been fixed so that when you create a new Platform or WebLogic Integration domain, and you want the domain to be created with fresh data, it is no longer necessary to remove existing WebLogic Integration tables from the database.
CR111173 | In WebLogic Workshop Help, the WebLogic Platform Tour documentation erroneously offers two invalid options Chapter 4, "Ordering Office Equipment," contains a documentation error. In the section called "Step 1: Place a New Order," the user is shown a set of four valid options that can be entered in the Item ID field. The four options are notebook_kit1, notebook_kit2, desktop_kit1, and desktop_kit2. Two of these options, however, are not valid: notebook_kit2 and desktop_kit2. Only the notebook_kit1 and desktop_kit1 options are valid. Note: This error appears only in the version of the WebLogic Platform Tour Guide that is provided with the WebLogic Workshop Help. Operating System: All Workaround: Use only the two valid options: notebook_kit1 and desktop_kit1. Fix Information: The WebLogic Platform Tour Guide provided in the online help has been corrected.
CR111210 | Server settings in IDE are lost after extending an existing WebLogic domain with the Configuration Wizard The Configuration Wizard does not take into account certain entries in the `workshop.properties` file for the domain. The IDE uses that file to determine and manage information about the domain and server an application is part of, including the classpath settings. When you extend a domain with the Configuration Wizard, this file is overwritten. As a result, any settings that are set in the IDE's WebLogic Server Application Properties panel are lost. Additionally, Portal domains use the classpath settings in the `workshop.properties` file to include portal-specific libraries in the application's classpath for the IDE. These settings are lost if a Portal domain is extended via the Configuration Wizard. Operating System: All Workaround: Make a backup copy of the `workshop.properties` file in the domain before running the Configuration Wizard. After running the Configuration Wizard, merge property values that were changed, especially the `class.path` values. Example: Suppose that before you run the Configuration Wizard, `class.path` in the `workshop.properties` file is defined as follows: `class.path=../../mystuff/something.jar` After you run the Configuration Wizard, the same `class.path` is defined as follows: `class.path=${wlsHome.path}/portal/lib/wps_system.jar; ${wlsHome.path}/p13n/lib/p13n_system.jar` If you like, you can then change it to the following: `class.path=../../mystuff/something.jar;${wlsHome.path}/portal/lib/wps_system.jar; ${wlsHome.path}/p13n/lib/p13n_system.jar` If you extend a Portal domain, you must add the following setting to the definition of the `class.path` property in the `workshop.properties` file: `${wlsHome.path}/portal/lib/wps_system.jar; ${wlsHome.path}/p13n/lib/p13n_system.jar` Use a semi-colon (;) as the path separator, regardless of whether you are working on a Windows or UNIX platform. Alternatively, you can use the IDE's WebLogic Server Application Properties panel to reset any settings you modified earlier. Fix Information: The Configuration Wizard has been fixed so that properties in the `workshop.properties` file are retained when you extend a domain.
CR111384 | Load Database for Microsoft SQL Server operation on a new Platform or WebLogic Integration domain results in "ERROR: Unable to get SQL data from URL" Use of the Microsoft SQL Server database is not supported for WebLogic Platform or WebLogic Integration. If you use the Configuration Wizard to perform a Load Database for MS SQL Server operation in a new Platform domain or a new WebLogic Integration domain, an error results and the following message is displayed: "ERROR: Unable to get SQL data from URL" and "Database Load Failed!" Operating System: All Workaround: Do not use Microsoft SQL Server for a new Platform domain or WebLogic Integration domain; it is not supported for either. Fix Information: For SP2, SQL Server is fully supported by all components of WebLogic Platform.
CR111444 | Configuration Wizard creates Start Menu Development and Administration tool folders When you create a new domain, the Configuration Wizard creates not only a User Projects folder, which is appropriate, but also a new Other Development and Administration tools folder, with a node manager entry. This replicates the node manager entry under the standard "Other Development Tools" folder. Neither the new folder nor the new node manager entry should be created. This erroneous behavior is confusing, but it does not break anything. Operating System: All Workaround: N/A Fix Information: Neither the new folder nor the new node manager entry are created.
CR111468 | WebLogic Platform Tour documentation cites the wrong names for security roles In "Configuring Security in Web Applications" (in Chapter 2 of the WebLogic Platform Tour Guide), the security roles defined in the file `e2ePortal/e2ePortalProject/WEB-INF/web.xml` are documented as follows: employeerole managerrole The documentation is incorrect. The correct security roles are: employee manager Operating System: All Workaround: N/A Fix Information: The documentation has been corrected.
CR122113 | PointBase initialization files should default to debug.log=false, instead of debug.log=true PointBase initialization files should default to `debug.log=false`, instead of `debug.log=true`. Operating System: All Workaround: This bug has been corrected. If you want to enable PointBase debugging, set this flag to `true`.
31613 | Character corruption occurs when there is static include file which contains multibyte characters in a JSP file Characters are corrupted when the JSP file contains a static `include` file with multibyte characters. JSP `include` files, which are used to import files dynamically, at run time, are required for successfully importing a file into a JSP when the file type is one that contains a header with character encoding specified, such as HTML, JSP, and XML. Regardless of whether you specify static `include` or JSP `include`, any `include` operation fails when you import a fragment for which the type of encoding used does not match the type of encoding used by the system. If no encoding header is specified, the file is included using its default encoding which is ISO 8859-1 for JSP and HTML files, and UTF-8 for XML. All other files are decoded using the system's default encoding. Operating System: All Workaround: Use `<jsp:include>` instead of static include files in your JSPs. If you must use static include files, then use the classic JSPC provided by WebLogic Server. To do so, delete the `jspServlet` entry from your `web.xml` file.