IBM Support

WebSphere Adapters V7.5.0.X fix list for WebSphere Message Broker V8.0, IBM Integration Bus V9.0 and IBM Integration Bus V10.0

Product Documentation


Abstract

WebSphere Adapters provide periodic fixes for editions of release version 7.5. The following is a listing of those fixes along with the corresponding WebSphere Message Broker (WMB) and IBM Integration Bus (IIB) versions with which they are packaged.

Content


Please use the index below to get the details of the Adapter versions packaged with different versions of IBM Integration Bus v10, IBM Integration Bus v9 and Websphere Message Broker v8. The individual tables provide details of the various fixes that the respective adapter versions package.

Adapter level packaged with Link to the details
IBM Integration Bus V10.0.0.13 Take me there
IBM Integration Bus V10.0.0.12 Take me there
IBM Integration Bus V10.0.0.11 Take me there
IBM Integration Bus V10.0.0.10 Take me there
IBM Integration Bus V10.0.0.9 Take me there
IBM Integration Bus V10.0.0.8 Take me there
IBM Integration Bus V10.0.0.7 Take me there
IBM Integration Bus V10.0.0.6 Take me there
IBM Integration Bus V10.0.0.5 Take me there
IBM Integration Bus V10.0.0.4 Take me there
IBM Integration Bus V10.0.0.3 Take me there
IBM Integration Bus V10.0.0.2 Take me there
IBM Integration Bus V10.0.0.1 Take me there
IBM Integration Bus V10.0.0.0 Take me there
IBM Integration Bus V9.0.0.10 Take me there
IBM Integration Bus V9.0.0.9 Take me there
IBM Integration Bus V9.0.0.8 Take me there
IBM Integration Bus V9.0.0.7 Take me there
IBM Integration Bus V9.0.0.6 Take me there
IBM Integration Bus V9.0.0.5 Take me there
IBM Integration Bust V9.0.0.4 Take me there
IBM Integration Bus V9.0.0.3 Take me there
IBM Integration Bus V9.0.0.2 Take me there
IBM Integration Bus V9.0.0.1 Take me there
IBM Integration Bus V9.0.0.0 Take me there
WebSphere Message Broker V8.0.0.9 Take me there
WebSphere Message Broker V8.0.0.8 Take me there
WebSphere Message Broker V8.0.0.7 Take me there
WebSphere Message Broker V8.0.0.6 Take me there
WebSphere Message Broker V8.0.0.5 Take me there
WebSphere Message Broker V8.0.0.4 Take me there
WebSphere Message Broker V8.0.0.3 Take me there
WebSphere Message Broker V8.0.0.2 Take me there
WebSphere Message Broker V8.0.0.1 Take me there



Adapter version packaged with WebSphere Message Broker V8.0.0.9

Note: When upgrading to Fix Pack 8.0.0.9, IBM WebSphere Adapters for SAP V7.5.0.5_IF32 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.16. We recommend that clients check the latest certified levels here and get the SAP JCo and SAP IDOC libraries from the SAP Marketplace

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF32JR57037When definition is changed on SAP side, xsd needs to be reloaded by clearing the segment cache in ALE Pass through scenarios
Siebel V7.5.0.5_IF11
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF02
WebSphere Adapter for JDE to support for NIST SP800-131a Compliance.
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index


Adapter version packaged with IBM Integration Bus V9.0.0.8 , V9.0.0.9, V9.0.0.10

Note: When upgrading to Fix Pack 9.0.0.8, 9.0.0.9 and 9.0.0.10, IBM WebSphere Adapters for SAP V7.5.0.5_IF32 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.16. We recommend that clients check the latest certified levels here and get the SAP JCo and SAP IDOC libraries from the SAP Marketplace

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF32JR57037When definition is changed on SAP side, xsd needs to be reloaded by clearing the segment cache in ALE Pass through scenarios
Siebel V7.5.0.5_IF11
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF03
Support for child events of array structure(occurs multiple times) in Real Time Events.
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index


Adapter version packaged with IBM Integration Bus V10.0.0.13

