IBM WebSphere Adapter for SAP Software, version 6.0.2.1 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 fix pack version 6.0.2.1.
Enhancements
#CRAPARTitleDetails
172087The SAP Enterprise Metadata Discovery (EMD) tool cannot generate IDOC service artifacts by loading the definitions from a file.
Symptom: The SAP EMD only supported the generation of IDOC service artifacts by loading the definitions from an SAP system.
Resolution: The SAP EMD has been enhanced to generate IDOC service artifacts by loading the definitions from either a file or an SAP System.
273688The adapter does not support the qRFC protocol for bi-directional communication with the SAP system.
Symptom: The adapter does not support the qRFC protocol for bi-directional communication with the SAP system.
Resolution: This support has been added.
372782The EMD needs to be enhanced to address User Centric Design (UCD) recommendations.
Symptom: The EMD needs to be enhanced to address User Centric Design (UCD) recommendations.
Resolution: The EMD has been enhanced to provide better usability, readability and navigability.
473578Enable SAP applications to call in to the WebSphere Adapter for SAP software for synchronous processing as if it was another SAP application.
Symptom: SAP applications cannot call in to the WebSphere Adapter for SAP Software for synchronous processing as if it were another SAP application.
Resolution: The EMD and the adapter have been enhanced to provide this functionality. The EMD generates the appropriate configurations and the adapter services RFC calls from SAP applications and provides a response to the originating application.
Fixes
#CRAPARTitleDetails
187871JR25980When running an ALE Outbound application, the adapter throws a NumberFormatException if there are more than 999 IDOC segments.
Symptom: The property containing the number of segments was incorrectly formatted.
Resolution: The property is now correctly formatted.
288462When running an ALE Outbound application, the IDOC data is truncated.
Symptom: When running an ALE Outbound application, the IDOC data being sent to the SAP application was truncated. In addition, the IDOC data in the RFC trace was truncated.
Resolution: The method that creates the IDOC data has been modified so that the data is no longer truncated.


This table lists new and modified connector properties
#VersionAdded or ModifiedPropertyLocation
No connector properties were introduced or modified for this version of the fix pack.


To upgrade to the fix pack version 6.0.2.1, 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 Fix Pack 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 - CWYAPSAPAdapter.rar, CWYAP.
   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.


June 29th, 2007 6:00 PM
(C) 2007 IBM Corporation. Proprietary and Confidential. All Rights Reserved.