| This table lists the enhancements and fixes in fix pack version 7.0.0.4. |
1 | 102613 | JR38440 | Enable JCA timer capability for inbound polling |
| Symptom: Adatper used one polling thread in the runtime, which will poll as per poll frequency interval. The polling thread will be only submitted once and always being in the runtime environment. When there is no event coming, the polling thread will be hung up after 15-20 minutes, which invoke an warning message. |
| Resolution: AFC Fix was required to fix this issue. Use JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the hung-up issue. |
|
| 2 | 102584 | JR38387 | JDBC Adapter has performance issue while processing large hierachy business objects. |
| Symptom: JDBC Adapter has performance issue while processing large hierachy business objects, this issue will cause high CPU usage. |
| Resolution: AFC Fix was required to fix this issue. Fixed. JDBC Adapter optimized the algorithm for hierachy business object handling. |
|
| 3 | 101164 | JR36457 | CPU utilization spikes when the Email adapter waits for response from the mail server |
| Symptom: When the adapter waits for the response from the mail server, in the mean time the CPU utilization goes up.
|
| Resolution: The problem has been resolved. As a part of the fix the a new property called Response Timeout has been introduced so that the adapter waits only for the number of milliseconds mentioned in the timeout. |
|
| 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 | 99888 | | When adapter gets ARM transaction factory name to process ARM transaction a WAS internal private API is being used. It should be replaced with public interfaces. |
| Symptom: When adapter gets ARM transaction factory name to process ARM transaction a WAS internal private API is being used. It should 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. |
|
| 2 | 100356 | | Adapter throws NullPointerException when working with two or more modules with the sme business obeject name but different namespace and structure. |
| 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 | | When an application is restarted with Adapter deployed in standalone mode, Adapter throws NullPointerException when querying the ASI information from the cache. |
| 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 from cache. |
| Resolution: The Business Object's namespace and name has been preserved as Business Object 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 | 77930 | | 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 |
|
| 5 | 78017 | | Adapter should support the feature of delivering bounced emails to an alternate email id. |
| Symptom: When the email id mentioned in the 'to' field is wrong, the adapter does not have the capability of sending a bounce email. |
| Resolution: Adapter now has the capability of sending bounced emails to an alternate email id. |
|
| 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. |
| e. 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 - CWYEM_EMail.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. |
|
|
July 08, 2011 6:00 PM
|
|
(C) 2011 IBM Corporation. Proprietary and Confidential. All Rights Reserved.
|
|