Product Documentation
Abstract
WebSphere Adapters provide periodic fixes for editions of release version 6.1. The following is a listing of those fixes alongwith the corresponding Websphere Message Broker versions with which they are packaged.
Content
Adapter fixes packaged with WebSphere Message Broker 6.1.0.11
Adapter fixes packaged with WebSphere Message Broker 6.1.0.10
Adapter fixes packaged with WebSphere Message Broker 6.1.0.9
Adapter fixes packaged with WebSphere Message Broker 6.1.0.8
Adapter fixes packaged with WebSphere Message Broker 6.1.0.7
Adapter fixes packaged with WebSphere Message Broker 6.1.0.5
Adapter fixes packaged with WebSphere Message Broker 6.1.0.4
Adapter fixes packaged with WebSphere Message Broker 6.1.0.3
Adapter fixes packaged with WebSphere Message Broker 6.1.0.2
Adapter fixes packaged with WebSphere Message Broker 6.1.0.1
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 6.1.0.11
| Adapter | APAR | Description |
| SAP v6.1.0.6_IF09 | JR40327 | Useless unique IDs for BAPI element & Array Index OOB exception |
| JR40048 | Websphere Adapter for SAP 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. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 6.1.0.10
| Adapter | APAR | Description |
| SAP v6.1.0.6_IF07 | JR38640 | Adapter throws NullPointer exception if non-mandatory level 1 IDoc segments are omitted when sending IDoc to SAP. This has been fixed. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 6.1.0.9
| Adapter | APAR | Description |
| SAP v6.1.0.6_IF06 | When an IDoc is sent from SAP to adapter, field's value are getting trimmed. An optional check-box is provided in EMD run to configure if data needs to be trimmed or not. Check-box is set to TRUE (which means trim is enabled) by default. Set the check-box to FALSE if leading spaces in the IDoc field need to be preserved. | |
| JR37259 | AEP INBOUND:BAR file cannot be deployed after setting any property using mqsicreateconfig command. This has been fixed. | |
| JR36753 | The WebSphere BI connector log prints the statement evt_id xxxx not found in the table /CWLD/EVT_Cur incorrectly, though the event exists and is processed. This has been fixed. | |
| JR36754 | Even when the trace is not enabled i.e., with just *=info, detailed logging is logged into the systemout log. This has been fixed. | |
| JR33249 | When there are one or more DATE fields in the return BAPI, the adapter needs to be tuned for better performance. This has been fixed. | |
| JR30725 | When the adapter is deployed at node level, all applications using the adapter receive events instead of just the end point having the same ASpec. This has been fixed. | |
| Siebel v6.1.0.6_IF01 | If Siebel adapter is active and is idle for a long time(resonateSupport = true), then an error will be thrown in the next attempt for connection. This has been fixed. | |
| JR36029 | During inbound processing, when the delivered BO has multiple children, some child BOs are null. This is due to some conversion error from SiebelPropertySet to BO if the BO has multiple children BO. This has been fixed. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 6.1.0.8
| Adapter | APAR | Description |
| SAP v6.1.0.6_NF01 | JR35905 | With SAPInput node, if the client has number of listeners set to 1, the adapter does not deploy and throws connection pool exhausted error. This has been fixed. |
| JR36038 | Connections still remain active even when the adapter is stopped. This has been fixed. | |
| JR35446 | Event data is not processed by the adapter during inbound when the SAP System participates in Load Balancing. This has been fixed. | |
| AEP transports - The logging is not being done correctly; it points to the old ABAP code. This is now fixed with the new set of AEP Transports provided. | ||
| AEP transports- when delete queue events operation is executed, adapter does not delete from the correct event table. This is now fixed with the new set of AEP Transports provided. | ||
| AEP transports - delete archive events is not deleting from correct archive table. This is now fixed with the new set of AEP Transports provided. | ||
| JR34901 | Event data is returned as blank even though there is data available for the fields. This has been fixed. | |
| JR34928 | Whenever there is no value for a field being sent to an AEP inbound node, the value is being set to CxIgnore. | |
| JR34964 | When using BAPI outbound with a BCD field, adapter causes corruption of the value for certain locales. This has been fixed; the adapter now sets the BCD value independent of locale and always use dot(.) as decimal seperator. | |
| JR35006 | For stand-alone deployment, after the application is restarted, a NullPointerException will be thrown when the adapter tries to query the ASI Information from cache. This has been fixed. The adapter does not use stale data from cache after the application is restarted. | |
| JR35196 | During adapter startup, any pre-queued events existing in the event table are not getting processed. This has been fixed. | |
| JR35479 | ALE pass through outbound does not throw any exception in case of malformed IDoc or incorrect partner charset value. Error handling is now fixed; adapter also sets the encoding to UTF-8 by default if SAP system is in unicode. | |
| JR33573 | With delete operation, some of the segment fields with no data being sent are still coming out as CxIgnore. This has been fixed. | |
| JR35631 | 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. | |
| JR35738 | AEP INBOUND: Unpopulated fields are being outputted incorrectly. This has been fixed. | |
| JR35482 | In WMB while running ALE inbound, user is unable to select the property to split IDOc packet. This has been fixed. A checkbox has been added now which can be configured to send IDoc as single or packet. | |
| JR36095 | Using 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 following error about those missing values: com.ibm.j2ca.sap.exception.SapAleOutboundException: Value ' ' cannot be converted to NUM type at field PSGNUM' (CHARACTER). This has been fixed. | |
| SAP adapter can send IDoc to endpoint in inline format (For example: each Control record 524 bytes and Data record 1063 bytes) only. Support for flat file IDoc is provided as an enhancemnent in EMD. Option has been provided in EMD to select flat file IDoc. If a user selects flat file IDoc in EMD, a 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. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 6.1.0.7
| Adapter | APAR | Description |
| PeopleSoft v6.1.0.4 | When using "unordered" delivery mode with "maximum connections" larger than 1, connection pool will not be used during the first poll cycle and NPE will be thrown. A fix has been delivered to have the ActivationSpec for one specific endpoint to be configured before polling for the first cycle, thus enabling connection pool be used for "unordered" mode. | |
| When two different business objects have the same name but different namespaces, inbound/outbound operations may fail. This has been corrected such that now the adapter not only uses BO name but also the namespace to differentiate between BOs during runtime. | ||
| SAP v6.1.0.6 | SAP adapter does not wait for sometime before invoking BAPI_TRANSACTION_COMMIT. This has been fixed. | |
| Support for multiple IDocs has been added in ALE pass through outbound. | ||
| JR34939 | Field naming of IDoc control record and data record cannot be handled independently. This has been fixed. Now, control record can be generated using field name and data record using field description and vice versa. | |
| When a BAPI contains fields of type String, the request fails with "No accessor-to-data mapping" found error. This has been fixed. | ||
| JR31207 | The adapter does not correctly handle stale connections to the SAP EIS. This is now fixed. The adapter also does a retry if the connection is invalid during request processing. | |
| JR34652 | SAP adapter throws error message when building a new SAP request adapter connection if BAPI contain changing parameter. This has been fixed. | |
| JR34424 | BAPI Inbound with namespace syntax "/<ABC>/<XYZ>" throws exceptions. This has been fixed. | |
| JR34330 | ALE Inbound with Extended IDocs fails when using the qRFC protocol. This has been fixed. | |
| JR34365 | 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. The following three options are provided now: 1.BEFORE_AND_AFTER - Sends empty field tags before and after one more populated IDoc field. 2.ONLY_BEFORE - Sends empty field tags before one more populated IDoc field. 3.ALL_UNPOPULATED_FIELDS_SEGMENTS - Sends empty field tags before and after unpopulated fields as well as segments. This is highly performance intensive and meant to be selected if there are no alternatives. | |
| JR32699 | Updating JCA SAP adapter to 6.1.0.4 causes SAPALEOutboundException when Enterprise Service Discovery has been run with adapter 6.1.0.3 version. This has been fixed. | |
| JR33266 | JCA SAP Adapter fails to receive a passthrough IDoc with Czech characters; instead they are replaced with '?'. This has been fixed. | |
| JR33557 | While running ALE pass through inbound adapter sends IDoc packet to endpoint with duplicate control record. This has been fixed. | |
| JR33951 | Maxlength asi property is incorrectly set to 0 for BAPI OUT and INOUT parameters. This has been fixed. | |
| JR33598 | The adapter always generates the Business Object attributes names in Camel casing inspite of the setting for "Use SAP Field names" checkbox during Metadata Discovery. This is now fixed. The adapter now provides options to choose casing for the Control Record and the Data Record separately. | |
| Siebel v6.1.0.6 | JR33660 | The complete list of Business Objects was not being retrieved from the Siebel system during discovery. This has been fixed. |
| When two different business objects have the same name but different namespaces, inbound/outbound operations may fail. This has been corrected such that now the adapter not only uses BO name but also the namespace to differentiate between BOs during runtime. | ||
| When using "unordered" delivery mode with "maximum connections" larger than 1, connection pool will not be used during the first poll cycle and NPE will be thrown. A fix has been delivered to have the ActivationSpec for one specific endpoint to be configured before polling for the first cycle, thus enabling connection pool be used for "unordered" mode. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker 6.1.0.6
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker version 6.1.0.5
| Adapter | APAR | Description |
| SAP v6.1.0.5 | JR31250 | Any activity in a listener thread causes a state change for other active threads. This is fixed. |
| JR32057 | Incorrect tags in messages for successful BAPI outbound. This is now fixed. | |
| JR31171 | The RFC function used to read data from SAP could not handle non-unicode data. The adapter now correctly handles non-unicode data. | |
| JR31759 | The adapter incorrectly handles time fields in BAPI. This has been fixed. | |
| JR31614 | The adapter incorrectly handles decimal values in BAPI. This has been fixed. | |
| Siebel v6.1.0.5 | JR32073 | When processing EMD for BO, if there are special characters in BC's attributes and short name is selected, BaseException will be thrown. This has been fixed by adding support for special characters. |
| JR32074 | When generating BO, the Calculated fields can't be generated. This has been fixed. | |
| JR31795 | During inbound, if the database crashes, the adapter can't resume polling after the database's recovery. This has been fixed. | |
| Adapters don't clean up stale connection after EIS shutdown. This has been fixed by enabling connection validation before an outbound process. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker version 6.1.0.4
| Adapter | APAR | Description |
| Siebel v6.1.0.4 | JR30832 | Failed to retrieve All View with a child BO that has one child BO itself. This has been fixed. |
| JR30339 | ESD fails with error when parent and child Siebel business components are selected. This has been fixed. | |
| Null namespace support added. | ||
| JR31009 | EMD can not work well with Business object having hyphen characters in its name. This has been fixed. | |
| JR30855 | The adapter goes into an infinite loop when assuredOnceDelivery is set to false. This has been fixed. | |
| Warning messages of the kind, "Method is deprecated" have been removed. | ||
| The progress monitor in the first screen of the EMD has hard coded english text. This has been corrected | ||
| Exception handling has been improved so that the work controller is notified appropriately of the work completion status. | ||
| BusinessObjectNotFound exception is thrown because incorrect classloader is used to load the BOs. This has been fixed. | ||
| SAP v6.1.0.4 | JR29552 | The adapter returns old information/data from the SAP EIS. This has been fixed. |
| JR29553 | JCO Connection pool error during server restart. The adapter now uses a unique pool name for all applications. | |
| When a simple BAPI call fails, the adapter does not rollback to remove table locks. This has been corrected. | ||
| ALE inbound fails with a null pointer exception after applying JR26701 on WebSphere Process Seerver. This has been fixed. | ||
| JR29609 | The adapter does not support more than 4 BAPIs in the EMD Object selection screen. This has been addressed. | |
| JR29885 | Commit or Rollback on BAPI should be done by the container and not by the adapter. This has been addressed. | |
| JR29884 | When the Import or Export section of a BAPI (instead the Tables section) contains tables, then a BAPI fails. The adapter now supports Table parameters in the Import/Export section. | |
| JR29741 | The adapter EMD run throws "Error: nothing found" while discovering BAPIs. This has been fixed. | |
| JR29879 | Decimal fields are not saved in BAPIs. This has been corrected. | |
| JR30118 | When more than one inbound application is running, during startup an error occurs saying the JCO pool name already exists. The adapter now creates unique pool names for each inbound module. | |
| JR30119 | ALE inbound listener threads still remain and not killed after the application is stopped. This has been fixed. | |
| JR30824 | ESD fails if 2 BAPIs having same field names separated a '_'. This has been fixed. | |
| JR30836 | Adapter throws an error if the data record is not populated. This has been fixed. | |
| The Adapter does not throw an exception if the gateway host setting is wrongly configured. It only logs a trace of the issue - thus the Message Broker cannot catch an exception to be able to report the issue to the user. This has been fixed. | ||
| Building Connection with Async q/tRFC BAPI with Out Params gives bad error. This has been fixed. | ||
| SAPManagedConnectionFactory.isGatewayConfigured thorws a NullPointerException. This has been fixed. | ||
| Executing SQI with BG throws exception. This has been fixed. | ||
| JR31245 | The adapter does not serialize a complex IDoc structure correctly in the endpoint. This has been fixed. | |
| JR31171 | The JCA SAP Adapter does not handle multibyte characters from non-Unicode systems correctly. This has been fixed. | |
| Adapter messages incorrectly uses the event type "E"BAPI trace messages that are actually non-error messages incorrectly uses the event type "E". This has been fixed. | ||
| Adapter returns the time value in 12 hour format without the AM/PM information which is not complete. The adapter now sends the time in 24 hour format correctly. | ||
| JR30771 | The JCA SAP adapter does not correctly generate the operation name for inbound using extension Idocs. This has been fixed. | |
| PeopleSoft v6.1.0.3 | When doing child record insert, the insert position is decided by the value of the effective date attribute and the effective sequence attribute whereas users may want to insert a record at current/oldest location without knowing the effective sequence number. This has been fixed. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker version 6.1.0.3
| Adapter | APAR | Description |
| SAP v6.1.0.3 | The adapter supports on synchronous processing of inbound events. The adapter now supports the asynchronous processing of events. With this fix pack, the adapter supports tRFC and qRFC asynchronous protocols for inbound processing. When using these protocols, the client SAP application does not wait for a response from the adapter. | |
| The adapter supports only synchronous processing of outbound events. The adapter now supports the asynchronous processing of events. With this fix pack, the adapter supports tRFC and qRFC asynchronous protocols for outbound processing. When using these protocols, the adapter does not wait for a response from the SAP server. | ||
| JR28793 | When version 6.1 of the adapter is used with WebSphere Message Broker, the user name and password properties are stored in an advanced configuration section of the adapter properties, even though they are basic, mandatory properties. This has been fixed and the properties have been moved to the basic properties section. | |
| JR29142 | When a BAPI outbound call fails, version 6.1 of the adapter does not embed the application exception in the FaultException message. This has been fixed. | |
| After applying a WebSphere(R) Process Server fix (6.0.2.1 for APAR JR26701), ALE inbound events fail with a NullPointerException. This has been corrected. | ||
| JR28827 | In some scenarios, when an outbound BAPI call from the adapter fails, the table corresponding to the BAPI is locked and all subsequent BAPI calls fail. The adapter now calls the BAPI_TRANSACTION_ROLLBACK function when an outbound call to SAP fails, which enables the underlying resources within SAP to be released. | |
| Siebel v6.1.0.3 | JR30204 | Siebel JCA Adapter does not return value for the Child BO during the query operation. This has been fixed. |
| PeopleSoft v6.1.0.2 | When running the Adapter Connection wizard for outbound PeopleSoft adapter on WMB, a java.lang.NullPointerException is thrown. This has been fixed. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker version 6.1.0.2
| Adapter | APAR | Description |
| SAP v6.1.0.2 | Support for generic IDoc type in ALE pass-through interface. This feature has been added. | |
| Support for custom SAP function module in QISS interface. This feature has been added. | ||
| Support inbound split IDoc packet in ALE pass-through interface. This feature has been added. | ||
| Transaction ID (event ID) for ALE inbound operation not populated in the business object. This has been fixed. | ||
| Siebel v6.1.0.2 | In EMD, when a component that starts with "BCBS" is selected, either the "Finish" button or "Next" button (or both) is not activated. This has been fixed. If a dependent component is added alone, the primary business component is automatically added to the import list. | |
| Improve discovery relationships using Siebel API. A new algorithm for discovering MultiValue lists has been implemented to improve Siebel business object discovery. | ||
| JR28322 | A NullPointerException occurs within the Siebel Adapter cleanup method. This has been fixed. | |
| JR28059 | Because some connections are not successfully logged off during a transaction, new connections being created cause the maximum connection limit to be reached. This has been fixed. | |
| PeopleSoft v6.1.0.1 | Because the primary key is validated at the child level, the adapter fails if the primary key is not defined. The validation for the primary key at the child level is not neccessary and has been removed | |
| The adapter continues to redeliver failed events indefinitely. A new property, FailedEventRetryLimit, has been added to the ActivationSpec. FailedEventRetryLimit allows you to set the number of times the adapter will attempt to deliver an event before marking it as FAILED. This only applies to failures that are normally retried; data binding errors and function selector errors are excluded. If the adapter or server is shut down and restarted, the adapter will start fresh and deliver the event the specified number of times, not counting any retries that were attempted before the adapter was shut down. |
The following list describes the adapter versions and the fixes for that version packaged with WebSphere Message Broker version 6.1.0.1
| Adapter | APAR | Description |
| SAP v6.1.0.1 | The ALE inbound interface does not support the processing of an incoming IDoc as an unparsed stream. This has been fixed. | |
| The adapter does not support Secure Network Communication (SNC). This support has been added. | ||
| The adapter continues to redeliver failed events indefinitely. A new property, FailedEventRetryLimit, has been added to the activation specification. Through this property, you can specify the number of times the adapter attempts to deliver an event before marking it as FAILED. This only applies to failures that are normally retried; data binding errors and function selector errors are excluded. If the adapter or server is shut down and restarted, the adapter will start fresh and deliver the event the specified number of times, without regard to any retries that were attempted before the adapter was shut down. | ||
| Siebel v6.1.0.1 | The adapter continues to redeliver failed events indefinitely. A new property, FailedEventRetryLimit, has been added to the ActivationSpec. FailedEventRetryLimit allows you to set the number of times the adapter will attempt to deliver an event before marking it as FAILED. This only applies to failures that are normally retried; data binding errors and function selector errors are excluded. If the adapter or server is shut down and restarted, the adapter will start fresh and deliver the event the specified number of times, not counting any retries that were attempted before the adapter was shut down. |
[{"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":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"6.1","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27016648