4 what’s in this document, What’s in this document – Sun Microsystems eWay SAP BAPI User Manual
Page 12
Chapter 1
Section 1.4
Introducing the SAP BAPI eWay
What’s In This Document
eWay™ Adapter for SAP BAPI User’s Guide
12
Sun Microsystems, Inc.
What’s New in Version 5.1.2
Support for SAP ECC 6.0 (Unicode only)
What’s New in Version 5.1.1
Supports automatic deployment of EAR files to WebLogic Application Server
(version 9.1).
What’s New in Version 5.1
Version Control: An enhanced version control system allows you to effectively
manage changes to the eWay components.
Manual Connection Management: Establishing a connection can now be performed
manually (using OTD methods from the Java Collaboration) for outbound Projects
only.
Multiple Drag-and-Drop Component Mapping from the Deployment Editor: The
Deployment Editor now allows you to select multiple components from the Editor’s
component pane, and drop them into your Environment component.
Support to obtain configuration from LDAP at Runtime: eWay configuration
properties now support LDAP key values.
MDB Pool Size Support: Provides greater flow control (throttling) by specifying the
maximum and minimum MDB pool size.
Connection Retry Support: Allows you to specify the number of attempts to
reconnect, and the interval between retry attempts, in the event of a connection
failure.
Relaunchable OTD Support: An OTD can be rebuilt and saved (under the same
name) then relaunched back to the same Java Collaboration or Business Process.
This allows you to rebuild the OTD with changed metadata without having to
completely recreate the business logic from scratch.
Connectivity Map Generator: Generates and links your Project’s Connectivity Map
components using a Collaboration or Business Process.
Additional methods to commit rollback BAPI/RFC in the Java Collaboration
Definition (JCD).
All BAPI OTDs can now be used to communicate with both Unicode and non-
Unicode SAP R/3 systems.
Support for BAPI/RFC with table types, changing parameters, and nested
structures.
Date fields are now represented as Java data type strings in the JCD.
1.4
What’s In This Document
This document includes the following chapters: