| This table lists the enhancements and fixes in fix pack version 6.1.0.1. |
| Enhancements |
| 1 | 76219 | | During outbound processing, server to server operation does not have a return value to determine the file transfer status |
| Symptom: During outbound processing, server to server operation does not have a return value to determine the success or failure of the file transfer. |
| Resolution: This is an enhancement which enables the server to server outbound operation to have a return value. The return value determines the success or failure status of the file transfer. |
|
| Fixes |
| 1 | 75700 | JR29939 | Adapter doesn't use the configured encoding during outbound |
| Symptom: The adapter takes the default encoding used by the base rather than the configured encoding during outbound operation. Adapter should be capable of passing the encoding to the base prior to setting the contents in the record. |
| Resolution: The adapter pre-sets the configured encoding in the record prior to setting the contents. |
|
| 2 | 75923 | JR30447 | Adapter fails when there is a directory path with a dot("."). |
| Symptom: The adapter fails when there is a dot (".") in the directory name. |
| Resolution: The adapter now has the capability to handle dot in the directory name. |
|
| 3 | 75977 | | Adapter throws inappropriate error messages during outbound request. |
| Symptom: The adapter throws inappropriate error messages during outbound request. |
| Resolution: The adapter now generates appropriate error messages while validating the directories. |
|
| 4 | 76026 | | When poll frequency is greater than the ftp server timeout, adapter throws a exception. |
| Symptom: The adapter throws a exception when poll frequency is greater than the ftp server timeout. |
| Resolution: The adapter now has the capability to handle such unknown exception. |
|
| 5 | 76027 | JR28166 | During outbound processing, create operation takes a long time when there are large number of files in the specified output directory. |
| Symptom: During outbound processing, create operation takes a long time to complete. |
| Resolution: This is a performance fix. The filename check performed during outbound was checking with all the files in the directory rather than with the filename. The check has been modified to include the filename. |
|
| 6 | 76028 | JR28535 | When inbound FTP adapter is configured to use partition drives for local event directory and local archive directory, the archiving of the event files fails. |
| Symptom: When inbound FTP adapter is configured to use partition drives for local event directory and local archive directory, the archiving of the event files fail as the java io api rename method cannot rename files from one partition drive to another. |
| Resolution: When java io api rename method fails, the adapter reads data from event file and writes to archive file. The adapter uses a buffer of 2 MB to read data. This type of archiving is performance intensive and may slow throughput for very large event files. |
|
| 7 | 76029 | | FTP server to server outbound operation precedence is not proper. |
| Symptom: The adapter does not take the servertoserver properties in proper precedence. |
| Resolution: The adapter handles the precedence of the servertoserver properties appropriately. The precedence is as follows : Properties set at wrapper business object> Interaction specification properties > Managed connection factory properties. |
|
| 8 | 76032 | | FTP inbound fails in databinding when no wrapper is used. |
| Symptom: The adapter does not process the inbound business object when the wrappers are not used, it fails to process such business objects. |
| Resolution: The adapter has the capability to handle business objects without wrapper during inbound processing. |
|
| 9 | 76033 | | The wrapper business object values must be set on the record only when isSet is true. |
| Symptom: The wrapper business object values must be set on the record only when isSet is true. |
| Resolution: The adapter now sets the wrapper business object values on the record only when isSet is true. |
|
| 10 | 76060 | JR30898 | Adapter throws a NPE after FTP server restart |
| Symptom: The adapter throws a NPE when it performs a outbound request after the FTP server restart |
| Resolution: The adapter now has the capability to handle such unknown exception |
|
| 11 | 95755 | JR28511 | During outbound retrieve operation,the adapter returns even a binary data in AsText attribute of UnstructuredContent. |
| Symptom: The adapter returns even a binary data in AsText attribute of UnstructuredContent for outbound retrieve operation. This must be set on AsBinary attribute instead. |
| Resolution: The adapter uses the file transfer type property of the request business object. If this value is set to ascii then the AsText attribute is populated. If it is set to binary then the AsBinary attribute of the UnstructuredContent business object is populated. The default value of file transfer type if it is not set in the request business object is binary. |
|
| 12 | 76119 | | Inbound with timestamp sorting fails |
| Symptom: Inbound with timestamp sorting fails as there is a mismatch in activation specification properties and resource adapter |
| Resolution: The value in the activation specification properties and resourceadapter is now matched |
|
| 13 | 76121 | | Adapter does not support null namespace using 6.1 version of adapter |
| Symptom: Adapter encounters errors while generating the wrapper objects for user defined objects when null namespace is used |
| Resolution: The adapter supports the null namespace objects. It generates wrapper objects successfully for user defeined objects with null namespace |
|
| 14 | 76122 | | Adapter is defaulting to UTF-8 if no encoding is used |
| Symptom: Adapter is defaulting to UTF-8 if no encoding is used |
| Resolution: The adapter uses the system's default encoding if the encoding is not set |
|
| 15 | 76126 | | The GenerateUniqueFile feature during append operation adds extraneous characters to the filename when the adapter runs on RedHat Platform |
| Symptom: Extra characters are appended to the generated unique filename when the Adapter is run on the RedHat platform |
| Resolution: With the fix,the Adapter is capable of creating the filename appropriately on the RedHat Platform |
|
| 16 | 76127 | | FileNotFound exception is generated while trying to read the file from archive directory at endpoint when using filepassbyreference |
| Symptom: For filepassbyreference feature the file is not available at the archive directory immediately when the business object reaches the endpoint |
| Resolution: The adapter archives the file appropriately, so that the business object is accessible in the enpoint |
|
| 17 | 76129 | | Port numbers are not automatically changed to default in properties view using assembly editor when protocol is changed |
| Symptom: Port numbers are not automatically changed to default in properties view using assembly editor when protocol is changed |
| Resolution: The adapter changes the port numbers automatically to corresponding default ports specific to the selected protocol using assembly editor |
|
| 18 | 76128 | | Outbound retrieve operation is not backward compatible with version 602 |
| Symptom: Outbound retrieve operation is not backward compatible with version 602 |
| Resolution: The adapter now supports the retrieve operation backward compatibility with version 602 |
|
| 19 | 76131 | | Outbound operation like create failed when using Apache ftp server |
| Symptom: The adapter failed to create a file when used with Apache ftp server as the NLST command failed with incorrect set of parameters |
| Resolution: The adapter passes the correct set of parameters for NLST to work |
|
| 20 | 93077 | | "Method is deprecated messages" in the log/console |
| Symptom: A lot of warning messages appear in the log/console when the adapter is running |
| Resolution: Filtered these messages in the log/console |
|
| 21 | 93143 | JR30855 | Infinite inbound loop when assuredOnceDelivery is false |
| Symptom: Infinite inbound loop when assuredOnceDelivery is false |
| Resolution: Change the source code to support this issue when assuredOnceDelivery is false |
|
| 22 | 93148 | | Improve the adapter exception case |
| Symptom: Crash or hang situation appears since Base Class does not handle the exception |
| Resolution: Handle the exception thrown by logging and ensure the work completion status be notified to workcontroller. |
|
| 23 | 76299 | | Adapter on WTX throws null pointer exception. |
| Symptom: Null Pointer Exception is generated while performing outbound or inbound communication with Websphere Adapter on WTX. |
| Resolution: NO more Null pointer exception are generated by the Adapter on WTX while performing outbound and inbound operation. |
|