| This table lists the enhancements and fixes in fix pack version 7.0.0.4 |
| Enhancements |
| 1 | 103390 | Internal | If any verification of Property gets fail, Print the value of the property with error message |
| Symptom: Flat File Adapter is not showing the value of any property if it gets fail. |
| Resolution: Flat File Adapter now will print the property value along with the error message. This has been fixed |
|
| 2 | 103388 | Internal | Considering Invaid directory path given in InteractiveSpec. |
| Symptom: If you specify the output directory in InteractionSpec Properties in zOs/Linux/Unix, Flat File Adapter is not able to find the directory |
| Resolution: Flat File Adapter was not able to convert the path to Operating system specific path. This issue has been fixed. |
|
| 3 | 103330 | JR39427 | PROBLEM ARCHIVING EVENTS WITH SAMBA SHARED FOLDERS. ADAPTER REPEATEDLY PROC. |
| Symptom: After mouting the Samba shared folder onto the local directory, the adapter is reading the file repeatedly. |
| Resolution: Flat File Adapter was not able to convert the back slashes to forward slashes.This has been fixed |
|
| 4 | 103260 | Internal | If the number reach 2147483647, then re-do create again. got wrong sequence number |
| Symptom:The largest sequence number would be 2147483647, then, the sequence number will return to 1. |
| Resolution:In Flat File Adapter, the sequence number will gets create are positive and uses the long value until 2^63-1. Then it gets reset to 1. This issue has been fixed. |
|
| 5 | 103261 | Internal | InteractionSpecProperties need to enable/disable during EMD. |
| Symptom: Some InteractionSpecProperties are need to enable/disable for certain operations. |
| Resolution:This has been fixed |
|
| 6 | 102362 | Internal | To display the name of Archive Directory in trace file. |
| Symptom:Archive Directory name was not getting display in trace file. |
| Resolution: Archive Directory name is getting display in trace file.This issue has been fixed. |
|
| 7 | 102237 | Internal | Enhance generate unique file feature to accept user input for the file extension. |
| Symptom: The generate unique file feature currently appends the .tmp extension to the files that are created using this option. User does not any option to define generateUniqueFile extension on there own. |
| Resolution: Flat File adapter now has the option of suffix and prefix for the user for generateUniqueFile option.This has been fixed |
|
| 8 | 102239 | Internal | Staging directory concept will work with generateUniqueFile. |
| Symptom: The value of staging directory is getting ignored when you specify it together with generateUniqueFile option. |
| Resolution: Staging Directory is working together with generateUniqueFile.This issue has been fixed. |
|
| 9 | 102243 | Internal | DuplicateRecordException in cluster environmnt in high load with sequence file. |
| Symptom: When outbound create module is configured with Sequencing file and deployed on a clustered environment, there is a duplicate record exception when there is huge load of outbound requests. |
| Resolution:This issue has been fixed |
|
| 10 | 102264 | Internal | Warning message should be logged with reason when adapter reset sequence file. |
| Symptom: No warning message is getting displayed in the trace file when the adapter resetting the sequence number in sequence file. |
| Resolution: A warning message will get displayed whenever the Flat File Adapter resets the sequence number.This issue has been fixed. |
|
| 11 | 102613 | JR38019 | Enable JCA timer capability for inbound polling. |
| Symptom: Adapter uses a polling thread in the runtime, which will poll as per the pollperiod. The polling thread will be only submitted once and always being in the runtime environment. When there are no events for a longer duration, the polling thread will be hung and throws a warning message from the JCA container. |
| Resolution: Use JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the thread hang issue.This issue has been fixed. |
|
| 12 | 103162 | JR39129 | Duplicate messages are created in the event table by Flat file Adapter due to unexpected database outage. |
| Symptom: During Adapter Inbound operation, after several unplanned database outages during event processing duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager. |
| Resolution: If the event is already delivered to the downstream components but the overall transaction is marked failure due to issues in downstream component, the event is deleted if no rollback is issued.This issue has been fixed. |
|
| This table lists the enhancements and fixes in fix pack version 7.0.0.3. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 101074 | Internal | If generateUniqueFile = true, and set stagingDirectory, new file has no content. |
| Symptom:During Outbound operation for Flat File, if generateUniqueFile = true, and set stagingDirectory, new file has no content. |
| Resolution: This is fixed. |
|
| 2 | 101248 | Internal | Remove unwanted set methods in FlatFileResourceAdapter class. |
| Symptom:The following properties in the FlatFileResourceAdapter class are used internally: flatFileUtil, verifier, bridge, endpointActivationCompleted. However, set methods, which are not used, are created for them, which is causing these properties to show up in the admin console. Hence the set methods for these properties need to be removed. |
| Resolution: This has been Fixed. |
|
| 3 | 101243 | Internal | When filePassByReference=Ture, the same file can't be polled for the second time. |
| Symptom:During inbound operation for Flat File, when filePassByReference=Ture, the same file can't be polled for the second time. |
| Resolution: This has been fixed. |
|
| 4 | 101244 | Internal | Using splitting and pollquantity=n, BO number=n+m, m can't be transacted correctly. |
| Symptom:Durng inbound operation for Flat File, using splitting and pollquantity=n, BO number=n+m, m can't be transacted correctly. |
| Resolution: This has been Fixed. |
|
| 5 | 101245 | Internal | If EMD deliveryType is not ORDERED, a NullPointerException is thrown at the end of the EMD run. |
| Symptom:If the deliveryType is set to UNORDERED during inbound EMD, a null pointer exception will be thrown at the end of the EMD run. |
| Resolution: This has been fixed. |
|
| This table lists the enhancements and fixes in fix pack version 7.0.0.1 |
| Enhancements |
| There are no enhancements in this fix Pack |
| Fixes |
| 1 | 100293 | Internal | BO related Exception when using COBOL copy book data binding. |
| Symptom:FFDC recorded BO related Exception, although the operations have done correctly. |
| Resolution: This is fixed. |
|
| 2 | 100356 | Internal | When BO name is same and BO namespace is different, inbound work may be failed. |
| Symptom:When adapter creates 2 or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. |
| Resolution: Redefined the methods of "hashCode()" and "equals()" in the SDOV1Type class. Then individual adapter can distinguish those BO correctly by "namespace + name" if those BOs name are equal. |
|
| 3 | 100406 | Internal | Adapter will encoutner NPE after restart the app on server. |
| Symptom:For Adapter inbound and outbound operation(standalone deployment), after the application is restarted, the NullPointerException will appear when the adapter tries to query the ASI Infor from cache. |
| Resolution: The BO's namespace and name has been preserved as BO instance's fields. After the application is restarted, adapter can still get them from those instance's field rather than the stale data cache. |
|
| 4 | 100418 | Internal | RootNameFunctionSelector missed from EMD.properties file. |
| Symptom:The description of RootNameFunctionSelector missed from EMD.properties file causes an exception when getting the display name in EMD. |
| Resolution: Appended the property descriptions for RootNameFunctionSelector in the EMD.properties file. |
|
| 5 | 99888 | Internal | Change to use PmiRmJmxService MBean to get arm transaction factory name. |
| Symptom:When adapter gets ARM transaction factory name to process ARM transaction, a WAS internal private API is used for it, which need to be replaced with public interfaces. |
| Resolution:Switched to Invoke PmiRmJmxService MBean, a set of public interfaces exposed by WAS to get ARM transaction fatory name. |
|
| 6 | 100559 | Internal | Shouldn't system out "O isGloable element=== false/true" in trace. |
| Symptom: System out for "O isGloable element=== false/true" is not coming in the trace. |
| Resolution:This is fixed. Added the required trace in the code. |
|
| 7 | 77930 | Internal | Printing out the AdapterFoundationClasses version in the Logs/traces. |
| Symptom:Currently with all the adapters , The AFC version is not printed out in the logs/traces. It would be really helpful to have this information printed out to the logs/traces especially in debugging issues due to conflicting AFC being loaded at runtime. |
| Resolution:Print AFC version in the trace. |
|
| 8 | 100740 | Internal | BOXMLSERIALZIER IS THROWING EXCEPTION WHEN PROCESSING IN ASYNCMODE. |
| Symptom: When the adapter is configured to use default data binding with no data handler, the EIS binding uses BOXMLSerializer to serialize the events. In such a scenario, no notification is sent to adapter when exception is encountered. |
| Resolution: This needs a fix from both the EIS binding as well as the adapter. The EIS binding fix is available in WPS v7.0.0.1. The adapter fix is available with this version. |
|
| 9 | 100803 | Internal | FilterFutureEvent check box should be removed from EMD dialog. |
| Symptom:FilterFutureEvent check box should be removed from EMD dialog as this property is not being used by the FlatFile Adapter. |
| Resolution:This is fixed.FilterFutureEvent has been removed from EMD. |
|
|
| To upgrade to the fix pack version 7.0.0.4, 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. |
|
|
May 23rd, 2011 6:00 PM |
|
(C) 2010 IBM Corporation. Proprietary and Confidential. All Rights Reserved.
|
|