- The Modules configuration property has been simplified. The new
configuration values are shorter and more intuitive. However, for
backward compatibility, the previous values are still accepted. For
the list of module names, see "Modules".
- The new Hierarchical Dynamic Retrieve Module processes
hierarchical or flat business objects in response to requests from
collaborations configured to work with the connector. For
information on this module, see "Overview of the
Hierarchical Dynamic Retrieve Module".
- The Advanced Outbound Wizard, which replaces the Outbound
Wizard, creates hierarchical or flat business object definitions by
stepping through the desired SAP transaction. Documentation of the
Outbound Wizard has been removed from
"Developing business objects for the ABAP Extension Module".
For information on using Advanced Outbound Wizard, see "Generating business
objects".
- The ALE Module provides non-invasive event processing. For more
information, see "Event processing
components", and "AleEventDir".
- The ALE Module uses Transaction IDs (TIDs) to guarantee that
each piece of data is delivered or processed once and only once.
For more information see "Overview of the ALE
Module".
- The connector supports multi-threading. For more information,
see "Processing
multiple concurrent interactions" and "NumberOfListeners".
- Important:
- BAPI business object handlers generated before the IBM
CrossWorlds Connector for SAP version 4.3.0 are not thread-safe. To
guarantee data consistency and integrity when using
multi-threading, you must regenerate these business object
handlers. The business objects do not require any change.
- The connector running on Solaris now uses SAP's Java API and
fully supports all connector modules. Because IBM WebSphere does
not ship the Java API, you must download it from SAP's website. For
more information, see "Prerequisites
for installation".
- Corrections have been made to the following sections of the
Overview:
- The connector no longer uses the CharacterEncoding
configuration property.
- The connector uses the RefreshLogonCycle configuration property
differently. For more information, see "RefreshLogonCycle".
- A new section that documents a namespace problem has been added
to the troubleshooting chapter: "Event distribution
problem on Microsoft Windows (connector version 4.2.7
only)".