Note: When upgrading to Fix Pack 10.0.0.13 , IBM WebSphere Adapters for SAP V7.5.0.5_IF32 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.16 and IDOC 3.0.12. We recommend that clients check the latest certified levels here and get the SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF32JR57037When definition is changed on SAP side, xsd needs to be reloaded by clearing the segment cache in ALE Pass through scenarios
Siebel V7.5.0.5_IF11
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF13
Support for JDE tools v9.2
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index


Adapter version packaged with IBM Integration Bus V10.0.0.12

Note: When upgrading to Fix Pack 10.0.0.12 , IBM WebSphere Adapters for SAP V7.5.0.5_IF32 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.16 and IDOC 3.0.12. We recommend that clients check the latest certified levels here and get the SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF32JR57037When definition is changed on SAP side, xsd needs to be reloaded by clearing the segment cache in ALE Pass through scenarios
Siebel V7.5.0.5_IF11
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF13
Support for JDE tools v9.2
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index



Adapter version packaged with IBM Integration Bus V10.0.0.9, V10.0.0.10 and V10.0.0.11

Note: When upgrading to Fix Pack 10.0.0.9, 10.0.0.10 and 10.0.0.11 , IBM WebSphere Adapters for SAP V7.5.0.5_IF32 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.16 and IDOC 3.0.12. We recommend that clients check the latest certified levels here and get the SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF32JR57037When definition is changed on SAP side, xsd needs to be reloaded by clearing the segment cache in ALE Pass through scenarios
Siebel V7.5.0.5_IF11
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF03
Support for child events of array structure(occurs multiple times) in Real Time Events.
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index


Adapter version packaged with IBM Integration Bus V10.0.0.8

Note: When upgrading to Fix Pack 10.0.0.8 , IBM WebSphere Adapters for SAP V7.5.0.5_IF32 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.15 and IDOC 3.0.12. We recommend that clients get the latest available SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF32JR57037When definition is changed on SAP side, xsd needs to be reloaded by clearing the segment cache in ALE Pass through scenarios
Siebel V7.5.0.5_IF10
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF03
Support for child events of array structure(occurs multiple times) in Real Time Events.
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index


Adapter version packaged with IBM Integration Bus V9.0.0.7

Note: When upgrading to Fix Pack 9.0.0.7 , IBM WebSphere Adapters for SAP V7.5.0.5_IF31 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.11. We recommend that clients get the latest available SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF31JR56613Under certain circumstances, when IDoc has large number of empty tags resulting in huge memory buildup is seen in IIB.
Siebel V7.5.0.5_IF10
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF03
Support for child events of array structure(occurs multiple times) in Real Time Events.
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index


Adapter version packaged with WebSphere Message Broker V8.0.0.8

Note: When upgrading to Fix Pack 8.0.0.8, IBM WebSphere Adapters for SAP V7.5.0.5_IF28 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.11. We recommend that clients get the latest available SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF28JR55768JCO_ERROR_CONCURRENT_CALL: The context with the session id [DEFAULT_SESSION_REFERENCE]... is currently used in thread Thread-14 [0x20].Current thread is Thread-21 [0x27]. exception is seen when multiple parallel outbound request is sent to SAP Adapter .
Siebel V7.5.0.5_IF10
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF02
WebSphere Adapter for JDE to support for NIST SP800-131a Compliance.
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index


Adapter version packaged with IBM Integration Bus V10.0.0.6, IBM Integration Bus V9.0.0.6

Note: When upgrading to Fix Pack 9.0.0.6 and 10.0.0.6, IBM WebSphere Adapters for SAP V7.5.0.5_IF28 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.11. We recommend that clients get the latest available SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF28JR55768JCO_ERROR_CONCURRENT_CALL: The context with the session id [DEFAULT_SESSION_REFERENCE]... is currently used in thread Thread-14 [0x20].Current thread is Thread-21 [0x27]. exception is seen when multiple parallel outbound request is sent to SAP Adapter .
Siebel V7.5.0.5_IF03
JCA Siebel Adapter 7.5 throws CWYEB3102S on empty payload
JDE V7.5.0.5_IF03
Support for child events of array structure(occurs multiple times) in Real Time Events.
AFC V7.5.0.5_IF08
When SAP adapter receives multiple values of a complex type element in BAPI/RFC, the adapter is processing only the first value and ignoring the others.
Back to the index


