SAP Mobile Development Kit

 

Release Notes

The following table describes the history of enhancements, bug fixes to the different editions of the MDK.

MDK edition

Feature, bug fix, enhancement Description
MDK 2.5 SP16 No enhancements
MDK 2.5 SP15
Error and Conflict handling

A new API for retrieving error or conflict response from the server. The application can retrieve an object that holds the information regarding the error or conflict as well as access the resolver object to which it can use in resolving the issue.

The old APIs (SyncBoInDeltaObserver, SyncBoOutDeltaObserver) are deprecated and should no longer be used.

System news A new API for handling of system news (see also this release note on SAP Help Portal) has been introduced.
MDK 2.5 SP14
RFID Reader Support on Client A new API for accessing RFID tags and their data has been introduced
MDK 2.5
SP13
SmartSync New SmartSync AWT example (Inventory example).
Performance Recommendations

Recommendations to improve the performance for the different MI APIs.

The recommendations also include the new SP13 methods:

  • SmartSync
    InboxNotifier: registerSyncReplyObserver(SyncReplyObserver)
    Field: modifyValue(Object)
    Row: modifyFieldValue(FieldDescriptor, Object)
    SyncBo: modifyRow(Row)
    SyncBoOutDeltaFacade: setSendType(SyncBoDescr, SyncBoOutDeltaSendTyp)
  • GenericSync
    InboundContainerElement: readNextElement()

 

MDK 2.5
SP12
MDK Plug-in Minor changes in checking the settings of the plug-in configuration.
MDK 2.5
SP11
SmartSync New SmartSync example (Inventory example).
AWT New persistence example with MI AWT GUI and advanced navigation.
MDK Plug-in The "Export JSP" function in the MDK Plug-in now also works when no valid MI project is selected.
PIOS New example that demonstrates the usage of the PIOS API.
MDK 2.5
SP10
Migration Guide Information how to convert an application using Transaction Manager to Persistence Manager.
JSP MI GUI New persistence example with MI GUI and advanced navigation.
MDK Plug-in The MDK Plug-in can be configured for AWT and JSP runtime simultaneously.
MDK 2.5
SP9
AWT New set of examples that contain UI components that can be used for other MI AWT applications. See AWT for more details.

MDK 2.5
1st edition

Collective note OSS 699348 This collective note contains all changes/problems with regards to this edition of MDK that were reported after the edition's official release. Please check the note for latest updates or before reporting any MDK issue via OSS.
What's new in MDK 2.5? For a complete list of changes and enhancements of MI and MDK releases 2.5 towards 2.1, please click here.
MDK 2.1
4th edition - revised
Collective OSS note 690044 This collective note contains all changes/problems with regards to this edition of MDK that were reported after the edition's official release. Please check the note for latest updates or before reporting any MDK issue via OSS.
Performance API The performance chapter describes the Performance API.
MDK Examples The name of the MDK examples given in the getApplicationName method match the name of the .war/.jar file.

The JSP examples allow now to navigate back to the ME Homepage by clicking on to the "SAP mobile engine" logo on top of every screen. The URL used to navigate back uses the standard port of the ME. Adjustments can be made in the JSP of the application.
MDK Plug-in enhancements

A "Create New MI Project" functions is now available. It creates an empty ME Project and sets the classpath and output path properly. This function is helpful to import existing sources. For more information see, Create New MI Project.

The classpath of a ME project is now always set correctly even if the listOfJars.txt file contains syntax errors or multiple entries of the same jar file.

MDK inside Eclipse The MDK documentation plug-in provides an interactive welcome page, that informs about usefule settings in Eclipse and provides links to the MDK.
New Version numbers The version number of the MDK plug-in starts now with the ME Version. The actual MDK Version in Eclipse is 2.1.4.1, indicating that it is for ME 2.1, 4th Edition, 1st revised Edition.
MDK 2.1
4th Edition
Collective OSS note 673651 This collective note contains all changes/problems with regards to this edition of MDK that were reported after the edition's official release. Please check the note for latest updates or before reporting any MDK issue via OSS.
SmartSync Information about the in and outbound handling of delta information. In/Outbound handling.
Performance A new performance chapter has been added. Enhancements for SP3 are described in "Rules for Persistence API".
MDK Plug-in enhancements The MDK Plugin for Eclipse supports now the precompilation of JSP on export and cooperates with the SAP Netweaver Development Studio.
MDK inside Eclipse The MDK documentation can now be installed and run locally as Eclipse Plug-In.
JSP examples fit on PDA The JSP examples of the MDK are adjusted so that a width of 250 pixel is not exceeded.
References A couple of new references have been added in the fields of SAP Developer Network and performance.
MDK 2.1
3rd edition
SmartSync

