bea.com | products | dev2dev | support | askBEA
 Search
 e-docs > WebLogic Platform > Release Notes > BEA WebLogic Platform 7.0 Release Notes

Release Notes

BEA WebLogic Platform 7.0 Release Notes

BEA WebLogic Platform Release: 7.0 Service Pack 6
Date: March 2005

This document includes the following topics:

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

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.

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\weblogic700, but you can situate WL_HOME in any directory.

What's New in BEA WebLogic Platform 7.0 Service Pack 6

BEA WebLogic Platform 7.0 Service Pack 6 (SP6) incorporates maintenance updates for all WebLogic Platform 7.0 components (WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal, and WebLogic JRockit). WebLogic Platform 7.0 SP6 can be used to update all WebLogic Platform 7.0 components.

WebLogic Platform 7.0 SP6 also includes the following updates:

• The WebLogic Server Administration Console has added the Servlet Extension Case Sensitive attribute to server and cluster configurations. In addition, the Web App Files Case Insensitive attribute has been added to security domain configuration.
• For more information, see "What's New in WebLogic Server 7.0 SP6?" in the WebLogic Server Release Notes at the following URL:

• WebLogic JRockit includes several changes to the set of system properties. WebLogic JRockit continues to support all system properties available from Sun. For more information, see "Changes in Service Pack 6" in the WebLogic JRockit 7.0 SDK Release Notes at the following URL:

For a complete list of the features that are new in previous WebLogic Platform 7.0.x releases, see the What's New page at the following URL:

Platform Support and System Requirements

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

http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs70/70_over/overview.html

Note: Because Red Hat stopped supporting Linux 7.2 on December 31, 2003, BEA also ended support at that time. We recommend that you upgrade to Red Hat Enterprise Linux and WebLogic JRockit.

General product installation instructions for all supported platform configurations are provided in Installing WebLogic Platform at the following URL:

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

For special installation procedures, such as for IBM AIX and SuSE Linux platforms, see "Installation Instructions For Your Platform" in the Supported Configuration for WebLogic Platform 7.0 at the following URL:

Special Installation Instructions

Special installation instructions are required for some operating system configurations. For WebLogic Platform 7.0, special installation and usage instructions are required for the following operating systems:

• IBM AIX 4.3.3, 5.1, 5.2, and 5.3
• SuSE Linux Enterprise Server 7 and 8 on IBM zSeries/S390

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

Using WebLogic Platform with the WebLogic JRockit SDK

Please review the following usage notes pertaining to the WebLogic JRockit SDK:

• If you would like to switch your Sun JVM to use WebLogic JRockit, use the procedure described in Switching JVMs in WebLogic Platform.
• If you are running an earlier 7.0.x release of WebLogic Platform with the WebLogic JRockit SDK, you can now use the available upgrade installer to upgrade your WebLogic Platform installation. (In earlier 7.0.x releases, you were required to use the full WebLogic Platform installer.) For more information about upgrading your installation, see "Installing Service Packs and Rolling Patches" in Installing WebLogic Platform at the following URL:
• For a description of the limitations on support, see Limitations on WebLogic JRockit SDK Support.

Switching JVMs in WebLogic Platform

The following instructions are provided for users who have already installed WebLogic Platform 7.0 SP6, and want to switch to a different JVM. Follow these instructions if you want to switch from the bundled Sun JVM to WebLogic JRockit, or vice versa, or switch to a non-bundled Sun JVM.

Note: To facilitate any future installation upgrades, this procedure is recommended when updating your installation to use a non-bundled JVM with WebLogic Platform.

Depending on the installer you choose, WebLogic Platform 7.0 SP6 is bundled with one of the following JVMs: Sun Java 2 SDK (jdk131_14) or WebLogic JRockit SDK (jrockit70sp6_131_14).

1. Move the BEA_HOME/jdk131_14 (Sun) or BEA_HOME/jrockit70sp6_131_14 (WebLogic JRockit) directory to a backup location.

• If you are installing WebLogic JRockit or the Sun Java 2 SDK that is bundled with WebLogic Platform 7.0, install the JVM into BEA_HOME.
• If you are installing a non-bundled Sun JVM, first install that JVM into a directory outside BEA_HOME. Then copy that JVM directory into a directory in BEA_HOME that matches the directory name that you backed up in step 1.

3. If you are using a different JVM vendor than that which was bundled with the installation, you must verify that the COMM_JAVA_VENDOR environment variable is set to Sun if you are using a Sun JVM, or BEA if you are using a WebLogic JRockit JVM. The COMM_JAVA_VENDOR environment variable is located in the commEnv file in one of the following directories:

BEA_HOME\weblogic700\common\bin\commEnv.cmd (Windows)
BEA_HOME/weblogic700/common/bin/commEnv.sh (Unix)

Note: The E-Business Control Center is not supported with WebLogic JRockit. If you are switching from a Sun SDK to WebLogic JRockit and you are planning to use the E-Business Control Center, you must also modify the -jdkhome line in the file BEA_HOME\weblogic700\ebcc\bin\ide.cfg so it points to the Sun Java 2 SDK 1.3.1_14 installation in the backup location in which you saved the SDK directory in step 1.

Migrating Domains Created Using the Configuration Wizard

The Configuration Wizard is a WebLogic Platform tool that allows you to create new domains quickly and easily. When you upgrade your WebLogic Platform 7.0 installation to a new 7.0 service pack (SP) release, you must migrate all domains that were created using the Configuration Wizard in order to use them in the new 7.0 SP release. This section provides instructions that apply to the following WebLogic Platform installations: 7.0 GA, 7.0 SP1, 7.0 SP2, 7.0 SP4, 7.0 SP5, and 7.0 SP6.

Notes: If you have not yet upgraded WebLogic Platform to the desired 7.0 SP release, do so now, and then return to this section once the installation is complete. For installation instructions, see "Installing Service Packs and Rolling Patches" in Installing WebLogic Platform at the following URL:

Ensure that a domain was run successfully in the previous 7.0.x releases before migrating it to the new release.

The migration process consists of the following steps:

1. Running the Migration Script

You need to run the migration script to upgrade the product JAR files in the domain directory.

2. Performing Manual Steps for Completing a Migration

You need to manually update specific files within the domain.

3. Updating Scripts and Configuration Files on New (Not Upgraded) Installations

This step is required only if you have installed WebLogic Platform in a directory other than the BEA_HOME directory. If you have upgraded an existing WebLogic Platform 7.0 installation, you can skip this step. This step involves updating the BEA_HOME environment variable in the domain startup scripts (such as startWebLogic) and configuration files (such as config.xml), and in any custom scripts that you have created.

These steps are explained in detail in the following sections. You will need to repeat this process for each domain that you want to migrate.

Note: The instructions apply regardless of whether the Sun Java 2 SDK or the WebLogic JRockit SDK is being run.

Running the Migration Script

The first step in migrating an existing domain that you created using the Configuration Wizard is to run the migration script to upgrade the product JAR files for that domain. To do so, navigate to BEA_HOME\weblogic700\server\bin and enter one of the following commands:

• On Windows: migrate.cmd domain mode
• On UNIX: migrate.sh domain mode

The following table defines the command-line arguments.

Table 1 Command-Line Arguments for migrate Script

Argument

Description

domain

Full pathname of the domain directory.

mode

Migration mode. The mode can be set to one of two values: upgrade or revert.

upgrade—Select this mode to upgrade the product JAR files in the domain directory, as required. For more information, see What Happens During an Upgrade?. This is the default mode.

revert—Select this mode to restore a migrated domain to its pre-migration state, using the backup files (for example, *.jar.orig) that were generated before the migration was launched. If no backup files exist, the command is ignored.

You are prompted to press any key to start processing.

If, for some reason, you decide to revert to a previous installation, you must first revert any domain that you have upgraded to its former state. Only after you revert your domains should you then revert your WebLogic Platform installation. To revert a migration, run the migration script again, specifying the revert option on the command line.

When you specify upgrade, the default migration mode, the script performs the following actions:

• The original product JAR files are saved:
• If you are migrating to 7.0 SP1, the files are named *.jar.orig.
• If you are migrating to 7.0 SP2, the files are named *.jar.orig_bfsp2.
• If you are migrating to 7.0 SP4, the files are stored, with the same names, in the pre_sp3backup directory.
• If you are migrating to 7.0 SP5, the files are stored, with the same names, in the pre_sp4backup directory
• If you are migrating to 7.0 SP6, the files are stored, with the same names, in the pre_sp5backup directory.

• If you are migrating a domain to 7.0 SP2, the migration script also performs the following changes:
• Replaces the Java options (-server, -hotspot) with the COMM_VM variable.
• Replaces all occurrences of %JAVA_VM% with %COMM_VM%.
• Copies any new security certificates to each WebLogic Integration domain.
• Replaces all occurrences of jdk131_03 with jdk131_06. (You must modify all custom scripts to reference the new SDK.)

• If you are migrating a domain to 7.0 SP4, the migration script also performs the following changes:
• Replaces all occurrences of jdk131_0x with jdk131_08. (You must modify all custom scripts to reference the new SDK.)
• Note: You need to manually replace all references to the Sun Java 2 SDK with jdk131_08 in the config.xml file and in any custom scripts that reference the SDK.

