This release of the document contains the following new information:
Editorial changes:
- The title of this manual has changed from Adapter for
mySAP.com User Guide (SAP R/3 V.4.x) to
Adapter for mySAP.com User Guide (for BASIS
4.0-4.6, SAP Web AS 6.20)
- Certain parts and chapters of this manual have been restructured for
editorial clarification.
- The title of the IBM CrossWorlds Station tool has changed to "IBM
WebSphere BI Station."
Adapter environment changes:
- 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 now runs with WebSphere Business Integration Adapter
FrameworkV2.6. For details about supported integration broker
versions, see Broker compatibility.
- 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 provides support for bidirectional (bi-di) data when the
adapter runs on Microsoft Windows 2003 and connects to an SAP 6.20+
Unicode system, exclusively.
SAPODA changes:
- New configure agent properties have been added to the Configure Agent
window of the Business Object Designer wizard. The properties enable
new connector features, such as BAPI transaction and ResultSet support.
For details, see Table 5.
- 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.
- SAPODA supports BAPI transaction objects. For details, see BAPI transaction business objects.
- SAP provides ResultSet support for DB2 Information Integrator. For
details, see ResultSet business objects.
BAPI Module changes:
- 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 supports BAPI transaction objects. For details, Business 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. For details, see Using custom business object handlers.
- The connector provides ResultSet support for DB2 Information Integrator,
and as such uses new standard connector properties. For details, see Business object structure for BAPI ResultSets, and Appendix D, Standard configuration properties.
ABAP Extension Module changes:
- Transport files are now installed in the
\connectors\SAP\dependencies\transports_40_45_46\ and the
\connectors\SAP\dependencies\transports_47\ directories, depending
on your version of SAP. For details see Connector transport files.
ALE Module changes:
- 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.
End-of-life feature changes:
- The Advanced Outbound Wizard has been removed in this release.
- The Object Definition Generator has been removed in this release.
- The following Unit Test Tools have been removed in this release:
- Test File Generation
- Unit Test Execution
- The ability to generate a business object definition using IBM WebSphere
BI Station (formerly called IBM CrossWorlds Station) has been removed in this
release.
- The following tools have been removed from the IBM WebSphere BI Station
(formerly called IBM CrossWorlds Station):
- Development tab:
- Transaction Based- Outbound-- Hierarchical
- Tools tab:
- CW object definition
- Unit Test Tools
