This topic covers the new and enhanced features of the mobile client. This includes both mobile client for laptops and handhelds.
Mobile Client for Laptops
Feature |
Type of Change |
Description |
---|---|---|
Synchronizing Mobile Devices with Different Logins |
New |
As a mobile device user, you can log in and use any mobile device More information: Synchronizing Mobile Devices with Different Logins |
Synchronizing Mobile Devices for Completeness Check |
New |
You can synchronize the mobile device with the DOE for data completeness. More information: Synchronizing Mobile Devices for Completeness Check |
Optimizing Performance of a Mobile Application |
New |
You can optimize performance of a mobile application by creating indices, updating parameters and statistics More information: Optimizing the Performance of a Mobile Application |
Enabling End-to-End Tracing Support |
New |
Allows you to enable end-to-end tracing support on the mobile device. More information: Enabling End-to-End Tracing Support |
Configuring the ICF Service |
New |
You use the Time Agentin the Data Orchestration Engine (DOE) and the mobile client for laptops to synchronize the date and time on devices with the date and time in the DOE. The mobile client connects to the DOE to obtain the date and time. The agent connects to the DOE through an ICF service. With this release, the DOE_TIMESERVICE ICF service is introduced, and your administrator must configure this service to work with the Time Agent. More information: Configuring the ICF Service |
Enhanced Database Support for Mobile Client |
New |
With this release, the file I/O is removed. Now a database is used on mobile clients for additional transactional security. The Microsoft Windows-based platforms (laptops and tablet PCs) use MaxDB. IBM DB2E can still be used on laptops. |
Progress bar for synchronization |
New |
When a user on the mobile client synchronizes with the data orchestration engine (DOE), the client displays the following progress bars:
|
Information on trace files |
New |
A mobile client now provides the following information for traces:
|
Icons indicating the state of propagation of the data |
New |
You can now confirm the status of the data transfer from the DOE to the client. A green button on the client indicates the completeness of the data transfer and a red button indicates that the device is yet to receive the complete data. |
Index management |
New |
Previously, you needed to re-deploy the application model in the client after making changes to the indices in the DOE. However, in this enhancement, you must upload the indices to the DOE through an MCD containing the index script. You then assign it to a device. The index MCD deployed on the client will create, update or drop indices on the client application tables. |
Mobile Client for Handhelds
Feature |
Type of Change |
Description |
---|---|---|
Mobile Client for Handhelds |
New |
SAP NetWeaver Mobile now supports the mobile client for handhelds based on the embedded Standard Widget Toolkit (eSWT) , ensuring that mobile applications for handhelds provide the same look and feel as native device applications. More information: Using the Mobile Client for Handhelds |
Integrating Custom UI Elements |
New |
You can create custom embedded Standard Widget Toolkit (eSWT) controls, customize the look and feel of these controls, and add them to a mobile application for handhelds. More information: Integrating Custom UI Elements |
Enabling End-to-End tracing Support |
New |
Allows you to enable end-to-end tracing support on the mobile device by setting the appropriate property in the configuration.properties file. More information: Parameters for Tracing |
Enhanced Database Support for Mobile Client |
New |
With this release, the file I/O is removed. Now a database is used on mobile clients for additional transactional security. The Microsoft Windows Mobile-based devices (PDAs) use MinDB. IBM DB2E can still be used on PDAs. |
Enabling SSO for the Mobile Client |
New |
Single Sign-On is a mechanism that you can use to can access multiple systems with a single user ID and password. This feature was already available for the mobile client for laptops. Now SSO has also been integrated for the mobile client for handhelds. More information: Enabling SSO for the Mobile Client |