IBM WebSphere Adapter for SAP Software, version 6.1.0.3 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.1.0.3.
Enhancements
#CRAPARTitleDetails
186210Support 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.
295726Support 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
#CRAPARTitleDetails
196046JR28793The 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.
296221JR29142The 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.
396094JR28825Ale 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.
496095JR28827Subsequent 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.


This table lists the enhancements and fixes in fix pack version 6.1.0.2.
Enhancements
#CRAPARTitleDetails
195574Support for generic IDoc type in ALE pass-through interface
Symptom: A separate IDoc definition is required for each IDoc that the adapter is expected to process. This can become unwieldy when the ALE pass-through interface is used to process many different IDoc types.
Resolution: The ALE pass-through interface supports a generic IDoc definition that enables the adapter to process any IDoc type. An IDoc type field in the object definition is used to indicate the IDoc type.
295236Support for custom SAP function module in QISS interface
Symptom: QISS interface uses the SAP RFC_READ_TABLE function module to retrieve data. On some SAP systems, the RFC_READ_TABLE function fails and causes SAP short dumps, which result in the following error: Error in ASSIGN statement in the program SAPLSDTX.
Resolution: To overcome this issue, SAP OSS note #758278 recommends creating and using a custom function module instead of the RFC_READ_TABLE function. After this custom function module is created on the SAP system, you can enter the custom function module name when running the external service wizard. The adapter uses this custom function module at run time.
395594Support inbound split IDoc packet in ALE pass-through interface
Symptom: The ALE pass-through inbound interface does not support a split IDoc packet.
Resolution: Each IDoc in the inbound packet can be sent as an individual business object.
495622Transaction ID (event ID) for ALE inbound operation not populated in the business object
Symptom: The transaction ID (event ID) is not populated in the business object.
Resolution: The transaction ID (event ID) is now populated in the business object.


This table lists the enhancements and fixes in fix pack version 6.1.0.1.
Enhancements
#CRAPARTitleDetails
There are no enhancements in this fix pack.
Fixes
#CRAPARTitleDetails
186215Support for IDoc streams with no partial parsing
Symptom: The ALE inbound interface does not support the processing of an incoming IDoc as an unparsed stream.
Resolution: The ALE inbound interface supports the processing of an incoming IDoc as an unparsed stream. The external service discovery wizard now generates the required artifacts to provide this support.
289221Support for Secure Network Communication (SNC)
Symptom: The adapter does not support Secure Network Communication (SNC).
Resolution: This support has been added.
390957Configurable retry for failed events
Symptom: The adapter continues to redeliver failed events indefinitely.
Resolution: 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.


This table lists new and modified connector properties
#VersionAdded or ModifiedPropertyLocation
1 6.1.0.2 Add customFunctionName - Custom function name SAPSQIInteractionSpec/customFunctionName
2 6.1.0.1 Add SncMode - Secure Network Communication (SNC) mode, 0 (off) or 1 (on) SAPManagedConnectionFactory/SAPActivationSpecWithXID
3 6.1.0.1 Add SncMyname - Secure Network Communication (SNC) name SAPManagedConnectionFactory/SAPActivationSpecWithXID
4 6.1.0.1 Add SncPartnername - Secure Network Communication (SNC) partner, for example, p:CN=R3, O=ABC-TES, C=EN SAPManagedConnectionFactory/SAPActivationSpecWithXID
5 6.1.0.1 Add SncQop - Secure Network Communication (SNC) level of security, valid values are 1 to 9 SAPManagedConnectionFactory/SAPActivationSpecWithXID
6 6.1.0.1 Add SncLib - Path to the library that provides the SNC service SAPManagedConnectionFactory/SAPActivationSpecWithXID
7 6.1.0.1 Add FailedEventRetryLimit ActivationSpec


To upgrade to the fix pack version 6.1.0.3 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 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 - 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 fix pack version 6.1.0.3 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. Go to "AdapterPackage" directory it should contain two file CWYAP_SAPAdapter.jar and CWYBS_AdapterFoundation.jar.
   a. Copy the above files to MQSI_INSTALL_PATH\adapters\prereqs\jar directory , where MQSI_INSTALL_PATH is WMB runtime install path .
   b. Restart your Broker and Configuration Manager .
   c. Fixpack installation is complete for WMB.
To upgrade to the fix pack version 6.1.0.3 on Websphere Message Broker Toolkit (WMBT), do the following.
1. Unzip the Package_WMBT.zip to your temp local directory , it would create following directory "Windows/SAP_6.1.0.3/deploy".
2. Go to "Windows/SAP_6.1.0.3/deploy" directory it should contain two file CWYAP_SAPAdapter_Tx.rar and Readme_en_US.htm.
   a. 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 .
   b. Restart WMBT .
   c. Fixpack installation is complete for WMBT.


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