IBM WebSphere Business Integration Adapter for i2, version 1.4.1 notes




Completed change requests
The following table shows the APARs (and CRs) fixed in Fix pack version 1.4.1
#CRAPARTitleDetails
184045Enable connection to an i2 system by specifying the appropriate host/port/ID
Problem: The adapter for i2 can just use the default host port 5015 and the user cannot specify the same. Also the user cannot specify the instanceId when generating business objects using the i2 ODA, There is a need to support enabling connections to i2 application through the adapter and ODA by specifying the appropriate host,port and ID.
Fix: The adapter now supports the same. There are a couple of new properties added to the i2 ODA, CISHostPort and InstanceId. There is also a new property, CISAgentHostPort added to the i2 adapter.
268131Support is needed for CIS 6.2.1
Problem: Support is needed for CIS 6.2.1.
Fix: Currency support for i2 CIS 6.2.1 has been added. The adapter for i2 now supports i2 Infrastructure Services (CIS) version 6.2.1.
366701NullPointerException occurs when polling
Problem: If the polling meta-object property AutoAcknowledge is set to true, the i2 adapter generates a NullPointerException when polling.
Fix: This issue has been fixed.
466457The property name DataHandlerMetaObject in the i2 template is not correct
Problem: The property name DataHandlerMetaObject in i2 template is not correct.
Fix: This issue has been fixed. The property name DataHandlerMetaObject has been changed to DataHandlerMetaObjectName in the i2 template.


The following table shows the APARs (and CRs) fixed in Fix pack version 1.4.0
#CRAPARTitleDetails
133546Support is needed for i2 CIS 6.1
Problem: Support is needed for i2 CIS 6.1
Fix: The adapter for i2 now supports i2 Infrastructure Services (CIS) version 6.1. Support is provided for durable subscriptions for event notification. The adapter can be configured for durable subscription by using the configuration property (UnregisterOperations) or by polling the meta-object attribute (Unregister). Support is now provided for event re-delivery. If an event failed to reach the integration broker, it can be re-delivered if the polling meta-object property AutoAcknowledge is set to false. The default for Unregister, UnregisterOperations, and AutoAcknowledge is true. The adapter will now clean up closed connections by removing them from the persistent store.


June 30th, 2006 6:00 PM
© 2006 IBM Corporation. Proprietary and Confidential. All Rights Reserved.