> Installation and Configuration Release Notes > BEA Products Installation and Configuration Release Notes

Installation and Configuration Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

BEA Products Installation and Configuration Release Notes

This document provides information about new capabilities, usage notes, and known limitations related to the installation and configuration of BEA Weblogic Server® 9.2, BEA Workshop for WebLogic Platform™ 9.2, BEA WebLogic Portal® 9.2 and BEA Weblogic Integration™. This document also provides information about WebLogic Server upgrade tools and the new capabilities provided for Independent Software Vendor (ISV) partners.

The following topics are included:

For the latest release note information for BEA Products, go to the BEA documentation Web site at the following URL: 


http://www.oracle.com/technology/documentation/index.html

For detailed information about the BEA products encompassed by the WebLogic Portal 9.2, BEA Workshop for WebLogic Platform 9.2, and WebLogic Server 9.2 releases, including BEA JRockit J2SE 5.0 (R26.0) JDK, which is contained in the installation of these products, see the corresponding Release Notes document as follows:

For detailed release
information about . . .
See the following Release Notes document . . .
WebLogic Server 9.2
BEA Workshop for WebLogic Platform 9.2
WebLogic Portal 9.2
http://download.oracle.com/docs/cd/E13218_01/wlp/docs92/relnotes/index.html
WebLogic Integration 9.2
BEA JRockit J2SE 5.0 JDK
BEA JRockit 5.0 (R26.0) JDK Release Notes

 

What’s New in Installation and Configuration

The following list summarizes new features and changes in the installation and configuration tools used with BEA WebLogic Server 9.2, BEA WebLogic Portal 9.2 and BEA Workshop for WebLogic Platform 9.2.

Upgrade

WebLogic 9.2 includes powerful tools to assist you with upgrading your application environments including the WebLogic Upgrade Wizard for upgrading domains, custom security providers, and custom node managers, and BEA Workshop for WebLogic Platform 9.2 for upgrading WebLogic Workshop and WebLogic Portal applications.

Most WebLogic Server applications can be run without modifications in the new WebLogic Server 9.2 application environment. WebLogic Workshop and WebLogic Portal applications developed in 8.1 must be upgraded first before they can be run in WebLogic 9.2.

Table 1 below provides pointers to additional documents with information on upgrading application environments to WebLogic 9.2.

Table 1 Upgrading Your Application Environment to WebLogic 9.2
To upgrade application environments based on...
From Version...
See...
WebLogic Server
6.1, 7.0, 8.1, 9.0, and 9.1
For information on upgrading WebLogic Server application environments from 6.1, 7.0, and 8.1, see Upgrading WebLogic Application Environments.
For information on upgrading WebLogic Server application environments from 9.0 and 9.1, see Roadmap for Upgrading WebLogic Application Environments.
WebLogic Workshop
8.1 SP4, SP5 and SP6
For information on upgrading WebLogic Workshop application environments, see Upgrading from WebLogic Workshop 8.1.
For information on domain upgrade see, Upgrading a WebLogic Domain in Upgrading WebLogic Application Environments.
WebLogic Portal
8.1 SP4, SP5 and SP6
For information on upgrading WebLogic Portal application environments, see the WebLogic Portal Upgrade Guide and the Upgrading WebLogic Portal Projects from Version 8.1 to Version 9.2 chapter of the Portal Development Guide.
For information about domain upgrade, see Upgrading a WebLogic Domain in Upgrading WebLogic Application Environments.
WebLogic Integration
8.1 SP4, 8.1 SP5, 8.1 SP6, 8.5, 8.5 SP5 and 8.5 SP6
For information on upgrading WebLogic Integration application environments, see the WebLogic Integration Upgrade Guide.
For information about domain upgrade, see Upgrading a WebLogic Domain in Upgrading WebLogic Application Environments.
BEA JRockit
 
N/A. There is no required procedure.

For information on changes between 8.1 and 9.2, and for a list of unsupported usage patterns with applicable workarounds, see:

Rolling Upgrade

Rolling Upgrade is the process of upgrading a running WebLogic Server cluster with a patch, maintenance pack, or minor release without shutting down the entire cluster or domain. During the rolling upgrade of a cluster, each server in the cluster is individually upgraded and restarted while the other servers in the cluster continue to host your application.

Prior to the WebLogic Server 9.2 release, to upgrade a cluster, you had to either shutdown the entire domain, or install the upgraded server version on a parallel domain on additional hardware and use a load balancer to transfer load from the old domain to the new domain. The rolling upgrade process minimizes downtime and allows you to install a patch, maintenance pack, or minor release while the domain is still running.

Note: Rolling Upgrade cannot be used to upgrade a WebLogic Portal or BEA Workshop for WebLogic Platform domain.

