IBM Support

WebSphere Adapters V7.0 fix list for WebSphere Message Broker V7.0

Product Documentation


Abstract

WebSphere Adapters provide periodic fixes for editions of release version 7.0. The following is a listing of those fixes alongwith the corresponding Websphere Message Broker versions with which they are packaged.

Content



The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 7.0.0.6

AdapterAPARDescription
PeopleSoft V7.0.0.6
No fix is delivered in this fix pack for this Adapter.
SAP V7.0.0.6
No event is thrown when retry limit(when the connection between the adapter and SAP server breaks and adapter tries to reconnect) exhausts. This issue has been addressed and correct event is thrown.
JR45307When a event is sent via qRFC channel from SAP to MQ - IDOC one way pattern, the parsing of the IDOC failed in second flow. This issue has now been addressed.
Siebel V7.0.0.6
No fix is delivered in this fix pack for this Adapter.
JDE V7.0.0.6
No fix is delivered in this fix pack for this Adapter.

The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 7.0.0.5

AdapterAPARDescription
PeopleSoft V7.0.0.5
A connection leak is observed during recovery. This has been fixed.

NullPointerExceptions seen in the logs during Inbound recovery in the Commit and Rollback calls when the event is null.

Failure in recovery of pending transactions. This was due to incorrect format check for pending xids, which has been fixed.

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

Illegal XML character check leads to performance degradation. This has been fixed.

If an exception occurs while trying to shutdown the EventManager, EventManager is tried to be shutdown infinitely. This has been fixed to ensure that the life cycles are in sync.

WorkRejectedException in logs, followed by adapter stopping to poll. 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. This has been fixed.

When the messageendpoint.release() method is not called for non-transacted delivery, the messageendpoint object won't be released back to the pool and the runtime easily run of memory over the a period of time. This has been fixed.

Connection retry limit is not working as expected. This has been fixed.

Failed event retry is not working as expected. This has been fixed.

Message flow hangs when the message flow is stopped during polling. This has been fixed.

Detect Illegal XML character property should not be visible during discovery in WebSphere Message Broker toolkit and Rational Application Developer. This has been fixed.

Added an additional option for handling invalid XML characters: Escape sequence illegal XML characters and log.
SAP V7.0.0.5JR38885StringIndexOutOfBoundsException is thrown when Parse option immediate or complete is selected. This has been fixed.
JR42301When transactionality is disabled, SAP adapter does not close sessions and the consequent requests fail. This has been fixed.
JR42645When applications are deployed with transaction set to yes as well as no, JCO resource error is seen if the same managed connection is being used from the connection pool. This has been fixed.
JR42177SAP Adapter thorws error if synchronous BAPI is discovered with an asynchronous. This has been fixed.
JR41981Wrong idoc number seen in SAP GUI while posting an idoc on SAP with a given idoc number. This has been fixed.
JR40936Data cross over happens when global variables are used in ABAP program. This has been fixed.

During trfc Inbound calls, the events are duplicated or lost when adapter is stopped abruptly or some exception occurs during event delivery. This has been fixed.
JR39757Return structure is not read for COMMIT and ROLLBACK BAPI's. So, an error in these structures is not captured. This has been fixed.

Added support for line type attributes in BAPI definition.
JR42132Added support for SAP Adapter Inbound Module with SNC enabled to connect with SNC credentials to SAP.

A connection leak is observed during recovery. This has been fixed.

NullPointerExceptions seen in the logs during Inbound recovery in the Commit and Rollback calls when the event is null.

Failure in recovery of pending transactions. This was due to incorrect format check for pending xids, which has been fixed.

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

Illegal XML character check leads to performance degradation. This has been fixed.

If an exception occurs while trying to shutdown the EventManager, EventManager is tried to be shutdown infinitely. This has been fixed to ensure that the life cycles are in sync.

WorkRejectedException in logs, followed by adapter stopping to poll. 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. This has been fixed.
JR42632When ALE QRFC with audit update is enabled, status code of AUDIT (ALEAUD) idoc on SAP is 75 instead on 64. This has been fixed.

FileNotFound issue when file URL points to file within a jar. This has been fixed.
JR41905ALE qRFC inbound module with audit update throws Field IDOC_DATA_REC_40 not a member of TABLES exception. This has been fixed.
JR41973SAP Adapter ale inbound module does not update control record fields not getting populated in ale audit idocs. This has been fixed.
JR41814Eventid field of adapter's inbound cbe does not contain SAPTransactionId. This has been fixed.
Siebel V7.0.0.5
A connection leak is observed during recovery. This has been fixed.

NullPointerExceptions seen in the logs during Inbound recovery in the Commit and Rollback calls when the event is null.

Failure in recovery of pending transactions. This was due to incorrect format check for pending xids, which has been fixed.

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