• Replaces the Java options (-server, -hotspot) with the COMM_VM variable.
• Replaces all occurrences of %JAVA_VM% with %COMM_VM%.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\paymentWSApp to the following directory of your Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\paymentWSApp.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\datasync\WEB-INF\lib to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\datasync\WEB-INF\lib.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\tools\WEB-INF\lib
to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\tools\WEB-INF\lib.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\toolSupport\WEB-INF\lib
to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\toolSupport\WEB-INF\lib.
• Copies all the .jar files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the BEA_HOME\user_projects\domain\beaApps\portalApp directory (by default) for your application.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\taxWSApp to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\taxWSApp.

• If you are migrating a domain to 7.0 SP5, the migration script also performs the following changes:
• Replaces all occurrences of jdk131_0x with jdk131_10. (You must modify all custom scripts to reference the new SDK.)
• Note: You need to manually replace all references to the Sun Java 2 SDK with jdk131_10 in the config.xml file and in any custom scripts that reference the SDK.

• Replaces the Java options (-server, -hotspot) with the COMM_VM variable.
• Replaces all occurrences of %JAVA_VM% with %COMM_VM%.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\paymentWSApp to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\paymentWSApp.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\datasync\WEB-INF\lib to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\datasync\WEB-INF\lib.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\tools\WEB-INF\lib
to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\tools\WEB-INF\lib.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\toolSupport\WEB-INF\lib
to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\toolSupport\WEB-INF\lib.
• Copies all the .jar files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the BEA_HOME\user_projects\domain\beaApps\portalApp directory (by default) for your application.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\taxWSApp to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\taxWSApp.

• If you are migrating a domain to 7.0 SP6, the migration script also performs the following changes:
• Replaces all occurrences of jdk131_0x with jdk131_14. (You must modify all custom scripts to reference the new SDK.)
• Note: You need to manually replace all references to the Sun Java 2 SDK with jdk131_14 in the config.xml file and in any custom scripts that reference the SDK.

• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\paymentWSApp to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\paymentWSApp.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\datasync\WEB-INF\lib to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\datasync\WEB-INF\lib.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\tools\WEB-INF\lib
to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\tools\WEB-INF\lib.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\toolSupport\WEB-INF\lib
to the following Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\toolSupport\WEB-INF\lib.
• Copies all the .jar files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the BEA_HOME\user_projects\domain\beaApps\portalApp directory (by default) for your application.
• Copies all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\taxWSApp to the following directory (by default): BEA_HOME\user_projects\domain\beaApps\taxWSApp.

Suppose you want to upgrade a domain called mydomain, which resides in the default user projects directory, BEA_HOME\user_projects. Run the command that is appropriate for your platform:

• On Windows: migrate.cmd c:\bea\user_projects\mydomain upgrade
• On UNIX: migrate.sh /bea/user_projects/mydomain upgrade

Revert Example

To undo the changes made to mydomain during the migration process, run the script appropriate for your operating system:

• On Windows: migrate.cmd c:\bea\user_projects\mydomain revert
• On UNIX: migrate.sh /bea/user_projects/mydomain revert

Performing Manual Steps for Completing a Migration

Depending on the domain template used to generate the domain, you may need to add or modify existing scripts or files to support an existing 7.0 SP release of WebLogic Platform.

The following sections describe the manual steps required to complete a migration, including:

Note: The migration steps described are cumulative for each 7.0 SP release. So, for example, if you are migrating to 7.0 SP6 from 7.0, you must complete the procedures described to migrate to 7.0 SP1, 7.0 SP2, 7.0 SP4, and 7.0 SP5, as indicated, before completing the steps described to migrate to 7.0 SP6.

Performing Manual Steps for WebLogic Platform 7.0 SP1 Migration

This section describes the manual steps that must be performed to migrate your domain to WebLogic Platform 7.0 SP1 from 7.0. Refer to the appropriate section below, based on the domain template used to generate the domain, and perform the steps described.

Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.

BPM Domain

For a domain that is based on the BPM Domain template, perform the following steps:

1. Add the WLISERVERCP variable to the startWebLogic.cmd (Windows) or startWebLogic.sh (UNIX) script to define the CLASSPATH. The startWebLogic scripts reside in the BEA_HOME\user_projects\domain directory.

The following sample excerpt from the startWebLogic.cmd script (Windows) shows the required update in bold:

:pointbase
REM Invoke a script to finish up work
set WLISERVERCP=%WLISERVERCP%;%PBCOMMONCP%;
set SCRIPT=%WLI_HOME%\lib\scripts\PointbaseChecker.xml

2. Add the PBCOMMONCP variable to the end of the CLASSPATH definition in the startManagedWebLogic.cmd (Windows) or startManagedWebLogic.sh (UNIX) script. The startManagedWebLogic scripts reside in the BEA_HOME\user_projects\domain directory.

The following sample excerpt from the startManagedWebLogic.cmd script (Windows) shows the required update in bold:

set CLASSPATH=%WLISERVERCP%;%PBCOMMONCP%

3. Modify the setDBVars.cmd (Windows) or setDBVars (UNIX) command to reflect the appropriate PointBase version (183 versus 172) in the JAR filenames defined in the CLASSPATH. The files for both commands are located in the following directory, by default:

BEA_HOME\user_projects\domain\dbInfo\pointbase

The following sample excerpt from the setDBVars.cmd script (Windows) shows the required updates in bold:

Before:

set CLCP=-classpath %WL_HOME%\..\samples\server\eval\pointbase\lib\pbserver42ECF172.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbclient42ECF172.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbtools42ECF172.jar;

After:

set CLCP=-classpath %WL_HOME%\..\samples\server\eval\pointbase\lib\pbserver42ECF183.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbclient42ECF183.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbtools42ECF183.jar;

EAI Domain

For a domain that is based on the EAI Domain template, see the procedure described in BPM Domain.

Platform Domain

For a domain that is based on the Platform Domain template, perform the following steps:

1. In the web.xml file for the tools Web application (located, by default, in the BEA_HOME\user_projects\domain\beaApps\portalApp\tools\WEB-INF directory), locate the Customer Profile and Order Pages security constraint and define the resources to which the security constraint applies using the <url-pattern> element.

The following sample excerpt from the web.xml file shows the required updates in bold:

