| This table lists the enhancements and fixes in fix pack version 7.5.0.1. |
| Enhancements |
| 1 | 103499 | | Extend the Adapter Monitoring Capabilities by Including Event Points for Connection and Authentication to EIS. |
| Additional event points were introduced in AFC to capture the connection and authentication related events: WBI.JCAAdapter.Connection.SUCCESS, WBI.JCAAdapter.Connection.FAILURE, WBI.JCAAdapter.Connection.LOST, WBI.JCAAdapter.Connection.CLOSE, WBI.JCAAdapter.Authentication.FAILURE |
|
| 2 | 103559 | | Enterprise metadata discovery code for the adapter should be thread safe. |
| Cast Iron Runtime requires the adapter to support thread safe Enterprise metadata discovery, for this requirement the adapter implements thread safe EMD. |
|
| 3 | 102699 | | Extend the DESPI to support XML Types |
| Cast Iron Runtime requires the adapter to support XML data types for sending and receiving business objects from adapters, for this requirement the adapter extends the DESPI implementation for support XML types. |
|
| Fixes |
| 1 | 103614 | | Adapter uses Java timer for polling, when JCA timer is not abilable from the container, the adapter polling thread hangs in this situation. |
| Symptom: The non-daemon Java timer polling thread hangs with WebSphere Message Broker runtime, during inbound operation when the JCA timer is not available from the container. |
| Resolution: When the JCA Timer is not available from the container, the adapter uses the older approach of using the WorkManager to manage and execute the polling thread. |
|
| 2 | 103512 | | Adapter Inbound throws UnsupportedOperationException on WebSphere Message Broker. |
| Symptom: The startup of the Adapter fails with the UnsupportedOperationException since WebSphere Message Broker does not support a JCA timer in its bootstrap context and the Adapter expects one to be available. |
| Resolution: Adapter catches the UnsupportedOperationException exception and uses the WorkManager to manage and execute the polling thread, when the JCA timer is not available from the container |
|
| 3 | 103589 | | Remove the transaction code from EventPersistenceMemoryImpl |
| Symptom: EventPersistenceMemoryImpl suspends and resumes the global transaction while the adapter is running with a in-memory persistence configuration, this could potentially affect the performance. |
| Resolution: Removed the code that performs suspend and resume of the global transaction for the in-memory persistence configuration. |
|
| 4 | 103584 | | Schema generation should support to set the maxOccurs to a desired number. |
| Symptom: The schema generator code does not allow to set the value of maxOccurs attribute to the desired number, instead only allows to set 0, 1 or unbounded. |
| Resolution: The schema generator code is fixed to allow for setting the value of maxOccurs attribute to the desired number. |
|
| 5 | 103302 | | XML attribute support in DESPI XML |
| Symptom: Current XML DESPI implementation does not consider xml attribute for processing. |
| Resolution: Support provided for processing xml attributes in DESPI XML. |
|
| 6 | 103539 | | Synchronous BAPI inbound fails in Node level deployment with the lazy BO parsing. |
| Symptom: SAP adapter throws exception in sync callback in lazy-mode node level deployment. Error is thrown when maxlength annotation is read. |
| Resolution: The issue has been fixed in Adapter foundation classes to ensure that the node level deployment works fine with lazy BO parsing. |
|
| 7 | 103796 | JR41084 | Detect Illegal XML Character property should be visible only on IBM Integration Designer tooling |
| Symptom: The detect illegal XML property should be visible only for IBM Integration Designer and not seen on Rational Application Developer / WebSphere Message Broker toolkit. |
| Resolution: Modified the AFC code such that the EMDUtil class returns null for the DetectIllegalXML property group if the runtime is other than IBM Integration Designer. |
|
| 8 | 103797 | JR41085 | JDBC Adapter outbound behavior with illegal xml returns ResourceException. |
| Symptom: JDBC Adapter throws exception when illegal xml character is used during outbound. The detect illegal XML property options does not work as expected. JDBC adapter uses setObject() method to set the string property. |
| Resolution: The validation of the illegal character is now done on setObject() method of the accesssor too if the parameter is a string. |
|
| 9 | 103800 | | Perform validation in EMD and runtime for the Inbound properties. |
| Symptom: External Service wizard allows and accepts negative values for the following properties (Interval between polling periods, Maximum events in polling period and Time between retries in case of system connection failure). |
| Resolution: Validation is now performed for these properties to not accept negative values during External Service wizard and in the runtime. |
|
| 10 | 103802 | | The tracing of the Adapter foundation classes version for outbound request should be at FINEST level. |
| Symptom: The tracing of the AFC version for each individual outbound request should be at FINEST level. Currently, the tracing is done at INFO level which causes a lot of I/O and unneccessary logs in high load conditions for each outbound request. |
| Resolution: The AFC version information is now traced only at the FINEST level. |
|
| 11 | 103803 | | Use UOWManager as the transaction API for Event Persistence |
| Symptom: Event persistence classes are currently using the deprecated WAS API. This change is to implement the new WAS API for Transaction handling in Event persistence classes. |
| Resolution: Modified the Event persistence classes now to use the UOWManager as its transaction API. |
|
| 12 | 103804 | | Modify getEventWithXid method in EventPersistence implementation |
| Symptom: getEventWithXid method is called during the adapter recovery path. This method uses incorrect event peristence column names. |
| Resolution: Fixed the getEventWithXid method to use the appropriate event persistence column name. |
|
| 13 | 103848 | JR41086 | Adapter tries to shutdown Event manager repeatedly |
| Symptom: When an exception occurs while trying to shutdown the Event Manager, the adapter tries to shutdown the event manager repeatedly. |
| Resolution: Cancel the JCA Timer even if there is an exception in Event Manager shutdown. |
|