This table lists the enhancements and fixes in fix pack version 7.5.0.2 |
Enhancements |
fixes |
1 | RTC 7013 | | FlatFile Adapter reading a file with corrupted Data in BINARY mode |
Symptom: When the FlatFile adapter reads a binary file in binary mode and then writes the file again to the file system (in binary mode) it does not have the same content. |
Resolution: Flat File Adapter now reads in the correct format as specified by fileEncodingType. This has been fixed |
|
2 | RTC 7153 | | FlatFile Adapter throwing NumberFormatException when splitCriteria disabled |
Symptom: When splitCriteria is disabled FlatFile adapter throws NumberFormatException. |
Resolution: This has been fixed.Flat File Adapter splitCriteria set to default (zero) when it is disabled. |
|
3 | RTC 5997 | | Flatfile adapter throws FileNotFoundException when filename contains invalid characters |
Symptom: When FlatFile Adapter Configured and run with outbound Create operation with invalid characters in filename ,it throws error as FileNotFoundException instead of throwing Invalid Property Exception. |
Resolution: Flat File Adapter now throws proper message when the file name contains invalid characters. This has been fixed |
|
4 | RTC 5998 | | Flatfile adapter throws Error accessing the file when invalid characters given in sequence filename |
Symptom: When FlatFile Adapter Configured and run with outbound Create operation with invalid characters in Sequence filename ,it throws an error occurred while accessing file instead of throwing Invalid Property error message. |
Resolution: Flat File Adapter now throws proper error message when the sequence file name contains invalid characters. This has been fixed. |
|
This table lists the enhancements and fixes in fix pack version 7.5.0.1_IF06 |
Enhancements |
fixes |
1 | | Internal APAR JR43237 | consume the behavior changes implemented in some Java API's like setWritable() and serReadOnly() |
Symptom: FlatFile Adapter throws permission denied exception during application installtion |
Resolution: Problem was occuring duw to the behaviour changes inplemented in Some Java API's.This has been fixed now. |
|
|
This table lists the enhancements and fixes in fix pack version 7.5.0.1_IF05 |
Enhancements |
AFC fixes |
1 | 7230 | | Incomplete XSD namespace package generated [RAD] |
Symptom: When regenerating the Business Object classes using an XSD schema file from SAP or PeopleSoft WebSphere Adapters, an incorrect package name is returned when the targetNamespace does not start with www. |
Resolution: Problem in the logic that converts the namespace to package name in the RecordGeneratorHelper class. |
|
1 | 7220 | | ALEInbound does not work when PI is enabled. Problem with the package name generated in RAD when the namespace is urn |
Symptom: RecordGeneratorHelper where the namespace to package conversion happens does not handle the namespace that is of urn type. |
Resolution: Support to handle namespace of urn type added in RecordGeneratorHelper. |
|
1 | 7162 | | Generated Java bindings have incorrect xsdLocation in the commented code section |
Symptom: Generated Java bindings have incorrect xsdLocation in the commented code section |
Resolution: The method generateDataBinding now returns only one top level root node matching to the business object previously mutliple root nodes were returned,hence the databindings had incorrect namespace. |
|
1 | 7187 | | CI Default value should be populated for attributes in the generated schemas for idocs, no support in AFC for enum types |
Symptom: CI Default value should be populated for attributes in the generated schemas for idocs, no support in AFC for enum types. |
Resolution: Support for enum types for xsd attributes added in AFC. |
|
|
This table lists the enhancements and fixes in fix pack version 7.5.0.1_IF04 |
Enhancements |
fixes |
1 | RTC7184 | JR42433 | FileNotFound issue during databinding generation in WBIDataBindingGenerator, when schema URL points to file within a jar |
Symptom: FileNotFound issue during databinding generation in WBIDataBindingGenerator, when schema URL points to file within a jar. |
Resolution: Problem was occurring because the AFC code assumed that the schema URL will always point to a file, support for other protocols was not provided. This is corrected to enable support for all protocols for schema URL. |
|
|
This table lists the enhancements and fixes in fix pack version 7.5.0.1_IF03 |
Enhancements |
fixes |
1 | RTC7266 |
| Problem archiving the files with proper extension using Samba Shared Folder |
Symptom: After mouting the Samba shared folder from another system,the file is archiving with dot null istead of dot success extension. |
Resolution: This has been fixed.Now the files will be archive with the proper extension. |
|
|
This table lists the enhancements and fixes in fix pack version 7.5.0.1_IF02 |
Enhancements |
fixes |
1 | | Internal APAR JR42402 | DB Connections are not released properly by FlatFile Adapter 7.5.0.1 |
Symptom: The database connections are not properly closed by the FlatFile adapter version 7.5.0.1. |
Resolution: This has been fixed. Now all the database connections are closed properly. |
|
1 | | Internal APAR JR42379 | FlatFile Adapter retrieves one event file maximum at a time |
Symptom: FlatFile Adapter is only retrieving one event file at maximum at a time.no matter what is the poll quantity value. |
Resolution: This has been fixed. Now FlatFile Adapter retrieves events from multiple files based on the poll quantity. |
|
|
This table lists the enhancements and fixes in fix pack version 7.5.0.1_IF01 |
Enhancements |
fixes |
1 | | JR41833 | FlatFile Adapter reading a file with corrupted Data in BINARY mode |
Symptom: When the FlatFile adapter reads a binary file in binary mode and then writes the file again to the file system (in binary mode) it does not have the same content. |
Resolution: Flat File Adapter now reads in the correct format as specified by fileEncodingType. This has been fixed |
|
|
This table lists the enhancements and fixes in fix pack version 7.5.0.1 |
Enhancements |
1 | 103768 | | Remove Depricated Transaction API from EventPersistence Classes |
Symptom: The event persistence classes use "com.ibm.ws.extensionhelper.TransactionControl" class to suspend the resume the runtime's global transactions. The com.ibm.ws.extensionhelper.TransactionControl class is deprecated from WAS since v7.0. |
Resolution: FlatFile Adapter will Use the com.ibm.wsspi.uow.UOWManager instead of deprecated com.ibm.ws.extensionhelper.TransactionControlc class. This has been fixed |
|
2 | 103715 | | If any verification of Property gets fail, Print the value of the property with error message in trace |
Symptom: Flat File Adapter is not populating the trace file if the property happens to be invalid with error message. |
Resolution: Flat File Adapter now will print the property value along with the error message in the trace log file. This has been fixed |
|
fixes |
1 | 103828 | JR40810 | Flatfile adapter not moving files from staging directory to output directory |
Symptom: Flatfile adapter not moving files from staging directory to output directory |
Resolution: Flat File Adapter now moves the files from Statging directory to output directory when the directory mounted to NFS. This has been fixed |
|
2 | | JR40952 | Invalid SplitCriteria for SplitBySize should throw error |
Symptom: When the SplitBySize is selected as SplitFunctionClassName , the invalid values are also been accepted |
Resolution: Flat File Adapter throws error when SplitFunctionClassName is incorrect and sets the spiltcriteria to 0 when SplitBySize is given any invalid char or null. Throws exception when a negative value is given. |
|
3 | | JR40954 | No Error when access restricted to event, Archive or output Directories |
Symptom: When we deny all access to the archive or event directory or output directory and run a inbound/outbound, the verify method does not throw any error in trace.log or any ffdc |
Resolution: The error messages are properly enabled when a directory on which FlatFile is working on is access restricted. Adapter will be stopped if the directories doesnt have requested access initially. |
|
|