Illegal XML character check leads to performance degradation. This has been fixed.

If an exception occurs while trying to shutdown the EventManager, EventManager is tried to be shutdown infinitely. This has been fixed to ensure that the life cycles are in sync.

WorkRejectedException in logs, followed by adapter stopping to poll. 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. This has been fixed.
JDE V7.0.0.5
A connection leak is observed during recovery. This has been fixed.

NullPointerExceptions seen in the logs during Inbound recovery in the Commit and Rollback calls when the event is null.

Failure in recovery of pending transactions. This was due to incorrect format check for pending xids, which has been fixed.

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

Illegal XML character check leads to performance degradation. This has been fixed.

If an exception occurs while trying to shutdown the EventManager, EventManager is tried to be shutdown infinitely. This has been fixed to ensure that the life cycles are in sync.

WorkRejectedException in logs, followed by adapter stopping to poll. 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. This has been fixed.



The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 7.0.0.4

AdapterAPARDescription
PeopleSoft V7.0.0.4_IF02JR38869Adapter fails to generate decimal attribute for properties of type NUMBER/SIGNED NUMBER with decimal positions. This has been fixed.
JR38019Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the 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.

A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log.
JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException during the call to BootStrapContext.createTimer(). This has been fixed.

During Inbound polling on WebSphere Message Broker, there is a thread deadlock situation encountered if the message flow is stopped during the processing of an event. The timer mechanism used to schedule the polling thread leads to deadlock situation. The polling mechanism on WMB is now handled by using the work manager to manage and execute the polling thread.

Detect Illegal XML character property should not be visible during discovery in WebSphere Message Broker toolkit and Rational Application Developer. This has been fixed.

When the messageendpoint.release() method is not called for non-transacted delivery, the messageendpoint object won't be released back to the pool and the runtime easily runs out of memory over the a period of time. This has been fixed.

During adapter polling cycle, if the adapter is not able to establish the connection to the EIS, it does not retry specified times. This has been fixed.

During adapter polling cycle, if the adapter is not able to deliver the event successfully to the endpoint, it retries for more than the specified times. This has been fixed.
SAP V7.0.0.4_IF04
During Inbound polling on WebSphere Message Broker, there is a thread deadlock situation encountered if the message flow is stopped during the processing of an event. The timer mechanism used to schedule the polling thread leads to deadlock situation. The polling mechanism on WMB is now handled by using the work manager to manage and execute the polling thread.

Detect Illegal XML character property should not be visible during discovery in WebSphere Message Broker toolkit and Rational Application Developer. This has been fixed.
JR41288When a user tries to view the properties of a BAPI outbound modules, a NullPointerException is seen on the Properties tab. This has been fixed.
JR41296When two modules are configured with the same RFC program ID and the modules are deployed on the server, the IDocs do not reach the endpoint. This has been fixed.
JR40310SAP Adapter now provides support for selection and deselection of optional segments during ALE discovery.

Added support for Single RFC Program ID.

For BAPI Result Set, the schema is generated incorrectly - SAPReturn is not created for the added BAPI. This has been fixed.

Adapter EMD cannot load msvcrt.dll in the PATH on Windows2008 R2 Enterprise. This has been fixed.

In Case of SAP ALEPT Inbound/Outbound. An additional "sap" text will be added to the BO name when moving back and forth between screens in EMD. This has been fixed.
JR37948The BAPI Result Set does not run the Detail-RFC although many entries from the Search-RFC are returned. This has been fixed.
JR34964Adapter corrupts BCD Value in BAPI calls when locale has a comma as decimal seperator. This has been fixed.

Second EMD run with the same RAR in same workspace will fail if missing msvcr71.dll. This has been fixed.

QISS Iterative: The Configuration Properties panel is not correct. This has been fixed.
JR37643ALE inbound with namespace syntax throws exceptions.This has been fixed.

API_BANK_GetList: Adapter will display one more bank info with non-set value. This has been fixed.

Optional changing parameters not listed in the Optional parameters list. This has been fixed.
JR37652Unable to find the field - about bapi table fields built using field names. This has been fixed.
JR36753Event not found error logged in the websphere bi connector log: aep inbound. This has been fixed.

Property "waitOnCommit" should not be applicable for for ALEPT/ALE outbound EMD. This has been fixed.
JR39274ALE AUD Packet update dosent work correctly. This has been fixed.
There are few defects fixed for the BAPI interface 1- MaxLength was incorrectly set for BAPI fields.Internal length was set instead of proper length. 2- Field Type was not set correctly for table types.WhiteSpace was padded in the type returned by adapter 3- Support was added for field types like: NUMC,DEC, TIMS, INT4 etc. This has been fixed.
User trace of the adapter does not state that the file SapBusinessObjectMetadata.xsd is missing in the deployed BAR file. This has been fixed.