Adapter version packaged with IBM Integration Bus V10.0.0.0, V10.0.0.1, V10.0.0.2, V10.0.0.3, V10.0.0.4, V10.0.0.5 and IBM Integration Bus V9.0.0.3, V9.0.0.4 and V9.0.0.5

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF07
Gateway Service needs to be set for outbound support for bluemix application to be able to communicate the request to SAP server via Data Power (solution only for "on-prem DP" flow).
Siebel V7.5.0.5_IF03
JCA Siebel Adapter 7.5 throws CWYEB3102S on empty payload
JDE V7.5.0.5_IF03
Support for child events of array structure(occurs multiple times) in Real Time Events.
AFC V7.5.0.5_IF02
When SAP adapter receives multiple values of a complex type element in BAPI/RFC, the adapter is processing only the first value and ignoring the others.
Back to the index


Adapter version packaged with IBM Integration Bus V9.0.0.2, WebSphere Message Broker V8.0.0.5 , V8.0.0.6 and V8.0.0.7

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF06JR49506 Field SEGNAM in data record is default throwing RFC_ERROR_SYSTEM_FAILURE.
JR48731 EMD fails with class cast exception.
JR48434 Module developed on V7 adapters fail to deploy on runtimes using V75 adapters.
JR48894 Limation in the number of attributes in an IDOC segment.
JR47684 In 'Discover IDoc From File', elements are named "NOATTRIBUTENAME" if 'Use SAP field names' is set in Data Record.
JR39274 ALEAUD is not created correctly, in case of packet IDOCs.
JR48587 Iterative Discovery of the module developed on V7 adapters fail with NPE on Toolkit using V75 adapters.
JR46854 JCA SAP Adapter does not support BAPI data type STRING_TABLE.
JR48608 SAP Adapter 7.5 throws nullpointer on data containing XSI:NIL="TRUE".
JR46639 Enable SNC/SSO on CI

WebSphere Adapter for SAP to support for NIST SP800-131a Compliance.
Siebel V7.5.0.5_IF03
JCA Siebel Adapter 7.5 throws CWYEB3102S on empty payload
JDE V7.5.0.5_IF02
WebSphere Adapter for JDE to support for NIST SP800-131a Compliance.
AFC V7.5.0.5_IF02
When SAP adapter receives multiple values of a complex type element in BAPI/RFC, the adapter is processing only the first value and ignoring the others.
Back to the index


Adapter version packaged with IBM Integration Bus V9.0.0.1, WebSphere Message Broker V8.0.0.4 and WebSphere Message Broker V8.0.0.3

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF01
AFC upgrade delivered. No fixes made.
SAP V7.5.0.5_IF01JR43619When BAPI outbound is run after ALE, outbound fails with NPE
JR45307QRFC support in WMB for MQ one-way pattern
JR45248Removal of hash codes or random numbers from segment names for ALE discovery
JR46343During iterative discovery on WMB as well as IID, the codepage is getting set with default value
JR46336Full JCO tracing fails on WMB v8.0
JR45947JCO session (if idle) times out after 10 or more mins
JR45439Issues when importing an XSD
JR44116SAP Node and JMS node in same EG will result in JMS node getting SAP nodes initial context. Need to pass initial context
JR45612Retry interval and time set on SAP Adapter inbound in WMB 8001 do not get serialized


Notify customer when connection with SAP breaks and retry limit exhausts
Siebel V7.5.0.5_IF01
AFC upgrade delivered. No fixes made
JDE V7.5.0.5_IF01JR44380JDE Adapter fails to handle JDEUtime ASI type values for outbound

JR44257V9.1 missing from descriptions in resource bundle for languages other than english
AFC V7.5.0.5_IF01JR44116SAP Node and JMS Node in same EG, will result in JMS Node getting SAP Node initial context. Need to pass initial context.
Back to the index