Complete information on development of Smart Sync applications has been integrated into the MDK. This information was priorly availably only as separate PDF document.
The chapters on deployment and testing from the original PDF are currently under revision and have not been integrated yet.

Smart Sync Wizard in MDK Plug-In

The new Smart Sync Wizard generates a fully implemented Eclipse project using the SmartSync API from any given Smart Sync meta-data XML file. Click here to learn more on how to use this feature.

MDK Plug-In needs to be upgraded in Eclipse.

Important: Eclipse Version 2.1 is necessary to use the new MDK Plugin.

Smart Sync Tutorial A tutorial including all necessary steps for developing and testing a simple Smart Sync-based application is provided here.
MDK Search The search function is an optional feature that allows to search the complete MDK documentation for terms and combination of terms. For more information see Using the MDK Search.
MDK Plug-in enhancements The classpath of a project can be updated by using the project properties - MDK properties. By pressing "Apply" the 'listOfJars.txt' in <ME_HOME> is read and the classpath is updated according to that list.
The user login performed by the Plug-in also works for AWT applications.
The source code of the project is now packaged into a srclib/myProject.src.zip (was: srclib/myProject.src.jar)
Persistence New documentation about increasing performance and how "delta" updates are handled.
JSP

Enhanced examples which demonstrate the encoding of HTML strings.

Transporting MSD For information on transporting of MSD, click here.
MDK installationon SAP J2EE Engine and Apache Tomcat MDK documentation can now be installed also on SAP J2EE Engine and Apache Tomcat 3.3 to 5.
Index tree restructuring The index tree on the left hand side of the MDK documentation has been restructured to simplify navigation.
Peripheral Support A short chapter on how peripherals (like printers, scanners etc.) can be accessed from ME can be found here.
Add-Ons As of ME 2.1 SP02, Add-Ons can be deployed in the same way as mobile applications. Administrators can thus bring virtually any set of files, libraries and even configurations to mobile devices and they'll be applied automatically during synchronization. More info...
References Useful Internet references on SAP Mobile Engine, Mobile Business, Java, JSP and SAP can be found here.
MDK 2.1
2nd edition

MDK Plug-In enhanced

Enhancements:

  • ME Login data can be set in the MDK preferences. If Login data is supplied, the MDK Plug-in does the login and starts the application directly.

MDK Plug-In needs to be upgraded in Eclipse.

JSP New basic syntax description
Persistence New examples with Object attributes, query and sorting.
AWT AWT example fixed
Contact us Contact SAP directly with your feedback or problems.
DK 2.1
1st edition revised

Release notes added

-

All examples use package names.

Class SystemInfo now contained in WAR files for the examples. Every example uses unique package names to match classloader requirements.

MDK Plug-In enhanced

Enhancements:

  • Resource Bundles had to be moved into the source folder package.
  • Classpath (external JARs) is adjusted according to listOjJars.txt in the ME_HOME folder. The classpath for existing projects can be adjusted automatically by selecting the MDK project properties. Confirming the MDK project properties menu with OK, will adjust the classpath.

MDK Plug-In needs to be upgraded in Eclipse.

MDK Startup class checks for JDK 1.4 If the MDK is started with the JDK 1.4 you are now informed (instead of an empty index tree)

ME classloader

ME classloader specification added.
Persistence Additional "how to" description in the API Overview.
Smart Sync Architecture document.
User Interface Guidelines New guidelines for "White collar" and "Blue collar" applications.
Mobile Solution Descriptor Architecture information on MSD and its usage in mobile projects.
Software logistics New software logistics chapter added.