Technical data

44 BEA WebLogic Integration Release Notes

53 CR082583

Problem

All out-of-the box domains shipped in WebLogic Integration 2.1 SP2 do not have the

B2B error queue configured. This causes the following warning to appear at regular

intervals, which can result in large log files:

####<Jul 17, 2002 5:02:44 PM PDT> <Warning> <EJB> <mymachine>

<The Message-Driven EJB: EBXMLErrorQListener is unable to

connect to the JMS destination: com.bea.b2b.ErrorQueue.

Platforms

All

Workaround

Add the B2B error queue definition to the config.xml file. Locate the

B2bOutboundQueue in your config.xml file:

<JMSQueue JNDIName="com.bea.b2b.OutboundQueue"

Name="B2bOutboundQueue"/>

Below this queue definition, add the B2B error queue definition as follows:

<JMSQueue JNDIName="com.bea.b2b.OutboundQueue"

Name="B2bOutboundQueue"/> <JMSQueue

JNDIName="com.bea.b2b.ErrorQueue" Name="B2bErrorQueue"/>

54 CR082585

Problem

The WebLogic Integration 2.1 SP2 upgrade installer overwrites the peers database user

schema and URL for the RosettaNet 2 Security sample. To use the RosettaNet 2 Security

sample, you must change at least one peer to use a different database user schema. After

performing an upgrade installation, the values of the URL and user-specified database

values in the

peer1 and peer2 directories reflect the default user schema and URL

used in the samples domain. The following files are overwritten in the

peer1 and

peer2 directories:

config.xml

setdbvars

setdbvarsext

Platforms

All

Workaround

After performing an upgrade installation but before running the migratedb script, edit

the database user schema and URL in the

peer1 and peer2 directories in the files listed

above. If you run the

migratedb script before editing the files, a database user schema

that was not intended for use will be migrated and the sample will not run properly.