Fix Pack Notes for
Version 5.5.x of the IBM WebSphere Business Integration Adapter for mySAP.com

(for IBM WebSphere Business Integration Infrastructure versions 4.1.0 through 4.2.2 and WBIA versions 2.0.0 through 2.4.0)

 

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

5.5.5

JR20670

44697

ALL

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

5.5.5

JR20575

60078

ALE Module

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

5.5.5

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.

5.5.5

JR20575

44080

ALE Module

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

5.5.5

JR20575

37455

ALE Module

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

5.5.5

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.

5.5.4

JR20290

59080

ALE Module

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

5.5.4

JR20290

58858

ALE Module

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

5.5.4

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.

5.5.4

JR20265

37005

Extension Module

Correct processing of child BOs when using the ABAP BAPI_Handler.

5.5.4

JR20232

58492

ALL

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

5.5.3

JR20092

35192

ALE Module

Performance was degrading when the Request directory fills up with many status files for ALE request processing.

5.5.3

JR20092

36006

ALE Module

Adapter was not using the configured connector property value for "AleEventDir" for creating the "Request" folder. Request folder holds the status message files for ALE request processing using TID management.

NOTE: Before applying this patch, complete all of your failed ALE Request flows. After applying this patch the connector creates and uses the "Request" folder under the configured parent directory. It will no longer cleanup the previous request directory. You will have to manually cleanup that directory.

5.5.3

JR20092

35673

ODA

When using IDOC files from SAP R/3 4.7 systems, the Application Specific information generated in the business objects was incorrect.

5.5.3

JR20092

42920

ODA

A Search By Description BAPI/RFC down the RFC node was not generating its corresponding BO correctly.

5.5.3

JR20092

35387

ALE Module

Correct the setting of the space characters that pad the fields in a segment when sending it to SAP.

5.5.2

JR19928

34205

ALE Module

When SAP server shuts down abruptly request events are no longer lost during request processing.

5.5.2

JR19942

34614

ALL

During startup SAPAdapter logs misleading error saying "JCO files missing" when MQ JMS libraries are not installed.The connector now logs proper message.

5.5.1

JR19534

33144

Extension Module

The value of ObjectEventId is preserved for request processing.

5.5.1

JR19534

32731

ALL

Configuration properties are case-insensitive beginning with ICS version 4.2.0 and WBIA 2.3.0.

5.5.1

JR19375

31502

ALE Module

When the connector dies due to a Fatal Error, the RestartRetryCount connector property will properly restart the connector.

UPGRADE INSTRUCTIONS

To perform an upgrade to this version of the connector:

  1. Upgrade to the most recent maintenance release (5.5.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)

5.5.5

WIN, UNIX

Replace

\connectors\SAP\dependencies\transports_4x\SAP4_Transports.txt

5.5.5

WIN, UNIX

Replace

\connectors\SAP\dependencies\transports_4x\47_EventTriggering.zip

5.5.5

WIN, UNIX

Replace

\connectors\SAP\dependencies\transports_4x\4_Utilities.zip

5.5.5

WIN, UNIX

Replace

\connectors\SAP\dependencies\transports_4x\4_Delivery.zip

5.5.5

WIN, UNIX

Replace

\ODA\SAP\SAPODA.jar

5.5.5

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

5.5.5

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt

5.5.5

WIN, UNIX

Replace

\repository\SAP\CN_SAP.txt

5.5.4

WIN, UNIX

Replace

\ODA\SAP\SAPODA.jar

5.5.4

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

5.5.4

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt

5.5.3

WIN, UNIX

Replace

\ODA\SAP\SAPODA.jar

5.5.3

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

5.5.3

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt

5.5.2

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

5.5.2

WIN, UNIX

Replace

\connectors\messages\SAPConnector.txt

5.5.1

WIN, UNIX

Replace

\connectors\SAP\CWSAP.jar

Add or remove the following connector properties using CSM:

For Connector Version

Platform

Add / Remove

Property (Case-Sensitive)

5.5.5

WIN, UNIX

Add

PartnerCharset

5.5.5

WIN, UNIX

Add

ArchiveUnsubEvents

5.5.4

none

 

 

5.5.3

none

 

 

5.5.2

none

 

 

5.5.1

none

 

 

 

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:

If receiving this error: "Unable to load message catalog - mqji" you may have an invalid value for the AleEventDir Application Specific property.  This property should contain the path where you want the EventState.log file to be saved.  Be sure not include the filename with the path, like C:\WebSphereAdapters\connector\SAP\ALE\EventState.log, since this will cause the error.

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.

February 24, 2004 10:17 AM

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