| This table lists the enhancements and fixes in fix pack version 6.1.0.4. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 75473 | | The adapter returns old information/data from the SAP EIS. |
| Symptom: When using the adapter to fetch a data that was recently modified, the returned value is not the latest one. |
| Resolution: Adapter will now correctly reset all connection resources so that the latest data is retrieved. |
|
| 2 | 75474 | | JCO Connection pool error during server restart |
| Symptom: After restarting the server, some deployed modules throw an exception which looks like:
MessageEndpoint activation failed for ActivationSpec com.ibm.j2ca.sap.SAPActivationSpecWithXid and MDB Application SAPInboundInvoiceServiceApp#SAPInboundInvoiceServiceEJB.jar#export.interfaces.SAPInvoiceInboundInterfaceEIS, due to the following exception:
com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool boy.novo.dk is removed.
at com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5006) |
| Resolution: The adapter now uses a unique pool name for all applications and the symptom is no longer reproducible. |
|
| 3 | 75643 | | When doing outbound using the BAPI WU interface, data was not correctly updated in the SAP EIS. |
| Symptom: When running an outbound using the BAPI WU interface, the adapter was resetting connection resource after each BAPI execution, thus resetting global state. This was causing BAPI called later not to get the latest values. |
| Resolution: This was corrected. The reset is now being called only once, after all BAPIs are executed. |
|
| 4 | 96037 | | When a simple BAPI call fails, the adapter does not rollback to remove table locks. |
| Symptom: While using the BAPI_GOODSMVT_CREATE BAPI, the adapter does not rollback correctly in cases of failure. |
| Resolution: This has been corrected. The adapter now rolls back correctly after any failure. |
|
| 5 | 96094 | | ALE inbound fails with a null pointer exception after applying JR26701 on WPS. |
| Symptom: The adapter was still excepting the WPS runtime to return an exception when the attribute being queries does not exist. The WPS runtime now returns a NULL instead this leading to an NPE. |
| Resolution: The adapter can now handle a null if the BO.getProperty() call fails, in line with the API specification change. |
|
| 6 | 75522 | | The adapter does not support more than 4 BAPIs in the EMD Object selection screen. |
| Symptom: When more than 4 BAPIs are selected for processing during an inbound EMD, the adapter does not correctly generate the artifacts and the event processing fails. |
| Resolution: The adapter can now handle more than 4 BAPIs and it generates the artifacts correctly. |
|
| 7 | 92875 | | EMD index out of range error for 3 BAPI during inbound processing. |
| Symptom: In the Configure Composite Properties panel, after selecting 3 BAPIs and Clicking Next, an error occurs:
Error in creating schema files. Array index out of range: 3 |
| Resolution: This issue has been fixed. The EMD now completes properly for any number of BAPIs. |
|
| 8 | 92924 | | Always one error message appears at runtime without any effect on the behaviour. |
| Symptom: While running any inbound or outbound scenarios, always one error messsage appears without any impacts for runtime.
[10/14/08 16:55:44:890 CST] 00000093 LogUtils E SAPRFCDataBinding 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. |
| Resolution: This issue has been fixed. |
|
| 9 | 75748 | | Commit or Rollback on BAPI should be done by the container. |
| Symptom: Adapter was calling Commit or Rollback on its own, inspite of the container setting. |
| Resolution: This has been fixed. Adapter will now call Commit or Rollback as per container request if it is Local Transaction. |
|
| 10 | 75654 | | When the Import or Export section of a BAPI (instead the Tables section) contains tables, then a BAPI fails. |
| Symptom: During runtime, a BAPI call with Table parameters in the Import or Export section fails with the exception:
CWYAP2044:The Z_READ_PRICING_DATA BAPI (without transaction) failed.
Error: Cannot convert field CONFIG of type TABLE to JCO.Structure
Explanation=In the input BAPI business object, the data, metadata or both are incorrect. |
| Resolution: The adapter now supports Table parameters in the Import/Export section. |
|
| 11 | 75545 | | The adapter EMD runs throws "Error: nothing found" while discovering BAPIs. |
| Symptom: When we attempt to discover a nested BAPI(more than 2 levels deep) using the EMD Discovery screen, ESD wizard connects to SAP with the Filter, if specified. While retrieving the metadata from SAP, the wizard terminates with the error ("Nothing found"). |
| Resolution: The adapter can now handle nested BAPIs in the discovery screen. |
|
| 12 | 75649 | | Decimal fields are not saved in BAPIs. |
| Symptom: When decimal fields are present in a BAPI, there are errors in the return type. |
| Resolution: The adapter can now correctly handle decimal fields in BAPI parameters. |
|
| 13 | 75878 | | When more than one inbound application is running, during startup an error occurs saying the JCO pool name already exists. |
| Symptom: The hostname of the SAP system was being used as the pool name during the start of the first inbound application. So when more than one application is started simultaneously, then an error was being thrown stating that the JCO Pool name already exists. |
| Resolution: The adapter now creates unique pool names for each inbound module. |
|
| 14 | 75880 | | ALE inbound listener threads still remain and not killed after the application is stopped. |
| Symptom: When running inbound ALE module, some listener threads still remain and try to process idocs after the application is stopped. |
| Resolution: Listener threads were taking more time to get stopped and this was happening after the application stops. This has been fixed. |
|
| 15 | 76039 | | ESD fails if 2 BAPIs ahving same field names separted a '_'. |
| Symptom: When we select two BAPIs in during the SCI interface ESD with field names that differ by a _ alone(though the structures are the same), the ESD fails to generate the artifacts. |
| Resolution: This has been fixed. The adapter now ignores case while trying to generate the second XSD. |
|
| 16 | 92923 | | Error message appear in the log without Business Graph. |
| Symptom: Create an Ale qRFC outbound and uncheck "generate business graph" when EMD, and deploy into WPS. At runtime, an exception, tagged "E", is seen in the logs as below:
[10/14/08 15:27:03:406 CST] 0000006d LogUtils E com.ibm.j2ca.sap.ale.outbound.AleInvoker postIDoc CWYAP3068:Cursor.getNext() method call failed, verify that the input business object Cursor com.ibm.j2ca.extension.dataexchange.sdo.InputCursorSDO@61b261b2 data is initialized. Error Message: Exception while getting accessor. Please make sure property exists with accessor name verb Explanation=The input data has not been populated in the input business object Cursor. UserAction=Input business object data may not have been initialized in the business object specified in the error message, make sure data in initialized before calling getNext(). |
| Resolution: This has been fixed. The adapter now throws an Information message in the log file. |
|
| 17 | 92929 | | Log file has no information about the partner character set information. |
| Symptom: If an incorrect value is given to the partner character set, like abc123, the adapter does not log an error indicating that the value set is not valid. |
| Resolution: This has been fixed. The adapter now throws an appropriate log message. |
|
| 18 | 93147 | | When deploy SAP adapter on the WPS, IllegalCharsetNameException is thrown. |
| Symptom: If no value is specified for the Partner character set, the adapter throws an IllegalCharsetNameException at runtime. |
| Resolution: This has been fixed. The adapter does not throw the exception if no value is set. The default value is used instead. |
|
| 19 | 76089 | | SQI with BG throws exception. |
| Symptom: Executing SQI without BG throws the following exception:
com.ibm.websphere.sca.ServiceRuntimeException: DataBinding Exception thrown in J2CMethodBindingImpl.invoke() commonj.connector.runtime.DataBindingException: Failed to initialize cursor at com.ibm.ws.sca.internal.j2c.J2CMethodBindingImpl.invoke(J2CMethodBindingImpl.java:360)
at com.ibm.ws.sca.internal.j2c.J2CInterfaceBindingImpl.invoke(J2CInterfaceBindingImpl.java:118)
at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.invokeDynamicImport(J2CImportHandler.java:1044)
at com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.processMessage(J2CImportHandler.java:338)
at ..................
|
| Resolution: This has been fixed. |
|
| 20 | 76042 | | Adapter throws an error if the data record is not populated. |
| Symptom: When using one or more SAPRequestNodes, the adapter fails to complete subsequent request after a failure. |
| Resolution: This has been fixed. |
|
| 21 | 75794 | | Poor Service Diagnostics for misconfigured SAP Gateway host setting. |
| Symptom: 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. |
| Resolution: This has been fixed. |
|
| 22 | 75795 | | Building Connection with Async q/tRFC BAPI with Out Params gives bad error. |
| Symptom: The adapter continues to execute a q/tRFC BAPI request which has a required Output paramater. Since the q/tRFC call is async, required Output parameters cannot be supported. |
| Resolution: This has been fixed. The adapter does not allow completion of the EMD wizard when selected BAPIs have required Output parameters for executing a q/tRFC BAPI call. |
|
| 23 | 75814 | | SAPManagedConnectionFactory.isGatewayConfigured NullPointerException. |
| Symptom: The Adapter Connection Wizard can allow a user to build an Inbound to SAP Adapter that will throw NullPointerException SAPManagedConnectionFactory.isGatewayConfigured if they only set "Gateway Service" and omit "Gateway Host". |
| Resolution: This has been fixed. |
|
| 24 | 76058 | 46390,082,000 | The JCA SAP adapter does not correctly generate the operation name for inbound using extension IDocs. |
| Symptom: The adapter was generating a different operation name during the EMD run and another at runtime. This mismatch caused a FunctionSelectorException at runtime. |
| Resolution: This has been fixed. |
|
| 25 | 90460,217,631 | | The time fields are being translated to hhmmss format(0-12hr format) with missing AM/PM information. |
| Symptom: Adapter returns the time value in 12 hour format without the AM/PM information which is not complete. |
| Resolution: The adapter now sends the time in 24 hour format correctly. |
|
| 26 | 52930,SGC,724 | | Adapter messages incorrectly uses the event type "E" |
| Symptom: BAPI trace messages that are actually non-error messages incorrectly uses the event type "E". |
| Resolution: This has been fixed. |
|
| 27 | 76149 | 40278,999,858 | The JCA SAP Adapter does not handle multibyte characters from non-Unicode systems correctly. |
| Symptom: When using the QISS module to retrieve data from a non-Unicode system, the BO gets filled incorrectly as soon as table contains multibyte characters. |
| Resolution: The adapter now correctly handles multibyte characters from non-Unicode systems. |
|
| 28 | 76163 | 52369,SGC,724 | The adapter does not serialize a complex IDoc structure correctly in the endpoint. |
| Symptom: A BO dump of a complex, multi-segment IDoc is not serialized correctly. |
| Resolution: This has been fixed. |
|
| 29 | 75915 | | Nullname space support in base class. |
| Symptom: Base class doesn't support null namespace using 6.1 adapter. |
| Resolution: This has been fixed. |
|
| 30 | 93155 | | TypeFactory is using ext classloader instead of application classloader in WAS. |
| Symptom: Class.forName method could not find the record and throws bo not found exception and Inbound on ALE fails. |
| Resolution: This has been fixed. |
|
| 31 | 76299 | | Adapter on WTX throws null pointer exception. |
| Symptom: Null Pointer Exception thrown while performing outbound or inbound communication with Websphere Adapter on WTX. |
| Resolution: NO more Null pointer exception are thrown by the Adapter on WTX while performing outbound and inbound operation. |
|
| This table lists the enhancements and fixes in fix pack version 6.1.0.3. |
| Enhancements |
| 1 | 86210 | | Support for asynchronous inbound processing of BAPI calls |
| Symptom: The adapter supports only synchronous processing of inbound events. |
| Resolution: 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. For more information about this feature, refer to the adapter documentation. |
|
| 2 | 95726 | | Support for asynchronous outbound processing of BAPI calls |
| Symptom: The adapter supports only synchronous processing of outbound events. |
| Resolution: 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. For more information about this feature, refer to the adapter documentation. |
|
| Fixes |
| 1 | 96046 | JR28793 | The basic properties user name and password are stored in an advanced configuration section |
| Symptom: 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. |
| Resolution: Because the user name and password are mandatory properties, they have been moved to the basic properties section. |
|
| 2 | 96221 | JR29142 | The adapter does not embed an application exception |
| Symptom: When a BAPI outbound call fails, version 6.1 of the adapter does not embed the application exception in the FaultException message. |
| Resolution: The adapter includes an application exception in the FaultException message when a BAPI outbound call fails. |
|
| 3 | 96094 | JR28825 | Ale inbound fails with NullPointerException |
| Symptom: After applying a WebSphere(R) Process Server fix (6.0.2.1 for APAR JR26701), ALE inbound events fail with a NullPointerException. |
| Resolution: This problem has been corrected. |
|
| 4 | 96095 | JR28827 | Subsequent calls to SAP fail after an outbound event fails |
| Symptom: 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. |
| Resolution: 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. |
|