The patch note contains the following sections:
This patch contains the following revisions since the last maintenance
release:
|
Available as of
Version |
APAR/CR Number |
Feature |
Description |
|
1.0.3 |
CR 34025/CR 34612 |
ReturnStatus Descriptor is
populated with wrong message. During polling multiple commits to the DB are done to update the
status of events in the event and archive tables as soon as possible. This is
required because some users filter events in the event table based on status.
This could be a performance issue for some users. |
The ReturnStatusDescriptor is populated
with wrong error message on a retrieve failure. The error says that the Child
Object doesnt exist in the database when the actual reason is that the Parent
Object doesnot exist in the database. The solution is no make the multiple commits configurable. A new connector
specific property SelectiveCommitForPoll has been introduced. If its value is true, then there is only
one commit - after an event has been processed. If its value is false then
the behaviour is the same as before – commits
to the DB will be done at each stage of event processing. The default value
for the property is false. |
|
1.0.2 |
JR
19645 CR
33394/ CR
33565 |
Column
EVENT_ID is hardcoded when using dynamic
query for polling. Problem
with setting foreign keys on a parent BO |
When
determining the type of the event_id
field, the EVENT_ID column was hardcoded,
and caused failure for dynamic queries. This has been fixed. When
setting foreign keys on a parent BO, if one of the single cardinality
child BOs was missing, the foreign keys
for all preceeding single cardinality
child BOs, were being overwritten by CxIgnore. This has been fixed to populate the forign keys appropriately. |
|
1.0.1 |
JR 19459 CR 32620 CR 33052 |
Failure updating a child BO with integer key value, that has leading zero. FAIL is not returned on delete if an integrity constraint existed. |
When the
retrieved BO and BO to be updated are compared, the string values of all key
attributes were being compared, so leading zeros resulted in a failure of the
comparison. Now the string value is converted to the appropriate type and
then compared, so that the problem is resolved. |
Add, replace, or remove the following files and directories as indicated (Note that these are rolled up in the patch you downloaded):
|
For Connector Version |
Platform |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
|
1.0.3 |
WIN & UNIX |
Replace the file |
%CROSSWORLDS%\connectors\ManugisticsAdapter\BIA_Manugistics.jar |
Configure the following for the patch to work:
|
Connector |
Platform |
Add / Remove |
Property/Legal values (Case-Sensitive) |
|
- |
- |
- |
- |
© 2004 IBM. Proprietary and Confidential. All Rights Reserved.