IBM WebSphere Business Integration Adapter for JText version 5.4.8 Fix Pack

Download Description

Fix Pack history

5.4.8
Internal tracking number: 35432
The JText adapter's performance was unsatisfactory for event processing when the SortFilesOnTimestamp property was set to "true" and the number of event files was very large. The fix for this problem significantly improves performance.

5.4.7
Internal tracking number: 35216
JText had a problem with the append mode for request processing on MVS systems using the dynamic child meta-object. The fix for this problem enables the JText connector to FTP files to an MVS system with the "FileWriteMode" specified as "a" (for append mode). The file name can be configured to either have an extension or not.

5.4.6
Internal tracking number: 34613
JText version 5.4.2 failed to poll a remote FTP server when the SortFilesOnTimestamp property was set to "true."

The SortFilesOnTimestamp property sorted the files based on the modification timestamp for files. The modification timestamp for remote files returned by any FTP server would generally be in a pre-defined fixed format. The FTP server used by the client returned the date and time in a different format. The fix takes care of the date and time format as returned by the FTP server of the client.

5.4.5
Internal tracking number: 31747
When the FTPKeepConnectionOpen property was set to "true" and the FTP server timed out, the first service call would be consumed for re-establishing the connection to the remote FTP server, and the the first request was not processed.

The connection to the FTP Server is now re-established in a timeout scenario, without the missing service calls.

Internal tracking number: 33411
When two files with the same FTPEventFileMask exist, and one of them was still being modified, the connector picked up the files that were not locked and processed them, but did not archive or delete them. It would continue to poll the same files over and over again in a loop, until all the files with the same mask were retrieved for processing.

This problem has been corrected. The agent now picks up only the files that are not being modified, and deletes or archives them normally. The file being modified is picked up later, after the write lock on the file has been released and it has been made available to the agent.

5.4.4
Internal tracking number: 32690
The adapter did not create output files in the FTP path specified in the dynamic child meta-object's OutFileName property. The adapter now creates the output files as expected, irrespective of the value in the OutFileName property being set to a local directory path or an FTP URL.

5.4.3
Internal tracking number: 30838
A customized data handler developed for a customer required the file name of an event file to be passed across to the data handler by setting the data handler options within the JText adapter. The JText adapter has been enhanced to pass the file name to the data handler.

5.4.2
Internal tracking number 31418
The adapter picked the files in the event directory based on the filenames.
A new boolean connector configuration property, SortFilesOnTimestamp, has been added. When set to "true," the adapter picks event files based on the creation timestamp. When set to "false," the files are picked up based on filenames
.
For maximum performance, you should set the SortFilesOnTimestamp property to "true" when there are few event files that each contain many events. This functionality can be overhead for smaller event files with single business objects.

5.4.1
Internal tracking number: 30237
The NetComponents.jar file has been modified, because the adapter experienced problems with the settings of an FTP server that used a Swedish locale sv_SE. The timestamp for the files in the format was 11.03 instead of 11:03, which caused problems when polling.

One of the files in the NetComponents.jar has been changed to fix this problem.