For more information see, WebLogic Server Rolling Upgrade.

Smart Update

Smart Update has been enhanced to support BEA WebLogic Server 9.2, BEA Workshop for WebLogic Platform 9.2, and BEA WebLogic Portal 9.2.

Smart Update is a standalone Java application that you can run independently of BEA software to upgrade your software installations quickly and easily with maintenance patches and service packs. When you install a BEA product for the first time, Smart Update is automatically installed in your BEA Home directory.

Smart Update is enhanced from time to time with new features, and is made available on the BEA download server.

The new version of Smart Update is placed on the BEA download server: if you log in using an earlier version of Smart Update, the latest version is pushed to your machine, and it is installed automatically.

After the installation, you will be prompted to close and start Smart Update again. Click Yes to start Smart Update, and continue with managing your patch maintenance.

When you start Smart Update at a later point, the updated version will be invoked.

For more information, see Installing Maintenance Updates and Service Packs.

Configuration Wizard

In this release, the Configuration Wizard has been enhanced to support the creation of BEA WebLogic Server, BEA Workshop for WebLogic Platform, and BEA WebLogic Portal enabled domains.

For more information, see Creating WebLogic Domains Using the Configuration Wizard.

Domain and Extension Templates

In this release, the following new domain and extension templates have been added:

For more information, see Domain Template Reference.

 

What’s New in BEA WebLogic Server 9.2

The following sections describe new and changed functionality in this WebLogic Server® release. For more information about new features, see What’s New in BEA WebLogic Server. For information about known limitations and problems fixed, see BEA WebLogic Server Known and Resolved Issues.

Security

The following features are new to WebLogic security in this release:

Administration Console Extensions

In this release, Administration Console extensions that use these third-party JSP tag libraries from the WebLogic Server installation must use predefined, absolute URIs to specify the tag libraries. The Administration Console web.xml file maps these URIs to tag libraries within the WebLogic Server installation. This mapping facility enables BEA to reorganize its installation directory without requiring you to change your JSPs.

JDBC and JTA

The following features are new to WebLogic JDBC and JTA in this release.

Diagnostics

Performance of the WebLogic Diagnostics Framework (WLDF) and the WLDF Console Extension have been enhanced with the addition of new features.

Messaging

This release of WebLogic Server includes the following improvements in WebLogic Server JMS, Messaging Bridge, and the Store-and-Forward service:

Web Services

Web Services in this release of WebLogic Server include the following new and changed features:

Deployment

The following deployment features were added in this release of WebLogic Server.

Filtering Class Loader

In this release of WebLogic Server; WebLogic FilteringClassLoader enables users to configure deployment descriptors to explicitly specify packages that are always loaded from the application, rather than being loaded using the system classloader.

Migration and Clustering

The following features related to migration and clustering were added in this release:

Web Applications, Servlets, and JSPs

In this release of WebLogic Server, Web applications, servlets, and JSPs include the following new and changed features:

WebLogic Tuxedo Connector

In this release of WebLogic Server, WebLogic Tuxedo Connector includes the following new and changed features:

WTC Performance Enhancements

 

What’s New in BEA Workshop for WebLogic Platform 9.2

Workshop for WebLogic Platform integrates open sources technologies into a development experience with a focus on easing the creation of complex applications. This release of Workshop for WebLogic Platform has the following enhancements and new features:

For more information about new features, see What’s New in BEA Workshop for WebLogic Platform.

For information about known limitations, see Known Limitations for Workshop for WebLogic Platform.

 

What’s New in BEA WebLogic Portal 9.2

BEA Workshop for WebLogic Platform™ 9.2 and WebLogic Portal® 9.2 provide new and improved functionality for building enterprise portal applications, including:

For more information about new features, see What’s New in BEA WebLogic Portal 9.2. For information about known limitations and workarounds, see Known Limitations and Workarounds in BEA WebLogic Portal 9.2.

 

What’s New in BEA WebLogic Integration 9.2

BEA WebLogic Integration 9.2 supports an Eclipse-based development environment, Apache Beehive integration controls, Java 5-compliant annotations, and a new Worklist subsystem. In addition to automated upgrade tools for applications from BEA WebLogic Integration 8.1 SP4, SP5 and SP6, or 8.5 (including SP5 and SP6), BEA WebLogic Integration 9.2 leverages the power of WebLogic Server 9.2, providing improved security, manageability, performance, scalability and availability.

BEA WebLogic Integration 9.2 includes the following new features and enhancements:

For more information about new features, see What’s New in BEA WebLogic Integration 9.2. For information about known limitations and workarounds, see Known Limitations and Workarounds in BEA WebLogic Integration 9.2.

 

