This table lists the enhancements and fixes in interim fix version 6.1.0.3_IF1. |
Enhancements\Fixes |
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 | | ASupport 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. |
|
3 | 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. |
|
4 | 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. |
|
5 | 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. |
|
6 | 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.
|
|
7 | CR | JR | Service Description improper when there are more than 4 Inbound BAPIs |
Symptom: In EMD Inbound BAPI, if more than 4 are chosen then only 4 of them are listed. |
Resolution: The EMD UI has been changed such that the BAPIs selected are shown against the available operations instead of vice versa. |
|
8 | CR | JR30572 | Adapter reports 0 bytes on ALE RFC inbound |
Symptom: There was a mismatch between operation name generated , Adapter generating operation name as execute+basictype+extension idoc type in runtime whereas in EMD the operation name generated as execute+extension idoc type |
Resolution: Adapter is fixed to generate operation name as execute+extension idoc type. |
|
This table lists the enhancements and fixes in interim fix version 6.1.0.2_IF4. |
Enhancements\Fixes |
1 | 75545 | JR29741 | Adapter fails saying "Nothing found" during metadata discovery if BAPI is
complex with deep structures. |
Symptom: When BAPI or BAPI work unit interface is used, the SAP adapter metada
discovery is failing with following errors: "SELECT...LIKE..." with lead, but no
closing inverted comma |
Resolution: Adapter is fixed to handle complex BAPIs having deep structures. |
|
2 | 75654 | JR29884 | Adapter EMD does not handle table types in import parameters and also global variables set as part of a BAPI work unit are lost in subsequent BAPIs. |
Symptom: Adapter runtime fails when the import has a table type parameter. Global variables set as part of the BAPI work unit are not visible in subsequent BAPIs. |
Resolution: Adapter is fixed to table types in import parameter list and the reset() calls in BAPIInvoker class are removed so that global variables are not lost across BAPIs. |
|
3 | 75748 | JR29884 | Adapter should perform commit or rollBack() as dictated by the container and not as part of the code flow. |
Symptom: Adapter should maintain perform the commit and rollback calls as per the container and not as per the code flow. |
Resolution: Adapter is fixed to handle commits and rollbacks as per container whenever managed mode deployment is done. |
|
This table lists the enhancements and fixes in interim fix version 6.1.0.2_IF2. |
Enhancements\Fixes |
1 | 75470 | JR29531 | Adapter BAPI inerface fails to set "N" type values into SAP. |
Symptom: When BAPI parameter contain "N" type values , adapter fails to set those values into BAPI. |
Resolution: Adapter is fixed to treate "N" types as "String" instead of "Integer". |
|
2 | 75471 | JR29546 | Adapter fails when multiple inbound applications are deployed on Websphere Message Broker (WMB) |
Symptom: If second inbound application is deployed on WMB then first inbound application starts failing because new application replaces previous applications endpoint. |
Resolution: Adapter is fixed to not overwright endpoints of earlier applications . |
|
This table lists the enhancements and fixes in interim fix version 6.1.0.2_IF1. |
Enhancements\Fixes |
1 | 96042 | | Receiving partner value not found in external service wizard for extension IDocs |
Symptom: On the Configure Composite properties page of the external service wizard, the receiving partner entry was not showing for extension IDocs. This prevents the user from correctly completing the ALE inbound operations configuration. |
Resolution: The external wizard is now showing the receiving partner entry for extension IDocs. The user can select one of these entry to configure ALE inbound operations |
|
|
To upgrade to the Interim fix version 6.1.0.3_IF1 on WebSphere Process Server, do the following. |
1. Ensure that you have followed the "Installation Instructions" section in the download link before proceeding. |
2. If you need to use the test fix for EMD, delete the connector project in WebSphere Integration Developer, import the new RAR file, and apply the enterprise information system (EIS) specific dependency files. |
a. Open the Java build path for the SCA module and remove the Connector project that is selected on Projects tab. |
b. Open the dependency editor and remove the connector project. |
c. Delete the connector project from the workspace. |
d. Import the new RAR file. Add any dependency files from EIS specific application-specific information as needed. |
e. Open the Java build path for the SCA module and select the Connector project that is selected on the Projects tab. |
e. Open the dependency editor and add the connector project if it is not already present and select Deploy with Module. |
3. If you need to update deployed applications on WebSphere Process Server, do the following: |
a. Select Update for the corresponding application on the WebSphere Process Server administrative console. |
b. Select Single Module with a relative path as name of the RAR file - CWYAP_SAPAdapter.rar, CWYAP_SAPAdapter_Tx.rar. |
c. Click Browse on the local file system to select the updated RAR file that has the changes. |
d. Select the default values in the remaining steps and click Finish. This will ensure that existing configurations, for example, are not changed and that only JAR files will be updated. |
To upgrade to the interim fix version 6.1.0.3_IF1 on Websphere Message Broker (WMB) runtime, do the following. |
1. Unzip the Package_WMB.zip to your temp local directory , it would create following directory "AdapterPackage". |
2. Stop all your Brokers that are using this install. |
3. Go to "AdapterPackage" directory it should contain the files CWYAP_SAPAdapter.jar and CWYBS_AdapterFoundation.jar. |
a. Backup the existing file CWYAP_SAPAdapter.jar and CWYBS_AdapterFoundation.jar jar files. |
b. Copy the above files to MQSI_INSTALL_PATH\adapters\prereqs\jar directory , where MQSI_INSTALL_PATH is WMB runtime install path. (eg. C:\Program Files\IBM\MQSI\6.1\adapters\prereqs\jars) . |
4. Restart your Brokers. |
5. 6.1.0.3_IF1 installation is complete for WMB. |
To upgrade to the interim fix version 6.1.0.3_IF1 on Websphere Message Broker Toolkit (WMBT), do the following. |
1. Unzip the Package_WMBT.zip to your temp local directory , it will create the directory "AdapterPackage". |
2. Stop your WMB Toolkit. |
a. Backup the existing CWYAP_SAPAdapter_Tx.rar file. |
b. Copy the above CWYAP_SAPAdapter_Tx.rar files to WMBT_INSTALL_PATH\ResourceAdapters\SAP_(version_number)\deploy directory , where WMBT_INSTALL_PATH is WMBT runtime install path. (eg. C:\Program Files\IBM\WMBT610\ResourceAdapters\SAP_6.1.0.3\deploy) . |
3. Restart WMBT . |
4. 6.1.0.3_IF1 installation is complete for WMBT. |
August 19th, 2008 5:00 PM
|
(C) 2008 IBM Corporation. Proprietary and Confidential. All Rights Reserved.
|
| | |