QISS iterative development failure. This has been fixed.
JR38117JCA SAP adapter v7 fails to load logon group members because sap 4.6 is missing a required structure in a lookup bapi. This has been fixed.
JR33249The adapter does not perform the its best when there are one or more DATE fields in the return when BAPI interface is used. This has been fixed.

When event is resubmitted from sap, its moved to the mqout,but not cleared from mq system queue. This has been fixed.

BaseException: A resource exists with a different case: when discovering BAPIs. This has been fixed.

ASI business object definition for SAP Adapter to be changed to have CHANGING PARAM enumeration. This has been fixed.

Submitted sapparse record fails at runtime- EXPRESS field accessor not found. This has been fixed.

Inbound retry connection only used JCo retry mechanism. This has been fixed.

Fetching metadataobject based on location ID for BOR does not work. This has been fixed.

Sap adapter throws npe with ale inbound when exception occurs. This has been fixed.

JCA SAP Sync inbound bapi returns the union of input and output table rows if the output table rows were modified. This has been fixed.
JR38060Easy way to retrieve the client value e.g. through connection factory without having to hardcode it. This has been fixed.

IDoc field Value are getting trimmed. This has been fixed.

BAPI: Integer field inside Structure is not created in SAP. This has been fixed.

Deploy fails after using mqsicreateconfig/ adding setter/getter for rfctracePath. This has been fixed.

QISS editBO error : editBO is erroneous when we select 2 or more BOs in QISS. This has been fixed.

Changing exception.printstacktrace to throw exception to stop adapter processing further. This has been fixed.
JR39129During AEP Inbound operation, after several unplanned SAP 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. This is the fix: 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.
JR39474The JCA SAP Adapter on V7 was failing if the segmenents that are not mandatory having maxoccurs =1 are not sent in the input xml during outbound. This has been fixed.
JR38885Adapter thows exception while fetching value for accessor EXPRESS. Adapter was incorrectly trying to fetch the value for EXPRESS, correct field is EXPRSS , This has been fixed.
JR37643ALE inbound with namespace syntax "//" is throwing exception using extension IDOCs, where the extended IDOC is having a linked IDOC who's name includes namespace in it. This has been fixed.
JR38640Adapter throws nullpointer exception if non-mandatory level 1 idoc segments are omitted when sending idoc to sap. This has been fixed.
JR38223Adapter unable to process IDocs via qRFC when the IDoc contains unreleased segments. This has been fixed.
JR38356 When using the SAP Adapter as inbound adapter, receiving following misleading error message: SAPRA001 E SAPtRFCServerDataBinding getDataObject CWYBS0499E: An invalid key was encountered while the adapter was using Resource Bundle com.ibm.j2ca.sap.LogMessages with Locale en_US. The key is either null or an empty string. Though it does not have any functional impact. This has been fixed.
JR38359If XSTRING is defined field type of the business object SAP Adapter throws an exception at runtime. ABAP data type XSTRING cannot be parsed correctly from SAP adapter at runtime. This has been fixed.

If msvcr71.dll is missing in the PATH then 2nd EMD run with the same RAR in the same workspace fails with the exception Array Out of Bounds. This has been fixed.
JR37644JCA SAP sync inbound bapi returns the union of input and output table rows if the output table rows were modified. This has been fixed.
WBI adapter did not contain the prefix sap_ which is being set by default while creating business object definitions using SAPODA. JCA adapter expecting sap_ as prefix in BO definition throws error. New Parameter "Default BO Prefix" is introduced in Activation Spec at runtime as part of the fix.
JR36754Even when the trace is not enabled i.e, with just *=info,detailed logging is logged into the systemout log. This is now fixed.
JR33249When there are one or more DATE fields in the return BAPI, the adapter needs to be tuned for better performance. This is now fixed.
Connections to SAP are not closed when BAPI calls fail. This is now fixed.

Concurrent requests to SAP Adpater fail with JCO_ERROR_CONCURRENT_CALL. This is now fixed.
JR37070Message flow does not stop on HP-UX. This is now fixed.
JR37493Detailed errors not written to syslog. This is now fixed.
JR37494SAP adapter throws npe with alein when exception occurs thus masking the original exception. This is now fixed.
JR37349IDOC datarecord values are getting truncated on non-unicode systems. This is now fixed.
SAP outbound ale/bapi connection lost and transaction goes stateless mode. This is now fixed.
JR36874IllegalStateException is thrown as AFTER_DELIVERY was called but message delivery didnt started with BEGAN_DELIVERY. This is now fixed.

Connections to SAP are not reset if JCoReset Connection is checked and rollback happens. This is now fixed.

