| This table lists the enhancements and fixes in fix pack version 6.1.0.3. |
| Enhancements |
| 1 | 100156 | | FTP Adapter does not support global elements in the Business objects |
| Symptom: The Adapter was not supporting the Business objects containing the global element |
| Resolution: After the fix, the FTP adapter supports the Business objects containing the global element. |
|
| Fixes |
| 1 | 77524 | | FTP Adapter traces reveals password when reporting a failed login attempt for Inbound. |
| Symptom: FTP adapter was displaying the password in the trace logs when the login attempt failed for the inbound operation. |
| Resolution: Adapter now does not display the password in the trace logs it will display the string "XXXXXX" instead of the password. |
|
| 2 | 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.
|
|
| 3 | 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.
|
|
| 4 | 100156 | 34626 | FTP adapter prefixes the login/home directory of FTP server to the remote event directory |
| Symptom: FTP adapter prefixes the login/home directory of FTP server to the remote event directory.The user hence will be unable to access directories outside the home directory hierarchy in Unix/MVS platforms. |
| Resolution: The issue has been fixed and it is now expected from the user to give the absolute path for the event directory. |
|
| This table lists the enhancements and fixes in fix pack version 6.1.0.2. |
| Enhancements |
| 1 | 76465 | | FTP Adapter is incompatible with FTPS servers like FileZilla server and Jscape FTPS server. |
| Symptom: The Adapter does not work properly with recent FTPS servers like FileZilla server and Jscape FTPS server in Implicit FTPS mode. These servers expect PBSZ and PROT commands to be issued before opening a data connection. |
| Resolution: This problem is fixed so that the Adapter works well with FTPS servers like Jscape FTPS server. The Adapter now issues PBSZ 0 and PROT P commands before opening a new data connection. |
|
| Fixes |
| 1 | 76286 | | BO framework not handling anonymous data types. |
| Symptom: In case of using anonymous data type in the XSD to declare customer's data object types, Adapter will always add the string "_._type" after the data type name when serializing the data object into xml file. |
| Resolution: Adapter will now serialize the data object into xml file correctly even in case of using anonymous data type to declare the type of data objects. |
|
| 2 | 76680 | | Adapter not able to process list commands when working with EMC-SNAS FTP server |
| Symptom: Adapter fails to process list commands as the output of the long list command(ls -l) is not as per the standard format. The name token has absolute path in it. The standard behavior is that it should have only the relative name. |
| Resolution: This problem is fixed by processing the absolute path and getting the name from it. |
|
| 3 | 76706 | 32353 | Adapter throws ArrayIndexOutOfBoundException when the files in the event directory are deleted before Adapter picks them. |
| Symptom: The Adapter throws ArrayIndexOutofBoundException when the files in the event directory are deleted before the Adapter pick these files for processing.The Adapter tries to download the files which are not existent on the FTP server. |
| Resolution: This problem is fixed so that the Adapter works well when the files in the event directory are deleted. |
|
| 4 | 76059 | 30790 | Adapter does not retrieve the specified files during Inbound when the event directory is present on MVS platform. |
| Symptom: The Adapter fails to retrieve the files when the EventFileMask property contains MVS specific wildcard characters. |
| Resolution: This problem is fixed so that the Adapter uses the MVS specific wildcard characters while retrieving the files from the event directory. |
|
| 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 tranfer 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 a 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 throws meaningful 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 fails 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 adater now 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 no wrappers are used, it fails to process such business objects. |
| Resolution: The adapter now has the capability to handle business objects wihtout wrapper during inbound processing. |
|
| 9 | 76033 | | The wrapper business object values should be set on the record only when isSet is true. |
| Symptom: The wrapper business object values should 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 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. This should 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 spec and resource adapter |
| Resolution: The value in the activation spec and resourceadapter is now matched |
|
| 13 | 76121 | | Adapter doesn't support null namespace using 6.1 version of adapter |
| Symptom: Adapter encounters errors in generating the wrapper objects for user defined objects when null namespace is used |
| Resolution: The adapter now 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 will now use the system's default encoding if no encoding is 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 thrown 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, which enables to access the business object 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 now 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 appears in the log/console when the websphere 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 the case 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 make sure the work completion status could be notified to workcontroller. |
|
| 23 | 76299 | | Adapter on WTX throws null pointer exception. |
| Symptom: Null Pointer Exception thrown while performing outbound or inbound communication with Websphere Adapter on WTX. |
| Resolution: NO more Null pointer exception are thrown by the Adapter on WTX while performing outbound and inbound operation. |
|