Adapter version packaged with IBM Integration Bus V9.0.0.0

AdapterAPARDescription
PeopleSoft V7.5.0.4_IF01
AFC upgrade delivered. No fixes made.
SAP V7.5.0.4_IF04JR46336Full JCO tracing fails on WMB v8.0
JR45947JCO session (if idle) times out after 10 or more mins
Siebel V7.5.0.4_IF01
AFC upgrade delivered. No fixes made
JDE V7.5.0.4_IF02
CI: Operation and Selection properties should not be translated
AFC V7.5.0.4_IF01JR44116SAP Node and JMS Node in same EG, will result in JMS Node getting SAP Node initial context. Need to pass initial context.
Back to the index


Adapter version packaged with WebSphere Message Broker V8.0.0.2

AdapterAPARDescription
PeopleSoft V7.5.0.4_IF02
A nullpointerException seen on creating Web Page for the PeopleSoft J2C bean.

Thread safe implementation of people soft connector. Business object generated using enterprise metadata discovery using multiple thread generating business name, properties conflict.
SAP V7.5.0.4_IF01JR45332During successive discovery of IDOC latest changes made on IDOC in SAP is not visible on CI.
JR45307When IDOC's are sent via qRFC channel the MB parser and adapter could not read the IDOC correctly in MQ IDOC one way pattern.
JR43619When multiple outbound modules are running in WMB, the second flow time out and in JCo trace we get thread hung exception.
JR45581When adapter inbound flows in WMB is restarted, Work Rejected Exception is seen.
Generating schema in SAP PI standards for BAPI inbound.

Send Idoc problem (adapter looking for data in the XML even if schema element it is minOccurs=0).

Send Idoc error while sending ALEAUD01.

ALEPT Inbound Idoc Data Stream for Packet Idoc does not have complete data.

ALE Inbound with PI enabled for Extended IDocs throws Exception.

Retrieve all for QISS table is returning all records irrespective of giving child field column.
JR42632When ALE QRFC with audit update is enabled, status code of AUDIT (ALEAUD) idoc on SAP is 75 instead on 64.
JR42645JCO Resource error when applications have transactionality set to yes as well as no.

Iterative Discovery (for PI enabled application) on adding RFC to an existing BOR BAPI module fails.

PI with BAPI BOR fails at the discovery EMD step and gives a NullPointerException.

Segment names in the Idoc has random number appended to it.

SAP RFC Inbound functionality gives malformed XML whilst running in asynchronous mode.

Configure two IDocs for ALE Outbound with SAP Naming Convention (PI). Then Execute both the Idocs. IDoc with the Xsd generated with random number for IDOC business object will fail.
JR42187JCo Repository cache needs to be cleared when EMD is closed.
JR42125With DateAsString set, exception is thrown when accessing uninitialised date.

Default value should be populated for attributes in the generated schemas for idocs.
JR42351Old projects using extended idoc is not working for send idoc activity.
JR43029When a Sync BAPI is discovered as Async in EMD, it fails during runtime saying TID is null.

Business object definition for 'BAPI_CUSTOMER_GETDETAIL' in namespace 'urn:sap-com:document:sap:business' not found.
Siebel V7.5.0.4_IF01
Show error on empty result set should be unchecked by default for Business Service.

Logic to check the encoding/codepage to connection establishment is not correct.

Inbound Event Monitor check box missing for Siebel Inbound scenario.
JDE V7.5.0.4_IF02
Property name for the table in selection properties screen is getting translated.
AFC V7.5.0.4_IF01JR44116SAP Node and JMS Node in same EG, will result in JMS Node getting SAP Node initial context. Need to pass initial context.
Back to the index


Adapter version packaged with WebSphere Message Broker V8.0.0.1

AdapterAPARDescription
PeopleSoft V7.5.0.2_IF01
The ASI 'KeepRelations' is not getting saved for the element which is of type child business object at top level business object after selecting from the advanced property. This has been fixed.

The ASI 'UID' is not getting saved for the element which is selected at the advanced configuraiton screen. This has been fixed.