No address data returned with an application containing 3 BAPIs or more. This is now fixed.

SAP Adapter throws ClassCastException when reading annotation in Synchronous BAPI Inbound with Lazy BO parsing mode, when the Adapter RAR is deployed at Node level. During Node level deployment, the default BO parsing for runtime is Eager parsing. Hence, properties generated in Lazy parsing mode will encounter issue while reading annotations. The issue is resolved by reading the annotations accordingly.
JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException will be thrown during the call to BootStrapContext.createTimer(). This has been fixed.
JR38019Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the 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.

A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log.
Siebel V7.0.0.4_IF02
When running EMD discovery wizard for Business Service Outbound, faults are getting generated for WMB (faults are applicable only for WPS). This has been fixed.

During Inbound polling on WebSphere Message Broker, there is a thread deadlock situation encountered if the message flow is stopped during the processing of an event. The timer mechanism used to schedule the polling thread leads to deadlock situation. The polling mechanism on WMB is now handled by using the work manager to manage and execute the polling thread.

Detect Illegal XML character property should not be visible during discovery in WebSphere Message Broker toolkit and Rational Application Developer. This has been fixed.

When the messageendpoint.release() method is not called for non-transacted delivery, the messageendpoint object won't be released back to the pool and the runtime easily runs out of memory over the a period of time. This has been fixed.

During adapter polling cycle, if the adapter is not able to establish the connection to the EIS, it does not retry specified times. This has been fixed.

During adapter polling cycle, if the adapter is not able to deliver the event successfully to the endpoint, it retries for more than the specified times. This has been fixed.

In WPS, adapter doesn't handle business error from Siebel server as fault. User cannot use BPEL to handle these business errors. This has been addressed by adding a new fault "InvalidRequestFault" for Siebel Exception.
JR39485Some field values in child BOs having "association" relationship with their parent BOs are missed during runtime. This has been fixed.
Siebel adapter ignores fields which contains string 'SBL-DAT' in repsonse message. This has been fixed.

XML character filter set properties in EMD will not take effect, if either of option B or C is selected; it will always be A at the end of the EMD run. The code has been fixed to preserve the selection in EMD.
JR39417When multiple/array requests are sent in business service, the adapter only returns one response. This has been fixed.
JR38016Siebel Adapter creates null as data type for some arguments of business services after metadata discovery. This issue is caused due to "Inactive" integration objects(IOs). The "inactive" IOs are now filtered out during the metadata discovery to fix this problem.
JR36907Adapter ignores fields with empty string value in both request and response of business services calls. This has been fixed. Added empty string value handling in business services request part. Added a property includeEmptyFields in MCF to determine whether adapter returns empty string fields in response BO. Activate this feature by setting the property to true.
JR38003If Siebel adapter is active and is idle for a long time (resonateSupport = true), then an error will be thrown in the next attempt to connect to the EIS. This has been fixed.
JR38019Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the 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.
JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException during the call to BootStrapContext.createTimer(). This has been fixed.
JDE V7.0.0.4_IF01
When XMLList BO is selected in EMD, NullPointerException is found in the .log file in the workspace/.metadata directory. This has been fixed.

A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log.
JR38019Adapter uses a single polling thread, which polls as per the poll frequency interval. The polling thread will be only submitted once when the adapter starts up. When there are no events, the polling thread will be hung up after 15-20 minutes, which invokes a warning message. This has been fixed by using the 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.
JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException during the call to BootStrapContext.createTimer(). This has been fixed.
JR38857When using JDE adapter to pull data into WPS with special characters, a ResourceException is thrown. For an accent on the E in HELLO, the string in the XML reads H\u00C9LLO. This has been fixed by encoding the input xml using "UTF-8" by default.

"Folder of failed events", the whole BO schema and data will be put into the folder. This assumes application having privilege to read and write local file of the broker. This has security risks. To address this, the "Folder of failed events" has been removed, and the event data is saved to the Event Data column of the persistent event store.

Timeout and MaxRecord are interaction specification properties only valid for XML List RetrieveAll operations. However they are shown when no XML List BO is selected. This has been fixed by hiding these properties when no XML list BO is selected.
JDE adapter does not acknowledge and delete processed event from event store on adapter restart. This has been fixed.

Added support for WebSphere Message Broker.
JR37204JDE Adapter does not support a container type Real-Time event with only one child. This has been fixed.
JR37670The migration code does not migrate JDE key references from first method call in a batched group to the rest of the group. This has been fixed.
JR36794Migration tool throws StringIndexOutOfBound exception when doing migration. This has been fixed.
JR38754When migrating from WICS environment to WPS 7.0 the JDE Adapter failed to generate some of attributes. The migration code path has been fixed.

