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 |
67530 |
EMD generates incorrect business object attribute type. |
'Long Character' type in the PeopleTools, will now be translated to 'String' instead of 'Long'. |
73040 |
BiDi support for the ASI, 'SoftDeleteValue' needed. |
The fix has been done. BiDi support was added to SoftDeleteValue ASI and BiDi data can be added against the same. BiDi format can be defined in related BiDi Context field. |
|
73657 |
EMD throws error when providing more than one folder in a relative path against the 'BO Location' property |
This has now been fixed - relative path can contain more than one folder. With the fix the relative path can be any hierarchical structure relative to the module path and would accept a path separator specific for the platform - so for Windows, "\" and for Unix, "/" e.g. inbound\data\module would be a valid path on Windows. |
|
73738 |
Inbound CEI events would not correlate. |
Fixed this to add correlation information. |
|
74565/JR22878 |
Single-quotes with parameters in LogMessages properties is causing parameter substitution to fail. |
Single quotes have been removed for two message IDs 7401 and 7402. |
|
73860 |
EMD needs to provide more meaningful messages instead of providing just the base exception message. |
Besides the base exception message, the exception would include the message received from PeopleSoft message collection object. The exceptions shown on EMD panels would include the error message from PeopleSoft if the failure happens at the PeopleSoft end. The EMD will also log this information in the log files too. |
|
74075/JR22657 |
PSFT Adapter provides generic error message when the PeopleTools API 'Save' fails. |
When 'Save' call fails, the resource exception thrown will now contain the error message from the PeopleSoft message collection object. |
|
74324 |
BiDi parameters are not treated correctly for Inbound. |
Some BiDi parameters are not treated correctly for Inbound. This has been fixed now. |
|
72436 |
'setReauthSupported' in Managed Connection Factory does not work. |
This has been fixed. The type has been changed from 'boolean' to 'Boolean'. |
|
48839 |
When polling in UNORDERED delivery mode, if an error occurred, events delivered could show up as undelivered in the event table. |
Events are now cleaned up when delivered in this scenario. |
|
73563 |
Publishing business objects as byte arrays caused performance problems. |
Changed the byte array to HexBinary encoding. |
|
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. |
|
73738 |
Inbound CEI events would not correlat. |
Fixed this to add correlation information. |
|
73449 |
BiDi format for connection metadata was not handling an empty string correctly |
This has been fixed. |
|
73477 |
Enhance BiDi log/trace capabilities |
Tracing has been added for BiDi diagnostics. |
|
73566 |
Business Object BiDi format not working correctly. |
This has been fixed. |
|
73143 |
BiDi properties were not validated in EMD |
The BiDi properties are now validated in EMD. |
|
73023 |
The 'TurnBiDiOff' property in EMD was appearing in a confusing way |
This has been fixed. The default is "false" when BiDi in EMD is active. |
|
73295 |
Contextual LTR or RTL component of BiDi format is not passed from EMD 1st screen to 5th. |
This has been fixed. |
|
72745 |
Inconsistent time and date format between log and trace. |
The trace time format has been updated to match the log's format. |
|
67575 |
AccessControlException thrown when Java 2 security is turned on in the WPS. |
Changes have been made to ensure that AccessControlException is not thrown when Java 2 security is turned on |
|
67845 |
Default ManagedConnectionFactory credentials do not work properly.. |
Updated connection code to use credentials specified in the outbound properties when no authentication alias is configured |
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 it is 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 - CWYES_PeopleSoft.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.
Last modified: Dec 10, 2005