IBM WebSphere Adapter for SAP Software, version 6.1.0.2_IF4 notes

This document contains the following sections:

Enhancements and fixes

New and modified connector properties

Upgrade notes

This table lists the enhancements and fixes in interim fix version 6.1.0.2_IF4. Enhancements\Fixes # CR APAR Title Details 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_IF3. Enhancements\Fixes # CR APAR Title Details 1 75649 JR29879 Decimal fields with value 0 create errors on return for BAPI Symptom: When BAPI have decimal fields , the adapter fails when the default value 0 is used. Resolution: Adapter is fixed to treate decimal fields as Strings so that correct value is set in BAPI. This table lists the enhancements and fixes in interim fix version 6.1.0.2_IF2. Enhancements\Fixes # CR APAR Title Details 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 # CR APAR Title Details 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 This table lists new and modified connector properties # Version Added or Modified Property Location No connector properties were introduced or modified for this version of the Interim fix. To upgrade to the Interim fix version 6.1.0.2_IF4 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.2_IF4 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 file CWYAP_SAPAdapter.jar.    a. Backup the existing file CWYAP_SAPAdapter.jar.    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.2_TF5 installation is complete for WMB. To upgrade to the interim fix version 6.1.0.2_IF4 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.2\deploy) . 3. Restart WMBT . 4. Fixpack installation is complete for WMBT. August 19th, 2008 5:00 PM (C) 2008 IBM Corporation. Proprietary and Confidential. All Rights Reserved.