This document contain the following sections:
This Fix Pack contains fixes for the change requests listed in the table below
|
Adapter Version |
CR Number/APAR Number |
CR details |
Description of fix done |
|
6.0.0.1 |
48839 |
When polling, in UNORDERED delivery mode, if an error occurred, events
that had been delivered could show up as undelivered in the event table.
|
Events are now cleaned up when delivered in this scenario. |
|
6.0.0.1 |
49329 |
The discovery-service.xml file had references to ASI schema. |
All references to ASI schema are removed. |
|
6.0.0.1 |
72436 | setReauthSupported in ManagedConnectionFactory didn't work. | Changed the type from boolean to Boolean. |
|
6.0.0.1 |
72743 | Byte arrays for published business objects would show up in the log as one line per byte. | Hexbinary encoding helps
this a lot. We also recommend running production systems with log level WARNING, so
these messages will not appear at all in the log with that level.
|
|
6.0.0.1 |
72745 | Inconsistent time and date format in log and trace. |
Updated trace time format to match log. |
| 6.0.0.1 | 73023 |
The TurnBiDiOff property in EMD was appearing in a confusing way. |
This is now fixed. The default is "false" when BiDi in EMD is active. |
| 6.0.0.1 | 73024 |
The ESD MCF Skip Bidi property has no empty valid value, it only has two values either true or false.MCF BiDi properties should not be initialized. |
Added empty string as a valid value for the ESD MCF Skip Bidi property.MCF BiDi properties initialization has been removed. |
| 6.0.0.1 | 73100 | Retrieve operation could not be performed on a file with only read permissions. | This is now fixed. Contents can be retrieved from files with only read permissions. |
| 6.0.0.1 | 73143 |
BiDi properties were not validated in EMD. |
Now BiDi properties are validated in EMD. |
| 6.0.0.1 | 73295 | Contextual LTR or RTL component of BiDi format is not passed from EMD 1st screen to 5th. | This is now fixed. |
|
6.0.0.1 |
73425 | The FlatFile.xsd present in the CWYFF_FlatFile.rar file was causing NullPointerExceptions during runtime. | The FlatFile.xsd has been removed from the code line. If present, it should also be removed from the updated CWYFF_FlatFile.rar file after applying this Fix Pack. |
|
6.0.0.1 |
73449 |
BiDi format for connection metadata was not handling an empty string correctly. |
This case is now handled. |
|
6.0.0.1 |
73477 |
Enhance BiDi log/trace capabilities. |
Added tracing for BiDi diagnostics. |
|
6.0.0.1 |
73563 |
Publishing business objects as byte arrays caused performance problems. |
Changed the byte array to hexbinary encoding.
|
|
6.0.0.1 |
73566 |
BO BiDi format not working correctly. |
BO level BiDi format now works. |
|
6.0.0.1 |
73738 | Inbound CEI events would not correlate. |
Fixed this to add correlation information. |
To upgrade to the Fix Pack version 6.0.0.1, do the following:
v Open the Java Build Path for the SCA module and remove the Connector project selected on projects tab.
v Open the dependency editor and remove the connector project.
v Delete the connector project from workspace.
v Import the new rar file. Add any dependency files from EIS specific APIs as needed.
v Open Java build path for the SCA module and select the Connector project selected on projects tab.
v Open the dependency editor and add the connector project if its not already present and check “Deploy with Module”.
v Select "Update" for the corresponding application on the WPS Admin Console.
v Select "Single Module" with relative path as name of the rar file - CWYFF_FlatFile.rar.
v Click the “Browse” button on local file system to select the updated rar file that has the changes.
v Select the default values in the remaining steps and click ‘Finish’. This will ensure that existing configurations e.g. MCF, are not changed and jars will be merely updated.
Nov, 17, 2005
© 2005 IBM Corporation. Proprietary and Confidential. All Rights Reserved.