This release of the document contains the following new information:
- Certain parts and chapters of this manual have been restructured for
editorial clarification.
- The adapter now runs with WebSphere Business Integration Adapter
FrameworkV2.6. For details about supported integration broker
versions, see Broker compatibility.
- As of version 6.0.x, the adapter for mySAP.com is not
supported on Solaris 7, so references to that platform version have been
deleted from this guide.
- The adapter is now supported on Solaris 9, Windows 2003, Red Hat
Enterprise Linux, SUSE Linux Enterprise Server, and SUSE Linux Standard
Server. For details about the various platform versions of each, see Adapter platforms.
- The connector now uses a single business object handler that supports all
BAPI calls, rather than multiple BAPI-specific business object handlers, each
one supporting a specific BAPI. For details, see Overview of the BAPI Module.
- The connector and SAPODA support BAPI transaction objects. For
details, see BAPI transaction business objectsBusiness object structure for BAPI transactions.
- SAPODA no longer generates custom business object handler templates for
the BAPI Module. To create a custom business object handler, you must
code it yourself from the templates provided.
- The connector and SAPODA provides ResultSet support for DB2 Information
Integrator, and as such uses new standard connector properties. For
details, see ResultSet business objects, Business object structure for BAPI ResultSets, Appendix D, Standard configuration properties for connectors.
- SAPODA provides caching support of search results in RFC nodes. The
caching service runs in the background whenever you start SAPODA and the
cached searches are purged when you end the session. For details, see Expand nodes and select objects.
- Transport files are now installed in the
\connectors\SAP\dependencies\transports_31 directory. For
details see Installing connector transport files.
- The connector supports breaking up IDoc messages into smaller units, each
of which is a JMS-MQ message that translates into a smaller business
object. For details see Event processing components.
