IBM WebSphere Adapter for Flat Files, version 7.5.0.5 notes

This document contains the following sections:
Enhancements and fixes
New and modified connector properties
Upgrade notes

This table lists the enhancements and fixes in Flat File Adapter version 7.5.0.5
Enhancements
#CRAPARTitleDetails
There are no enhancements in this interim fix.
Fixes
#CRAPARTitleDetails
1RTC8787JR44171Flatfile Adapter truncating the trailing spaces at the end Of a file
Symptom: With FlatFile Adapter customer seeing truncating the trailing and leading spaces of the BusinessObect content
Resolution: This has been fixed.Now the FlatFile Adapter returns the content as it is.

This table lists the enhancements and fixes in Adapter foundation classes interim fix version 7.5.0.4_IF01.
Enhancements
#CRAPARTitleDetails
There are no enhancements in this interim fix.
Fixes
#CRAPARTitleDetails
1RTC 8841JR44116SAP node and JMS node in same eg, will result in JMS node getting SAP nodes initial context.
Symptom: Initial context not found for SAP adapter.
Resolution:An AFC level fix provided for this issue.

This table lists the enhancements and fixes in fix pack version 7.5.0.3
Enhancements
#CRAPARTitleDetails
fixes
1RTC8532JR43571Customer encounters performance degradation when the Adapter processes large no of records
Symptom: With FlatFile Adapter customer sees performance degradation processing large no of records over a period of time
Resolution: This has been fixed with adding optimized method for performance improvement when handling large set of records

This table lists the enhancements and fixes in fix pack version 7.5.0.2_IF01
Enhancements
#CRAPARTitleDetails
fixes
1RTC7236
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.2
Enhancements
#CRAPARTitleDetails
fixes
1RTC 7013FlatFile 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
2RTC 7153FlatFile 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.
3RTC 5997Flatfile 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
4RTC 5998Flatfile 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
#CRAPARTitleDetails
fixes
1Internal APAR JR43237consume 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
#CRAPARTitleDetails
AFC fixes
17230Incomplete 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.
17220ALEInbound 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.
17162Generated 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.
17187CI 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
#CRAPARTitleDetails
fixes
1RTC7184JR42433FileNotFound 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
#CRAPARTitleDetails
fixes
1RTC7266
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
#CRAPARTitleDetails
fixes
1Internal 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.
1Internal 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
#CRAPARTitleDetails
fixes
1JR41833FlatFile 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
#CRAPARTitleDetails
1103768Remove 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
2103715If 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
1103828JR40810Flatfile 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
2JR40952Invalid 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.
3JR40954No 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.

This table lists new and modified connector properties
#VersionAdded or ModifiedPropertyLocation
No connector properties were introduced or modified for this version of the fix pack.

To upgrade to the fix pack version 7.5.0.3, do the following.
1. Ensure that you have followed the "Installation Instructions" section in the download link before proceeding.
2. If you need to use the Fix Pack for EMD, delete the connector project in WebSphere Integration Developer, import the new RAR file, and apply the enterprise information system (EIS) specific dependency files.
   a. Open the Java build path for the SCA module and remove the Connector project that is selected on Projects tab.
   b. Open the dependency editor and remove the connector project.
   c. Delete the connector project from the workspace.
   d. Import the new RAR file. Add any dependency files from EIS specific application-specific information as needed.
   e. Open the Java build path for the SCA module and select the Connector project that is selected on the Projects tab.
   f. Open the dependency editor and add the connector project if it is not already present and select Deploy with Module.
3. If you need to update deployed applications on WebSphere Process Server, do the following:
   a. Select Update for the corresponding application on the WebSphere Process Server administrative console.
   b. Select Single Module with a relative path as name of the RAR file - CCWYFF_FlatFile.rar.
   c. Click Browse on the local file system to select the updated RAR file that has the changes.
   d. Select the default values in the remaining steps and click Finish. This will ensure that existing configurations, for example, are not changed and that only JAR files will be updated.


Jan 17th, 2013 6:00 PM
(C) 2012 IBM Corporation. Proprietary and Confidential. All Rights Reserved.