The user is given an option to select 'Prompt for additional configuration settings when adding business object' which is not needed. The option has been removed.

A 'java.lang.NullPointerException' is thrown while moving the metadata object from left to right panel on the metadata tree panel. This has been fixed.

The ASIs related to effective date configuration are not getting saved at the top level and child business objects. This has been fixed.

Currently, keep relationship flag can only be set for the child business objects and not for grand child business objects. This has been fixed.

The list of 'Alternate key fields for RetrieveAll operation' during metadata configuration of Outbound process should display only FindKeys for component interface and not all the fields. This has been fixed.

The list of 'Fields that represent the generated key in PeopleSoft' property duing metadata configuration for outbound process should display only primary key fields. This has been fixed.
SAP V7.5.0.2_IF01
Support has been added for Password-less authentication (SSO / X509) using SAP adapter.

"The option "Send IDoc with Unparsed Data Record" option should be disabled when the "Use SAP Field Names" option is enabled in the "Configuration Properties" panel". This has been fixed.

For ALE, Invalid IDoc version does not throw an error, when IDocs are discovered by file. This has been fixed.

During trfc Inbound calls, the events are duplicated or lost. This has been fixed.
JR40936Data cross over happens when global variables are used in ABAP program. This has been fixed.
JR41367The output schema generated by the Adapter while working with PI style artifacts had a nested structure if one of the table parameter is not specified. This is encountered while working with Cast Iron. This has been fixed.
JR41368Table types in Import and Export parameters should contain an item field during PI standard artifact generation. This has been fixed.

ALE PassThrough with generic idoc fails with the following error "Business object definition for the BO in namespace not found". This has been fixed.

Advanced Configuration Properties does not contain explanation for the individual fields. This has been fixed.

During EMD create Outbound -> ALE -> Orders05/Alereq01 -> Fails with Null Pointer Exception. This has been fixed.

On using language as one of the dynamic parameter for testing it is observed that a new connection is not made in SAP for new language. This has been fixed.

SNC token not getting printed in the traces when the logging is set to finest. This has been fixed.

Optional Parameter information is not synchronized when we do iterative discovery for BAPI. This has been fixed.
JR41324In case of wrong credential it's not showing proper error message but generating FFDC on RAD/WAS. This has been fixed.
JR41974The variables in import and export parameters which contain nested table type parameter is not generated correctly during PI generation. The item element is not generated in the schema. This has been fixed.
JR42125An exception is thrown when serializing a BAPI response containing an uninitialised date field, if the schemas are generated with date field as a string parameter. This problem is now fixed to read the value from the BAPI table only for initialized fields.
Siebel V7.5.0.2_IF01
Connection retry was happening for inbound scenario in case of incorrect user or password. This has been fixed.

When retrieving events for event status 0, adapter queries the event table for all records whose event status is 0 irrespective of value of the xid. This situation occurs whenever wps is restarted after a unexpected wps process kill. This has been fixed.
JR42249Siebel inbound scenario fails if number of records exceed 10,000 in event table. This has been fixed.
JDE V7.5.0.2_IF01
When UNORDERED delivery is selected, minimum and maximum properties under "Number of connections for event deilivery" are not seen in EMD screen. This has been fixed.

User name and password fields are empty in "deployment properties screen" for outbound scenario. The values entered in discovery properties screen are not carried to deployment properties screen. This has been fixed.

JDE Adapter fails to validate the timeout property properly in deployment properties screen. A positive long value higher than MAX_INT can get cast to a negative integer and result in execptions at runtime. This has been fixed.

When JDE adapter receives an event which is not configured through EMD, it throws a NullPointerException since the BO definition for that event could not be found. This has been fixed by updating the adapter to throw ResourceException when BO definition could not be found.

NullPointerException seen in .log after discovery with XMLLists. This has been fixed.

If the server is terminated while event processing is in progress, any entries with status 1 are left undeleted from the event table. When event processing resumes after server is restarted, the event entries remain in the event table. This has been fixed.

