Technical data

28 BEA WebLogic Integration Release Notes
3 CR050226
Problem
Under the following conditions, WebLogic Integration can start the wrong workflow on
receipt of a business message:
The same endpoint URI is assigned for different business protocols or different versions
of the same business protocol.
The repository contains two collaboration agreements between the same trading
partners.
Those collaboration agreements define the same roles and parties, but are associated with
different business protocols (or different versions of the same business protocol).
Platforms
All
Workaround
Assign different endpoint URIs for each business protocol (or for each version of a
business protocol).
For example, if one collaboration agreement references RosettaNet 1.1 and the other
references RosettaNet 2.0 (through the trading partner delivery channels), you must
assign one endpoint URI for RosettaNet 1.1 and another for RosettaNet 2.0.
4 CR050432
Problem
In the Studio, run-time exceptions occur when variable names begin with numeric
characters.
Platforms
All
Workaround
Begin variable names with alphabetic characters.
5 CR051059
Problem
You cannot update the data for parties in a collaboration agreement in the WebLogic
Integration B2B Console.
Platforms
All
Workaround
If you create a party for a collaboration agreement, and subsequently want to modify any
of the attributes associated with it (such as trading partner name, party identifier, role
name, or delivery channel), you must delete the party, and then create a new one with the
desired attributes.