When migrating from version 6.2 to 7.0, migration tool throws MigrationException. This has been fixed.



The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 7.0.0.3

AdapterAPARDescription
PeopleSoft V7.0.0.3_IF03JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException will be thrown during the call to BootStrapContext.createTimer().
WMB currently does not return a timer in createTimer() call. The issue has been resolved by handling the exception at the adapter end and creating a Timer instance to handle the inbound polling.

Detect Illegal XML character feature does not apply to WebSphere Message Broker runtime. This property should not be visible in the external service wizard during Inbound and Outbound on WMB.
The property is removed from the external service wizard when the tooling is Message Broker toolkit.
SAP V7.0.0.3_IF14
Adapter currently doesnt support flatfile format IDocs.
Support for flat file IDoc is provided as an enhancemnent in EMD.Option provided in EMD to select flat file IDoc.If a user select flat file IDoc in EMD , field appears to select IDoc version and enter the delimiter value.IDoc Version can be left blank if unreleased segment also needs to be discoverd. If IDoc version selected in EMD is less than the version of IDoc sent from SAP,extraneous data if present in segments would be truncated automatically.

Detect Illegal XML character feature does not apply to WebSphere Message Broker and WebSphere Application server runtimes. This property should not be visible in the external service wizard during Inbound and Outbound on WMB and RAD.
The property is removed from the external service wizard when the tooling is Message Broker toolkit or Rational Application Developer.

During Inbound polling on WebSphere Message Broker, there is a thread deadlock situation encountered if the message flow is stopped during the processing of an event.
The timer mechanism used to schedule the polling thread leads to deadlock situation. The polling mechanism on WMB is now handled by using the work manager to manage and execute the polling thread.
JR40048Adapter throws an exception for a data type having number of characters(actual length) more than the output length of the data type.
Websphere Adapter for SAP currently calculates the max length based on the "Output Length" of the data type created, but it should be calculated as per the length of the datatype or number of characters. Now, it is resolved.
JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException will be thrown during the call to BootStrapContext.createTimer().
WMB currently does not return a timer in createTimer() call. The issue has been resolved by handling the exception at the adapter end and creating a Timer instance to handle the inbound polling.
JR39474The JCA SAP Adapter on V7 fails if the segmenents that are not mandatory, having maxoccurs =1 , are not sent in the input xml during outbound. This has been fixed.
JR38117The JCA SAP Adapter on V7 is unable to make use of inbound loadbalancing via the Logon group. The adapter fails as it performs a lookup to query all active SAP Application Servers that are members of the target Logon Group. The failure is caused by SAP 4.7 and its BAPI, 'TH_SERVER_LIST' missing a structure for 'LIST_IPV6'.
The JCA SAP Adapter code is now fixed so that even on SAP 4.6 it can perform the inbound load balancing.
JR38885Adapter thows exception while fetching value for accessor EXPRESS. This has been fixed.
JR37643ALE inbound with namespace syntax "//" throws exception using extension IDOCs, where the extended IDOC is having a linked IDOC who's name includes namespace in it. This has been fixed.
JR38223Adapter unable to process IDocs via qRFC when the IDoc contains unreleased segments. This has been fixed.
JR38356When using the SAP Adapter as inbound adapter, receiving following misleading error message: SAPRA001 E SAPtRFCServerDataBinding getDataObject CWYBS0499E: An invalid key was encountered while the adapter was using Resource Bundle com.ibm.j2ca.sap.LogMessages with Locale en_US. The key is either null or an empty string. This has been fixed.
JR38359If XSTRING is defined field type of the business object SAP Adapter throws an exception at runtime. ABAP data type XSTRING cannot be parsed correctly from SAP adapter at runtime. This has been fixed.

If msvcr71.dll is missing in the PATH then 2nd EMD run with the same RAR in the same workspace fails with the exception Array Out of Bounds. This is now fixed.
JR37644JCA SAP sync inbound BAPI returns the union of input and output table rows if the output table rows were modified.This has been fixed.

WBI adapter did not contain the prefix sap_ which is being set by default while creating business object definitions using SAPODA. As JCA adapter expects sap_ as prefix in BO definition it throws error. This has been fixed.
JR36754Even when the trace is not enabled i.e, with just *=info,detailed logging is logged into the systemout log. This has been fixed.
JR33249When there are one or more DATE fields in the return BAPI, the adapter needs to be tuned for better performance. This has been fixed.
Connections to SAP are not closed when BAPI calls fail. This has been fixed.

