Technical data

Best Practices
BEA WebLogic Integration Release Notes 13
Oracle 9i Driver Setup for RosettaNet 2 Security Sample
If you experience failures when running the RosettaNet 2 Security sample on Solaris
systems using the Oracle 9i thin driver, ensure that the driver has been properly set up.
Unlike the other samples which use the
WLICP and WLISERVERCP values specified in
the
setenv script, the RosettaNet 2 Security sample refers to its own setup. Add the
Oracle 9i thin driver to
START_WL_CLASSPATH in the startWeblogic script for both
the peer1 and peer2 domains. This issue was originally reported as CR081061.
Using the Proper JDK
Ensure that you are using JDK version 1.3.1. On a Windows NT or Windows 2000
machine, WebLogic Integration installation fails at the Choose Install Set window if
you are using a version of the JDK that is earlier than 1.3.x.
Note: JDK 1.3.1 is shipped with WebLogic Server 6.1, so it should already be
installed on your system.
If you have not installed the JDK on a new Windows NT or Windows 2000 system,
then the installer fails when the Choose Install Set window is displayed, instead of
giving you the option of selecting or creating a
BEA_HOME directory.
Add
BEA_HOME\jdk131\bin to the Windows PATH environment variable. Install JDK
1.3.1 on the target machine and start the installation again.
This issue was originally reported as CR065631.
Support for Null Variables
WebLogic Integration 2.1 SP2 supports null values in variables through the
wli.bpm.server.evaluator.supportsNull option in the startWebLogic script.
When this option is set to
true, all variables are initialized to a null value. When this
option is set to
false, all variables are initialized to their default values. The default
setting for this option is
false.
For details about this option, see Starting, Stopping, and Customizing BEA WebLogic
Integration.