bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
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:
http://www.oracle.com/technology/documentation/index.html
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:
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:
For more information, see "What's New in WebLogic Server 7.0 SP6?" in the WebLogic Server Release Notes at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs70/notes/new.html
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:
http://download.oracle.com/docs/cd/E13196_01/platform/docs70/interm/whatsnew.html
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:
http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs70/70_over/install_info.html
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:
These installation instructions are now 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/install_info.html
Using WebLogic Platform with the WebLogic JRockit SDK
Please review the following usage notes pertaining to the WebLogic JRockit SDK:
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).
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:
http://download.oracle.com/docs/cd/E13196_01/platform/docs70/install/update.html
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:
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.
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:
The following table defines the command-line arguments.
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.
What Happens During an Upgrade?
When you specify upgrade, the default migration mode, the script performs the following actions:
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.
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.
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.
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:
To undo the changes made to mydomain during the migration process, run the script appropriate for your operating system:
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.
For a domain that is based on the BPM Domain template, perform the following steps:
BEA_HOME\user_projects\domain\dbInfo\pointbase
The following sample excerpt from the setDBVars.cmd script (Windows) shows the required updates in bold:
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;
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;
For a domain that is based on the EAI Domain template, see the procedure described in BPM Domain.
For a domain that is based on the Platform Domain template, perform the following steps:
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.
catalog\category_add_remove_items.jsp
catalog\item_property_edit.jsp
catalog\item_property_edit_mr.jsp
catalog\item_property_edit_mu.jsp
catalog\item_property_edit_sr.jsp
catalog\item_property_edit_su.jsp
catalog\item_search.jsp
usermgmt\groupuser_property_edit_mr.jsp
usermgmt\groupuser_property_edit_mu.jsp
usermgmt\groupuser_property_edit_sr.jsp
usermgmt\groupuser_property_edit_su.jsp
usermgmt\group_add_remove_users.jsp
usermgmt\group_edit.jsp
usermgmt\group_scope_property.jsp
usermgmt\user_create.jsp
usermgmt\user_edit_info.jsp
usermgmt\user_scope_property.jsp
edit_titlebar.properties
error\configurationerror.properties
error\footer.inc
error\header.inc
error\header.properties
error\missingformfield.properties
error\parameters.properties
error\pipeline.properties
error\request.properties
error\runtimeerror.properties
hnav_bar.properties
maximize_titlebar.properties
minimize_titlebar.properties
normal_titlebar.properties
security\help.properties
security\meta.inc
vnav_bar.properties
edit_titlebar.inc
error\configurationerror.jsp
error\error.jsp
error\missingformfield.jsp
error\parameters.jsp
error\pipeline.jsp
error\request.jsp
error\runtimeerror.jsp
error\sessiontimeout.jsp
error\sessiontimeout.properties
floated_portlet.jsp
hnav_bar.jsp
maximize_titlebar.inc
minimize_titlebar.inc
normal_titlebar.inc
security\help.jsp
security\login_header.inc
security\need_group.jsp
security\new_user.jsp
security\set_password.jsp
tools\header.jsp
tools\header.properties
tools\portal_prefs.jsp
vnav_bar.jsp
ent_taglib.jar
es_taglib.jar
i18n_taglib.jar
lic_taglib.jar
p13n_servlet.jar
portal_servlet.jar
portal_taglib.jar
portlet_taglib.jar
ren_taglib.jar
res_taglib.jar
um_taglib.jar
util_taglib.jar
visitor_taglib.jar
webflow_servlet.jar
webflow_taglib.jar
weblogic-tags.jar
For a domain that is based on the WebLogic Workshop Domain template, perform the following steps:
BEA_HOME\user_projects\domain
The following sample excerpt from the startWebLogic.cmd script (Windows) shows the required updates in bold:
set PB_CLASSPATH=
%POINTBASEDIR%\eval\pointbase\lib\pbserver42ECF172.jar;
%POINTBASEDIR%\eval\pointbase\lib\pbclient42ECF172.jar
set PB_CLASSPATH=.\;
%POINTBASEDIR%\eval\pointbase\lib\pbserver42ECF183.jar;
%POINTBASEDIR%\eval\pointbase\lib\pbclient42ECF183.jar
setWorkshopEnv.cmd
setWorkshopEnv.sh
startPointBaseConsole.cmd
startPointBaseConsole.sh
URLs.dat
For a domain that is based on the WLI Domain template, perform the following steps:
BEA_HOME\user_projects\domain\dbInfo\pointbase
The following sample excerpt from the setDBVars.cmd script (Windows) shows the required updates in bold:
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%
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%
To migrate a domain that is based on the WLP Domain template, complete the procedure described in Platform Domain.
For a domain that is based on the WLS Domain template, you do not need to add or modify existing scripts or files.
For a domain that is based on the WLS Examples domain template, perform the following steps:
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:
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
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
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:
set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%POINTBASE_HOME%\lib\
pbserver42ECF172.jar;%POINTBASE_HOME%\lib\
pbclient42ECF172.jar;%SERVER_CLASSES%;%COMMON_CLASSES%
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:
Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.
To migrate a domain that is based on the BPM template to WebLogic Platform 7.0 SP2, complete the following steps:
Note: The following instructions apply to both a single-server or cluster domain configuration, except where indicated.
<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>
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.
Note: This example shows a cluster system (mycluster) with one administration server (myserver) and two managed servers (c1, c2).
<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>
<JMSQueue Name="WLI_BPM_FP-c1"
JNDIName="com.bea.wli.bpm.FilePluginQueue-c1"
StoreEnabled="true"
Template="WLI_JMSTemplate-c1"/>
To migrate a domain that is based on the EAI Domain template, complete the procedure described in BPM 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:
To migrate a domain that is based on the WLI Domain template, complete the procedure described in BPM 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:
Note: Be careful not to overwrite any files that you have customized.
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:
<!-- 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>
<!-- 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>
<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>
<!-- 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:
<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:
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 SP2, as described in Performing Manual Steps for WebLogic Platform 7.0 SP2 Migration. |
|
You do not have to complete any prerequisite manual steps. Proceed to step 2. |
Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.
To migrate a domain that is based on the Platform Domain template to WebLogic Platform 7.0 SP4, perform the following steps:
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
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:
set MEM_ARGS=-Xms64m -Xmx128m
set MEM_ARGS=%COMM_MEDIUM_MEM_ARGS%
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:
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 SP4, as described in Performing Manual Steps for WebLogic Platform 7.0 SP4 Migration |
|
You do not have to complete any prerequisite manual steps. Proceed to step 2. |
Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.
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:
set JAVA_VM=%COMM_VM% %JAVA_DEBUG% %JAVA_PROFILE%
set JAVA_VM=%JAVA_DEBUG% %JAVA_PROFILE%
To migrate a domain that is based on the WLP Domain template to WebLogic Platform 7.0 SP5, perform the following steps:
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:
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 SP5, as described in Performing Manual Steps for WebLogic Platform 7.0 SP5 Migration |
|
You do not have to complete any prerequisite manual steps. Proceed to step 2. |
Note: Before adding or modifying any files, as described in the following sections, it is recommended that you back up the original files.
To migrate a domain that is based on the WLP Domain template to WebLogic Platform 7.0 SP6, perform the following steps:
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
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:
Updating Scripts and Configuration Files on New
(Not Upgraded) Installations
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:
Step 1: Configure Your Database
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.
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:
http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs70/70_over/supported_db.html
Step 3: Edit setDBVars and setDBVarsExt for Your Database Environment
To edit setDBVars and setDBVarsExt for your database environment:
http://download.oracle.com/docs/cd/E13214_01/wli/docs70/config/keycmd.htm
Before you can access the WebLogic Administration Console, you must start the WebLogic Server.
In your domain directory, start the WebLogic Server:
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.
In your domain directory, stop WebLogic Server by running the appropriate script:
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:
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:
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:
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).
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:
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 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.
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.
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
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:
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):
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.
Recommended setting as long as your application does not require COMM_CLIENT_VM or COMM_SERVER_VM. |
||
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:
http://download.oracle.com/docs/cd/E13188_01/jrockit/docs70/relnotes/relnotes.html
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:
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.
The following Windows script uses commEnv.cmd to run the WebLogic JRockit JVM:
SET WL_HOME=c:\bea\weblogic700
SET JDK_HOME=c:\bea\jrockit70sp6_131_14
CALL %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.
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.
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.
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.
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.
The following table lists the problem fixed in BEA WebLogic Platform 7.0 SP5, including the CR (Change Request) number.
Warning message displayed when running SmartUpdate on Linux installers. |
The following table lists the problem fixed in BEA WebLogic Platform 7.0 SP6, including the CR (Change Request) number.
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.
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
When WebLogic Platform is uninstalled, the hidden .Workshop file is not deleted. The .Workshop file contains user-specific configuration parameters for the WebLogic Workshop visual development environment. As a result, after reinstallation, attempts to invoke WebLogic Workshop may result in errors because the tool is referencing an obsolete configuration information within this file. For more information on the .Workshop file, refer to the following URL: http://download.oracle.com/docs/cd/E13226_01/workshop/docs70/help/index.html |
||
Delete the hidden .Workshop file before reinstalling WebLogic Workshop. The .Workshop file is located in the user's home directory. On Windows platforms, the user's home directory is indicated by the %USERPROFILE% environment variable. On UNIX and Linux platforms, the .Workshop file is located in the ~ (tilde) directory (sometimes also represented in the environment by $HOME). |
||
The PointBase server does not automatically terminate when WebLogic Portal servers are stopped using Ctrl-C. |
||
When you stop a WebLogic Portal server by pressing Ctrl-C instead of running a stop script or closing the command window (by clicking the close icon), the PointBase server continues to run in the background. |
||
Stop the server by running a stop script or closing the command window (by clicking the Close icon). If you stop the server by pressing Ctrl-C to close the command window, stop the PointBase server by stopping the background java.exe process. |
||
No executable permission for startWeblogic file under user domains on Solaris |
||
After a user domain is created using a BPM Domain, EAI Domain, and WLI Domain template, some files under user_domain (such as wliconfig and startWeblogic) do not have execute permision. |
||
Before trying to execute a script within the domain, make sure the script has execute permissions. If it does not, enable execution permissions using the chmod command. For example, to enable execution permissions for the startWebLogic.sh script, enter the following command: |
||
If a PointBase database is running on a Solaris platform as a result of executing the wliconfig command and you attempt to re-execute the wliconfig command, the command will not complete. |
||
You can shut down the PointBase server before re-executing the wliconfig command to avoid this condition. However, please note that you cannot modify existing parameters for a previously selected database type using the wliconfig command. |
||
WebLogic Integration does not support some options that are selectable from the Configuration Wizard. |
||
The BPM Domain, EAI Domain, and WLI Domain templates support only two of the four Configuration Wizard server types. You must select one of the following server types: The Managed Server(s) or Managed Server options result in an invalid configuration for the Administration Server. |
||
When the BPM Domain, EAI Domain, and WLI Domain templates are used, you must select one of the following server types: |
||
Switch Database configuration option to the wliconfig command fails the second time if it is issued for the same database. |
||
By design, you cannot modify existing parameters for a previously selected database type using the wliconfig command. For example, if you have selected Oracle as the database type, you cannot use the wliconfig command to change parameters for your Oracle database. You can, however, use the command to switch to another database type. |
||
Edit the setDBVars and setDBVarsExt files to set or change the database connection parameters. The setDBVars and setDBVarsExt files are located in the following locations: In the above pathnames, SAMPLES_HOME is the samples installation directory and database_type is the type of database to which you are connecting. For more information about the setDBVars and setDBVarsExt files, see "WebLogic Integration Commands" in Starting, Stopping, and Customizing WebLogic Integration at the following URL: http://download.oracle.com/docs/cd/E13214_01/wli/docs70/config/keycmd.htm |
||
Platform Domain template icon is missing in the Configuration Wizard. |
||
If you uninstall the WebLogic Platform sample application (Platform Tour), the Platform Domain template will no longer be available through the Configuration Wizard. |
||
Make sure the WebLogic Platform sample application (Platform Tour) is installed. The Platform Domain template also requires: |
||
User needs indication that PointBase connection is not closed. |
||
Because the PointBase command window is no longer visible, the user does not have an indication that PointBase is still running. The PointBase connection is not terminated immediately when a user stops a server. If the user attempts to restart the server on PointBase before the PointBase connection closes, the user receives an error message saying that it is not possible to create a database connection. |
||
Be aware that terminating the PointBase connection can take up to 4-5 minutes to close. If you receive an error message when attempting to restart the server, wait a few minutes and then try again. |
||
java.security.PrivilegedActionException when modifying SecurityConfiguration credential. |
||
If you modify the SecurityConfiguration element in the config.xml file and subsequently attempt to start the server, a java.security.PrivilegedActionException is logged. |
||
Shut down the server and delete the _ServletContextidnameDbmsEvent*****.xml and _ServletContextidnameDbmsEvent*****_temp files from e2eDomain. Then restart the server. |
||
Application View E2EAppView.sav fails to deploy when server is started on another port. |
||
The e2eAppView is tightly coupled with port 7501. The port number is defined in the e2eAppViewDeployer.java source file which is used, at run-time, while the e2eAppView is being deployed. |
||
To deploy the application view on port other than 7501, you must change all port number references from 7501 to the new port number in e2eSetupAppView.cmd or e2eSetupAppView.sh, and in the SetSampleData script that is called from the e2eSetupAppView script. |
||
PointBase does not shut down when stop scripts are used in domains created with Configuration Wizard and WLI templates. |
||
A stopWeblogic script populated in a domain that was created using the Configuration Wizard and WLI templates does not shut down PointBase. |
||
When the Configuration Wizard is run as part of the installation process, only a few user domain shortcuts are created on the Start Menu, depending on the order of the domains being created. |
||
Initiate the Configuration Wizard outside the installation process and create your user domains. This problem does not occur when you create user domains by launching the Configuration Wizard independently of the installation process. |
||
If you run QuickStart at the end of the Solaris installation, QuickStart launches and the installation program ends, but no shell remains running. Because there is no shell running to receive output from a server started through QuickStart, when you click on a link, you cannot tell if/when the server has started successfully. Most of the links on the QuickStart page start up a separate browser for an application when the server has finished booting. However, if you click on the Portal Example Server, you must click on a second link, Start the Portal Example, to run the example. Because you cannot easily see when the server has finished booting, it is difficult to know when to click on Start the Portal Example link to run the example. |
||
Launch QuickStart from the quickstart.sh script found in the BEA_HOME\weblogic700\common\bin directory. You can also check the corresponding weblogic.log file to see if the server has booted. For example, the weblogic.log file for Portal Example Server is located in BEA_HOME\weblogic700\samples\portal\sampleportalDomain\logs. |
||
While the upgrade installer is being used, an error message similar to the following may appear in the log file: ####<Jul 17, 2002 11:30:49 AM MDT> <Error> <Connector> <joe-2k> <e2eServer> <Thread-7> <kernel identity> <> <190004> <ManagedConnectionFactory not found for jndiName com.bea.wlai.connectionFactories.E2EAppView.sav_connectionFactoryInstance.> |
||
This error message does not affect the functionality of the product; it can be ignored. The display of the error message is caused by the deployment sequence of the code; it does not have any negative impact. |
||
If, after launching QuickStart on a UNIX platform (Solaris and HP-UX only), you select a link, a dialog box might appear prompting you to choose a Web browser. Even if you select the correct Netscape browser, QuickStart may fail to start the application. |
||
Terminate QuickStart, unset the LANG environment variable (manually or by using a wrapper function), and restart the QuickStart application. |
||
ArrayIndexOutOfBoundsException occurs intermittently when wliconfig.cmd is being used to create a database. |
||
Occasionally, the following error message is displayed when running the wliconfig script: Exception occurred during event dispatching: java.lang.ArrayIndexOutOfBoundsException: No such child: 0 This exception is harmless; a database of the selected type is created without problems. |
||
This error message does not affect the functionality of the product; it can be ignored. |
||
Running JRockit 7.0 SP1 SDK with -Xthinthreads is not supported. |
||
JRockit 7.0 SP1 does not support the use of the -Xthinthreads option with J2SE 1.3.1. Therefore this option is not available when you are running WebLogic Platform 7.0 SP1. |
||
In the WLI 7.0 SP2 Samples domain, port number "7001" is hard-coded. |
||
The port number 7001 is popular: it is used in WLW and WLS samples, as well as in the WLI Samples domain. Users should keep in mind that this number is hard-coded in multiple components. |
||
If you are having trouble, consider the possibility that the same port is being used by other users on the same machine. |
||
Username containing a comma does not work in compatibility mode security realms. |
||
If you use the Configuration Wizard or the WebLogic Server Administration Console to create a username that contains a comma, the username will not exist in a domain that has been configured to use Compatibility security. |
||
There is no workaround. Usernames defined in a security realm in a domain that has been configured to use Compatibility security cannot contain a comma. |
||
There are issues with using Smart Update with a proxy. During the Smart Update process, the hard-coded proxy settings are not carried over or recognized. |
||
Applications deployed in a WebLogic Workshop domain can only reference the log4j.jar file shipped with WebLogic Workshop. |
||
Applications that are deployed in a WebLogic Workshop domain can only reference the log4j.jar file shipped with WebLogic Workshop.WebLogic Workshop uses log4j for debugging, and loads its installed version when the server is started. Applications that reference a different log4j.jar file will fail at deployment time. |
||
Oracle 10g driver - setString() using multibyte character set with Japanese characters fails. |
||
The Oracle 10g GA driver has a known issue: When you are using the multibyte character set with Japanese characters, a call to the setString() method fails. A patch to the Oracle 10g GA driver is required (Oracle TAR 3584729.994, Oracle Bug3437365). |
||
WebLogic Platform 7.0 SP6 is certified with the Oracle10g driver that is bundled with the kit and includes this patch. If you are using the Oracle 10g GA driver, you are strongly encouraged to obtain the related patch from Oracle. |
||
WebLogic Workshop does not start appropriately on the Windows 2003 platform. When invoked, the initial screen opens and then closes, and the file javaw.exe stays running in the Task Manager. |
||
WebLogic Server jDriver problems using the AL32UTF8 character set with Oracle 9.2. |
||
The WebLogic Server jDriver does not function properly with Oracle 9.2 when using the AL32UTF8 character set. |
||
A software patch is available. Please contact your customer service representative to obtain a copy of the patch. |
||
The batch value cannot exceed 16383 when using the Oracle Thin Driver 10g. |
||
Ensure that the batch size does not exceed 16383. Alternatively, you can use the Oracle 9.2.0 driver. |
||
Server running WebLogic Platform sample generates exceptions after rollback from SP5 to SP4. |
||
If you complete the following procedure, the WebLogic Platform sample application runs, but generates exceptions. |
||
To avoid causing an exception when you start the WebLogic Platform sample application after performing a rollback from 7.0 SP5 to 7.0 SP4, after the rollback procedure remove the following files from the e2eDomain folder. (This folder is located in the WL_HOME/samples/platform directory.) If you remove these files before starting the WebLogic Platform sample application, no exception is thrown. |
||
When you use the stopWeblogic script to stop a server that is running in a domain that has been upgraded to 7.0 SP6, the server fails to stop and the following message is displayed: Server "myserver" failed to shutdown successfully ... This problem occurs in domains based on the BPM, EAI, and WLI templates. |
||
After you 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 so that the value of the acl.shutdown.weblogic.admin property is set to Administrators. For example: |
||
JSP compilation fails on solaris due to use of space in webapp name |
||
Including a space character in the name of a Web application causes the compilation of the application's associated JSP files to fail. This problem occurs in WLI domains. |
||
None. The name of a Web application created in a WLI domain cannot contain a space character. |
||
Cannot start WebLogic Server from WebLogic Workshop in the samples domain |
||
If you try to start WebLogic Server from the WebLogic Workshop IDE to run the HelloWorld.jws sample Web service, WebLogic Server fails to start. This problem happens when attempting to start WebLogic Server from the IDE to run any of the sample applications in WL_HOME/samples/workshop directory. |
||
After you click the Start button to run an application from the Workshop IDE, and click Ok to start an instance of WebLogic Server, enter a valid username and password in the command window in which WebLogic Server is started. |
||
Screens in the WebLogic Platform 7.0 SP6 upgrade installer for Windows have the wrong label. |
||
Some of the screens in the package upgrade installer for WebLogic Platform 7.0 SP6 contain the label "WebLogic Server 7.0 SP6" instead of "WebLogic Platform 7.0 SP6." This occurs in the upgrade installer when run in either graphical mode or console mode. |
||
None. These incorrect labels have no effect on the ability of the package upgrade installer to upgrade the entire set of WebLogic Platform components. You may use this installer to upgrade all WebLogic Platform components, as appropriate, or WebLogic Server only. |
Limitations on WebLogic JRockit SDK Support
The following lists the limitations on WebLogic JRockit 7.0 SP1/SP2/SP4/SP5/SP6 SDK support:
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
For more information about HotSpot, go the following URL:
http://java.sun.com/products/hotspot
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:
Considerations About Apache Version 2.0.4.3
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:
Considerations About Apache Versions Prior to 2.0.48
If your configuration includes an Apache Web server version prior to 2.0.48, keep in mind the following restrictions:
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |