Technical data

42 BEA WebLogic Integration Release Notes
46 CR081732
Problem
Using WebLogic Server 6.1 SP3 with WebLogic Integration 2.1 SP2 and the Sybase
database, an exception similar to the following is thrown when starting the server:
SET CHAINED command not allowed within multi-statement
transaction
Platforms
All, with Sybase 11.9.2 database
Workaround
Use the following patch for WebLogic Server 6.1 SP3: CR081732_610sp3.jar.
To obtain this patch, contact BEA Customer Support. To apply this patch, add the path
of the JAR file to the beginning of the classpath in
$WLI_HOME/setenv.sh as
follows:
WLICOMMONCP=../CR081732_610sp3.jar:$WLI_LIB/wlicommon.jar
47 CR081833
Problem
The wliconfig and createdb scripts behave differently in detecting changes to the
setenv script. The Configure shortcut on the WebLogic Integration menu uses
wliconfig.jar, which does not detect the changes in your setenv script. If you are
going to use the Oracle9i thin driver or you need to detect changes in your
setenv
script, you must run the createdb script from the command line.
Platforms
Windows
Workaround
Run the createdb script from the command line to ensure that changes to the setenv
script are detected.
48 CR081880
Problem
If a dash is used in a trading partner name, WebLogic Integration - Business Connect
converts the dash to the characters %2d% in the exported file name. This results in an
ebXML import error with an exception message similar to the following:
Exception:SAX Exceptioncom.bea.b2b.B2BException:
SAX Exception at
com.bea.b2b.bulkloader.BulkLoader.processDataFile
(BulkLoader.java:267)
Platforms
All
Workaround
Do not use dashes in the trading partner name. If dashes are required, you must manually
remove the resulting %2d% characters from any filenames before importing the files.