Concurrent requests to SAP Adpater fail with JCO_ERROR_CONCURRENT_CALL. This has been fixed.
JR37070Message flow does not stop on HP-UX. This has been fixed.
JR37487When a failed to deliver event is resubmitted from sap, its moved to the mqout,but not cleared from MQ system queue. This has been fixed.
JR37493Detailed errors not written to syslog. This has been fixed.
JR37494SAP adapter throws NPE when exception occurs thus masking the original exception. This has been fixed.
JR37349IDoc datarecord values are getting truncated on non-unicode systems. This has been fixed.
SAP Outbound ALE/BAPI connection lost and transaction goes stateless mode. This has been fixed.
JR36874IllegalStateException is thrown as AFTER_DELIVERY was called but message delivery didnt started with BEGAN_DELIVERY. This problem is now fixed, BEFORE_DELIVERY and AFTER_DELIVERY are paired.

Connections to SAP are not reset if JCoReset Connection is checked and rollback happens. This has been fixed.

No address data returned with an application containing 3 BAPIs or more. This has been fixed.
Siebel V7.0.0.3_IF08
Detect Illegal XML character feature does not apply to WebSphere Message Broker runtime. This property should not be visible in the external service wizard during Inbound and Outbound on WMB.
The property is removed from the external service wizard when the tooling is Message Broker toolkit.

During Inbound polling on WebSphere Message Broker, there is a thread deadlock situation encountered if the message flow is stopped during the processing of an event.
The timer mechanism used to schedule the polling thread leads to deadlock situation. The polling mechanism on WMB is now handled by using the work manager to manage and execute the polling thread.
JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException will be thrown during the call to BootStrapContext.createTimer().
WMB currently does not return a timer in createTimer() call. The issue has been resolved by handling the exception at the adapter end and creating a Timer instance to handle the inbound polling.
JR39485Some field values in child BOs are missed in runtime. Those child BOs have "association" relationship with their parent BOs. This has been fixed.
JR39417Send multiple/array request in business service, but adapter only has one response. This has been fixed.
Siebel adapter ignores fields which contains string 'SBL-DAT' in repsonse message. This has been fixed.
JR38016Siebel Adapter creates null as data type for some arguments of business services after metadata discovery. This has been fixed.

XML character filter set properties in EMD will not take effect, if you select option B or C, it will always be A after EMD. This has been fixed.
JDE V7.0.0.1_IF07
Detect Illegal XML character feature does not apply to WebSphere Message Broker runtime. This property should not be visible in the external service wizard during Inbound and Outbound on WMB.
The property is removed from the external service wizard when the tooling is Message Broker toolkit.

During Inbound polling on WebSphere Message Broker, there is a thread deadlock situation encountered if the message flow is stopped during the processing of an event.
The timer mechanism used to schedule the polling thread leads to deadlock situation. The polling mechanism on WMB is now handled by using the work manager to manage and execute the polling thread.
JR39773Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException will be thrown during the call to BootStrapContext.createTimer().
WMB currently does not return a timer in createTimer() call. The issue has been resolved by handling the exception at the adapter end and creating a Timer instance to handle the inbound polling.
JR38016JDE adapter does not acknowledge and delete processed event from event store on adapter restart. This has been fixed.



The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 7.0.0.2

AdapterAPARDescription
PeopleSoft V7.0.0.3JR35982PeopleSoft Adapter fails with JOAException when trying to set get keys a second time when doing Update operation for some Component Interfaces. This has been fixed.
JR35830When Child BO has no primary key ASI, Update operation cannot succeed in some cases. This has been fixed. Child BOs with no primary key ASI are supported.
JR35978When adapter gets ARM transaction factory name to process ARM transaction, a WebSphere Application Server internal private API is used for it, which need to be replaced with public interfaces. This has been fixed.

When IgnoreEffectiveSequence and InsAtOldestEffDtPos are set to true and EIS has no child, if input data contains child, the adapter fails when trying to create the child. This has been fixed.

When KeepRelations is false, and EIS has some children but input data has no child, Update operation returns incorrect response that has a dummy child, sometimes even returns a dummy child with a non dummy grand child. This has been fixed.
JR36715If a property is not getkey, but is key, after running ESD, PrimaryKey ASI will be set to true for this property. This leads to runtime error when calling set method for this property. This has been fixed.

When doing update for some specific CI, update will take no effect. This has been fixed. A flag has been added to differentiate whether Peoplesoft record is used in producing command or generating response. The extra get operation is supposed to be performed when generating response.
SAP V7.0.0.3
The xsd schema generated by the JCA SAP ESD marks some control fields as required. However, the adapter treats these fields as optional. This problem is now fixed.
JR36038Even when the message flow is stopped i.e., adapter is stopped, connections are still active when tested using SM59. This problem is now fixed.
JR36606When client tries to create a SAP-Outbound-Adapter From WebSphere Message Broker Toolkit Adapter V7 Wizard they get error message: com.ibm.adapter.framework.BaseException. This problem is now fixed.

