| This table lists the enhancements and fixes in fix pack version 6.1.0.4. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 99998 | | Make adapter 6.1 comply with the new WPS v7.0 SDO implementation. |
| Symptom: Currently the Adapter 6.1 version only supports EMF, and doesn't support XCI. |
| Resolution: A fix has been delivered to make Adapter 6.1 comply with the new WPS v7.0 SDO implementation. |
|
| 2 | 93528 | JR34574 | When two different business objects have the same name but different namespaces, inbound/outbound operations may fail. |
| Symptom: In multiple applications, if some Business Objects have the same BO name but different BO namespaces, inbound or outbound operation may fail, e.g., retreive may report NullPointerException. This issue impacts both inbound and outbound. |
| Resolution: Delivered a fix to not only use BO name but also namespace to differentiate BO during runtime. |
|
| 3 | 100313 | JR34869 | Adapter does not use connectionpool in the first pollcycle during "unordered" delivery. |
| Symptom: When using "unordered" delivery mode with "maximum connections" larger than 1, connection pool will not be used during the first poll cycle and NPE will be thrown. |
| Resolution: A fix has been delivered to have the ActivationSpec for one specific endpoint to be configured before polling for the first cycle, thus enable connection pool be used for "unordered" mode. |
|
| This table lists the enhancements and fixes in fix pack version 6.1.0.3. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 96206 | | Forward Fit CR96143 to Okemo - Effective Sequence number should not be required. |
| Symptom: When doing child record insert, the insert position is decided by the value of the effective date attribute and the effective sequence attribute. While users may want to insert a record at current/oldest location without knowing the effective sequence number. |
| Resolution: A new optional BO level ASI tag, IgnoreEffectiveSequence, is introduced. Users need manually add this ASI in the BO to override the effective sequence number. This tag has the value of 'true' or 'false'. The default is 'false' When set to true, the effective sequence number is ignored and the record is inserted either at the lowest index, which has the current effective date or at the highest index, which has the oldest effectve date. If this parameter is set, either InsAtCurrentEffDtPos or InsAtOldestEffDtPos must also be set. This parameter is used only for the effective dated items. |
|
| 2 | 75915 | | Null name space support in base class. |
| Symptom: Base class doesn't support null namespace using 6.1 adapter. |
| Resolution: One is adding the Head Alias "xsd:" to all vocabulary scoped in w3c namespace. The other is that cut off those alias with declaration of null namespace from schema. |
|
| 3 | 93006 | JR30832 | Failed to retrievaAll View with a child BO that has one child BO itself. |
| Symptom: retrieveAll a View with a child BO that has one child BO itself.There is no error message any more, but the result of the query does not match the data in the database. |
| Resolution: Change the source code on retrievaAll method and add support for this kind of case. |
|
| 4 | 93077 | | "Method is deprecated messages" in the log/console. |
| Symptom: A lot of warning messages appears in the log/console when the websphere adapter is running. |
| Resolution: Remove this message from system out. |
|
| 5 | 93143 | JR30855 | Infinite inbound loop when assuredOnceDelivery is false. |
| Symptom: Infinite inbound loop when assuredOnceDelivery is false. |
| Resolution: Change the source code to support the case when assuredOnceDelivery is false. |
|
| 6 | 93148 | | Improve the adapter exception case. |
| Symptom: Crash or hang situation appears since Base Class does not handle the exception. |
| Resolution: Fix it by catching the exception thrown by logging and ignore it for making sure the work completion status could be notified to workcontroller. |
|
| 7 | 93155 | | TypeFactory is using ext classloader instead of application classloader in WAS. |
| Symptom: forName method could not find the record and throws bo not found exception. |
| Resolution: Change the source code tto make sure correct classloader is used. |
|
| 8 | 93182 | | English text over the Progress Monitor Indicator. |
| Symptom: The progress monitor in the first screen of the EMD has har coded english text. |
| Resolution: Modify some source files and also message files to solve this issue. |
|
| This table lists the enhancements and fixes in fix pack version 6.1.0.1. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 90852 | | PeopleSoft Adapter has no need for child key validation |
| Symptom: Because the primary key is validated at the child level, the adapter fails if the primary key is not defined. |
| Resolution: The validation for the primary key at the child level is not neccessary and has been removed |
|
| 2 | 90957 | | Configurable retry for failed events |
| Symptom: The adapter continues to redeliver failed events indefinitely. |
| Resolution: A new property, FailedEventRetryLimit, has been added to the ActivationSpec. FailedEventRetryLimit allows you to set the number of times the adapter will attempt to deliver an event before marking it as FAILED. This only applies to failures that are normally retried; data binding errors and function selector errors are excluded. If the adapter or server is shut down and restarted, the adapter will start fresh and deliver the event the specified number of times, not counting any retries that were attempted before the adapter was shut down. |
|