When an instance of JDEInboundHandlerWithXid is created, a failure to create a sync event session can result in connection to JDE server not being logged off. The connection is logged off only when close() is called on the instance. But then an exception thrown by the constructor leaves no chance to call close() thus leading to connection leaks. This has been fixed.
AFC V7.5.0.2_IF01
Connection Leak during XARecovery. AFC recovery implementation modified to handle the connection leak issue.

Adapter was returning both in-doubt and new events to AFC while executing the getEvents API. This has been fixed.

NullPointerExceptions seen in the logs during Inbound processing of events during Commit and Rollback calls when event is null. This has been fixed. With the fix when an event for a requested Xid is not found in the EventStore, an XA exception will be thrown, which will be sent to the container. Depending on the error code set on the XAException based on one phase or two phase commit, the container will send an appropriate call. Example in case of two phase commit the container will reissue a commit call.

Format check for pending xids from adapter was failing, because of which recovery of pending transactions was not taking place. This has been fixed.

Events that have been rolled back during recovery are not picked up for future processing. This has been fixed.

Use of String in CheckIllegalXMLCharacter leads to creation of large number of String objects as String is immutable, heap profiling showed increasing number of String objects that are not getting cleaned up, this has a potential to cause a problem when the input size is large. This has been fixed by replacing String with StringBuffer.

When the retry connection limit is set to a value greater than 0, the connection is checked for validity, If valid, the connection is returned, else null signalling container to create a new connection. This whole process has to be repeated until a valid connection is found in the given candidate connection set before returning null. However, this stops at the first matching connection in the given set of candidate connections by the container. This has been fixed. With the fix when the "retry connection limit" is > 0, you will have the AFC component iterate through all matched managed connections and return one which is valid. If none is found to be valid it would return null.
JR42534WorkRejectedException is seen in logs, followed by adapter stopping to poll. This has been fixed. Work that was rejected was not getting removed from the workInPorgress list which was resulting in no new work to be added for submission, as a result of which adapter could not poll once a poll work was rejected.

The Adapter throws NullPointerException when updating the event persistence table with XID as null on the rollback() method of the XAResource. This has been fixed.

Adapter throws ArrayIndexOutOfBoundException during recovery, if the event being recovered does not exist in the event persistence table. This has been fixed.

While running in a local transaction in a non-auto commit mode, the adapter attempts to close the SQL connection if the SQL operations fails. This results in a DataStoreAdapterException due to attempt to closing a connection which is in transaction. The issue has been fixed so that rollback is called on the failed transaction before closing the transaction.

Adapters require to query all the events in the event persistence table. Currently there is no helper method in foundation classes to retrieve all the events. A method getAllEvents() is provided to retrieve all the events from the event persistence table.

FileNotFound issue when file URL points to file within a jar. Problem was occurring because the AFC code assumed that the URL will also point to a file, support for other protocols was not provided. This is corrected to enable support for all protocols in URL.
Back to the index


Adapter version packaged with IBM Integration Bus V10.0.0.7

Note: When upgrading to Fix Pack10.0.0.7, IBM WebSphere Adapters for SAP V7.5.0.5_IF31 introduces a higher minimum level requirement for the SAP JCo libraries of 3.0.11. We recommend that clients get the latest available SAP JCo and SAP IDOC libraries from the SAP Marketplace.

AdapterAPARDescription
PeopleSoft V7.5.0.5_IF02
Compliance for NIST SP 800-131A for PeopleSoft Adapter
SAP V7.5.0.5_IF31JR56613In production like environments, a large number of empty tags are coming which results in huge memory build up in IIB incase of Adapter AEP inbound.
Siebel V7.5.0.5_IF10
AFC Upgrade to 7.5.0.5 IF09
JDE V7.5.0.5_IF02
WebSphere Adapter for JDE to support for NIST SP800-131a Compliance.
AFC V7.5.0.5_IF09JR56308Exception is thrown in tracing code that is effective only with FINEST level logging, but executes irrespective of the logging level. Added check so that the code executes only with FINEST logging
Back to the index

[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Adapter \u2013 Non-specific","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"7.5","Edition":""}]

Document Information

Modified date:
17 August 2018

UID

swg27035733