SAP Adapter V7 fails connecting to non-unicode SAP Systems when the password is entered in lower case. This problem is now fixed.
JR34424When using a registered namespace on the SAP system for BAPI artifacts, the SAP adapter throws the following exception: "Business Object definition for 'SapStfcWriteToTopicWrapper' in namespace ...not found" This problem is now fixed.
JR36123SAP Adapter Outbound QISS interface: only the first of several child tables is retrieved. The other child table remain null. This problem is now fixed.
JR36095Using ALE Passthrough for outbound messages going to SAP, not all the fields are set SAP throws an error and the SAP request node gets the error about those missing values. This problem is now fixed.
JR36223The client is using the JCA SAP Adapter V7 and is not able to extend or add to their existing EIS artifacts using the WebSphere Adapter's 'Iterative Development' feature. This problem is now fixed.
JR35371IDocs sent from SAP EIS from AEP custom handler contain only CxIgnore values. This problem is now fixed.

BOR discovery for all filter patterns not containing asterisk does not work. This problem is now fixed.

In SAP Adapter, BAPI ZPM_TEST_RFC outbound generates the following FFDC entry: Field NUMBER not a member of BAPIRETURN. This problem is now fixed.

Iterative discovery does not work for BOR. This problem is now fixed.

Set "*Cross" as BOR filter, BAPI which begin with Cross, such as "Cross-System command", will be listed. This problem is now fixed.

The description of BAPI in "Find Objects in Enterprise System" should be divided by "/" or something else. This problem is now fixed.

SAP Adapter to provide an optional feature for preserving leading spaces in the IDoc fields. This support has now been added.

In EMD, the panel's progress bar information is not translated accordingly. This problem is now fixed.

No CBE 'delivery.entry' event for SAP Inbound event delivery. This problem is now fixed.

SAP Adapter CBEs must have correlation in order to track the events in a flow. This support has now been added.

Dummykey behavior is different from basic IDoc to extension IDoc. This problem is now fixed.

When selecting one basic IDoc and one extension IDoc or two basic IDocs to generate artifacts, the generated method bindings are not the expected ones. This problem is now fixed.

For multi-IDocs, in top level BO the generated methodname attribute belonged to operation element does not reflect the value, which fills during EMD process in Specify Composite Property panel. This problem is now fixed.

When load balancing is enabled - can not deploy the sapinput note if number of listeners is set to 1. This problem is now fixed.
JR36754Even when the trace is not enabled i.e, with just *=info, detailed logging is logged into the systemout log. This problem is now fixed.

JCO_ERROR_SESSION_REF_NOT_VALID error happens when testing ALE inbound. This problem is now fixed.

Event not found error logged in the WebSphere bi connector logs -aep module. This problem is now fixed.
JR33249Performance fixes along with the stringoutofbounds exception fix.

Sending out the BAPI request to SAP server with default MaxRows value, when the request is sent out, then un-deploying this app from WebSphere Process Server runtime, but the log messages still are printed. This problem is now fixed.
JR35842With WMB Toolkit V6.1 and SAP Adapter V6.1, the ESD Wizard shows the option to receive an individual message per IDoc sent but it cannot be changed. This problem is now fixed.

With some certain steps, AEP inbound EMD fails with a "java.lang.RuntimeException: Unable to create definitions null" error. This problem is now fixed.

The finish button in the last panel of ALEPT iterative does not work correctly. This problem is now fixed.

If the first run of the discovery wizard contains a File, Folder or Schema type property, subsequent iterative discovery wizard runs fail to launch and an error message is displayed to the user. This problem is now fixed.
Siebel V7.0.0.3
Some extra null BOs and fields are returned in the inbound processing of business service. Fixed the conversion problem between SiebelPropertySet, which is returned by business service, and BO.
JR35750Some field value in child BOs are missed during runtime for child BOs that have "simplelink" relationship with their parent BOs. This has been fixed by activating all fields in child BOs before all field values are retrieved.
JDE V7.0.0.1_IF03
JDE adapter supports outbound and inbound interaction with WMB broker.

When the 'Folder of failed events' property is set, the whole BO schema and data will be put into the folder. This assumes application having privilege to read and write local file of the broker. This has security risks. This property has now been removed and the event data is now saved in the Event Data column of the persistent event store.

Timeout and MaxRecord are interaction specification properties only valid for XML List RetrieveAll operations. However they are shown when no XML List BO is selected. These properties are now hidden when no XML List BO is selected.
JR37204JDE adapter does not support a container type real-time event with only one child. The adapter now supports a container type Real-Time event with only one child.



The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 7.0.0.1