<security-constraint>  <!-- Define a resource collection -->  <web-resource-collection>    <web-resource-name>      Customer Profile and Order Pages    </web-resource-name>    <description>      Customer Profile and Order Pages    </description>  <!-- URL pattern for the resource collection -->    <url-pattern>/tools/*</url-pattern>    <url-pattern>/repository/*</url-pattern>    <url-pattern>/security/*</url-pattern>    <http-method>GET</http-method>    <http-method>POST</http-method>  </web-resource-collection></security-constraint>

Note: WebLogic Server validates each web-resource-collection element within a security-constraint element to ensure that it contains at least one URL pattern. If you have other Web applications in your domain, verify that all web-resource-collection elements contain at least one URL pattern, appropriate for the security constraint.

2. Copy the following files from the BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\tools\tools directory to the tools directory of your tools Web applications. Be careful not to overwrite any files that you have customized.
catalog\category_add_remove_items.jspcatalog\item_property_edit.jspcatalog\item_property_edit_mr.jspcatalog\item_property_edit_mu.jspcatalog\item_property_edit_sr.jspcatalog\item_property_edit_su.jspcatalog\item_search.jspusermgmt\groupuser_property_edit_mr.jspusermgmt\groupuser_property_edit_mu.jspusermgmt\groupuser_property_edit_sr.jspusermgmt\groupuser_property_edit_su.jspusermgmt\group_add_remove_users.jspusermgmt\group_edit.jspusermgmt\group_scope_property.jspusermgmt\user_create.jspusermgmt\user_edit_info.jspusermgmt\user_scope_property.jsp

3. Copy the weblogic-application.xml file from the BEA_HOME\weblogic700\samples\portal\p13nDomain\beaApps\p13nApp\META-INF directory to BEA_HOME\user_projects\domain\beaApps\portalApp\META-INF directory. Be careful not to overwrite any file that may have been created using this filename.

4. If you have created a portal Web application in your domain, you need to perform the following steps for each application:

1. Copy the following files from the BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\framework directory to the framework directory of your portal Web application. Be careful not to overwrite any files that may have been created using one of these filenames.
2. edit_titlebar.propertieserror\configurationerror.propertieserror\footer.incerror\header.incerror\header.propertieserror\missingformfield.propertieserror\parameters.propertieserror\pipeline.propertieserror\request.propertieserror\runtimeerror.propertieshnav_bar.propertiesmaximize_titlebar.propertiesminimize_titlebar.propertiesnormal_titlebar.propertiessecurity\help.propertiessecurity\meta.incvnav_bar.properties

3. Update the following JSP files in the framework directory of your portal Web application using the corresponding files in the BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\framework directory as a guide for comparison. Because you may have modified the JSP files to customize your portal, it is not recommended that you overwrite the existing files unless you are certain that they have not been customized.
4. edit_titlebar.incerror\configurationerror.jsperror\error.jsperror\missingformfield.jsperror\parameters.jsperror\pipeline.jsperror\request.jsperror\runtimeerror.jsperror\sessiontimeout.jsperror\sessiontimeout.propertiesfloated_portlet.jsphnav_bar.jspmaximize_titlebar.incminimize_titlebar.incnormal_titlebar.incsecurity\help.jspsecurity\login_header.incsecurity\need_group.jspsecurity\new_user.jspsecurity\set_password.jsptools\header.jsptools\header.propertiestools\portal_prefs.jspvnav_bar.jsp

5. Copy the following files from the BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\WEB-INF\lib directory to the WEB-INF\lib directory of your portal Web applications. Be careful not to overwrite any files that you have customized.
6. ent_taglib.jares_taglib.jari18n_taglib.jarlic_taglib.jarp13n_servlet.jarportal_servlet.jarportal_taglib.jarportlet_taglib.jarren_taglib.jarres_taglib.jarum_taglib.jarutil_taglib.jarvisitor_taglib.jarwebflow_servlet.jarwebflow_taglib.jarweblogic-tags.jar

WebLogic Workshop Domain

For a domain that is based on the WebLogic Workshop Domain template, perform the following steps:

1. Modify the startWebLogic.cmd (Windows) or startWebLogic.sh (UNIX) command to reflect the appropriate PointBase version (183 versus 172) in the JAR filenames defined in the CLASSPATH. The files for both commands are located in the following directory, by default:
BEA_HOME\user_projects\domain

The following sample excerpt from the startWebLogic.cmd script (Windows) shows the required updates in bold:

Before:

set PB_CLASSPATH=%POINTBASEDIR%\eval\pointbase\lib\pbserver42ECF172.jar;%POINTBASEDIR%\eval\pointbase\lib\pbclient42ECF172.jar

After:

set PB_CLASSPATH=.\;%POINTBASEDIR%\eval\pointbase\lib\pbserver42ECF183.jar;%POINTBASEDIR%\eval\pointbase\lib\pbclient42ECF183.jar

2. Copy the following files from the BEA_HOME\weblogic700\samples\workshop directory to the BEA_HOME\user_projects\domain directory of your WebLogic Workshop domain. Be careful not to overwrite any files that may have been created using one of these filenames.
setWorkshopEnv.cmdsetWorkshopEnv.shstartPointBaseConsole.cmdstartPointBaseConsole.shURLs.dat

WLI Domain

For a domain that is based on the WLI Domain template, perform the following steps:

1. Add the SVRCP variable to the startWebLogic.cmd (Windows) or startWebLogic.sh (UNIX) script to define the CLASSPATH. The startWebLogic scripts reside in the BEA_HOME\user_projects\domain directory.

The following sample excerpt from the startWebLogic.cmd script (Windows) shows the required update in bold:

:pointbaseREM Invoke a script to finish up workset SVRCP=%SVRCP%;%PBCOMMONCP%;set SCRIPT=%WLI_HOME%\lib\scripts\PointbaseChecker.xml

2. Open the startManagedWebLogic script:

• On Windows: BEA_HOME\user_projects\domain\startManagedWebLogic.cmd
• On UNIX: BEA_HOME\user_projects\domain\startManagedWebLogic

3. Add the PBCOMMONCP variable to the end of the CLASSPATH definition.

4. If you are running a WLI, BPM, or EAI domain created in 7.0 GA, also delete (or comment out) the following line:

JAVA_VM=-server

The following sample excerpt from the startManagedWebLogic.cmd script (Windows) shows the required update in bold:

set CLASSPATH=%WLISERVERCP%;%WLI_HOME%\lib\hlcommon.jar;%WLI_HOME%\lib\mekshared.jar;%WLI_HOME%\lib\powerapi.jar;%PBCOMMONCP%

5. Modify the setDBVars.cmd (Windows) or setDBVars (UNIX) command to reflect the appropriate PointBase version (183 versus 172) in the JAR filenames defined in the CLASSPATH. The files for both commands are located in the following directory, by default:
BEA_HOME\user_projects\domain\dbInfo\pointbase

The following sample excerpt from the setDBVars.cmd script (Windows) shows the required updates in bold:

Before:

set CLCP=-classpath %WL_HOME%\..\samples\server\eval\pointbase\lib\pbserver42ECF172.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbclient42ECF172.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbtools42ECF172.jar;%WLI_DOMAIN_HOME%

After:

set CLCP=-classpath %WL_HOME%\..\samples\server\eval\pointbase\lib\pbserver42ECF183.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbclient42ECF183.jar
set CLCP=%CLCP%;%WL_HOME%\..\samples\server\eval\pointbase\lib\pbtools42ECF183.jar;%WLI_DOMAIN_HOME%

WLP Domain

To migrate a domain that is based on the WLP Domain template, complete the procedure described in Platform Domain.

WLS Domain

For a domain that is based on the WLS Domain template, you do not need to add or modify existing scripts or files.

WLS Examples

For a domain that is based on the WLS Examples domain template, perform the following steps:

1. Modify the CLASSPATH definition in the startExamplesServer.cmd (Windows) or startExamplesServer.sh (UNIX) command to:

• Reflect the appropriate PointBase version (183 versus 172) in the JAR filenames.

The files for both commands are located in the following directory, by default:

BEA_HOME\user_projects\domain

The following sample excerpt from the startExamplesServer.cmd script (Windows) shows the required updates in bold:

Before:

set CLASSPATH=c:\bea\jdk131_03\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF172.jar;%POINTBASE_HOME%\lib\pbclient42ECF172.jar;%CLIENT_CLASSES%;%SERVER_CLASSES%;%COMMON_CLASSES%;%CLIENT_CLASSES%\utils_common.jar

After:

set CLASSPATH=c:\bea\jdk131_03\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF183.jar;%POINTBASE_HOME%\lib\pbclient42ECF183.jar;%CLIENT_CLASSES%;%SERVER_CLASSES%;%COMMON_CLASSES%;%CLIENT_CLASSES%\utils_common.jar;c:\bea\weblogic700\server\lib\webservices.jar

2. Copy the Webservices_trader.ear file from the BEA_HOME\samples\server\config\examples\applications directory to the BEA_HOME\user_projects\WLSExampleDomain\applications directory of your Web applications. Be careful not to overwrite any files that you have customized.

WLS Petstore

For a domain that is based on the WLS Petstore domain template, modify the startPetStore.cmd (Windows) or startPetStore.sh (UNIX) command to reflect the appropriate PointBase version (183 versus 172) in the JAR filenames defined in the CLASSPATH.

The files for both commands are located in the following directory, by default:

BEA_HOME\user_projects\domain

The following sample excerpt from the startPetStore.cmd script (Windows) shows the required updates in bold:

Before:

set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF172.jar;%POINTBASE_HOME%\lib\pbclient42ECF172.jar;%SERVER_CLASSES%;%COMMON_CLASSES%

After:

set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%POINTBASE_HOME%\lib\pbserver42ECF183.jar;%POINTBASE_HOME%\lib\pbclient42ECF183.jar;%SERVER_CLASSES%;%COMMON_CLASSES%

Performing Manual Steps for WebLogic Platform 7.0 SP2 Migration

This section describes the manual steps that must be performed to migrate your domain to WebLogic Platform 7.0 SP2:

1. If you are migrating a WebLogic Platform 7.0 domain, ensure that you have completed the manual steps required to migrate your domain to WebLogic Platform 7.0 SP1, as described in Performing Manual Steps for WebLogic Platform 7.0 SP1 Migration.

2. Perform the steps described in the following sections to migrate to WebLogic Platform 7.0 SP2 a domain based on one of the following templates:

No additional steps are required if you are migrating a domain based on one of following templates: Platform Domain, WLS Domain, WLS Examples, or WLS Petstore.

Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.

BPM Domain

To migrate a domain that is based on the BPM template to WebLogic Platform 7.0 SP2, complete the following steps:

2. To support two new features—BPM JSP Worklist and BPM File Plug-in—update the domain config.xml file to include the required deployable components, as described below.

Note: The following instructions apply to both a single-server or cluster domain configuration, except where indicated.

In the following descriptions, name indicates the name of the single-server or cluster and cluster_server_name indicates the name of the server in the cluster that you are referencing.

1. To support the BPM JSP Worklist, add the following component under <Application Name ="WebLogic Integration">:
2. <WebAppComponent Name="WLI-BPM JSP Worklist"
Targets="
name"
URI="worklist.war"/>

3. To support the BPM File Plug-in, add the following component under <Application Name ="WebLogic Integration">:
4. <EJBComponent Name="WLI BPM File Plug-in"
Targets="
name"
URI="fileplugin-ejb.jar"/>

Add the following component under the JMSServer text block, ignoring the cluster_server_name variable for a single-server domain configuration, and repeating for each server in a cluster domain configuration:

<JMSQueue Name="WLI_BPM_FP-cluster_server_name"
JNDIName="com.bea.wli.bpm.FilePluginQueue-
cluster_server_name"
StoreEnabled="true"
Template="WLI_JMSTemplate-
cluster_server_name"/>

For a cluster domain configuration only, add the following components under <Application Name ="WebLogic Integration">:

<JMSDistributedQueue Name="WLI_BPM_FP"
JNDIName="com.bea.wli.bpm.FilePluginQueue"
Targets="name">
<JMSDistributedQueueMember
Name="WLI_BPM_FP-
cluster_server_name"
JMSQueue="WLI_BPM_FP-
cluster_server_name"
Weight="1"/>
<JMSTemplate Name="WLI_BPM_FP"/>
</JMSDistributedQueue>

Example:

The following provides an example of how to migrate a domain that is based on the BPM Domain template, demonstrating how to update the database schema and configure the BPM File Plug-In.

1. Update the BPM database table with FILEPOLL, a new database table used by the BPM File Plug-In. To do so, run the following script:

BEA_HOME\weblogic700\integration\dbscripts\database_type\migrate\
BPM_70-70SP2.sql

In the preceding line, BEA_HOME represents the WebLogic Platform home directory.

2. Prepare to migrate a single-server domain by configuring the BPM File Plug-in for the domain in the config.xml file:

1. To deploy the fileplugin-ejb.jar as one component of a WebLogic Integration application, add the following:
2. <EJBComponent Name="WLI-BPM File Plug-in"
Targets="
Customer_Server_Name" URI="fileplugin-ejb.jar"/>

3. To add the JMS queue for the BPM File Plug-in, add the following:
4. <JMSQueue JNDIName="com.bea.wli.bpm.FilePluginQueue"
Name="WLI_BPM_FP" Template="WLI_JMSTemplate"/>

3. Prepare to migrate to a clustered domain by configuring the BPM File Plug-in for the domain in the config.xml file:

Note: This example shows a cluster system (mycluster) with one administration server (myserver) and two managed servers (c1, c2).

1. To deploy fileplugin-ejb.jar on a cluster server, add the following:
2. <EJBComponent Name="WLI BPM File Plug-in"
Targets="mycluster"
URI="fileplugin-ejb.jar"/>

3. To configure the JMS Queue for the BPM File Plug-in, add the following:
4. <JMSDistributedQueue Name="WLI_BPM_FP"
JNDIName="com.bea.wli.bpm.FilePluginQueue"
Targets="mycluster">
<JMSDistributedQueueMember Name="WLI_BPM_FP-c1"
JMSQueue="WLI_BPM_FP-c1"
Weight="1"/>
<JMSDistributedQueueMember Name="WLI_BPM_FP-c2"
JMSQueue="WLI_BPM_FP-c2"
Weight="1"/>
<JMSTemplate Name="WLI_BPM_FP"/>
</JMSDistributedQueue>

5. On the cluster node c1 JMS server, add the following:
6. <JMSQueue Name="WLI_BPM_FP-c1"
JNDIName="com.bea.wli.bpm.FilePluginQueue-c1"
StoreEnabled="true"
Template="WLI_JMSTemplate-c1"/>

7. On the cluster node c2 JMS server, add the following:
8. <JMSQueue Name="WLI_BPM_FP-c2"
JNDIName="com.bea.wli.bpm.FilePluginQueue-c2"
StoreEnabled="true"
Template="WLI_JMSTemplate-c2"/>

EAI Domain

To migrate a domain that is based on the EAI Domain template, complete the procedure described in BPM Domain.

WebLogic Workshop Domain

To migrate a domain that is based on the WebLogic Workshop Domain template to WebLogic Platform 7.0 SP2, update the startweblogic script for your domain as follows:

call %WL_HOME%\common\bin\commEnv.cmd

2. Set the JAVA_DEBUG variable as follows:

JAVA_DEBUG=%COMM_CLIENT_VM%

3. Set the JAVA_HOME variable as follows:

JAVA_HOME=%JAVA_HOME%

WLI Domain

To migrate a domain that is based on the WLI Domain template, complete the procedure described in BPM Domain.

WLP Domain

To migrate a domain that is based on the WLP Domain template to WebLogic Platform 7.0 SP2, you must complete the following three phases:

Phase 1: Copy Files

Note: Be careful not to overwrite any files that you have customized.

1. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\datasync to your datasync Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\datasync.

2. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\tools
to your tools Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\tools.

3. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\toolSupport
to your toolSupport Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\toolSupport.

4. Copy all the .jar files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the BEA_HOME\user_projects\domain\beaApps\portalApp directory for your application.

5. If you have created a portal Web application in your domain, copy all the .jar files from the BEA_HOME\weblogic700\common\templates\webapps\portal\
baseportal\j2ee\WEB-INF\lib
directory to the WEB-INF\lib directory for each of your portal Web applications.

We strongly recommend that you run the Portal Consistency Checker after performing these migration steps to ensure all the necessary files have been copied. The Portal Consistency Checker is available on the dev2dev site at:

http://dev2dev.bea.com/codelibrary/code/portal_consistency_checker.jsp

Phase 2: Modify Your web.xml File

To modify the web.xml file for your Web application, you can use either of two methods:

1. Replace the weblogic.xml file for your Web application with the weblogic.xml.stock version in the following directory:

BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\
WEB-INF

Then incorporate your previous changes into the newly copied file.

2. Copy and paste the new code shown in steps a-d into the following sections of the weblogic.xml file for your Web application: <listener>, <servlet-mapping>, <taglib>, and <ejb-ref>.

1. Add the following lines after the <listener> section:
2. <!-- Filter to fire click through events --><filter>   <filter-name>ClickThroughEventFilter</filter-name>--> <filter-class>com.bea.p13n.tracking.clickthrough.ClickThroughEventFilter</filter-class></filter><filter-mapping>   <filter-name>ClickThroughEventFilter</filter-name>   <url-pattern>/application/*</url-pattern></filter-mapping>

3. Add the following lines after the <servlet-mapping> section:
4. <!-- The ShowDoc Servlet --><servlet>  <servlet-name>ShowDocServlet</servlet-name>  <servlet-class>com.bea.p13n.content.servlets.ShowDocServlet</servlet-class>     <!-- Make showdoc always use the local ejb-ref DocumentManager -->  <init-param>    <param-name>contentHome</param-name>    <param-value>java:comp/env/ejb/DocumentManager</param-value>  </init-param></servlet><!-- The AdClickThru Servlet --><servlet>  <servlet-name>adClickThru</servlet-name>  <servlet-class>com.bea.p13n.ad.servlets.AdClickThruServlet</servlet-class></servlet><!-- The ClickThrough Servlet --><servlet>  <servlet-name>clickThroughServlet</servlet-name><servlet-class>com.bea.p13n.tracking.clickthrough.ClickThroughServlet</servlet-class></servlet><servlet-mapping>  <servlet-name>ShowDocServlet</servlet-name><url-pattern>/ShowDoc/*</url-pattern></servlet-mapping><servlet-mapping>   <servlet-name>adClickThru</servlet-name>   <url-pattern>/adClickThru/*</url-pattern></servlet-mapping><servlet-mapping>   <servlet-name>adClickThru</servlet-name>   <url-pattern>/AdClickThru/*</url-pattern></servlet-mapping><servlet-mapping>  <servlet-name>clickThroughServlet</servlet-name>  <url-pattern>/clickThroughServlet/*</url-pattern></servlet-mapping>

5. Add the following lines to the <taglib> section:
6. <taglib>   <taglib-uri>cat.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/cat_taglib.jar</taglib-location></taglib><taglib><taglib-uri>eb.tld</taglib-uri><taglib-location>/WEB-INF/lib/eb_taglib.jar</taglib-location></taglib><taglib><taglib-uri>productTracking.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/productTracking_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>ad.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/ad_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>cm.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/cm_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>ph.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/ph_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>ps.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/ps_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>pz.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/pz_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>tracking.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/tracking_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>dam.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/dam_taglib.jar</taglib-location></taglib><taglib>   <taglib-uri>vum.tld</taglib-uri>   <taglib-location>/WEB-INF/lib/vum_taglib.jar</taglib-location></taglib>

7. Add the following lines to the <ejb-ref> section:
8. <!-- This is used by the various <cm:> tags --><ejb-ref>  <description>     The ContentManager EJB for this webapp  </description>  <ejb-ref-name>ejb/ContentManager</ejb-ref-name>  <ejb-ref-type>Session</ejb-ref-type>  <home>com.bea.p13n.content.document.DocumentManagerHome</home>  <remote>com.bea.p13n.content.document.DocumentManager</remote></ejb-ref><!-- This is used by the ShowDocServlet --><ejb-ref>  <description>     The DocumentManager for this webapp  </description>  <ejb-ref-name>ejb/DocumentManager</ejb-ref-name>  <ejb-ref-type>Session</ejb-ref-type>  <home>com.bea.p13n.content.document.DocumentManagerHome</home>  <remote>com.bea.p13n.content.document.DocumentManager</remote></ejb-ref><!-- This is used by the Placeholder tag --><ejb-ref>  <description>     The PlaceholderService Session EJB for the placeholder tag.  </description>  <ejb-ref-name>ejb/PlaceholderService</ejb-ref-name>  <ejb-ref-type>Session</ejb-ref-type>  <home>com.bea.p13n.placeholder.PlaceholderServiceHome</home>  <remote>com.bea.p13n.placeholder.PlaceholderService</remote></ejb-ref><!-- This is used by the AdClickThruServlet and the adTarget tag--><ejb-ref>  <description>     The AdService for this webapp  </description>  <ejb-ref-name>ejb/AdService</ejb-ref-name>  <ejb-ref-type>Session</ejb-ref-type>  <home>com.bea.p13n.ad.AdServiceHome</home>  <remote>com.bea.p13n.ad.AdService</remote></ejb-ref><!-- This is used by the AdClickThruServlet --><ejb-ref>  <description>     The AdBucketService for this webapp  </description>  <ejb-ref-name>ejb/AdBucketService</ejb-ref-name>  <ejb-ref-type>Session</ejb-ref-type>  <home>com.bea.p13n.ad.AdBucketServiceHome</home>  <remote>com.bea.p13n.ad.AdBucketService</remote></ejb-ref><!-- This is used by the various <pz:> tags --><ejb-ref><description>     The EjbAdvisor for this webapp  </description>  <ejb-ref-name>ejb/EjbAdvisor</ejb-ref-name>  <ejb-ref-type>Session</ejb-ref-type>  <home>com.bea.p13n.advisor.EjbAdvisorHome</home>  <remote>com.bea.p13n.advisor.EjbAdvisor</remote></ejb-ref>

Phase 3: Modify Your weblogic.xml File

To modify the weblogic.xml file for your Web application, you can use either of two methods:

1. Replace the weblogic.xml file for your Web application with the weblogic.xml.stock version in the following directory:

BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\
WEB-INF

Then incorporate your previous changes into the newly copied file.

2. Copy and paste the following new code into the <ejb-reference-description> section of the weblogic.xml file for your Web application:
    <ejb-reference-description>        <ejb-ref-name>ejb/ContentManager</ejb-ref-name>        <jndi-name>${APPNAME}.BEA_personalization.DocumentManager</jndi-name> </ejb-reference-description> <ejb-reference-description> <ejb-ref-name>ejb/DocumentManager</ejb-ref-name> <jndi-name>${APPNAME}.BEA_personalization.DocumentManager</jndi-name>     </ejb-reference-description>    <ejb-reference-description>        <ejb-ref-name>ejb/PlaceholderService</ejb-ref-name>        <jndi-name>${APPNAME}.BEA_personalization.PlaceholderService</jndi-name> </ejb-reference-description> <ejb-reference-description> <ejb-ref-name>ejb/AdService</ejb-ref-name> <jndi-name>${APPNAME}.BEA_personalization.AdService</jndi-name>    </ejb-reference-description>    <ejb-reference-description>        <ejb-ref-name>ejb/AdBucketService</ejb-ref-name>        <jndi-name>${APPNAME}.BEA_personalization.AdBucketService</jndi-name> </ejb-reference-description> <ejb-reference-description> <ejb-ref-name>ejb/EjbAdvisor</ejb-ref-name> <jndi-name>${APPNAME}.BEA_personalization.EjbAdvisor</jndi-name>    </ejb-reference-description>

Performing Manual Steps for WebLogic Platform 7.0 SP4 Migration

This section describes the manual steps that you must perform to migrate your domain to WebLogic Platform 7.0 SP4:

1. Make sure that you have completed the prerequisite steps described in the following table.

If you are migrating a domain created with the following 7.0.x releases ...

Make sure that you have completed the manual steps required to migrate the domain to ...

WebLogic Platform 7.0

WebLogic Platform 7.0 SP1

WebLogic Platform 7.0 SP2, as described in Performing Manual Steps for WebLogic Platform 7.0 SP2 Migration.

WebLogic Platform 7.0 SP2

You do not have to complete any prerequisite manual steps. Proceed to step 2.

2. If you are migrating a domain based on the Platform Domain, WebLogic Workshop Domain, or WLP Domain, perform the steps in the appropriate section below:

No additional steps are required if you are migrating a domain based on one of following templates: BPM Domain, EAI Domain, WLI Domain, WLS Domain, WLS Examples, or WLS Petstore.

Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.

Platform Domain

To migrate a domain that is based on the Platform Domain template to WebLogic Platform 7.0 SP4, perform the following steps:

1. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\datasync to your datasync Web application directory, by default BEA_HOME\user_projects\domain\beaApps\portalApp\datasync.

2. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\tools
to your tools Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\tools.

3. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\toolSupport
to your toolSupport Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\toolSupport.

4. Copy all the .jar files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the BEA_HOME\user_projects\domain\beaApps\portalApp directory (by default) for your application.

5. If you have created a portal Web application in your domain, copy all the .jar files from the BEA_HOME\weblogic700\common\templates\webapps\portal\
baseportal\j2ee\WEB-INF\lib
directory to the WEB-INF\lib directory for each of your portal Web applications.

We strongly recommend that you run the Portal Consistency Checker after performing these migration steps to ensure all the necessary files have been copied. The Portal Consistency Checker is available on the dev2dev site at:

http://dev2dev.bea.com/codelibrary/code/portal_consistency_checker.jsp

WebLogic Workshop Domain

To migrate a domain that is based on the WebLogic Workshop Domain template to WebLogic Platform 7.0 SP4, update the value of MEM_ARGS in the startweblogic script for your domain. By default, the script is located in the following directory:

BEA_HOME\user_projects\domain

The following excerpt from the startWebLogic.cmd script (for Windows) shows the required updates in bold:

Before:

set MEM_ARGS=-Xms64m -Xmx128m

After:

set MEM_ARGS=%COMM_MEDIUM_MEM_ARGS%

WLP Domain

To migrate a domain that is based on the WLP Domain template, complete the procedure described in Platform Domain.

Performing Manual Steps for WebLogic Platform 7.0 SP5 Migration

This section describes the manual steps that you must perform to migrate your domain to WebLogic Platform 7.0 SP5:

1. Make sure that you have completed the prerequisite steps described in the following table.

If you are migrating a domain created with the following 7.0.x release ...

Make sure that you have completed the manual steps required to migrate the domain to ...

WebLogic Platform 7.0

WebLogic Platform 7.0 SP1

WebLogic Platform 7.0 SP2

WebLogic Platform 7.0 SP4, as described in Performing Manual Steps for WebLogic Platform 7.0 SP4 Migration

WebLogic Platform 7.0 SP4

You do not have to complete any prerequisite manual steps. Proceed to step 2.

2. If you are migrating a domain based on the WebLogic Workshop Domain or WLP Domain templates, perform the steps in the appropriate section below:

No additional steps are required if you are migrating a domain based on one of following templates: BPM Domain, EAI Domain, Platform Domain, WLI Domain, WLS Domain, WLS Examples, or WLS Petstore.

Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.

WebLogic Workshop Domain

Note: The steps described in this section are only required if you are using the WebLogic JRockit SDK. If you are using the Sun Java 2 SDK, no additional migration steps are required.

If you are using the WebLogic JRockit SDK, to migrate a domain that is based on the WebLogic Workshop Domain template to WebLogic Platform 7.0 SP5, update the value of JAVA_VM in the startweblogic script for your domain to remove the COMM_VM variable. By default, the script is located in the following directory:

BEA_HOME\user_projects\domain

The following excerpt from the startWebLogic.cmd script (for Windows) shows the required updates:

Before:

set JAVA_VM=%COMM_VM% %JAVA_DEBUG% %JAVA_PROFILE%

After:

set JAVA_VM=%JAVA_DEBUG% %JAVA_PROFILE%

WLP Domain

To migrate a domain that is based on the WLP Domain template to WebLogic Platform 7.0 SP5, perform the following steps:

1. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\datasync to your datasync Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\datasync.

2. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\tools
to your tools Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\tools.

3. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\toolSupport
to your toolSupport Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\toolSupport.

4. Copy all the .jar files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the BEA_HOME\user_projects\domain\beaApps\portalApp directory for your application.

5. If you have created a portal Web application in your domain, copy all the .jar files from the BEA_HOME\weblogic700\common\templates\webapps\portal\
baseportal\j2ee\WEB-INF\lib
directory to the WEB-INF\lib directory for each of your portal Web applications.

We strongly recommend that you run the Portal Consistency Checker after performing these migration steps to ensure all the necessary files have been copied. The Portal Consistency Checker is available on the dev2dev site at:

http://dev2dev.bea.com/codelibrary/code/portal_consistency_checker.jsp

Performing Manual Steps for WebLogic Platform 7.0 SP6 Migration

This section describes the manual steps that you must perform to migrate your domain to WebLogic Platform 7.0 SP6:

1. Make sure that you have completed the prerequisite steps described in the following table.

If you are migrating a domain created with the following 7.0.x release ...

Make sure that you have completed the manual steps required to migrate the domain to ...

WebLogic Platform 7.0

WebLogic Platform 7.0 SP1

WebLogic Platform 7.0 SP2

WebLogic Platform 7.0 SP4

WebLogic Platform 7.0 SP5, as described in Performing Manual Steps for WebLogic Platform 7.0 SP5 Migration

WebLogic Platform 7.0 SP5

You do not have to complete any prerequisite manual steps. Proceed to step 2.

2. If you are migrating a domain based on the WLP, BPM, EAI, or WLI Domain templates, perform the steps in the appropriate section below.

No additional steps are required if you are migrating a domain based on one of following templates: Platform Domain, WebLogic Workshop, WLS Domain, WLS Examples, or WLS Petstore.

Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.

WLP Domain

To migrate a domain that is based on the WLP Domain template to WebLogic Platform 7.0 SP6, perform the following steps:

1. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\datasync to your datasync Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\datasync.

2. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\tools
to your tools Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\tools.

3. Copy all files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal
\webapps\toolSupport
to your toolSupport Web application directory (by default): BEA_HOME\user_projects\domain\beaApps\portalApp\toolSupport.

4. Copy all the .jar files under BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\apps\jars to the BEA_HOME\user_projects\domain\beaApps\portalApp directory for your application.

5. If you have created a portal Web application in your domain, copy all the .jar files from the BEA_HOME\weblogic700\common\templates\webapps\portal\
baseportal\j2ee\WEB-INF\lib
directory to the WEB-INF\lib directory for each of your portal Web applications.

We strongly recommend that you run the Portal Consistency Checker after performing these migration steps to ensure all the necessary files have been copied. The Portal Consistency Checker is available on the dev2dev site at:

http://dev2dev.bea.com/codelibrary/code/portal_consistency_checker.jsp

BPM, EAI, and WLI Domains

To migrate a domain to WebLogic Platform 7.0 SP6 that is based on the BPM, EAI, or WLI Domain template, modify the domain fileRealm.properties file as follows:

1. Change to the top-level directory of the domain. For example:

prompt> cd BEA_HOME/user_projects/myWLIdomain

2. Bring the fileRealm.properties file into a text editor.

3. Change the value for the acl.shutdown.weblogic.admin property to Administrators as follows:

Before:

After:

Updating Scripts and Configuration Files on New

Note: This step is required only if you have installed WebLogic Platform in a directory other than the BEA_HOME directory. If you have upgraded an existing WebLogic Platform 7.0 installation, you can skip this step.

The domain startup scripts (such as startWebLogic) and configuration files (such as config.xml) define the full pathnames of files within the BEA_HOME directory. You need to search for and update these pathnames to reference the new location of the BEA_HOME directory. In addition, you must update any custom scripts, such as build scripts, that define the full pathnames of files within the BEA_HOME directory so that the pathnames reflect the new BEA_HOME location.

Note: Many startup scripts set environment variables in your current shell, including variables that reference your BEA_HOME directory. After updating the BEA_HOME references in script files, you should open a new shell to ensure that the latest environment settings are used.

Switching the Database Used by the Platform Domain

This section walks you through the process of switching the database used by a domain created from the Platform Domain template. You may want to switch databases, for example, if you want to replace the default database for WebLogic Platform, PointBase, with another database supported by WebLogic Platform, such as Oracle.

For information on switching the database used by WebLogic Portal or WebLogic Integration domains, refer to the following documentation:

• For WebLogic Portal domains, follow the procedures described in "Database Administration" in "System Administration" in the BEA WebLogic Portal Administration Guide at the following URL:
• For WebLogic Integration domains, use the Integration Database Wizard, or the wliconfig command, as described in "Customizing WebLogic Integration" in Starting, Stopping, and Customizing BEA WebLogic Integration at the following URL:

Before you switch from the default PointBase database to another supported database, you must configure that database. For configuration instructions, see the README.html file for your database in the following location:

BEA_HOME\weblogic700\portal\db\db_type\version\admin

Step 2: Edit db_settings.properties for Your Database Environment

In your domain directory, open the db_settings.properties file. For the database type you are using, replace the @...@ variables with actual values, and save the file.

We recommend that you set up two database user accounts (with separate usernames and passwords): one for accessing the database used by WebLogic Portal; the other, for accessing the database used by WebLogic Integration.

The following code sample shows the Oracle section of the db_settings.properties file before any modifications are made.

Listing 1 db_settings.properties File: Before Modifications

#------Oracle Thin Driver------------------------###@IF_USING_ORACLE_THIN@#database=ORACLE_THIN#db_version=817#jdbcdriver=oracle.jdbc.driver.OracleDriver#server=@ORACLE_NET_SERVICE_NAME@#port=@ORACLE_PORT@#dblogin=@ORACLE_USER@#dbpassword=@ORACLE_PASSWORD@#wlidblogin=@ORACLE_WLI_USER@#wlidbpassword=@ORACLE_WLI_PASSWORD@#connection=jdbc:oracle:thin:@@ORACLE_SERVER@:@ORACLE_PORT@:@ORACLE_SID@#@ENDIF_USING_ORACLE_THIN@

The following code sample shows the modified file.

Listing 2 db_settings.properties File: After Modifications

#------Oracle Thin Driver------------------------##database=ORACLE_THIN#db_version=817#jdbcdriver=oracle.jdbc.driver.OracleDriver#server=MY817SVC#port=1521#dblogin=my_portal_db_username#dbpassword=my_portal_db_password#wlidblogin=my_wli_db_username#wlidbpassword=my_wli_db_password#connection=jdbc:oracle:thin:@myhost:1521:MY817SID#@ENDIF_USING_ORACLE_THIN@

Note: Do not add or remove the # signs (indicating that a line is a comment) in this file, at this time. In Step 7: Edit db_settings.properties to Uncomment Your Database, you will add and remove # signs, as required, so that the new values take effect when you start the WebLogic Server.

The exact number of the db_version setting is important, because it controls which DDL is used. The following table shows the value you must specify for the db_version parameter for each type of database listed.

For the following database version ...

Use the following number as the value of db_version ...

DB2 7.2

7

Oracle 8.1.7

817

Oracle 9i

901

Oracle 9.2.0

920

PointBase 4.2

42

Microsoft SQL Server 2000

2000

Sybase 12.5

125

Note: Not all the databases listed in the previous table may be supported currently. For a list of currently supported databases, see "Supported Database Configurations" in Supported Configurations for WebLogic Platform 7.0 at the following URL:

Step 3: Edit setDBVars and setDBVarsExt for Your Database Environment

To edit setDBVars and setDBVarsExt for your database environment:

1. Go to the dbInfo directory in your domain directory. Then, go to the directory for the database you want to use: DB2, MSSQL, Oracle, PointBase, or Sybase.

2. Open the files in one of the following sets:

• On Windows: setDBVars.cmd and setDBVarsExt.cmd
• On UNIX: setDBVars and setDBVarsExt

3. In each file, set the environment variables, as appropriate for your database. For details, see "Environment Variables" in "WebLogic Integration Commands" in Starting, Stopping, and Customizing BEA WebLogic Integration at the following URL:
http://download.oracle.com/docs/cd/E13214_01/wli/docs70/config/keycmd.htm

Step 4: Start WebLogic Server

Before you can access the WebLogic Administration Console, you must start the WebLogic Server.

In your domain directory, start the WebLogic Server:

• On Windows: startWeblogic.cmd
• On UNIX: startWeblogic.sh

Note: If you want to use PointBase for your database, you do not need to perform any additional steps to create your database; the script will create it for you.

Step 5: Set up the Connection Pools and Realm in the WebLogic Administration Console

For this procedure, open the db_settings.properties file in your domain folder (which you updated in Step 2: Edit db_settings.properties for Your Database Environment), and copy values from this file into the WebLogic Administration Console.

1. With WebLogic Server running, go to the following URL in your browser to launch the WebLogic Administration Console: http://hostname:port/console.

For example, if you are working on the machine on which WebLogic Server is installed, go to http://localhost:7501/console.

3. In the Console, choose domain—>Services—>JDBC—>Connection Pools.

4. Click and edit commercePool by pasting values from the db_settings.properties file. For details, see Table  2.

5. Click Apply before clicking a hyperlinked field or moving to another secondary tab.

6. Click and edit dataSyncPool by pasting values from the db_settings.properties file. For details, see Table  2.

7. Click Apply before clicking a hyperlinked field or moving to another secondary tab.

8. Click and edit wliPool by pasting values from the db_settings.properties file. For details, see Table  2.

9. Click Apply before clicking a hyperlinked field or moving to another secondary tab.

Table 2 Connection Pool Values for Using Oracle or MS SQL Thin Drivers

Tab

Field

Value

General

URL

For the database type you are using, copy the value of connection in the db_settings.properties file.

Driver Classname

For the database type you are using, copy the value of jdbcdriver in the db_settings.properties file.

Properties (key=value)

Enter the list of properties passed to the JDBC Driver to use when creating physical database connections. The properties vary, depending on the database driver you are using. For example, when you are using an Oracle Thin driver, only the user key is required. When MS SQL is used, both user and server keys are required. To determine which properties to use, see the documentation for the driver you are using.

If you are specifying properties for commercePool or dataSyncPool, copy the value of dblogin in the db_settings.properties file for the database type you are using. For example, if you are using an Oracle Thin driver, specify user=my_portal_db_username.

If you are specifying properties for wliPool, copy the value of wlidb_login in the db_settings.properties file for the database type you are using. For example, if you are using an Oracle Thin driver, specify user=my_wli_db_username.

ACLName

Leave blank.

Click Change. You are prompted to enter and retype your database user password for the connection pool you are editing.

If you are specifying the password for commercePool or dataSyncPool, copy the value of dbpassword in the db_settings.properties file for the database type you are using.

If you are specifying the password for wliPool, copy the value of wlidbpassword in the db_settings.properties file for the database type you are using.

10. In the Console, go to domain_name—>Compatibility Security—>Realms—>wlcsRealm.

11. On the Database tab, enter the same Driver Classname and URL you entered in the previous steps, as described in Table  2. In the User Name field, copy the value of dblogin in the db_settings.properties file for the database type you are using.

12. Click Apply.

13. In the Password field, click Change, and enter and retype your database user password. This password should match the one you specified as the value of dbpassword in the db_settings.properties file.

14. Click Apply.

15. Click Continue.

16. On the Schema tab, in the Schema Properties (key=value) field, enter the same properties you entered in the previous steps, as described in the previous table.

17. Click Apply.

Step 6: Stop WebLogic Server

In your domain directory, stop WebLogic Server by running the appropriate script:

• On Windows: stopWeblogic.cmd
• On UNIX: stopWeblogic.sh

Step 7: Edit db_settings.properties to Uncomment Your Database

Edit db_settings.properties file to uncomment the values that you defined in Step 2: Edit db_settings.properties for Your Database Environment:

1. Open the db_settings.properties file.

2. Remove the # sign from the beginning of each line in which you specify properties for the database you are using.

3. Comment out the PointBase database settings (by including a # sign at the beginning of each line), and save the file.

Step 8: Run create_db

Run the create_db script in your domain folder to create and populate the database. Verify that the output written to create_db.log does not contain fatal errors.

Step 9: Restart WebLogic Server

In your domain directory, restart the WebLogic Server:

• On Windows: startWeblogic.cmd
• On UNIX: startWeblogic.sh

Step 10: Run sync

Run the sync command in your domain folder to update the server with the new database data.

Setup is now complete. You should now be able to start and run your Platform domain application against your database.

Step 11: Oracle Only - Rebuild Indexes

The create_db script places indexes for the WebLogic Portal tables in the WEBLOGIC_INDEX tablespace. If you are not using the default WEBLOGIC_INDEX tablespace, you must first edit rebuild_indexes.sql to reflect your tablespace name. To run the script to rebuild indexes, complete the following procedure:

1. In a command window, change directories to:

Here PORTAL_HOME is the pathname of the directory in which the WebLogic Portal software is installed (typically, in BEAHOME/weblogic700/portal).

2. Run the following command to start a SQL*Plus session:

• username is the name of the Oracle user account (WEBLOGIC by default)
• password is the password for the Oracle user account (WEBLOGIC by default)
• net_service_name is the name of the Net Service that you defined for the Oracle database.

3. Run the following command to rebuild indexes:

@rebuild_indexes.sql

Best Practices

This section provides tips, based on best practices, for installing WebLogic Platform, using the Configuration Wizard, and running the out-of-the-box examples:

Character Limit for the BEA Home Directory Name

It is recommended that you use 12 characters or fewer when naming your BEA Home directory. If you approach the maximum value of 12 characters, the CLASSPATH resolution may not be performed properly.

Naming the Installation Directory

It is recommended that you install WebLogic Platform in a directory with a name that contains no spaces. If the name of your installation directory contains spaces, you may have problems with the startup scripts for the samples and E-Business Control Center (EBCC).

WebLogic Portal Sample Data

As stated in Installing BEA WebLogic Platform (http://download.oracle.com/docs/cd/E13196_01/platform/docs70/install/index.html) WebLogic Portal sample data is installed when you install either the E-Business Control Center (EBCC) or the WebLogic Portal examples. However, before you can run the WebLogic Portal examples, you must have the WebLogic Portal server installed, as well.

Note: When you uninstall either the EBCC or the WebLogic Portal examples, the WebLogic Portal sample data is removed from your system.

Using the Platform Domain Template

When using the Platform Domain template to create a domain that supports all the WebLogic Platform components, keep the following guidelines in mind:

• When creating a Platform Domain Cluster, you must change the targets for b2bconsole.war from the Cluster to the Administration Server in the Administration Console.
• If you want to change the username and password after running the Configuration Wizard, you must manually update the sync.cmd or sync.sh.
• If you change your username and password using the Administration Console after running the Configuration Wizard to create your domain, you must make the same changes in the sync.cmd or sync.sh scripts found in BEA_HOME\user_projects\domain\beaApps\portalApp-project.

• Run sync.cmd or sync.sh before accessing the portalApp tools.
• Run the sync.cmd or sync.sh script after starting the server to load the run-time data required by the WebLogic Portal application deployed in the domain.

• The domain name is hardcoded as platformDomain in the following files and should not be modified:
• create_db.cmd
• create_db.sh
• create_wli.cmd
• create_wli.sh
• db_settings.properties

This setting of the domain name enables the WebLogic Integration create_db scripts to load the DDLs required for platformDomain. Do not change these values.

• Applications provided by BEA are stored in BEA_HOME\user_projects\domain\beaApps. However, any new application created using the WebLogic Workshop IDE is created in the BEA_HOME\user_projects\domain\applications directory.

Running the WebLogic Platform Sample Application

This section provides a list of best practices to follow when running the WebLogic Platform sample application that is shipped with WebLogic Platform. For specific instructions on running the sample, see Tour of the BEA WebLogic Platform Sample Application at the following URL:

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

• If, after installing WebLogic Platform, you switch databases by running the create_db script and following the WebLogic Integration database instructions, then you must edit your config.xml file and remove the E2EappView_connectionFactory Application Integration (AI) application.
• If you change the port for the server, then redeploy your application views. Change the port number for your e2eSetupAppView, and then run it to deploy on an active server.
• To access the Doc Portlet links for technical information when running the sample application, right-click the link and select Open In New Window. This method is recommended to prevent possible run-time errors that can be thrown when using the browser BACK button.
• To launch the "Take a Live Platform Tour" from the QuickStart page on Solaris, you must first copy the URL into the browser.
• To run the sample application, do not modify the configuration with new passwords, port numbers, and so on. Modifications to the packaged configuration are not supported.

Accessing the Documentation Using Netscape Browser 6.x

If you are viewing the WebLogic Platform online documentation using Netscape 6.x, you may notice some formatting or font discrepancies. For optimal viewing, we recommend you use Netscape 4.7 or 5.x.

Specifying JVM Options in WebLogic Platform 7.0 SP2 and Later

In SP2 and later service pack releases of WebLogic Platform 7.0, the commEnv script is provided to make it easier to specify options to be invoked with your JVM, such as -client.

The commEnv script defines the following environment variables that determine whether a client or server JVM should be run:

• COMM_CLIENT_VM
• COMM_SERVER_VM
• COMM_VM

In 7.0 SP4, SP5, and SP6, WebLogic Platform also includes the following commEnv environment variables for setting the standard memory arguments passed to the Java executable (that is, WebLogic JRockit JVM or the Sun JVM):

• COMM_SMALL_MEM_ARGS
• COMM_MEDIUM_MEM_ARGS
• COMM_LARGE_MEM_ARGS

The following table provides usage information for the commEnv environment variables. Which JVM options are valid and available to you depends on which platform you are using and which Java executable is being run.

Table 3 commEnv Environment Variables Usage Information

Use this environment
variable...

For the following type of application...

For example...

COMM_CLIENT_VM

Client (such as a GUI)

-hotspot or -client

COMM_SERVER_VM

Server (such as WebLogic Server)

-server or -jrockit

COMM_VM

Either client or server.

Recommended setting as long as your application does not require COMM_CLIENT_VM or COMM_SERVER_VM.

COMM_CLIENT_VM or COMM_SERVER_VM

COMM_SMALL_MEM_ARGS

Either client or server

WebLogic JRockit JVM:

-Xms64m -Xmx64m

Sun JVM:

-Xms64m -Xmx64m -XX:MaxPermSize=64m

COMM_MEDIUM_MEM_ARGS

Either client or server

WebLogic JRockit JVM:

-Xms128m -Xmx128m

Sun JVM:

-Xms128m -Xmx128m -XX:MaxPermSize=128m

COMM_LARGE_MEM_ARGS

Either client or server

WebLogic JRockit JVM:

-Xms256m -Xmx256m

Sun JVM:

-Xms256m -Xmx256m -XX:MaxPermSize=256m

Note: If you are using the WebLogic JRockit JVM with SP4 or SP5, or if you are using SP6 with scripts from a version of WebLogic Platform earlier than 7.0 SP3, make sure that you are using valid command-line options when starting WebLogic JRockit. If you use an invalid option, particularly any -XX option, WebLogic JRockit exits. (In previous versions, invalid options were ignored.) For more information, see "Using WebLogic JRockit 7.0 SP6 with Older WebLogic Platform Scripts" in the BEA WebLogic JRockit 7.0 SDK User Guide at the following URL:

The commEnv variables are used in both the WebLogic Platform samples and any custom domains created with the Configuration Wizard.

We recommend setting JVM options by using the environment variables provided by commEnv. See the script that is appropriate for your platform:

• On Windows: BEAHOME\weblogic700\common\bin\commEnv.cmd
• On UNIX: BEAHOME/weblogic700/common/bin/commEnv.sh

When you use commEnv instead of hard-coding your environment variables, you no longer need to specify the platform or the WebLogic JRockit SDK when you run your script.

Example Script

The following Windows script uses commEnv.cmd to run the WebLogic JRockit JVM:

SET WL_HOME=c:\bea\weblogic700SET JDK_HOME=c:\bea\jrockit70sp6_131_14CALL %WL_HOME%\common\bin\commEnv.cmd"%JDK_HOME%\bin\java" %COMM_SERVER_VM% myclass

In this example, WL_HOME represents the directory in which you installed WebLogic Platform.

Problems Fixed

This section provides solutions to problems found in WebLogic Platform. Specifically, it provides:

Each list of resolved problems may not be all-inclusive since there may have been other internal-only product changes in the service pack. If you experience product issues, please contact BEA Customer Support for assistance with diagnosing the root cause of your issue and finding an acceptable resolution.

To review the problems fixed in WebLogic Platform product components, see their respective release notes: WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal, WebLogic JRockit.

Fixes Delivered in SP1

The following table lists selected problems fixed in BEA WebLogic Platform 7.0 SP1, including a CR (Change Request) number for each problem. Some of these problems were originally documented in the BEA WebLogic Platform Release Notes for Release 7.0.

Table 4 Problems Fixed in BEA WebLogic Platform 7.0 SP1

Change Request Number

Description

CR078423

Startup scripts do not allow servers to start.

This problem was caused in some cases by the length of the input line. The length of the CLASSPATH has been reduced. Note that the definition of BEA_HOME should be limited to a maximum range of 10 to 12 characters.

CR078737

The Platform Domain template should support clustering, not just a single server.

CR080029

The QuickStart link to the WebLogic Integration tutorial targets the incorrect document.

CR080377

b2c throws run-time error on Netscape 4.7. Unable to locate portlet state for portlet checkout.

Fixes Delivered in SP2

The following table lists selected problems fixed in BEA WebLogic Platform 7.0 SP2, including a CR (Change Request) number for each problem. Many of these problems were originally documented in the Release Notes for BEA WebLogic Platform 7.0 or BEA WebLogic Platform 7.0 Service Pack 1.

Table 5 Problems Fixed in BEA WebLogic Platform 7.0 SP2

Change Request Number

Description

CR080423

In QuickStart, screen appears blank when Netscape browser is used on a UNIX platform. As a result, QuickStart is inaccessible when Netscape browser is launched.

CR080526

Explanation on e2eAppTools returns HTTP 404 error:

CR081153

Generic installer fails to detect lack of sufficient space for complete installation.

CR081523

On UNIX platforms other than Linux (that is, on AIX, HP-UX, or Solaris), you cannot install WebLogic Workshop Application View Control.

CR081842

When executing the stop command within a domain to stop the running server, an exception may be written to the weblogic.log file.

CR82012

WebservicesEJB.jsp does not compile in domains created using the Configuration Wizard that are based on the WLS Example domain template.

CR083994

startWebLogic.sh does not handle nopointbase argument.

CR083997

When a domain is generated by using one of several domain templates (for Platform, WLP, WLS, and so on) the Listen Address is not added, by default, to the config.xml file in BEA_HOME\user_projects\domain.

CR084109

WebLogic Platform clustered domain: exceptions are logged in Administration Server log file when Managed Servers are being shut down.

CR084155

QuickStart application is not displayed correctly on Red Hat Linux 7.2 platform.

CR084292

WLP Template:SSL information for Managed Server is not stored in the config.xml file on an Administration Server.

CR084464

Assertion exceptions in Configuration Wizard Platform Domain template.

CR084695

Problem with WebLogic Platform Sample Application on UNIX systems.

CR085203

SSL exception with RosettaNet2 in firewall configuration and IIS proxy.

CR085531

Update GPR to reflect WebLogic Workshop as a component in all eligible releases.

CR085583

Typical installation does not result in full installation.

CR087360

Portal EBCC component is not supported with JRockit 7.0 SP1 SDK on Windows.

CR087956

JRockit may deadlock or crash if SIGHUP is received during execution of the WebLogic Integration samples or the WebLogic Integration RosettaNet samples on Red Hat Linux Advanced Server 2.1 with JRockit 7.0 SP1 SDK.

CR090148

PointBase server dies unexpectedly during execution of WebLogic Integration Samples with PointBase on top of JRockit.

CR090186

WLS 7.0 SP1 - java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction

CR091228

Got NPE in firewall RN2.0 test.

CR091239

WLW 7.0 SP1 - Large number of transactions roll back when an event is run on an AppView Control

CR091702

Regression: Got core dump when running managed server on Solaris.

CR092483

Server startup/shutdown problems with JRockit for WLS SP2

CR092681

ORA-01591: lock held by in-doubt distributed transaction using Oracle Thin XA driver during BPM recovery testing

CR092703

Got NPE thrown by certicom in firewall RN2.0 test

CR092742

The RN11 workflow failed to complete in a cluster.

CR092851

Using the DTD part of the XML document, it is possible to cause the XML parser to consume 100% of the CPU or a lot of memory.

CR092895

Steps are needed for upgrading domains to use the new BPM features.

CR093003

Callback from async is not invoked

CR093007

Use aiimportexport script to import Application View gave exception

CR093116

CR093119

CR093127

Failed to deploy AppView to one of the managed servers in a cluster.

CR093195

XA failure in WLI recovery, when Oracle 9.2.0.1 Thin XA driver and 9.2.0.1 server were used.

CR093280

xmlx.jar is not updated when WebLogic Platform 7.0sp2 ja upgrade installer is run.

CR093281

Workflow will not be started by a post-XML event, if the organization ID is specified in Japanese.

CR093307

JRockit: AppView control callback from async is not invoked.

CR093382

Managed server fails to reboot using previous config file after admin server down.

CR093510

RN2Security sample hangs on Solaris with outOfMemory error

CR093663

Entity EJB with concurrency strategy of Exclusive is not locked across cluster.

CR093724

JVM crash (core dump) when kill (Control + c) the managed server (WLI-Other)

CR093753

Problem with accessing Repository with HTTP adapter.

CR093828

WLS 6.1 SP4 - a Web tier communicating with an EJB tier hangs when the EJB tier closes the ConnectionManager due to missed RJVM heartbeats

CR093929

One managed server fails to reboot using previous config file after admin server down.

CR094008

JVM failed to deploy AppView to one of several managed servers in a cluster.

CR095162

Fixes Delivered in SP4

The following table lists selected problems fixed in BEA WebLogic Platform 7.0 SP4, including a CR (Change Request) number for each problem. Many of these problems were originally documented in the Release Notes for BEA WebLogic Platform 7.0 or BEA WebLogic Platform 7.0 SP1 or SP2.

Table 6 Problems Fixed in BEA WebLogic Platform 7.0 SP4

Change Request Number

Description

CR094041

JTA and JMS migration sometimes fail as a result of a race condition.

CR094109

Failover functionality in Apache plugins does not work.

CR094722

socketWrite error on Administration Server in clusters while the Managed Servers are being booted.

CR099887

Smart Update does not work on HP-UX.

CR100933

JRockit 7.0 SP2 RP1 cannot recognize -XX:MaxNewSize option

CR101796

Platform template will generate problematic domain if the template is used in silent mode

Fix Delivered in SP5

The following table lists the problem fixed in BEA WebLogic Platform 7.0 SP5, including the CR (Change Request) number.

Table 7 Problems Fixed in BEA WebLogic Platform 7.0 SP5

Change Request Number

Description

CR120193

Warning message displayed when running SmartUpdate on Linux installers.

Fixes Delivered in SP6

The following table lists the problem fixed in BEA WebLogic Platform 7.0 SP6, including the CR (Change Request) number.

Table 8 Problems Fixed in BEA WebLogic Platform 7.0 SP6

Change Request Number

Description

CR173360

Configuration Wizard silent mode fails to target cgJMSServer in a cluster.

CR175635

WebLogic Server installation for HP-UX 11.0 on PA-RISC and Windows: Issue when creating a WebLogic Workshop domain.

CR177600

Edit required in commEnv file after Smart Update from WebLogic Platform 7.0 SP4 with WebLogic JRockit to 7.0 SP5 with Sun SDK.

CR194073

BAD_CERTIFICATE exception is generated during 2 way SSL

Known Limitations

This section describes limitations that have been identified in the current service pack of BEA WebLogic Platform. The following sections provide descriptions and, whenever possible, workarounds:

To review the known limitations in WebLogic Platform product components, see their respective release notes: WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogicPortal, WebLogic JRockit.

Tracked Problems

The following table presents a list of limitations that have been identified in this service pack. For each problem described, a CR (Change Request) number is specified. These numbers are used by BEA to track solutions to problems as they are being developed. If you need assistance in tracking unresolved problems, please contact BEA Customer Support and refer to the appropriate CR number.

For contact information, go to the following URL:

http://www.bea.com/support/contact_cs.shtml

Limitations on WebLogic JRockit SDK Support

The following lists the limitations on WebLogic JRockit 7.0 SP1/SP2/SP4/SP5/SP6 SDK support:

• The WebLogic JRockit SDK does not support JVMDI (the JVM debugging interface). Therefore, when you launch a WebLogic Workshop server, include the nodebug option on the startWebLogic.cmd or startWebLogic.sh command line. Your command line should look like one of the following:
• ./startWebLogic.sh nodebug
• startWebLogic nodebug

• The WebLogic Workshop IDE runs on Sun JRE 1.4.0, which is installed under BEA_HOME/weblogic700/workshop/jdk1.4. However, because the WebLogic JRockit SDK does not support JVMDI (the JVM debugging interface), the WebLogic Workshop IDE has not been tested to collect debugging information while WebLogic Workshop servers are running on the WebLogic JRockit SDK.

JVM Configurations

A problem has been identified with configuring the Java 2 SDK versions 1.3.1_06, 1.3.1_08, 1.3.1_10, and 1.3.1_14 to run the Java HotSpot server VM (-server option) on Windows. The workaround is to use the -hotspot option, which invokes the Java HotSpot client VM. For example, to invoke the HotSpot client to start your server, you add the following line to your start script(s):

set JAVA_VM=-hotspot

http://java.sun.com/products/hotspot

Performance Considerations

Relative performance of WebLogic Platform may vary, depending on your selection of SDK and the nature of your application. For proper configuration options, see one of the following:

• BEA WebLogic Server Performance and Tuning:
• BEA WebLogic JRockit 7.0 SDK Performance Tuning Guide:
• Appropriate Java SDK documentation

DB2 Considerations

• If you run the WebLogic Integration Sample with the DB2 database without setting the DB2_RR_TO_RS=ON flag (in the DB2 configuration file), then the Sample fails. Be sure to set this flag. For more information, see your DB2 documentation.
• The DB2 Type 2 driver, COM.ibm.db2.jdbc.app.DB2Driver, includes both application and network drivers. The URL for it is jdbc:db2:db-alias, where db-alias represents the name of the appropriate database instance.

If the Apache server hangs when you are trying to use the BEA Apache plugin mod_wl_20.so on an HP-UX platform, then you are probably using obsolete versions of ld and/or libdld.sl. Apache binaries require the B.11.32 (or higher) version of ld and libdld.sl.

To determine which version of ld is installed on your system, complete the following procedure:

1. Enter: ld -V

2. Enter: what /usr/lib/libdld.sl

The version numbers of ld and libdld.sl are displayed.

• If both ld and libdld.sl have the same version number and that number is 11.32 or higher, then you are using the appropriate versions and you can quit this procedure; you are ready to run the mod_wl_20.so plugin.
• If the version numbers for ld and libdld.sl do not match, or if the numbers match and that number is lower than 11.32, then you need to install an HP patch. For instructions, proceed to step 3.

3. Determine which patch you need for your system:

• For an HP-UX 11.00 platform you need PHSS_26559.
• For an HP-UX 11i (11.11) or higher platform, you need PHSS_26560.

4. Go to the appropriate IT Resource Center:

5. Under Maintenance/Support, click Individual Patches.

6. Scroll down to the following entry:

Retrieve a specific patch by entering the patch name

7. Enter the patch number in the input field.