Supported Configurations and Special Installation Instructions

Information about configurations supported by BEA WebLogic Server, BEA WebLogic Portal and BEA Workshop for WebLogic Platform, including hardware and software requirements, is provided from the Supported Configurations page at the following URL:

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

The documents available from the preceding page also include special installation and usage instructions, which are required for some operating systems.

 

Licensing

To use the WebLogic Portal and BEA Workshop for WebLogic Platform software, you must have a valid license file installed on your system. When you install WebLogic Portal 9.2 or BEA Workshop for WebLogic Platform 9.2, the installation program installs a non-expiring development license to enable you to start using the software immediately. The development license is a full license, enabling use of all component features of the product software available from the installer.

To add a license for additional functionality, you need to update the license.bea file in your BEA Home directory. Please refer to “ Installing and Updating License Files” in the BEA Products Installation Guide for more information.

In this release, the following BEA JRockit licenses are available:

For more information about the license packages available, see Licensing.

 

Switching JDKs

The following instructions are provided for users who have already installed either WebLogic Portal 9.2, BEA Workshop for WebLogic Platform 9.2, or WebLogic Server 9.2 and want to switch from Sun Java 2 to BEA JRockit, or vice-versa:

  1. Examine the WebLogic Server start script. This script is located in the bin subdirectory of 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.

    4. The following set JAVA_VENDOR and set JAVA_HOME commands specify the BEA JRockit J2SE 5.0 JDK, where c:\bea is the BEA home directory:

    set JAVA_VENDOR=BEA
    set JAVA_HOME=c:\bea\jrockit90_150_04

    For Sun, the equivalent commands are as follows:

    set JAVA_VENDOR=Sun
    set JAVA_HOME=c:\bea\jdk150_04

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

    5. The following two code snippets show the switching of the default JDK from Sun Java 2 JDK 5.0 to BEA JRockit J2SE 5.0 (R26.0) JDK 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 JDK 5.0 as the default: 

    if "%JAVA_VENDOR%"=="BEA" (
           set JAVA_HOME=C:\bea\jrockit90_150_04
    ) else (
           if "%JAVA_VENDOR%"=="Sun" (
                 set JAVA_HOME=C:\bea\jdk150_04
           ) else (
                 set JAVA_VENDOR=Sun
                 set JAVA_HOME=C:\bea\jdk150_04
           )
    )

    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\jrockit90_150_04
    ) else (
           if "%JAVA_VENDOR%"=="Sun" (
                 set JAVA_HOME=C:\bea\jdk150_04
           ) else (
                 set JAVA_VENDOR=BEA
                 set JAVA_HOME=C:\bea\jrockit90_150_04

For more information about BEA support for BEA JRockit and the Sun Java 2 JDK, see Supported Configurations for WebLogic Server, WebLogic Portal, and Workshop for WebLogic Platform - Version 9.2.

 

Customer Support

If you have any questions about this version of WebLogic Server 9.2, WebLogic Portal 9.2 or BEA Workshop for WebLogic Platform 9.2, 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:

 

Known Limitations

This section describes problems that have been identified in the installation and configuration software delivered with WebLogic Server 9.2, WebLogic Portal 9.2 and BEA Workshop for WebLogic Platform 9.2. Whenever possible, workarounds are provided.

For each problem described, a tracking number is specified. These numbers enable BEA and users to monitor the status of issues while solutions are being developed.

Problem ID
Description
CR214849
Thread dump occurs when Ctrl+C is used to stop server
Using Ctrl+C to stop a WebLogic Server instance results in a thread dump in the command window from which the server was started. This problem occurs because the RDBMS configured for the domain halts before the WebLogic Server shutdown procedure is completed.
This problem can happen in either the WebLogic Server Examples domain or Avitek Medical Records domain when configured with the default PointBase RDBMS, but potentially can happen in any domain in which the RDBMS is configured to start and stop with WebLogic Server.
Operating System: Windows
Workaround: The recommended way to shut down a WebLogic Server instance is via the WebLogic Server Administration Console. For details, see “Starting and Stopping Servers” in Managing Server Startup and Shutdown.
CR220653
WebLogic Server fails to start and displays the message that the server is not found in the WL_HOME directory
A message similar to the following is displayed when you try to start WebLogic Server:
The WebLogic Server wasn't found in directory directory-name. Please edit the setWLSEnv.cmd script so that the WL_HOME variable points to the WebLogic installation directory. Your environment has not been set.
This problem is caused by a Windows bug that limits the length of the directory name you can use for the BEA Home directory.
Operating System: All
Workaround: Do not choose a BEA Home directory name that contains more than 12 characters.
CR224184
PointBase is not disabled after a domain is extended using two or more extension templates, and an extension template other than the first is used to change the database from PointBase to a production RDBMS
If you extend a domain using two or more extension templates, and switch the database from PointBase to a production RDBMS when applying the second template or a subsequent one, PointBase is not disabled for the domain.
Operating System: All
Workaround: Two workarounds can be used to avoid this problem, as follows:
  • When extending the domain using the first extension template, specify the production RDBMS. This step ensures that subsequent extension templates do not re-enable PointBase.
  • When starting the domain, run the WebLogic Server start script specifying the nopointbase option. For example:

    • UNIX:

    startWebLogic.sh nopointbase

    Windows:

    startWebLogic nopointbase

CR224337
Server fails to start when domain name includes a dot and the dot is preceded and followed by strings of a certain length
If you create a domain and assign a name that has all the following characteristics, the domain will not start:
  • The name includes the period character (.).
  • Two alphanumeric characters precede the period.
  • Five or more alphanumeric characters follow the dot.
For example, a domain created with the name zq.domain will not start.
Operating System: All
Workaround: When choosing a domain name, do one of the following:
  • Do not use a name that contains a dot character.
  • If you use a dot character, make sure that you provide more than two characters preceding the dot.
CR227881
Limited support in Template Builder for compatibility-mode security
When using the Domain Template Builder to create a template from a domain that contains a Compatibility security configuration, you cannot create or assign additional users, groups, and global roles.
Operating System: All
Workaround: After you create a domain based on a template that contains a Compatibility security configuration, boot the domain and add users, groups, and roles via the WebLogic Server Administration Console.
CR228401
A single-server domain cannot be configured correctly by deleting all but one server from a clustered domain template
Neither the Configuration Wizard nor WLST offline support the creation of a single-server domain based on a template of a clustered domain from which all but one server are removed. The reason for this restriction is that a clustered domain template contains no initial single-server targeting state, which is needed when you attempt to make this type of customization.
Operating System: All
Workaround: If you are creating a single-server domain, choose a template that is not created from, or based on, a domain that is clustered.
CR229655
Exception java.lang.UnsupportedOperationException thrown from domain configured using WLST offline
When operating in offline mode, WLST does not support the creation of security roles. If a WLST offline script includes statements that define security roles, WLST terminates abnormally when executing the script, throwing the java.lang.UnsupportedOperationException exception.
Operating System: All
Workaround: Use WLST in online mode to specify security roles.
CR229700
QuickStart is not displayed correctly after installation
When installing AquaLogic Service Bus or WebLogic Server, if you specify a directory for either the BEA Home directory or WebLogic Server Home directory that contains a multibyte character set in the directory name, QuickStart is not displayed correctly after the installation is complete.
Operating System: Any system in which the Sun Java 2 J2SE 5.0 is used.
Workaround: During installation, choose directories for BEA Home and WebLogic Server Home with names that include only the ASCII character set.
CR230483
Configuration of application-scoped resources cannot be changed in domain template
If you create a template or extension template of a domain that contains application-scoped resources, and then create or extend a clustered domain on the basis of that template or extension, the Configuration Wizard may not properly retarget the application-scoped resources. If the template on which a clustered domain is based contains application-scoped JMS or JDBC resources, the domain may fail to start.
Operating System: All
Workaround: Note the following best practices for creating domains and templates:
  • When creating a domain or extension template, include only JMS and JDBC resources that are global to the domain and that can be customized during the domain creation process; for example, JDBC data source and JMS file store settings for the domain, or cluster configuration settings.
  • Rely on the application and on the application deployment process to create the required application-scoped resources in the target environment.
  • If you are migrating an application from a non-clustered to a clustered domain, and the application includes packaged JMS resources for which you want to have scalability and load balancing, you can do the following:

    • — In place of each JMS queue in the packaged JMS module, create a uniform distributed JMS queue.

    — Configure a JMS server for each Managed Server in the cluster.

    — Include the connection factory and the uniform distributed queues in the same sub deployment group, and deploy them to the cluster.

    When the application is deployed, each Managed Server in the cluster has a connection factory and a member for each distributed queue. For information about configuring JMS for a clustered environment, see “Configuring Clustered WebLogic JMS Resources” in Configuring and Managing WebLogic JMS.

  • After you create or extend the domain, you may need to perform additional steps to make sure that the application and its application-scoped resources are targeted and deployed properly for a clustered environment. For more information on the targeting and deployment of application-scoped modules, see “Deploying Applications and Modules” in Deploying Applications to WebLogic Server.
CR234871
Installer hangs on Windows XP during Node Manager configuration
If you choose to install Node Manager as a Windows service, which is an option available via a custom installation, the installation program may hang after you specify a listen port for Node Manager.
This problem may occur if Windows Firewall is running, and the listen port chosen for Node Manager has not been specified as a Windows Firewall exception.
Operating System: Windows XP Professional with Service Pack 2
Workaround: Before you run the installation program, do either of the following:
  • Turn off Windows Firewall (recommended)
  • Add the port you want to use for the Node Manager listen port as a Windows Firewall exception
If you choose to turn off Windows Firewall prior to installation, you can turn it back on after the installation procedure is complete.
CR244593
Servers for both WebLogic examples and Avitek Medical Records sample cannot be started at the same time due to database conflicts
You cannot start or run the servers in the domains for the WebLogic examples and Avitek Medical Records (MedRec) sample at the same time because both servers reference the same database files.
Operating System: All
Workaround: Do not attempt to run both sample servers simultaneously. Stop one server before starting the other one.
CR250829
QuickStart and Start menu options are not working properly after installing WebLogic Platform
Some QuickStart menu options like start WebLogic Server, Start AquaLogic Server Bus are not working properly. In addition, options like Start Menu->BEA Products->Examples->WebLogicServer->Start Examples Server or Start MedicalRecords Server are not working properly.
Operating System: All
Workaround: Make sure that the WebLogic Server path does not contain the . (period) character.
CR251454
GUI cannot refresh patches installed from command line without restart
If you use the Smart Update graphical and command-line interfaces simultaneously, patches that you apply via the command-line interface are not visible from the GUI when you refresh the view.
Operating System: All
Workaround: Exit and restart the Smart Update GUI to view the new patch.
CR253493
Uninstall component does not remove component patches automatically
If you uninstall any component, the patches associated with that component are not removed automatically. The patched artifacts may have been removed as part of the un-installation but the patch is still shown as applied.
Operating System: All
Workaround: Use Smart Update to remove the patches associated with the component before un-installation.
CR254744
Smart Update graphical interface displays java.util.ConcurrentModificationException in rare cases
In rare cases, when using the Smart Update graphical interface, the following exception may be displayed:
java.util.ConcurrentModificationException
at
java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1031)
at java.util.TreeMap$KeyIterator.next(TreeMap.java:1058)
at
com.bea.plateng.patch.gui.PatchStoreTableModel.getRowCount(PatchStoreTableModel.java:199)
Operating System: All
Workaround: This exception can be ignored.
CR255640
Smart Update’s patch profile maintenance snapshot text file is poorly formatted when viewed in Notepad
The patch profile maintenance snapshot file produced by Smart Update cannot be easily viewed in common text editors, such as Notepad. The snapshot file does not contain conventional line breaks, which results in poorly formatted columns that cannot be easily read.
Operating System: All
Workaround: Use a text editor such as WordPad or TextPad to view this file. You do not need to reformat this file when sending it to BEA Customer Support.
CR255650
Invalidated patches should not list other invalidated patches as their replacement
When you display details about an invalidated patch, the ID of the replacement patch may be provided. But if the replacement patch is subsequently invalidated by BEA Customer Support, this ID will not be updated and will refer to an invalidated patch.
Operating System: All
Workaround: Contact BEA Customer Support.
CR265983
During application upgrade, annotations for com.bea.control.ServiceControl are not generated
While upgrading from 8.1.x to 9.2, annotations are sometimes not generated for the service control during application upgrade.
Operating System: ALL
Workaround: In Workshop, right-click on the control source file and select the Upgrade Source File(s)... option.
The appropriate annotation is added in the Java file. For example, the annotation could be
@ServiceControl.Location(urls = {
"http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx";;
})
If all the annotations have not been added after this operation, a compiler error is displayed. You need to then manually add the missing annotations to the control.
After updating the Java file, you can build and deploy the service control.
CR266759
Callbacks do not work with bumpy case packages
Web Services that define a Callback interface with a mixed case package name will fail to compile with jwsc.
Operating System: All
Workaround: Create the Callback interface in a lower cased package.
CR270499
Editing wsrp-wsdl-template.wsdl requires supporting files to be copied to the web-app
If you copy and edit wsrp-wsdl-template.wsdl to your web application, you also need to copy the following files from wlp-wsrp-producer-web-lib.war to you your web-app:
  • wlp_wsrp_v11_types.xsd
  • wlp_wsrp_v1_types.xsd
  • wsrp_v1_full.wsdl
  • wsrp_v1_types.xsd
  • wsrp-wsdl-template.wsdl
  • wlp_wsrp_v1_bindings.wsdl
  • wsrp_v1_bindings.wsdl
  • wsrp_v1_interfaces.wsdl
  • wsrp-wsdl-full.wsdl
  • xml.xsd
Operating System: All
CR271218
Unknown Publisher Security Alert
On the Windows platform, an Unknown Publisher security alert may be encountered when launching a downloaded 9.2 installer, even though BEA's digital signature is present and correctly registered.
This is a known Microsoft Windows problem with very large digitally-signed files. BEA has already filed a support case with Microsoft, Case # SRX060608602617. Contact BEA Customer Support for more information.
Operating System: Windows
CR274160
When you create a cluster domain using Configuration Wizard by modifying the admin server name from default AdminServer, and the admin server listen-address to IP address or DNS name, not with localhost, some of the applications may not be deployed on managed servers.
The following errors may be seen while starting managed servers due to inappropriate applications target to cluster from All Local Addresses (the default listen-address) to a specific IP address or DNS name. The errors do not occur if you create the cluster domain using the WLST Offline script.
If you have created an ALSB Cluster Domain, the following error message is displayed:
####<Jun 21, 2006 2:58:51 PM EDT> <Error> <Deployer> <pint21> <ms1> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1150916331219> <BEA-149231> <Unable to set the activation state to true for the application 'XBus Kernel'.java.lang.NullPointerException
If you have created Portal Cluster Domain, the following error message is displayed:
####<Jun 21, 2006 3:22:08 PM EDT> <Error> <Store> <pint21> <ms1> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
Kernel>> <> <> <1150917728094> <BEA-280061> <The persistent store
"pfProliferationJMSStore_auto_1" could not be deployed:
weblogic.store.PersistentStoreException: Can't find JDBC DataSource
portalFrameworkPoolNeverXA:
Workaround:
Do one of the following:
  • While creating the cluster domain using Config Wizard, change the admin server name from the default name AdminServer, but retain the listen address as default All Local Addresses. After you have created the cluster domain, start admin server and change admin server listen-address using WLS console. For more information about changing the listen-address from WLS console, see http://download.oracle.com/docs/cd/E13222_01/wls/docs91/ConsoleHelp/taskhelp/channels/ConfigureListenAddresses.html
  • In the configuration Wizard, select the WebLogic Server checkbox, and create a WebLogic Server cluster domain, with a specified Admin Server Name and IP address. Secondly, select the ALSB or Portal checkboxes, and extend the created cluster domain with ALSB or Portal component.
Operating System: All
CR275553
Warning messages displayed while bringing up the BEA Workshop for WebLogic Platform IDE
While bringing up the BEA Workshop for WebLogic Platform IDE on Solaris 10, you might encounter warning messages.
This is a Solaris 10 issue. These are harmless messages. You can ignore the messages and proceed.
Operating System: Solaris 10
CR280837
On Solaris, when multiple users run Domain Provisioning tools like the Configuration Wizard, Domain Stop Server Script or WLST Off-Line Scripting, it is possible that subsequent users of the tool might encounter error messages like:
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/jdk150_04/lib/tools.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/weblogic91/server/lib/weblogic.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/weblogic91/server/lib/webservices.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/jdk150_04/jre/lib/rt.jar'
*sys-package-mgr*: can't write cache file for
'/home/wimbledon/load12/jdk150_04/jre/lib/jsse.jar'
This message appears because WLST creates a temporary directory (for example, on Solaris it is /var/tmp/wlstTemp) that gets shared by all users and it is unable to differentiate between users. As a result, access to the directory gets blocked when the user accessing the directory is not the one who originally created the directory.
Workaround: Manually adjust directory permissions.
CR283064
Specifying an incorrect custom profile causes bsu to display warning messages and execute the command against the default profile
When using Smart Update (bsu) in the console mode, if you specify an incorrect custom profile using the -profile argument with -install, -remove and -view, the tool prints out a warning message and executes the command against the Default profile.
In certain circumstances, especially with the remove command, this might produce undesirable results, requiring you to reinstall a patch to the Default profile.
Operating System: All
CR283601
Smart Update Help displays an ‘Unable to Open’ error message if the URL being accessed contains the shortcut character ‘#’
On Windows 2000, you might encounter an ‘Unable to Open’ error message when Smart Update Help tries to access a page that contains the shortcut character ‘#’.
Workaround: Open a browser window and directly type the URL or invoke Smart Update Online Help from: BEA_HOME\utils\bsu\doc\en\smartupdatehelp\index.html
Operating System: Windows 2000
CR286040
Using WLST to run a script that uses loadProperties fails when a property name in the file contains improper characters.
An error message is displayed when you use loadProperties to load a property that contains a . (period) character in the property name.
Operating System: All
Workaround: In the loadProperties file, specify the property name without using the . (period) character. For example, use sbm instead of sbm.db.default as property name.
CR288438
Patch application does not enforce product check in command-line mode
If you installed WebLogic Integration in command-line mode, and opted to apply patches automatically (by selecting option 1) after successful completion of the installation, the installer automatically applies patches to WebLogic Server, BEA Workshop for WebLogic Platform, and WebLogic Portal. The installer does not check whether WebLogic Portal is installed or not; the patches to WebLogic Portal are applied even when WebLogic Portal is not installed.
If WebLogic Portal is installed at a later point, the installer overwrites the patches but Smart Update shows the patches as applied.
Operating System: All
Workaround: Uninstall the patches, then install WebLogic Portal, and then apply the WebLogic Portal patches using Smart Update.
CR301572
Patch installation during install overwrites newer patch catalog
If you apply patches to WebLogic Server, provided after WebLogic Integration 9.2 GA is released, the patch catalog on your installation would be updated. If you later install WebLogic Integration 9.2 from a GA kit, the patch catalog bundled with it would overwrite the existing (newer) patch catalog.
This older patch catalog from the WebLogic Integration installer may not contain patches applied before installing WebLogic Integration 9.2. Because of that, Smart Update may not accurately reflect the Server patches earlier applied to the installation. This could also lead to inconsistent or unpredictable behavior in Smart Update (offline mode) while applying or removing patches.
Operating System: All
Workaround: Connect to the BEA patch repository and acquire the latest patch catalog. Copy it to all the offline machines on which this problem occurs.
CR325556
CR306052
WLI server raises an exception after downgrading to an earlier version
WLI server raises an exception if the installation is downgraded to a previous version, and the sample domain versions in the config.xml file are also not rolled back. For example, if WLI 9.2 MP1 installation is rolled back to 9.2, the sample domain versions are not rolled back to 9.2.
Operating System: All
Workaround: Back up the existing product installation and domain before upgrading to a new version.
CR326514
SmartUpdate 3.0 does not recognize WebLogic Integration 9.2
WebLogic Platform 9.2 MP1 SmartUpdate 3.0 does not recognize WebLogic Integration 9.2 as a supported product. This problem occurs when WebLogic Integration 9.2 is the only WebLogic product installed on a computer.
Operating System: All
Workaround: Delete prod-info.xml from BEAHOME\utils\bsu\cache_dir and run the bsu script.
CR326725
The uninstaller provides the rollback option after downgrading to a previous version
After downgrading to a previous version of WLS using the SmartUpdate tool, when the uninstall.sh command is run, the uninstaller provides the rollback option along with the Uninstall the entire product option. If the rollback option is selected, the uninstaller terminates with a fatal error.
Operating System: UNIX
Workaround: Use WLS Upgrade Installer to uninstall the application.
CR335835
The commEnv.cmd and commEnv.sh files refer to patch_weblogic920 instead of patch_weblogic921 in WebLogic Server 9.2 MP1
When you upgrade from WebLogic Server 9.2 to WebLogic Server 9.2 MP1, the patch directory must be patch_weblogic921, but commEnv.cmd and commEnv.sh files still use patch_weblogic920.
Operating System: All
Workaround: Rename patch_weblogic920 to patch_weblogic921 after the upgrade.
CR360270
Product upgrade from WebLogic Server or Platform 9.2 MP2 to 9.2 MP3 using Smart Update fails for Windows EM64T
When Smart Update is used to upgrade WebLogic Server or Platform 9.2 MP2 to 9.2 MP3, the upgrade fails.
Operating System: Windows EM64T
Workaround: Use the WebLogic Platform package upgrade installer to upgrade from a WebLogic Server or Platform 9.2 MP2 installation to 9.2 MP3.
CR357969
No option is provided for rollback after consecutive upgrades
After the installation has been upgraded in steps to successive versions, rollback to previous installation does not work correctly. For example, the installation is upgraded from 9.2MP1 to 9.2MP2, and then to 9.2MP3. The first rollback from 9.2 MP3 to 9.2 MP2 works. However, the uninstaller.sh script does not provide an option for further rollback from 9.2MP2 to 9.2MP1.
Operating System: All
Workaround: None
CR331812
Incorrect install directory in registry.xml after Platform is upgraded
When the Platform installation is upgraded from 9.2.x to any MP (such as 9.2.1 or 9.2.2 ) using the upgrade installer, registry.xml may contain an incorrect entry of install directory for Workshop as 'weblogic92' as shown below: 
<component name='Workshop for WebLogic Platform' version='9.2.1.0' InstallDir='D:\bea\WLW92GA\weblogic92'>
This problem is observed only in 9.2 MP1 and 9.2 MP2 upgrade installers.
Platforms : All
Workaround: Correct the registry.xml entry manually before you proceed with your future upgrades as shown below: 
<component name='Workshop for WebLogic Platform' version='9.2.1.0' InstallDir='D:\bea\WLW92GA\workshop92'>

 

Problems Fixed

The following table describes problems that have been fixed in the installation and configuration software delivered with WebLogic Server 9.2, WebLogic Portal 9.2 and BEA Workshop for WebLogic Platform 9.2.

Problem ID
Description
CR234354
After you extend a base WebLogic domain with the WebLogic Server Default Domain and WebLogic Server Examples extension templates, the resulting domain will not boot. This problem occurs if, after creating a domain in the Configuration Wizard, you navigate backward in the Configuration Wizard to the initial window and extend the newly created domain without having first exited from that tool.
This problem has been resolved.
CR234973
A Managed Server template created using the pack command includes all the end-user applications, including application files, for the domain from which the template was created. This results in a template JAR file that is potentially very large.
This problem has been resolved.
CR247833
Garbled characters are displayed when you run the ls() command, and there is a configuration MBean with named multi-byte characters.
This problem has now been resolved.
CR253610
While installing WebLogic Platform, if you clear the Mercury profiling tools check box on the Optional Tools screen, select Next, subsequently return to the Optional Tools screen using the Previous button, and then select to install the Mercury profiling tools option, the tools are not be installed.
This problem has been resolved. You no longer need to ensure that the Mercury Profiling Tools option is selected in the Optional Tools screen at the time of installation.
CR255916
After having applied multiple patches that contain patch JAR files with the same name, if you remove and then attempt to reapply any of those patches, you may see an exception similar to the following:
java.lang.IllegalArgumentException: JarEntry must not be null.
at com.bea.plateng.common.util.JarHelper.extract(JarHelper.java:646)
at com.bea.plateng.common.util.JarHelper.extract(JarHelper.java:605)
at com.bea.plateng.common.util.JarHelper.extract(JarHelper.java:563)
at
com.bea.plateng.patch.ClasspathPatchInstaller.install(ClasspathPatchInstaller.java:118)
at
com.bea.plateng.patch.PatchInstallationHelper.install(PatchInstallationHelper.java:258)
This problem has been resolved. You no longer need to exit and restart Smart Update, and reapply the patch that previously caused the exception.
CR256979
The relative PointBase database.home parameter in the pointbase.ini file was not translated to absolute path for the DB upgrade plug-in to find the data and index files of the database.
This problem has now been resolved.
CR261740
Sometimes, the Domain Upgrader can hang during the “JMS Store Upgrade” step of domain upgrade if the JMS stores are backed by Pointbase. This can happen primarily on Workshop 8.1 domains that do not have Portal installed.
This problem has been resolved.
CR267027
Using org.apache.xmlbeans.XmlObject as a web service operation parameter or return type is not fully functional. It is not fully functional even when XmlObject is referenced from a class that is the parameter type. Messages passed into an operation that has XmlObject as the parameter type or references XmlObject from a parameter type may not result in valid representations of the original message to the web service.
This problem has been resolved. Support for XmlObject now exists.
CR267159
Web Services that use an array of XMLBeans as parameters and or return types will cause a jwsc compile error.
This problem has been resolved.
CR268328
During installation, the relative paths specified in the pluggableTModel.file.list parameter in the uddi.properties file were not substituted with the absolute path.
This problem has now been resolved.
CR268739
Deploying portal applications with a service control fails during EJB assembly. When the value of the operation message element is not the same as the operation name, the SOAP bindings in a WSDL file are incorrectly identified as type DOCUMENT/LITERAL/BARE. Deployment fails in such a scenario.
This problem has been resolved.
CR268947
RPC/Encoded soap messages can optionally include the xsi:type attribute associated with the data. For instance: <cost xsi:type="xsd:float">29.95</cost>
However, this adds additional overhead to the message so, to minimize performance degradation, and since this attribute is not required, it has not been included by default. Therefore the cost element in the RPC/Encoded message would look like:
<cost>29.95</cost>
Some web service stacks require the xsi:type element so, a property that allows users to force marshal to include the xsi:type element has been created:
((weblogic.wsee.jaxrpc.StubImpl)stub)._setProperty(weblogic.wsee.jaxrpc.WLStub.MARSHAL_FORCE_INCLUDE_XSI_TYPE,"true");
This problem has been resolved.
CR276800
The UpdateLicense command and script limited the number of EVAL licenses to the number of IP addresses allowed for a licensed version of WebLogic Platform.
This problem has been resolved, and the EVAL license now supports unlimited number of IP addresses.


  Back to Top       Previous  Next