AdapterAPARDescription
PeopleSoft V7.0.0.1
Adapter will not use connection pool for event delivery if max connection number is 1 and delivery mode is "UNORDERED". In this situation, multiple thread will share one connection without thread safe mechanism, which will cause exception. This has been fixed.

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.This has been fixed.

When adapter gets ARM transaction factory name to process ARM transaction, a WebSphere Application Server internal private API is used for it, which need to be replaced with public interfaces. This has been fixed.

When adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException. This has been fixed.

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.This has been fixed.

When adapter caches some BeanTypes that have a great deal of properties, Java™ OutOfMemmory Exception be thrown during performing inbound and outbound operation with some events (persisting 20-50 times in WebSphere Application Server broker). This has been fixed.
SAP V7.0.0.1
A java.lang.NullPointerException is thrown when an application is configured for AEP Inbound processing with Non Unicode SAP Systems This problem is now fixed.

With the AEP interface: Event data being retuned as blank even though there is data available for the fields. This problem is now fixed.

BAPI Work Unit doesnt update data successfully when JCO Reset is enabled This problem is now fixed.

No value fields are being set to "CxIgnore" during AEP Inbound This problem is now fixed.

AEP - Delete archived events are not being deleted correctly This problem is now fixed.

AEP - Delete queue events not working This problem is now fixed.

AEP - Log updates not working This problem is now fixed.

Error appear when invoke BAPI update two times with JCO reset on WebSphere Message Broker V7 This problem is now fixed.

Inbound Processing with extended IDocs does not work This problem is now fixed.

Error message when building a new SAP request adapter connection (Changing Parameters). This problem is now fixed.

Empty tags are included in the message if the fields are followed by other populated fields, but all unpopulated fields at the end of a segment do not have empty tags outputted xml. This problem is now fixed.

BCD Value corrupt during a BAPI call when the underlying locale uses COMMA (,) for a decimal DOT (.) This problem is now fixed.

SAP Input node doesnt work correctly under SAP Load Balancing setup This problem is now fixed.

When an ALE IDoc processing is not succesful, two ALE AUD IDocs, one for failure and success each are getting created. This has been fixed.

IDoc Data from the second/child segments is not processed - AEP Oubound This problem is now fixed.

When you send an IDoc that is not properly constructed from WebSphere Message Broker to SAP using SAP Adapter, the SAP Adapter does NOT pass it over to SAP at all (which is correct behaviour) - but does NOT throw any error message about the fact that the IDoc is not correct. This has to be fixed, so that the adapter will report an error when it receives an invalid IDoc. This problem is now fixed.

Retries not stopping though the adapter is stopped This problem is now fixed.

When connection to SAP System with the default value as sapgw00 in EMD, but the system Number is 02, user need to modify it manually to sapgw02 in the last panel of EMD. This problem is now fixed.

Consecutive requests followed by a failed AEP outbound request FAIL This problem is now fixed.

Load balancing-Not required connect properties should be disabled This problem is now fixed.

Problems with BAPI result set call with a queryBO that has multiple entries This problem is now fixed.

The SAP BAPI fault to show the right error code returned from SAP This problem is now fixed.

The SAP BAPI fault shows only the ID and doesnt include the Number This problem is now fixed.

When BO name is same and BO namespace is different, inbound work may be failed This problem is now fixed.

Adapter will encoutner NPE after restart the app on server. This problem is now fixed.

Memory leak in WebSphere Application Server Inbound with BeanType This problem is now fixed.

Printing out the AdapterFoundationClasses version in the Logs/traces is not available. This problem is now fixed.
Siebel V7.0.0.1
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.This has been fixed.

When adapter gets ARM transaction factory name to process ARM transaction, a WebSphere Application Server internal private API is used for it, which need to be replaced with public interfaces. This has been fixed.

Adapter will not use connection pool for event delivery if max connection number is 1 and delivery mode is "UNORDERED". In this situation, multiple thread will share one connection without thread safe mechanism, which will cause exception.This has been fixed.

When adapter creates two or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException.This has been fixed.

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 This has been fixed.

When the name of Integration object (IO) and Integration Component (IC), the schema file for service binding will missed after EMD. Added a prefix "BS" for schema file if generated file has same file name and has been fixed.

During EMD, NullPointerException will occur if an integration object (IO) has been chosen as input for several times. Added a filter to handle duplicated IO selections and has been fixed.

If primary key field in WBIA adapter project is not the same as EIS side, runtime will have error after migration to JCA.This has been fixed.

When adapter caches some BeanTypes that have a great deal of properties, Java OutOfMemmory Exception be thrown during performing inbound and outbound operation with some events (persisting 20-50 times in WebSphere Application Server broker).This has been fixed.

[{"Product":{"code":"SSMKUK","label":"WebSphere Adapters Family"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2018

UID

swg27019165