Patch Notes for
Version 6.0.x of the IBM WebSphere Business Integration Adapter for mySAP.com

(for IBM CrossWorlds Infrastructure versions 3.0.1 through 4.3.x and WBIA versions 2.x.

 


The patch note contains the following sections:

CONNECTOR REVISIONS

UPGRADE INSTRUCTIONS

 


CONNECTOR REVISIONS

This patch contains the following revisions since the last maintenance release:

Available as of Version

APAR Number

CR Number

Feature

Description

6.0.3

JR22318

73110

ALE Module

Trace message was displayed incorrectly because the message ID was wrong.  It is displayed correctly with this fix pack.

6.0.3

JR22318

72339

RFC Server Module

SAP MQ queue configuration was required to start the RFC Server module.  With this fix pack they are not longer required when starting this module.

6.0.3

JR22318

72078

All Modules

mySAP ERP04 is now supported by the adapter.

6.0.3

JR22318

71641

ODA

The maximum length displayed in BAPI and RFC Server objects were incorrect for FLOAT data types.  With this fix pack the field maximum length is displayed properly.

6.0.3

JR21129

71277

All Modules

The log message utility now sends back the severity of the message to the broker.

6.0.3

JR22318

71450

ODA, BAPI Module

The ODA updates the verb ASI with the actual BAPI name for namespace BAPIs instead of replacing the "/" with an underscore. The adapter writes an error message if the BAPI name in the verb ASI cannot be found.

6.0.3

JR22318

71306

ALE Module

For malformed IDocs, the adapter was not creating an MQ message in the ALE error queue. With this fix, the adapter will send the failed IDocs to the ALE error queue.

6.0.3

JR22318

71156

Extension Module

The adapter now does not go into an endless loop when trying to process a field from SAP that does not exist in a child BO. This error was happening when the adapter was trying to set the BO values with the RFC data from SAP.

6.0.3

JR21509

66792

ALE Module

Adapter throws OutOfMemory error during event recovery in ALE module. This error happens when there are many events sitting in the ALE event queue. A new connector specific property "MaxInMemoryBufferSize" has been added to limit the the size of the in memory buffer used for performance optimization. For more details on configuring this property refer to the Technote "Memory utilization for the IBM WebSphere Business Integration Adapter for mySAP.com v6.0.0 (ALE module)". With this fix adapter manages the memory properly.

6.0.3

JR22318

70697

Extension Module

When an event fails in a poll cycle the remaining events stayed in the event table with status ‘R’. With this fix the remaining polled events will be processed.

6.0.3

JR22318

48259

Extension Module

A new configuration property called TrimSpaces has been created for users that want to remove white space at the beginning and end of the attribute values received from SAP Extension Module.  To use this new property, set TrimSpaces to “yes”.  Otherwise, the default behavior of trimming the trailing spaces will remain.

6.0.2

JR21157

60220

ODA

The ODA was failing to create business objects that contain the same structure in the import and export fields.  With this fix, the structures are uniquely renamed and the object is created successfully.

6.0.2

JR21157

59037

ALE Module

When the Dummy_key attribute does not exist in the business object, the adapter would fail.  With this fix, the adapter will process the event successfully without dummy_key mapping.

6.0.2

JR21157

47692

ALE Module

The restart/retry feature was not restarting the connector correctly. This needs to be implemented in conjunction with an adapter framework fix. Contact WBI Technical Support for information on the adapter framework fix.

6.0.2

JR21157

45003

ALE Module

When the connector is paused, events were sent to the error queue.  With this fix, the events will remain in the event queue to be reprocessed again when the connector becomes un-paused again.

6.0.1

JR20671

44688

ALL

The Unix start script was incorrect.  The script has been modified with this fix.

6.0.1

JR20670

44697

ALL

Support for MS932, Japanese characters is now supported.  The new configuration property, PartnerCharset must be used to specify the PartnerCharset encoding.

6.0.1

JR20575

60078

ALE Module

The adapter no longer hangs after sending a business object with CR LF characters.

6.0.1

JR20575

60038

Extension Module

The Event Linkage mechanism will work on the SAP 4.7 system with this fix.  This change requires importing transports in 47_EventTriggering.zip file.

6.0.1

JR20575

44080

ALE Module

When the adapter is paused some events disappeared.  With this fix, all events are accounted for in the event queue.

6.0.1

JR20575

37455

ALE Module

When processing IDOCs with an empty text segment the adapter will not longer fail with an MQ error.

6.0.1

JR20575

37323

Extension Module

Events sent when the connector is paused no longer go to the Archive Table with Status ‘3’.  They remain in the Event Table ready to be polled with a status of ‘Q’.  This change requires importing transports from the following files, 4_Delivery.zip and 4_Utilities.zip.

6.0.1

JR20290

59080

ALE Module

SAP Adapter RfcServer no longer terminates when an invalid response message is received from WebSphere Message Broker.

6.0.1

JR20290

58858

ALE Module

SAP Adapter no longer throws the NullPointerException in case of wrong control record data (SAP ALE).

6.0.1

JR20265

58954

RFC Server Module

If a BO is not supported, do not terminate the adapter, rather, log an error and keep the adapter alive.

6.0.1

JR20265

37005

Extension Module

Correct processing of child BOs when using the ABAP BAPI_Handler.


UPGRADE INSTRUCTIONS

To perform an upgrade to this version of the connector:

  1. Upgrade to the most recent maintenance release (6.0.0) if you have not already done so.
  2. Apply the changes prescribed in each table below, beginning with the entries at the bottom of each table and working up to the most recent patch.

Add, replace, or remove the following files and directories as indicated:

For Connector Version

Platform [WIN;UNIX]

Add / Replace / Remove

File (Starting from %CROSSWORLDS% / $CROSSWORLDS)

6.0.3

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

6.0.3

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt - Only English Delivered

6.0.3

WIN, UNIX

Replace

\ODA\SAP\SAPODA.jar

6.0.3

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

6.0.3

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt - Only English Delivered

6.0.3

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

6.0.3

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

6.0.3

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt - Only English Delivered

6.0.3

WIN, UNIX

Replace

\bin\Data\App\SAPConnectorTemplate

6.0.2

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

6.0.2

WIN, UNIX

Replace

\ODA\SAP\SAPODA.jar

6.0.2

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt - Only English Delivered

6.0.1

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt - Only English Delivered

6.0.1

WIN, UNIX

Replace

\bin\Data\App\SAPConnectorTemplate

6.0.1

UNIX

Replace

\connectors\SAP\start_SAP.sh

6.0.1

WIN, UNIX

Replace

\dependencies\transports_40_45_46\40_45_46_Infrastructure.zip

6.0.1

WIN, UNIX

Replace

\dependencies\transports_40_45_46\SAP40_45_46_Transports.txt

6.0.1

WIN, UNIX

Replace

\dependencies\transports_47\47_Infrastructure.zip

6.0.1

WIN, UNIX

Replace

\dependencies\transports_47\SAP47_Transports.txt

6.0.1

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

6.0.1

WIN, UNIX

Replace

\ODA\SAP\SAPODA.jar

Add or remove the following connector properties using CSM:

For Connector Version

Platform

Add / Remove

Property (Case-Sensitive)

6.0.3

WIN, UNIX

Add

MaxInMemoryBufferSize

6.0.3

WIN, UNIX

Add

TrimSpaces

6.0.2

none

 

 

6.0.1

WIN, UNIX

Add

PartnerCharset

6.0.1

WIN, UNIX

Add

ArchiveUnsubEvents

UPGRADE NOTES:

A new queue management utility helps manage the new queues in version 5.3.2. It is available on Windows. Please see BIA_AleEventUtil_readme.txt for information and usage of the utility.

To upgrade the Ale Module from version 4.8.1 and earlier or version 5.0.0 to 5.3.3 or later:

This version of the adapter manages ALE transaction id's and IDocs using MQ Series. As a result, it is imperative that you allow the current IDoc processing cycle to complete before applying this patch.                Temporarily halt the transmission of IDocs both to and from the adapter and verify that there are no IDocs (files) in the following directories when you upgrade:

CrossWorlds\connectors\SAP\ale\events 

CrossWorlds\connectors\SAP\ale\wip

Also verify that any failed or unsubscribed IDocs (files) in the following directory have been reviewed, corrected and re-processed:

CrossWorlds\connectors\SAP\ale\archive

Once all IDocs (files) complete successfully, apply the upgrade and follow the new configuration instructions in the documentation.

Six new queues are needed:

    · SAPALE_Archive_Queue
    · SAPALE_Event_Queue
    · SAPALE_Wip_Queue
    · SAPALE_Error_Queue
    · SAPALE_UnSubscribed_Queue
    · SAPtid_Queue

Also an empty text file called EventState.log is required in the %CROSSWORLDS%\connector\SAP\ALE directory.

For further details, please refer to the adapter guide.

To upgrade the Ale Module for request processing from versions 4.8.2 through 5.2.4 to version 5.3.2 or later:

    * Process all of your failed events in the SAPTid_Queue.
    * Clear the messages out of the SAPTid_Queue.

The ArchiveDays connector configuration property determines the number of days when the TIDManagement files should be deleted from the %CROSSWORLDS%\connectors\SAP\ale\request directory. A file is created after an event has been processed successfully. All failed events will remain in the SAPTid_Queue until they are resubmitted again. The default is seven days if no value is given. 

TROUBLESHOOTING:

To use the ALE Module to process large IDocs or IDoc Packets:

Refer to the MQSeries System Administration publication for more information on configuring the log files.


May 02, 2005 03:30 PM

© 2005 IBM Corp. Proprietary and Confidential. All Rights Reserved.