Mobile Docs Cloud Version en

PUBLIC
SAP Mobile Documents 1.0 SP05

Document Version: 1.4 May,2016
SAP Mobile Documents (Cloud Version)

Content
1 SAP Mobile Documents (Cloud Version). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 What's New in SAP Mobile Documents 1.0 Cloud Version (Release Notes). . . . . . . . . . . . . . . . . . . 6
2.1 Support Package 00, Patch 01 (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Support Package 01 (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Support Package 01 - Documentation Corrections (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
2.3 Support Package 02 (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Support Package 02 - Documentation Corrections (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Support Package 03 - Documentation Corrections (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Support Package 03 - Patch 01. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Support Package 05 - Documentation Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.7 February 2016 Release Notes for SAP Mobile Documents Cloud Version. . . . . . . . . . . . . . . . . . . . . . . .18
2.8 March 2016 Release Notes for SAP Mobile Documents Cloud Version. . . . . . . . . . . . . . . . . . . . . . . . . .19
2.9 April 2016 Release Notes for SAP Mobile Documents Cloud Version. . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.10 May 2016 Release Notes for SAP Mobile Documents Cloud Version. . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.1 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 Launching the End User Web App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2 Enabling Easy File Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Using Member Shares. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4 Connecting Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Connecting Your iOS App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Connecting Your Android App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Connecting Your Desktop App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Connecting Your Native Windows App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6 Administrator's Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1 Assigning Users to Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2 Configuring the Server and App Settings (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring the General Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
PUBLIC SAP Mobile Documents (Cloud Version)

2 2016 SAP SE or an SAP affiliate company. All rights reserved. Content
Configuring the Additional Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring the Web App Branding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring the iOS App Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring the Android App Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Configuring the Desktop App Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuring the Outlook Add-In Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuring the Windows Mobile App Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuring the Shared Documents Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Steps to Configure Notification Mails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Using Your Own Icons for File Types (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.3 Displaying User Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.4 Configuring Corporate Content Using Custom Repositories (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . .78
Configuring Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configuring Corporate Documents Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.5 Allowing iOS Users to Access Files from Outside of SAP Mobile Documents. . . . . . . . . . . . . . . . . . . . . 87
6.6 Activating the Repository Recycle Bin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7 Document Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.1 Security Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8 Monitoring with Usage Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
9 Developer's Guide (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

9.1 Developing Clients (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
CMIS Open Standard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
CMIS Enhancements for SAP Mobile Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
REST API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
URLs for App-to-App Integration of SAP Mobile Documents (Cloud). . . . . . . . . . . . . . . . . . . . . . . .112
Configuring the Server URL with a URL Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
9.2 Connecting Your ABAP Back End as a Content Source (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
SAP Mobile Documents ABAP Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Implementing the SAP Mobile Documents ABAP Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
9.3 CMIS Extension for Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
10 Supported CMIS 1.1 Features (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
11 Open Source Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

11.1 Apache License, Version 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.2 Creative Commons License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.3 Eclipse License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
11.4 Hypersonic SQL License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
11.5 Mozilla Public License Version 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
SAP Mobile Documents (Cloud Version) PUBLIC

Content 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
11.6 The BSD 3-Clause License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
11.7 The MIT License (MIT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

4 2016 SAP SE or an SAP affiliate company. All rights reserved. Content
1 SAP Mobile Documents (Cloud Version)
The help library of SAP Mobile Documents (cloud version) contains the complete description of this product.
It protects your content in easy-to-use native applications. You can run it on the following:
Microsoft Windows
Apple Mac OS
Apple iPad and Apple iPhone
Android
HTML5-enabled browsers
Windows phone and Windows tablet
This document describes the cloud edition of SAP Mobile Documents. You use the cloud administration user
interface to manage the cloud component of SAP Mobile Documents. For example, you can assign users to roles
and monitor the usage statistics on the HOME tab.
If you are interested in the on-premise use case, see the Master Guide on SAP Help Portal.
Prerequisites
You have a subscription to the cloud version of SAP Mobile Documents.

One of your employees is entered as an account member on the account page. Apart from assigning roles,
this account member can create new account members, for example, to divide out the administrative tasks
among several users.
For more information about account members, see the SAP HANA Cloud Platform documentation.
Your users have registered themselves on the accounts page at https://
account.<data_center>.ondemand.com/.

SAP Mobile Documents (Cloud Version) 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
2 What's New in SAP Mobile Documents 1.0
Cloud Version (Release Notes)
The release notes give you an overview of the new features and functions in the cloud version of SAP Mobile
Documents 1.0.
Support Package 00, Patch 01 (Cloud) [page 7]

The release note gives you an overview of changes and enhancements in release 1 SP0 Patch 01 of the
cloud version for SAP Mobile Documents.
Support Package 01 (Cloud) [page 7]

This Support Package for the cloud version of SAP Mobile Documents comprises changes and
improvements to the Web user interface as well as for the SAP Mobile Documents iOS apps. In addition,
we deliver the all new SAP Mobile Documents Android app.

improvements to the Web user interface as well as to the SAP Mobile Documents mobile apps.

improvements to the Web user interface as well as to the SAP Mobile Documents desktop app and the
SAP Mobile Documents mobile apps.

This support package of SAP Mobile Documents comprises changes and improvements to the Web user
interface as well as to the SAP Mobile Documents desktop app and the SAP Mobile Documents mobile
apps. Features that are available for only one deployment option are marked accordingly.

This support package of SAP Mobile Documents comprises changes and improvements to the Web user
interface as well as to the SAP Mobile Documents desktop app and the SAP Mobile Documents mobile
apps. Features that are available for only one deployment option are marked accordingly.
February 2016 Release Notes for SAP Mobile Documents Cloud Version [page 18]
March 2016 Release Notes for SAP Mobile Documents Cloud Version [page 19]
April 2016 Release Notes for SAP Mobile Documents Cloud Version [page 20]
May 2016 Release Notes for SAP Mobile Documents Cloud Version [page 21]

6 2016 SAP SE or an SAP affiliate company. All rights reserved. What's New in SAP Mobile Documents 1.0 Cloud Version (Release Notes)
2.1 Support Package 00, Patch 01 (Cloud)
The release note gives you an overview of changes and enhancements in release 1 SP0 Patch 01 of the cloud
version for SAP Mobile Documents.
Table 1:
Function Type of Change Description
Rebranding New SAP NetWeaver Cloud is now part of

SAP HANA Cloud. The documentation
now reflects this rebranding.
Self-registration URL Changed Adjusted the URL for accessing the ac

counts page.
List of PAM links New Added direct links to the Product Availa
bility Maps for SAP Mobile Documents.
2.2 Support Package 01 (Cloud)
This Support Package for the cloud version of SAP Mobile Documents comprises changes and improvements to
the Web user interface as well as for the SAP Mobile Documents iOS apps. In addition, we deliver the all new SAP
Mobile Documents Android app.
New Features that Affect All Apps
New wizards guide the users through the publishing workflow.

Security policies based on document classification now support you in protecting confidential data, as you
can disable dedicated actions on the different apps. The administrator defines security levels for each
repository and the documents contained in the respective repository inherit the security classification. In
addition to this security classification, the administrator selects security policies that enable or disable certain
actions for classified documents, for example, the publish action.
Quotas per user: If the PUBLISHED DOCUMENTS repository resides in the cloud, administrators can define
the space size for uploads to the cloud to limit cost. Administrators can set and modify the default user
quotas, including the warning level at which the users get a notification, that they almost used up their space.
The administrator can also set and modify the quotas for single users to allow exceptions and enable them to
still work even if the usually allocated space is used up.
The SAP Mobile Documents cloud version also supports user quotas for the MY DOCUMENTS repository.
Usage statistics are displayed in an analyst section added to the administration UI that is available for users
having the analyst role. This new screen area supplies general statistics as well as statistics on usage data on
repositories and apps during a defined period of time.
Additional security measures for the anonymous access to published folders: An additional protection
measure was implemented to prevent guessing the share password using brute-force attacks (throttling of
log on attempts).

What's New in SAP Mobile Documents 1.0 Cloud Version (Release Notes) 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
Administrators can configure additional app settings in the form name=property in the text field so that they
are transmitted to the related apps in the same form as the specific defined properties.
Administrators can configure additional connections and repositories (on-premise connectivity) for the cloud
version of SAP Mobile Documents.
The following terms changed:
External Sharing Publishing
PUBLIC DOCUMENTS repository PUBLISHED DOCUMENTS repository
SAP Mobile Documents Web User Interface
In addition to some small improvements, the Web application has the following new features:
Users can upload documents or folders in asynchronous mode from the Mobile Docs folder in the browser
(not Microsoft Internet Explorer) to other repositories, for example, to the MY DOCUMENTS or PUBLISHED
DOCUMENTS repositories, using drag and drop or copy and paste. This function is also available in the
anonymous sharing UI that the recipients of the users shared link access.
Thanks to the asynchronous handling of the delete, upload, copy, move, create, and publish operations, long
lasting operations no longer interfere with other tasks users execute in the web UI.
The users receive notifications, for example, about file uploads or file deletions. By double-clicking these
notifications, the users can display a detailed progress view where the users could also cancel the action.
SAP Mobile Documents Mobile Apps
The user interfaces for the iOS apps were redesigned, and the iPhone is now also supported.
You can use custom theming for branding on the iOS apps.
The presentation mode for the iPad, which enables users to present PDFs on external devices, was
redesigned for better user interaction.
The new Android app is available through Google Play. It offers similar features as the iOS app.
In addition, the SD card is supported. If the user switches to or from an SD card for storage, the cached and
synced documents are moved between the two, instead of requiring a re-download.
2.2.1 Support Package 01 - Documentation Corrections (Cloud)
The documentation was updated and enhanced.
Table 2:
Updated Added table of supported CMIS features.

the Web user interface as well as to the SAP Mobile Documents mobile apps.
New Features Affecting All Apps
New Sharing Concept

In SP02 there is a new concept for sharing files and folders with other users. Users can still create a public link
to a folder (share), and send this link to recipients who may not have installed SAP Mobile Documents. In
addition, users can now create a share and add named users (members) who have installed SAP Mobile
Documents and who are assigned to roles for this share (administrator, contributor, and reader). To inform
these members about updates on the share, you can use an internal link that is created automatically and
included in a mail if you choose the Mail to Members option.
This change is also reflected in the terminology: "Public Folders" and "Publish" are now only used if a app
connects to a SAP Mobile Documents server 1 SP01. For SAP Mobile Documents with SP02 components only,
the new terms are "Share" instead of "Published Folder", "Share" instead of "Publish" (the action), and
"Shared Documents" instead of "Published Documents".
Note
If you have used Published Documents in a prior release, existing public folders have been migrated to be
compatible with the new sharing solution. Users can find their existing public folders in a special share
called Migrated Public Folders and all the public folder settings, including the public URL, are still valid.
For more information, see the Sharing Files sections in the User Guide.
SAP Mobile Documents Web App
A redesign of the Web app is available with a mobile-compliant, SAP Fiori-like user interface, including a
loading indicator and breadcrumbs.
Access to Corporate Documents repositories.
New sharing process.
The Web app displays up to 50,000 files per folder. If your folder contains more files than this, you can view
them using the desktop app.
SAP Mobile Documents Desktop App
Notification on Failed Upload Due to Virus Infection

If an upload fails because the file to be uploaded is infected with a virus, the user receives a notification.

Real Time Update of Notification Window
Even if the Notifications window is open, the list of notifications is updated automatically with new
notifications.
Corporate Content Folder Available in Mobile Docs Folder
Users can view documents from corporate repositories (for example, Microsoft SharePoint and Knowledge
Management) in the Mobile Docs folder of the desktop app. Users can configure the synchronization of these
corporate documents.
New Icons to Indicate Synchronization Status:
No icon: The file or folder is not yet synchronized.
Blue arrow: The file or folder is currently being synchronized.
Green arrow: The file or folder has been synchronized but might not be up to date if you are in offline
mode.
The Mobile Docs folder is now listed under Favorites in Microsoft Explorer or Mac Finder.
Selective Sync
Users can now choose which folders they want to keep in sync. Only the My Documents folder is always
synchronized.
A new Microsoft Outlook add-in for the SAP Mobile Documents desktop app is available for Microsoft
Windows. For more information, see Sending Mail Attachments Using the Microsoft Outlook Add-In in the User
Guide.
New Icons to Indicate Synchronization Status:

No icon: The file or folder is not yet synchronized.
Green arrow on white: The file or folder is currently being synchronized.
White arrow on green: The file or folder is already synchronized.
Resume Download
If the synchronization of documents is interrupted because the app stops, the downloads are paused. When
the app starts again, the downloads can be resumed manually. This feature saves the user a lot of time and
bandwidth because the download does not have to start from the beginning each time.
Cancel Upload
On iOS apps, you can cancel the file upload. This is currently not possible on Android apps.
Sync over Cellular Network
For more information, see the Synchronizing Documents Automatically section of the User Guide on the Help
Portal.
Better Branding of UI Texts
The Setting screen is branded with standard fonts in the app. If the user changes the global setting for fonts in
the device level settings, SAP Mobile Documents is not affected, and standard fonts are applied to ensure a
standard look and feel of the app. The branding is not applied to context menu actions and pop-up display
lists.
Saving Files in SAP Mobile Documents
Users can open a file from any application using SAP Mobile Documents and save this file to any SAP Mobile
Documents folder, for which they have write permission.
Add or Delete Folders
Users can create new folders in the My Documents, Company Documents and Shared Documents folders.
Users can also delete folders from these folders.

Users can rename folders and files. For more information, see the Working with Selected Files in the
Documents List section of the User Guide on the Help Portal.
In the My Documents and the Shared Documents folders, the Add action is displayed for documents lists.
Improvements for Pictures
The document list features thumbnails for PDF files, pictures, and movies (only Apple Quicktime videos)
for files that have been downloaded to the device or that are available on the device.
Pictures in fullscreen mode can be browsed using swipe gestures.
You can import photos, take photos, and use photos.
On iOS only, the documents list can be sorted by name, type, date, and size.
The presentation mode is now available on iPhones.
Android-Only Features:
The Open, Publish, and Email actions are displayed in the action bar on selection of the relevant folders or
files.
Users can start the Android app using a mail link with the following format: mobiledocs://<link>.
2.3.1 Support Package 02 - Documentation Corrections

(Cloud)
An overview of the most important document changes of the cloud version library of SAP Mobile Documents .
Table 3:
Updated Restructured the opening topics.
Added the Glossary [page 23].
the Web user interface as well as to the SAP Mobile Documents desktop app and the SAP Mobile Documents
mobile apps.
URL Scheme
You can build URLs that perform actions in the SAP Mobile Documents app and that can be used for app-to-
app integration or as links in emails.
For more information, see URLs for App-to-App Integration of SAP Mobile Documents (Cloud) [page 112].
SAP Mobile Documents ABAP Connector

The SAP Mobile Documents ABAP connector enables ABAP applications to expose a CMIS interface to SAP
Mobile Documents. Any CMIS app can use the SAP Mobile Documents server to view or update content
stored and/or managed in an ABAP system.
For more information, see Connecting Your ABAP Back End as a Content Source (Cloud) [page 121].
Pushing Content to Devices
Content managers and administrators can collaborate to synchronize content to a user's device or to the
devices of a role-based subset of users. This is to ensure that the pushed content is available to all intended
recipients in your company independently of the individual user's sync settings.
For more information, see Configuring Corporate Content Repositories (Cloud).
Content Search
You can search for content by keywords in any repository and browse the search results quickly and easy. For
more information, see Searching for Content or Searching for Files and Folders in the User Guide.
Viewing Properties
You can view the properties of a file or a folder. For more information, see the Viewing Properties of Files and
Folders sections in the User Guide.
New language versions available
The desktop app is now available in 11 languages, the latest of which is Norwegian. For more information, see
the Configuring SAP Mobile Documents section in the Desktop Application How-Tos of the User Guide.
Suppress the My Documents Repository
The administrator can disable the My Documents repository so that end users do not have a My Documents
folder.
Using the Microsoft Outlook Add-In, you can restrict access to a newly created mail attachment share to the
recipients of the mail. In the Mobile Docs Preferences window, the Validity field was renamed to Expires In. For
more information, see Sending Mail Attachments Using the Microsoft Outlook Add-In in the User Guide.
You can display any file or folder available in your Mobile Docs folder in the Web app.
For more information, see Open File or Folder in Web App in the User Guide.
The notification that users receive if their desktop app version is lower than the one defined by the
administrator can now contain a download link set by the administrator. For more information, see .
You can choose a location for your Mobile Docs folder other than the default location. For more information,
see Configuring SAP Mobile Documents in the User Guide.
You can now set a separate synchronization interval for the Shared Documents and the Corporate Documents
repositories. For more information, see the Configuring SAP Mobile Documents section in the Desktop
Application How-Tos of the User Guide.
You can display the last 50 files and folders that have been synchronized to your desktop app. For more
information, see Displaying Recently Synchronized Files and Folders in the User Guide.
You can delete folders once they are deselected for auto-sync.
There is a dedicated tray icon ( ) that indicates that the user has logged off.

Invitations to Shares
Administrators and contributors of a share can invite other users to become share members. If new users
who have never logged on to SAP Mobile Documents before are invited to a share, they are displayed in the
members list of the share as pending users until they log on to SAP Mobile Documents for the first time.
You can also set up an invitation notification process that automatically sends mail notifications to the newly
added members of a share. For more information, see and Receiving an Invitation to a Share in the User Guide.
You can remove your own name from a share to which you have been invited.
For more information, see Receiving an Invitation to a Share in the User Guide.
ZIP files download
You can now download ZIP files using the Web app. For more information, see Downloading Folders in the
User Guide.
Adding a Public Link to a Share
You can create a public link for an existing share. For more information, see Adding a Public Link to a Share in
the User Guide.
Enhanced sorting criteria for the mobile apps.

During the installation of the mobile app, the setting of the passcode can be postponed using Skip or Skip for
Now.
For the Pushed Documents repository, the number of unread files is displayed next to the repository.
A dot marks unread files that have been pushed to the mobile device.
The SAP Learning Content format is now supported. The learning content comprises movies with the file
extension .slc and can now be opened from the Documents List. For more information, see Working with
Selected Files in the Documents List in the User Guide.
iOS: New navigation using the breadcrumb feature:
A long tap on the breadcrumb opens a list of parent folders to which the user can then switch. For more
information, see Navigating Using Breadcrumbs in the User Guide.
iOS: You can use the new help menu ( ) to start the Help Page that your administrator has configured or
send a request for support by mail with an attached log file to a preset mail address.
Android: When a user selects a client certificate, the certificate is picked from the Android KeyStore. Hence
the manual import is not required.
Android also supports fetching the user ID and server URL from the configuration on the server.
Android: If you select one or more files or folders, a Done action is shown, where you can deselect these items
again.
Android: In the documents list, a long tap on a file or folder selects this item and the actions bar shows the
respective actions.
Android: In Synced Documents, the actions for selected files and folders are shown.
Android: There is background synchronization for new devices that need to download a large number of files
and folders. The app does not time out during this synchronization.

2.4.1 Support Package 03 - Documentation Corrections
(Cloud)
The following corrections have been made to the SP03 version of this guide.
Table 4:
Type of Change Description
Updated Added the specification for the CMIS extension for search to
the Developer's Guides. For more information, see CMIS Ex
tension for Search [page 133].
2.4.2 Support Package 03 - Patch 01
The following corrections have been made to the SP03 version of SAP Mobile Documents.
The SAP Mobile Documents Modern UI of the desktop app presents the files and folders that the desktop app
synchronizes in a more touch-friendly way. The UI is available for Intel-based tablets running on Microsoft
Windows 8.1 on which the SAP Mobile Documents desktop app is installed.
For more information, see Modern UI How-Tos in the User Guide.
This support package of SAP Mobile Documents comprises changes and improvements to the Web user interface
as well as to the SAP Mobile Documents desktop app and the SAP Mobile Documents mobile apps. Features that
are available for only one deployment option are marked accordingly.
The Web app and the Microsoft Outlook Add-In offer a simplified sharing workflow.
For more information, see Sharing Files (Web app) and Sharing Files (Outlook Add-In) in the User Guide.
To optimize content distribution, administrators can select public shares to be cached on a Content Delivery
Network (CDN). Users get the files from the CDN servers instead of from the SAP Mobile Documents server
directly.
For more information, see .
For the cloud version, there is a new corporate repository type Local Repository Connection to create
repositories in the SAP HANA Cloud Platform document service. The subfolders of these repositories use the
document service permissions for granting the users access to the files and folders. Permissions for these
repositories can be managed directly in the Web app.
For more information, see Managing Folders in Document Service Repositories [page 85].
The SAP Mobile Documents ABAP connector now fully supports the CMIS 1.1 interface.

For more information, see Supported CMIS 1.1 Features (Cloud) [page 135].
For on-premise, the SAP Mobile Documents KM connector has an improved TREX search and support quota.
For more information, see Scheduling KM Quota Consistency Reports in the on-premise documentation.
The Web app, the Microsoft Outlook Add-In, and the Android app now also support branding.
For more information, see and .
All apps are available in additional languages:
Canadian French
Chinese (traditional)
Colombian Spanish
Italian
Korean
Romanian
Russian
Thai
Turkish
The following terms have been updated.
Table 5: Terminology Changes

Old Term New Term
anonymous user guest
Edit Offline, Create Version Check Out, Check In
When connected to an on-premise server, the desktop app displays user names instead of user IDs , for
example, on the Recently Changed Documents screen.
The Selective Sync option is now directly accessible from the context menu of the tray icon.
The desktop app supports pushed content to ensure that the user automatically receives documents
provided by the content administrator. The Pushed Documents folders are available on the corporate
repository level and are displayed on the Selective Sync screen.
For more information, see Synchronizing Selected Folders in the User Guide.
Users can indicate the number of log files they want to keep before the oldest log file is deleted.
For more information, see Configuring SAP Mobile Documents in the User Guide.
The Microsoft Outlook Add-in for the desktop app has a new and improved workflow with a redesigned user
and administration interface.
For more information, see Sending Mail Attachments Using the Microsoft Outlook Add-In in the User Guide.
The performance of the desktop app has been enhanced using technical improvements and updates.
For the Web app and the sharing UI, administrators can now configure links to a copyright page and a privacy
page. For more information, see Configuring the General Settings in the User Guide.

Users can now upload more than one file using the upload dialog.
For more information, see Uploading and Downloading Files in the User Guide.
Users can now remove themselves from shares they have been invited to by using the Unsubscribe action.
If users add a public link to shares that were formerly restricted to share members, only the public link is
displayed.
There is a preview available for certain file types, for example, JPG, PDF, and text files. Clicking the file names
opens the preview instead of downloading them.
For more information, see Uploading and Downloading Files in the User Guide.
Users only need to hover over the line of a file or folder in the documents list to display the properties icon ( ).
They no longer have to select the file or folder.
Users can now view the properties of files, folders, and shares and also edit basic properties.
For more information, see Viewing and Editing Properties of Files, Folders, and Shares in the User Guide.
Users can create and edit text files.
For more information, see Creating and Editing Text Files in the User Guide.
The search has been improved, for example, the three-character restriction for an entry in the search field has
been removed.
The share owner's display name is shown in the documents list and you can use it as a sort criterion.
For on-premise, the Web app displays a thumbnail view for files, if the back-end repository supports
thumbnails and has the thumbnails feature activated.
There are technical improvements and updates, for example, the high contrast black theme.
The read all feature ( ) has been updated for Android and iOS with the option to deactivate (and reactivate)
the confirmation dialog.
Depending on the server configuration, users can now log on using the OAuth logon method.
Users can edit additional properties for documents and folders.
For more information, see Viewing and Editing Properties of Files and Folders in the User Guide.
Android App
Users can refresh the list of files and folders on any screen by pulling it down.
The Android app displays user names instead of user IDs when connected to an on-premise server.
Users have quick access to the most common actions.
iOS App
There is a new executive mode with a clear, simplified user interface.
For more information, see Starting and Using Executive Mode for iOS in the User Guide.
Users can annotate PDF files.
For more information, see Editing PDF Files on iOS in the User Guide.
Users can create and edit text files.
For more information, see Adding and Deleting Files and Folders in the User Guide.
Users can upload multiple files, photos, or videos. If some files were already imported, you can decide to
overwrite the existing ones.
There is native support for iPhone 6 and iPhone 6 Plus devices.
There is a new icon indicating the connection status of the iPad app and running synchronization tasks.
For more information, see Checking the App Connection Status (iPad) in the User Guide.

This support package of SAP Mobile Documents comprises changes and improvements to the Web user interface
as well as to the SAP Mobile Documents desktop app and the SAP Mobile Documents mobile apps. Features that
are available for only one deployment option are marked accordingly.
For the cloud edition, there is now a repository-specific recycle bin with which users can restore files and
folders that were deleted.
For more information, see Using the Recycle Bin in the User Guide and Activating the Repository Recycle Bin
[page 87] in the administration guide.
When a user has opened a share, there is a new Share Details button available to change the share settings.
For shares for members, there is a new E-Mail Addresses button available that displays all email addresses of
the share members. Every share member can copy the addresses and insert them in the address field of a
mail containing the link to a share.
UI5 no longer supports Internet Explorer 8. Therefore, you have to use a modern browser, for example,
Internet Explorer 9 or higher, or Chrome, or Firefox.
iOS App
Swipe actions have been implemented for the most commonly used actions.
For more information, see Working with Selected Files in the Documents List in the User Guide.
Users can now access files from other applications supporting Apples Document Provider extension to open
files and save them back in SAP Mobile Documents. Users are able to import documents directly to SAP
Mobile Documents from other applications supporting Apples Document Picker.
For more information, see Open Files From Outside of SAP Mobile Documents in the User Guide and Allowing
iOS Users to Access Files from Outside of SAP Mobile Documents [page 87].
Users can now use the Apple Watch to control the presentations.
For more information, see Presenting PDF Files on iOS in the User Guide.
Android App
The stability has been improved.

Custom metadata properties of type URI are displayed as clickable links.
Users can enable logs before logging on to the app for first time.
Users can create folders while saving one or more files in the Android app.
For more information, see Sharing Files in the User Guide.

The performance and stability of the desktop app have been improved.
Users can now log on using OAuth.
For more information, see Installing the Desktop App for Microsoft Windows and Installing the Desktop App for
Mac OS in the User Guide.
The logon user interface has been redesigned.
SAP Mobile Documents Windows Native App
This is a completely new app for SAP Mobile Documents on Windows phones and Windows tablets.
For more information, see Installing the Microsoft Windows App and Microsoft Windows Application How-Tos
in the User Guide.
2.6.1 Support Package 05 - Documentation Update
The following changes have been applied to the SP05 version of SAP Mobile Documents.
New Features Affecting All Clients
The new Getting Started guide is linked to the tile of the SAP Mobile Documents service in the SAP HANA
Cloud Platform cockpit.
2.7 February 2016 Release Notes for SAP Mobile Documents

Cloud Version
Applications can use MIME type mapping to provide own icons for the documents they expose to SAP Mobile
Documents.
For more information, see Using Your Own Icons for File Types (Cloud) [page 72]
A group of custom properties can have a display text configured.
For more information, see Custom Groups in Properties [page 124].
Administrators can view the up-to-date usage of an individual user with the Recalculate Usage button in the
administrators user interface.

For more information, see Displaying User Information [page 77].
2.8 March 2016 Release Notes for SAP Mobile Documents

Cloud Version
SAP Mobile Documents General
There is a Getting Started guide that helps administrators to set up SAP Mobile Documents.
For more information, see Getting Started [page 25].
Users can easily access the download location of the desktop app. The URL for this location is specified by the
administrator.
For more information, see and Configuring the Desktop App Settings [page 59].
There is a new troubleshooting section that provides help for errors in the desktop app.
In the browser and on the sharing UI, users can easily download multiple files and folders as a ZIP file.
SAP Mobile Documents iOS App
You can configure a display text for a group of custom properties.

For more information, see Custom Groups in Properties [page 124].
Applications can use MIME type mapping to provide their own icons for the documents they expose to SAP
Mobile Documents.
For more information, see Using Your Own Icons for File Types (Cloud) [page 72].

2.9 April 2016 Release Notes for SAP Mobile Documents
Cloud Version
The term "client" was replaced with the term "app" for the desktop, iOS, Android, and Microsoft Windows apps.
For the Outlook add-in "client", the term client was removed and it is now called Windows Outlook add-in.
The Outlook add-in has better error handling on the share creation screen. In addition, the share table screen
that is displayed in the e-mails is now improved.
Users can now sync files to Microsoft Windows PCs even if their file paths are more than 255 characters long.
If a user tries to set an expiration date for a public link and this date is too far in the future, the system
automatically sets the expiration date to the maximum date allowed by the administrator.
SAP Mobile Documents iOS App
The initial start of the iOS app now only requires the user to enter an app passcode if the administrator
enforces app passcodes.
For more information, see Installing the iPad or the iPhone App in the User Guide.
When opening a PDF file that has a table of contents, users can now navigate directly to a specific chapter or
bookmark.
For more information about creating such a link, see URLs for App-to-App Integration of SAP Mobile
Documents (Cloud) [page 112].

2.10 May 2016 Release Notes for SAP Mobile Documents
Cloud Version
This delivery is mainly focused on performance, reliability, and health of the different apps. This includes
customer-specific and app-specific technical improvements, fixes, and enhanced support of authentication
methods, as well as a stable sync logic.
In addition, we harmonized the apps, by reworking text messages and improving user workflows so the tasks are
more understandable to the users.

3 Limitations
Some user expectations are not met with the current release.
Table 6:
App User Expectation Workaround or Fix
iOS I want to open very large PDF documents (over None.

80 MB) with the iOS app that is based on the
source code release.
iOS In an external application, I want to open files Only works if you do not use an app passcode.
from SAP Mobile Documents or save files in SAP
Mobile Documents.
Android I want to play videos for Workforce Performance None.

Builder.
Web app I am an administrator and want to upload files in Either use a Chrome or Firefox browser to upload
the admin UI under Theme Assets or Mail Assets files in the admin UI. If you are using Internet Ex
using Internet Explorer 9. plorer 9, completely reload the admin UI after the
upload.
Web app For on-premise installations, file names in non- None.

Latin languages are encoded incorrectly when
you download a folder as a ZIP file.
Web app After upgrading on-premise installations with Share owners have to disable the public link and
versioned repositories from SP04 to SP05, guest then enable it again to enable guest users to
users can access the public UI using a public link download files from the public UI.
but can no longer download any files.
Web app I want to have a reliable preview for PDF files us Download the PDF file and use a native PDF
ing a browser. viewer.
Outlook add-in In Microsoft Outlook 2010: I disabled the SAP SP04 and SP05: User has to start Microsoft Out
Mobile Documents add-in and restarted Micro look 2010 as an administrator and then disable
soft Outlook. I expect the SAP Mobile Documents the add-in.
add-in to be disabled.

22 2016 SAP SE or an SAP affiliate company. All rights reserved. Limitations
4 General
SAP Mobile Documents is a solution that securely puts critical business documents in the palm of your hand. It
gives users anytime, anywhere access to view, edit, and collaborate on corporate and personal documents.
The central documentation parts are:
Release Notes [page 6]

Getting Started [page 25] guide
Administrator's Guide [page 45]:
Configuring the Server and App Settings (Cloud) [page 46]
Configuring Corporate Content Using Custom Repositories (Cloud) [page 78]
Developer's Guide (Cloud) [page 93]
On the SAP Help Portal, you can download a PDF version of this documentation at http://help.sap.com/
mdocs_cloud10.
Related Information
Master Guide for On-Premise

Product Availability Matrix
Account Members
4.1 Glossary
Some of the central terms used in SAP Mobile Documents are defined below.
Table 7: Glossary for SAP Mobile Documents

Term Definition
app passcode Secures the application on mobile devices.
Content Management OASIS standard that works towards enabling interoperability between content management sys
Interoperability Serv tems.
ices (CMIS)
Corporate Documents Repository containing company documents and non-private documents of the user. The user does
not own these documents.
executive mode Executive mode provides a clear, minimized user interface and only shared content.
mail assets The resources used to configure the mail notifications for new share members in SAP Mobile
Documents. The administrator uploads the configuration files, mail templates, and so on.

General 2016 SAP SE or an SAP affiliate company. All rights reserved. 23
Term Definition
My Documents Repository containing the user-specific folder with the user's private documents.
password Secures the user data on the server. Used for basic authentication.
Different passwords are used to secure the access to the link that users create to enable others to
access their share.
public link A link that can be applied to a share. The link makes the share available to anonymous users.
Pushed Documents Repository that contains files and folders that are automatically synchronized to the user's apps. Ad
ministrators can restrict access to this repository to users who are assigned a specific role.
SAP Mobile Documents Application for accessing and sharing your documents and corporate documents on mobile devices,
laptops, and desktops.
SAP Mobile Documents Native mobile application, running on Microsoft Windows, Apple MAC OS, Apple iPad, Apple iPhone,
app Android, Windows Phone and tablet, and on HTML5-enabled browsers.
SAP Mobile Documents Server component running on SAP NetWeaver AS for Java. It grants unified access to repositories.
server
share To make documents available to other users.
share The root folder that is used for collaboration with other users. It can contain folders and files. Users
can create any number of shares (until their quota is used up).
Shared Documents Repository containing the shared documents and folders of a user.
Sharing UI User interface to which the recipient of the link to the published documents is taken. The recipient
does not need to be a registered user of SAP Mobile Documents.
sync Function for synchronizing documents between the server and the app. This function stores the
documents on the respective device and keeps the documents in sync.
theme assets The resources used to adjust the look and feel or graphical appearance of the user interface. For SAP
Mobile Documents, the administrator can adjust the appearance of the user interface of the Web
app, the iOS apps, and the Android apps to a company's branding by using, for example, logos, back
ground images, and lock-screen images.
user quota Space that is assigned to an individual user to store documents.
Related Information
OASIS Web page

24 2016 SAP SE or an SAP affiliate company. All rights reserved. General
5 Getting Started
You can use SAP Mobile Documents as a content service for your SAP HANA Cloud Platform account.
The following tasks contain step-by-step instructions on how to activate and set up SAP Mobile Documents.
Related Information
Launching the End User Web App [page 25]

Enabling Easy File Sharing [page 27]
Using Member Shares [page 33]
Connecting Apps [page 35]
5.1 Launching the End User Web App
Once your SAP HANA Cloud Platform account has the SAP Mobile Documents service enabled, you can start the
Web app of SAP Mobile Documents.
Procedure
1. Log on to the SAP HANA Cloud Platform cockpit.

2. Choose Services in the navigation area.
3. Select the Mobile Documents service.
4. Choose Go to Service.

Getting Started 2016 SAP SE or an SAP affiliate company. All rights reserved. 25
Results
You can now create folders or upload files, for example, by using drag and drop.
For more information about the features of the Web app, see Web Application How-Tos.

26 2016 SAP SE or an SAP affiliate company. All rights reserved. Getting Started
5.2 Enabling Easy File Sharing
Use your SAP HANA Cloud Platform service, SAP Mobile Documents, for easy file sharing.
Context
To use the ready-to-use file-sharing capabilities of SAP HANA Cloud Platform, you need to enable sharing on the
SAP Mobile Documents administration user interface (UI).
Procedure
1. Log on to the SAP HANA Cloud Platform cockpit.

2. Choose Services in the navigation area.
3. Select the Mobile Documents service.
4. To open the SAP Mobile Documents administration UI, choose Configure Mobile Documents under Service
Configuration.
5. On the administration UI, choose SETTINGS Shared Documents .

6. Select the Allow Sharing checkbox.

7. Set the other sharing parameters as necessary.
For more information, see Configuring the Shared Documents Settings [page 65].
8. Log back on to the end user Web app of SAP Mobile Documents, where you will now see the Shared navigation
area.

9. To share files, simply select them and choose Copy to Share or Move to Share, depending on your scenario.
10. Choose Create Share.

a. Enter a name for the share.
b. Choose Anyone with the link has access.
c. You can set an expiration date or enable password protection.
d. To allow the recipient of the link to upload or delete files, select Write Permission.
e. Choose Save.
Do not select the option Share with members for now. This is described in Using Member Shares [page 33].

11. Copy the URL and provide it to the recipient. Alternatively, choose Send Mail with Link to Share.
Results
The recipient can use this URL to access the files (provided the recipient knows the password).

The recipient can preview the pictures.

5.3 Using Member Shares
Create shares that are only available to a select group of people (members). As the share owner, you can only
invite users who are known to the Identity Provider.
Prerequisites
The users who create the shares and will be members of the shares must be available to SAP HANA Cloud
Platform. Therefore, the users must be maintained in the connected Identity Provider.
The users who are added as share members must be assigned the User role so they can access SAP Mobile
Documents.
You have set up a Shared Documents repository. For more information, see Enabling Easy File Sharing [page
27].
Context
The member shares help teams to collaborate on files. Development teams, for example, often share design
documents, mock-ups, and test results with each other. The team members access these documents in different
roles:
Administrator: Owns the team share and can assign members.

Contributor: Can add, edit, or delete documents in the team share.
Reader: Can view the documents in the team share.
The documents stored in team shares contribute to the quota of the share owner.
Procedure
1. Open the SAP Mobile Documents Web app to create team shares.
2. In the Web app, choose Shared. You see all the team shares where a role (administrator, contributor, or
reader) has been assigned to you.
3. Choose + Create.
4. Enter a name for the share.
5. Select Share with members.
a. To add share members, enter the logon ID or the e-mail address of the user you want to add.
Note
If you use logon IDs, users can only be resolved if they have logged on to SAP Mobile Documents at
least once.

b. Specify the member's role as Administrator, Reader, or Contributor.
c. Choose Add.
d. The members are displayed in a list with subsections for administrators, contributors, and readers. If a
newly added member has never before logged on to SAP Mobile Documents, the name is displayed with
the status Awaiting user's initial logon.
e. To copy the e-mail addresses of the share members, for example, to use them in the To field of an e-mail
containing the share link, choose E-Mail Addresses. In the box that opens, you can then select and copy
the addresses.
6. To make the team share available to people outside the team, create a public link by additionally selecting
Anyone with the link has access. You have the option to configure a password to protect the link, define a
specific time frame during which the link is available, and enable write access.

5.4 Connecting Apps
Once your SAP HANA Cloud Platform account has the SAP Mobile Documents service enabled and you have set
up the Web app of SAP Mobile Documents, you can activate the mobile and desktop apps as well.
Connecting Your iOS App [page 35]

Connecting Your Android App [page 37]
Connecting Your Desktop App [page 39]
Connecting Your Native Windows App [page 42]
For more information about the SAP Mobile Documents apps, see the User Guide.
Related Information
Launching the End User Web App [page 25]
5.4.1 Connecting Your iOS App
Before you can use the SAP Mobile Documents mobile app on your iOS device, you have to set it up.
Prerequisites
Your iOS device has version 7.0 or higher installed.
Procedure
1. Download and install the SAP Mobile Documents app by using the App Store app on your Apple device.
2. Open the SAP Mobile Documents app.
3. Choose Skip For Now. You can set the passcode later if you want to.
4. Get the server URL of your SAP HANA Cloud Platform account for SAP Mobile Documents as follows:
a. Log on to the SAP HANA Cloud Platform cockpit.
b. Choose Services in the navigation area.
c. Select the Mobile Documents service.
d. Right-click Go to Service, and copy the link address.

5. Paste the link address into the URL field of the SAP Mobile Documents app, and remove the URL part /
mcm/... so that the URL looks like this: https://<your account>.ondemand.com
6. Enter your registered e-mail address as the user name, then enter your password and choose Log On.

5.4.2 Connecting Your Android App
Before you can use the SAP Mobile Documents mobile app on your Android device, you have to set it up.
Prerequisites
Your Android device has version 4.1 or higher installed.
Procedure
1. Download and install the SAP Mobile Documents app from Google Play Store.
3. Choose Skip For Now. You can set the passcode later if you want to.
5. Paste the link address into the URL field of the SAP Mobile Documents app, and remove the URL part /
mcm/... so that the URL looks like this: https://<your account>.ondemand.com


5.4.3 Connecting Your Desktop App
Before you can use the SAP Mobile Documents desktop app on your device, you have to set it up.
Procedure
1. Download and install the SAP Mobile Documents desktop app for your OS.
2. Start the SAP Mobile Documents desktop app.

4. Paste the link address into the URL field of the SAP Mobile Documents logon window, and remove the URL
part /mcm/... so that the URL looks like this: https://<your account>.ondemand.com

5. Choose Next.

5.4.4 Connecting Your Native Windows App
Before you can use the SAP Mobile Documents native Windows app on your device, you have to set it up.
Prerequisites
Your device has Microsoft Windows 8.1 or higher installed.

Procedure
1. Download and install the SAP Mobile Documents app from Windows Store.
4. In the Log On window, paste the link address into the URL field of the SAP Mobile Documents app, and remove
the URL part /mcm/... so that the URL looks like this: https://<your account>.ondemand.com

6 Administrator's Guide
System administrators configure and administrate users and features of SAP Mobile Documents 1.0.
6.1 Assigning Users to Roles
The specific Web roles for SAP Mobile Documents contain the access authorizations for the user interfaces (UIs).
Context
SAP Mobile Documents supplies the following Web roles:
User
Enables the user to use the SAP Mobile Documents application.
Sharing User
Enables the user to access shares in the SAP Mobile Documents sharing UI to which he or she was invited.
The role does not enable the user to create shares.
Administrator
Enables the user to manage the SAP Mobile Documents administration UI. The administrator role contains
the user role. Administrators without the additional analyst role cannot view the STATISTICS page.
Analyst
User for SAP Mobile Documents with access to the SAP Mobile Documents statistics on the admin Web UI.
Analysts without the additional administrator role can only view the STATISTICS page.
Procedure
1. Log on with a user (who is an account member) to the SAP HANA Cloud Platform cockpit, using the relevant
URL for your region as described in the Logon section under Cockpit in the documentation of SAP HANA
Cloud Platform.
2. Assign the necessary role to the user as described in Managing Role Assignments under Assigning Users to
Roles in the documentation of SAP HANA Cloud Platform.
Related Information
Managing Role Assignments

Cockpit

Administrator's Guide 2016 SAP SE or an SAP affiliate company. All rights reserved. 45
6.2 Configuring the Server and App Settings (Cloud)
The administrator configures the settings that apply to the SAP Mobile Documents server and the apps.
6.2.1 Configuring the General Settings
The administrator configures general settings that apply to the SAP Mobile Documents server.
Procedure
1. Log on with an administrative SAP Mobile Documents user to the SAP Mobile Documents administration UI,
using the relevant URL for your region.
https://smd-<account_name>.<data_center>.ondemand.com/mcm/admin
For more information, see the Logon section in SAP HANA Cloud Platform Cockpit.
2. Choose SETTINGS General , and then define values as appropriate.
Table 8: My Documents Settings

Setting Possible Values Comment
Disable "My Unselected checkbox If set, the end users do not have a My Documents folder.
Documents" Default
Repository Selected checkbox
Enable Recycle Bin Unselected checkbox Only available for Local Repository Connection.
Default
Only if you enable the recycle bin for the repository can the
Selected checkbox
users restore deleted files and folders of this repository.
Recycle Bin number of days Only available for Local Repository Connection.
Retention Time
If you leave this field blank, it will be Defines a time period in days after which the repository will
(Days)
be emptied by a cleanup job. The maximum retention time
displayed with a value of 0 the next
is 999 days. If you set the number of days to 0, then the re
time you open the Manage Repository
cycle bin will not be emptied.
dialog for this repository.
Table 9: Quota Settings

Default User Quota <numerical value>. Defines the standard size in megabytes for the repository space
(MB) allocated to each user. If the value is 0, there is no space restric
Default value: 0. tion.

46 2016 SAP SE or an SAP affiliate company. All rights reserved. Administrator's Guide
User Quota <A number between 0 and Defines the quota size limit at which a notification is sent to the
Warning Level (%) 100>. user that the allocated space is almost used up.
Default value: 80
Table 10: Security Settings

Default Document Strictly Confidential Sets the classification level for the My Documents and the
Classification Confidential Shared Documents repositories.
Internal
Customer Note
Public All documents in this repository inherit the classification
level of the repository. For more information, see Docu
ment Classification.
Hide Corporate No Restriction Allows administrators to not display corporate repositories

Repositories in Default value. in the Web app depending on the security classification of
Web App Strictly Confidential the repository.
Confidential - Strictly Confidential

Internal - Strictly Confidential
Customer - Strictly Confidential
Public- Strictly Confidential
Table 11: Logging

Statistics Data Unselected checkbox (default) Enables collection of data about the daily usage, for example, the
Selected checkbox number of active logons, read accesses, and write accesses per day.
Table 12: URLs

Setting Possible Comment
Values
URL to "Privacy" <URL> Inserts a button on the landing page and on the sharing UI. If you leave the field blank,
the SAP default values are used. To hide the button, select the checkbox Disable URL
to "Privacy".
URL to "Legal <URL> Inserts a button on the standard landing page and on the sharing UI. If you leave the
Disclosure" field blank, the SAP default values are used. To hide the button, select the checkbox
Disable URL to "Legal Disclosure".
URL to "More Info" <URL> Inserts a button on the standard landing page.
on Landing Page
URL for "Help" Link <URL> Inserts a link button on the Web app using the URL you indicate, for example, to the
in Web App SAP Help Portal page at http://help.sap.com/mdocs. If you leave the field
blank, the SAP default values are used. To hide the button, select the checkbox
Disable URL for "Help" Link in Web App.
Common Download <URL> Replaces the standard download page. To not display any download button, select
URL the checkbox Disable Common Download URL.

Table 13: Theme
Theme Name <SAP UI5 theme Name of the theme you created. Currently, the sap_bluecrystal and
name> sap_hcb (High Contrast Black) themes are supported.
For more information, see SAPUI5 Theming.
Theme Root <theme folder path> Root URL of the theme.
3. Save your entries.
Related Information
SAPUI5 Theming
Security Policies [page 89]
Document Classification [page 89]
SAP HANA Cloud Platform Cockpit
6.2.2 Configuring the Additional Settings
For the iOS, Android, Web, and desktop app, you can define the settings using a properties file instead of setting
them individually.
Context
There are the following use cases for setting properties with a file instead of individually in the administration UI:
You can import the settings defined for one server to another server, for example, when you define all settings
in the test environment and then want to use identical settings in the productive environment.
After you set all properties for the app in the admin UI, you can download this settings file and reimport it into
another server. The properties file is located in the My Documents repository under Settings. The settings are
then applied in the new server. They are displayed in the Additional Settings field and the respective fields on
the settings page of the app are set.
You have a new app with new options and want to use these with a lower server version.
The new app offers more settings than the server admin UI. You can set these additional settings as key-value
pairs in the Additional Settings field.
Procedure

2. Choose SETTINGS <respective> App Additional Settings .

3. In the Additional Settings field, paste the content of the properties file or enter key-value pairs as appropriate.
5. For the new settings to take effect, restart the application.
6.2.3 Configuring the Web App Branding
Using SAP Mobile Documents, administrators define the look and feel of the Web app and adapt it to your
company's branding. Administrators define the page title, the logo, as well as the header logo.
Context
This task is optional and only required if you want to change the default settings provided by the SAP Mobile
Documents server. For the changes to take effect, restart the Web app.
Tip
The size of uploaded logo images is not adapted automatically. If an image is too large it will cover the entire
left-hand side of the Web app. We recommend a size of 80 x 40 pixels.
You set the general theme that applies to the Web app (browser) as well as the Web admin UI on the General tab.
For more information, see Configuring the General Settings [page 46].
Procedure
2. To upload logo images, choose Upload under Settings Theme Assets .
3. To use a custom page title, choose SETTINGS Web App , and then enter your text in the Page Title field.
This title is displayed right after the folder name as the tab title in the browser. Most browsers only display one
or two title characters. To see the full title, users can hover over the tab page. The full tab title is also used in
the browser history to give more details and provide a better overview.
4. To use a custom logo or header logo, choose SETTINGS Web App and select an image from the
dropdown box next to the respective logo field.

You can select different images for the logo header displayed in the upper left corner and the logo displayed in
the lower left corner.
6. For the new settings to take effect, restart the Web app.
6.2.4 Configuring the iOS App Settings
Using SAP Mobile Documents, administrators define the default settings for the iOS app.
Context
This section is optional and only required if you want to change the default settings provided by the SAP Mobile
Documents server. For the changes to take effect, you need to restart the application.
Procedure
2. Choose SETTINGS IOS App General Settings , and then define default values as appropriate.
Table 14: General Settings

Minimum App <3_digit_version_number> Defines the minimum version of the app software.
Version If the app is a lower version, the user is instructed
to upgrade to a higher version before proceeding.
Recommended App <3_digit_version_number> Defines the recommended version of the app soft
Version ware. If the app is a lower version, the user is noti
fied about the higher recommended version.

Maximum Cache No limit Sets the maximum cache size on the device. The
Size Caching is not limited. user can select a smaller but not a larger maximum
Default value. cache size. Synced documents are not taken into
account in the cache size.
None
Disables caching.
Note
50 MB
100 MB No Cache means that the documents are down
1000 MB loaded again every time the document is ac
cessed. This increases the traffic and probably
5000 MB
the costs. On the other hand, No Cache in
creases security as the documents are not
stored on the device.
Disable Support Log Unselected checkbox Allows or disallows users to activate application
The user can activate the support log. logging on their app.
Default value.
Selected checkbox
The user cannot activate the support log.
Mail Address for <Mail address of support person> Defines the mail address for support requests.
Support Requests
Mail Address for <Mail address of support person> Defines the mail address for support requests that
Support Requests in is displayed on the screen of the executive mode.
Executive Mode
Help Link for Support URL of help page Enables you to link to a help page. If set, the Help
Requests Page entry in the help menu is displayed on the iOS
screen.
Disable Automatic Unselected checkbox Defines whether users can prevent synchroniza
Sync Over Cellular The user can activate the support log. tion of their files when they cannot use a WiFi net
Default value. work.
Selected checkbox
Cellular Data <integer> Triggers the display of a warning for downloads of

Threshold (MB) or above this threshold size.

4. For the new settings to take effect, restart the iPad or iPhone application.
Related Information

6.2.4.1 Configuring the Security Settings and Security
Policies for iOS
Using SAP Mobile Documents, administrators define the security requirements that users have to fulfill when
defining their passcodes. In addition, administrators use the security policies to define which actions are available
to users in the mobile apps.
Procedure
2. Choose SETTINGS IOS App Security Settings or Security Policies, and then define values as
appropriate.

Application Passcode Checkbox selected Defines whether the application passcode

Required Application passcode is enforced. that the user sets is enforced.
Default value.
Checkbox not selected
Application passcode is not enforced.
Lock Timeout Immediately Defines the period of inactivity after which

The user has to enter the passcode immedi users have to re-enter their passcode. The
ately. user may select a shorter but not a longer
timeout.
Default value.
60 seconds
300 seconds
600 seconds
Maximum Number of 20 Defines how many times users can attempt

Failed Passcode Default value. to enter their passcode. If all attempts fail,
Attempts 3 all data is erased from the app. The user can
set a lower number of passcode attempts
5
but not a higher number.
10
Minimum Passcode 8 Defines the minimum number of characters

Length Default value. required for a passcode.
<Any number>

Passcode Must Checkbox not selected Defines whether the passcode must contain
Contain: The passcode does not have to contain such the listed character.
a character.
Lowercase Char
Default value.
acters
Checkbox selected
Uppercase Char
The passcode must contain such a charac
acters
ter.
Digits
Special Charac
ters

4. To define which actions are available to users in their iOS app, set the security policies.
For more information, see Security Policies.

6. For the new settings to take effect, restart the iPad or iPhone app.
Related Information

6.2.4.2 Configuring the iOS App Theming
Using SAP Mobile Documents, administrators define the look and feel of the iOS apps and adapt them to your
company's branding. Administrators define the highlight color as well as background or lock screen images.
Context
Documents server. For the changes to take effect, users need to restart the iOS app.
The following file formats are supported:
Table 16: Supported Formats
Format File Name Extension
Tagged Image File Format (TIFF) .tiff, .tif

Joint Photographic Experts Group .jpg, .jpeg

(JPEG)
Graphic Interchange Format (GIF) .gif
Portable Network Graphic (PNG) .png
Windows Bitmap Format (DIB) .bmp, .BMPf
XWindow bitmap .xbm
Procedure
2. To upload background or lock screen images, choose Upload under SETTINGS Theme Assets .
3. To define the highlight color and images, choose SETTINGS IOS App Theming .
4. To define the highlight color for the iPad or iPhone app, click inside the entry field and choose a color by
moving the slider, clicking the colors field, or entering values.
5. To set the theme images, select an image from the dropdown box next to the respective resolution field.
You can select different images, for example, for the portrait or landscape mode.
7. For the new settings to take effect, users restart the iPad or iPhone app.
Related Information

6.2.5 Configuring the Android App Settings
Using SAP Mobile Documents, administrators define the default settings for the Android app.
Procedure
2. Choose SETTINGS Android App General Settings . and then define default values as appropriate.
Minimum App <Version> Defines the minimum version of the app software. If the app
Version is a lower version, the user is instructed to upgrade to a
higher version before proceeding.
Recommended App <Version> Defines the recommended version of the app software. If
Version the app is a lower version, the user is notified about the
higher recommended version.
Maximum Cache Size No Limit Sets the maximum cache size on the device. The user can
Caching is not limited. select a smaller but not a larger maximum cache size.
Default value. Synced documents are not taken into account in the cache
size.
No Cache
Disables caching.
Note
50 MB
100 MB No Cache means that the documents are downloaded
1000 MB again every time the document is accessed. This in
creases the traffic and probably the costs. On the other
5000 MB
hand, No Cache increases security as the documents are
not stored on the device.
Disable Support Log Unselected checkbox Allows or does not allow users to activate application log
The user can activate the sup ging on their app.
port log.
Default value.
Selected checkbox
The user cannot activate the
support log.
Mail Address for <Mail address of support Defines the e-mail address for support requests.
Support Requests person>

Disable Automatic Unselected checkbox Defines whether users can prevent synchronization of their
Sync Over Cellular The user can activate the sup files when they cannot use a WiFi network.
port log.
Default value.
Selected checkbox
The user cannot activate the
support log.
Cellular Data <integer> Triggers the display of a warning for downloads of or above
Threshold (MB) this threshold size.

4. For the new settings to take effect, restart the Android app.
Related Information
6.2.5.1 Configuring the Security Settings and Security

Policies for Android
Using SAP Mobile Documents, administrators define the security requirements that users have to fulfill when
defining their passcodes. In addition, administrators use the security policies to define which actions are available
to users in the mobile apps.
Procedure
2. Choose SETTINGS Android App Security Settings , and then define values as appropriate.

Application Checkbox selected Defines whether the application passcode that the
Passcode Required Application passcode is enforced. user sets is enforced.
Default value.
Application passcode is not enforced.
Lock Timeout Immediately Defines the period of inactivity after which users
The user has to enter the passcode im have to re-enter their passcode. The user may se
mediately. lect a shorter but not a longer timeout.
Default value.
60 seconds
300 seconds
600 seconds
Maximum Number 20 Defines how many times users can attempt to enter
of Failed Passcode Default value. their passcode. If all attempts fail, all data is erased
Attempts 3 from the app. The user can set a lower number of
passcode attempts but not a higher number.
5
10
Minimum Passcode 8 Defines the minimum number of characters re

Length Default value. quired for a passcode.
<Any number>
Device Encryption Checkbox selected Defines whether the device must have device-level
Required Default value. encryption enabled by the Android OS to run SAP
Checkbox not selected Mobile Documents.
If this flag is set and the device is not encrypted by

Android OS, then SAP Mobile Documents will not
run on this device.
Disable Use of Checkbox selected Defines whether removable storage, for example,
Removable Storage Default value. an SD card, can be used.
Passcode Must Checkbox not selected Defines whether the passcode must contain the
Contain: The passcode does not have to contain listed character.
Lowercase such a character.
Characters Default value.
Uppercase Checkbox selected
Characters
The passcode must contain such a char
Digits
acter.
Special Charac
ters

4. To define which actions are available to users in their Android app, set the security policies.

Related Information

6.2.5.2 Configuring the Android App Theming
Using SAP Mobile Documents, administrators define the look and feel of the Android apps and adapt them to your
company's branding. Administrators define the background or lock-screen images.
Context
Documents server. For the changes to take effect, users need to restart the app.
The following file formats are supported:
Table 19: Supported Formats
Joint Photographic Experts Group JPEG (jpg)

(JPEG)
Graphic Interchange Format (GIF) GIF (.gif)
Portable Network Graphic (PNG) PNG (.png)
Windows Bitmap Format BMP (.bmp)
WebP WebP (.webp)
Procedure
2. To upload background or lock-screen images, choose Upload under SETTINGS Theme Assets .
3. To set the theme images, select an image from the dropdown box next to the respective resolution field.
You can select different images, for example, for the portrait and landscape mode.

6.2.6 Configuring the Desktop App Settings
The administrator defines default settings for the desktop app of SAP Mobile Documents.
Context
Documents server. For the changes to take effect, users need to restart the application.
Procedure
2. Choose SETTINGS Desktop App General Settings , and then define default values as appropriate.

Minimum App Version <Version> Defines the minimum version of the

app software. If the app is a lower ver
sion, the user is instructed to upgrade
to a higher version before proceeding.
Recommended App Version <Version> Defines the recommended version of

the app software. If the app is a lower
version, the user is informed about the
higher recommended version.
Minimum Synchronization Interval for 1 minute Defines the synchronization interval of

'My Documents' Default value. the My Documents repository. Users
5 minutes can choose larger but not smaller in
tervals than the default interval.
15 minutes
30 minutes
60 minutes
90 minutes
120 minutes


'Corporate Documents' 5 minutes the Corporate Documents repository.
15 minutes Users can choose larger but not
smaller intervals than the default in
30 minutes
terval.
60 minutes
Default value.
90 minutes
120 minutes

'Shared Documents' 5 minutes the Shared Documents repository.
15 minutes Users can choose larger but not
Default value. smaller intervals than the default in
terval.
30 minutes
60 minutes
90 minutes
120 minutes
Maximum Bandwidth No limit Defines the maximum bandwidth.

Largest possible value. Users can choose larger but not
Default value. smaller values than the default value
set by the administrator.
64 KB
128 KB
256 KB
512 KB
1024 KB
Disable support log Unselected checkbox Allows or does not allow users to acti
The user can activate the support vate the application logging on their
log in the app settings. app.
Default value.
Selected checkbox
The user cannot activate the sup
port log.
Mail Address for Support Requests <Mail address of support Defines the e-mail address for support
person> requests.

Download URL for Desktop App <URL to the download page for The URL must consist of the protocol
Updates the desktop app> http:// or https:// followed by
the host and page location.
The link is used in these places:
The URL is displayed in the notifi

cation that users get if their desk
top app version is lower than the
one defined in the Recommended
App Version field.
The URL is called up from the
context menu of the SAP Mobile
Documents tray icon. Under
Help Download Latest
Desktop App .

4. For the new settings to take effect, restart the desktop app.
Related Information
6.2.6.1 Configuring the Security Settings for the Desktop

App
You use these settings to define the security requirements that users have to fulfill when defining their passcodes.
Procedure
2. Choose SETTINGS Desktop App Security Settings , and then define default values as appropriate.

Allow Local Storage of Mobile Checkbox selected Defines whether the users are allowed to save the
Docs Logon Password Local storage is allowed. logon password locally on the desktop app.
Default value.
Local storage is not allowed.
3. Choose SETTINGS Desktop App Security Policies , and then define default values as appropriate.
Table 22: Security Policies
Disable Sync for Corporate <Security policy> Defines whether the users are allowed to disable the synchronization
Repositories of files in the corporate content repository on the desktop app.

5. For the new settings to take effect, restart the desktop app.
Related Information

6.2.7 Configuring the Outlook Add-In Settings
On the SAP Mobile Documents administration UI, you define the default settings of the Outlook Add-In.
Context
Documents server. For the changes to take effect, users need to restart the Outlook Add-In.
Procedure

2. Choose SETTINGS Outlook Add-In , and then define default values as appropriate.
Minimum File Size Currently not supported.

(MB)
Defines the minimum size of a file that is sent using SAP Mobile Documents
instead of as a mail attachment.
Table 24: Text Settings of the Sharing Dialog
Setting Default Values Comment
Dialog Header Text <SAP Mobile Documents> Allows you as administrator to enter
the product name that appears in the
sharing dialog header.
Tab Header Text <SAP Mobile Documents> Allows you to define the product name
that appears on all Outlook Add-In
tabs.
Table 25: Tab Color Settings of the Sharing Dialog
Font Color #FFFFFF Allows you to set the tab font color of
the sharing dialog using the color
picker dialog box.
Headers Background Color #009CE3 Allows you to set the headers back
ground color of the sharing dialog us
ing the color picker dialog box.
Background Color #FFFFFF Allows you to set the background

color of the sharing dialog using the
color picker dialog box.
Table 26: Table Settings of the HTML Table
Header Settings Allows you to define the font, font

color, and background color of the ta
Font Arial
ble header using the fonts dropdown
Font Color #009de0 list and the color picker dialog box.
Background Color #FFFFFF
Divider Row Settings Allows you to define the background

color of the divider row of the table us
Background Color #26A8E0
ing the color picker dialog box.
Uploader Row Settings Allows you to define the font, font

Font Arial
ble uploader row using the fonts drop
Font Color #333333 down list and the color picker dialog
box.

Background Color #E6F2F9
Files Section Settings Allows you to define the font, font

Font Arial
ble files section using the fonts drop
Font Color #333333 down list and the color picker dialog
box.
Background Color #FFFFFF
Title Settings Allows you to define the table title font

and font color settings using the fonts
Font Arial
dropdown list and the color picker dia
Font Color #343434 log box.

4. For the new settings to take effect, restart the Outlook Add-In.
6.2.8 Configuring the Windows Mobile App Settings
On the SAP Mobile Documents administration UI, you define the default settings of the Windows App.
Procedure
2. Choose SETTINGS Windows App and define default values as appropriate.
Minimum App 3_digit_version_number Defines the minimum version of the app software.
Version If the app is a lower version, the user is instructed
to upgrade to a higher version before proceeding.
Recommended App 3_digit_version_number Defines the recommended version of the app soft
Version ware. If the app is a lower version, the user is noti
fied about the higher recommended version.

Disable Support Log Unselected checkbox Allows or denies users the option of activating ap
The user can activate the support log. plication logging on their app.
Default value.
Selected checkbox

4. For the new settings to take effect, restart the Windows app.
6.2.9 Configuring the Shared Documents Settings
On the SAP Mobile Documents cloud administration UI, you define the default settings for the Shared Documents
repository.
Context
A Shared Documents repository offers the possibility to share documents with other SAP Mobile Documents
users and external users. If Shared Documents is enabled on the server, every user can create shares, invite
members to collaborate, and manage the access rights of these members. You can also create public links to a
share with security settings such as expiration date, password, and so on. A public link can be accessed through a
dedicated non guessable URL, which can be password protected. If enabled, anonymous users can also upload or
delete documents in a share.
Procedure
2. Choose SETTINGS Shared Documents , and then define values as appropriate.
Allow Sharing Selected checkbox Defines whether sharing is enabled.

Enabled.
Unselected checkbox
Disabled. Default value.

Maximum <number of days> Defines availability period (in days) of public links.
Expiration
Default: 0 This setting affects only the public access to docu
Time (Days)
ments. Named share members can access docu
0 means that the validity is not limited.
ments in a share for as long as they remain share
members.
If a user tries to set an expiration date that is too far

in the future, the system automatically sets the ex
piration date to the allowed maximum.
Default <number of days> Defines default period (in days) for which public
Expiration links are available. This default is displayed in the
Time (Days) Default: 0 UIs before you enter a value.
0 means that the validity is not limited.
Minimum <minimum number of characters> Defines minimum number of characters in your pub
Password lic link passwords.
Length Default: 8
This setting affects only the public access to docu
0 means that no password is enforced.
ments. Named share members can access docu
ments in a share without presenting a password.
Allow Upload Selected checkbox Enables users to decide whether they want to allow
Enabled. users who are not share members to upload files to
Unselected checkbox their share.
Disabled. Default value. This setting affects only the public access to docu
ments. Named share members can upload docu
ments to a share depending on their member role.
Share Lock <Integer value> Length of time for which the public link is locked for
Time users who are not share members if any one user
(Seconds) enters a wrong password to access the public link.
Invitation Mail None Determines whether e-mails are sent.

No e-mails are sent. Default value.
Internal
The SAP Mobile Documents server sends e-
mails.
Invitation Mail Blank Determines which recipients users can send e-mails
Domains Users can send e-mails to any mail address. to.
(Comma- Default value.
Separated)
<Name of your mail domain>
Example
sap.com,sap.de
Users can only send e-mails to recipients

whose mail account belongs to one of the
listed mail domains.

Enable Recycle Unselected checkbox Only available for Local Repository Connection.
Bin Default
Only if you enable the recycle bin for the repository
Selected checkbox
can the users restore deleted files and folders of this
repository.
Retention Time
(Days) If you leave this field blank, it will be displayed with Defines a time period in days after which the reposi
tory will be emptied by a cleanup job. The maximum
a value of 0 the next time you open the Manage
retention time is 999 days. If you set the number of
Repository dialog for this repository.
days to 0, then the recycle bin will not be emptied.
Table 29: Maximum and Default Validity of Public Links
Maximum Expiration Value Default Expiration Value By default, a new public link expires...
0 0 never
0 21 in 21 days
30 0 in 30 days
30 21 in 21 days
6.2.9.1 Configuring the CDN Access Settings for Shared

Documents
On the SAP Mobile Documents administration UI, you specify which shares can be hosted by a Content Delivery
Network (CDN).
Prerequisites
The share you want to share using a CDN must not be shared with members only but must be accessible by
anybody who receives the link to the share.
The link to the share must not be protected with a password.
Context
Because every gigabyte that is transferred using a CDN raises costs, you define that only specific shares are
allowed to be hosted by a CDN, using a whitelist. You can combine the following options to create the whitelist:
You specify individual shares that can be hosted.

You specify that all shares owned by certain users can be hosted. This option makes maintaining the list
easier for administrators.
Procedure
2. Choose SETTINGS Shared Documents , and then list the respective shares.
Table 30: Settings for CDN Access
Shares of user_id_1; The shares of the owners you list here can be hosted by a CDN.
Owners user_id_2
(User IDs
Separated
by Commas)
Shares (One share_id_1 The shares you list here can be hosted by a CDN. You find the share ID in the Web UI on
Share ID per the Access Settings of Share tab. The last part of the Link to Share entry is the share ID,
Line) share_id_2 that is, everything following shr=.
share_id_3
Example
share_id_4
In this sample URL https://example.com/mcm/public/v1/open?
shr=hSX3tyfls4MWW8zXpvPGpFdnCbrw1M_zUIY5BdwH3HM, the share ID
is hSX3tyfls4MWW8zXpvPGpFdnCbrw1M_zUIY5BdwH3HM.
6.2.10 Steps to Configure Notification Mails
The SAP Mobile Documents server provides a notification process with configurable HTML mail templates.
Currently, you can automatically send invitation mails to new members of a share if you have executed the
following setup steps:
1. Configure your mail template as described in Configuring the Mail Templates [page 69].
2. Enable the sending of mail invitations to future share members in the General settings.
For more information, see the entries referring to mails in Configuring the Shared Documents Settings [page
65].
3. Enable future share members to access the share:
The future member has a user that is linked to his or her mail address. The user is either created by the
administrator or by the users themselves in a company-specific workflow.

The future member is assigned the Sharing User role.
6.2.10.1 Configuring the Mail Templates
If the SAP Mobile Documents server is configured to send mails, the mail templates have to be configured.
Prerequisites
The SAP Mobile Documents server has been configured to send mails.
A mail template has been uploaded to the SAP Mobile Documents server. See Creating a Mail Template
Configuration File [page 69].
Procedure
2. Choose SETTINGS Mail Assets .

3. To upload a properties file with the template key and the corresponding files, choose Upload.
6.2.10.1.1 Creating a Mail Template Configuration File
To send mail notifications in SAP Mobile Documents, you must upload a properties file with a defined name that
contains the configuration of the mail template.
Procedure
1. Create the <template key>.properties configuration file that consists of key/value pairs that build the
configuration.

Currently, the following template keys are available:
Table 31:
Template Configuration Keys Comment
invitation Send to all members that are added to a share.
The template configuration is a property file that has the name <template key>.properties and consists of
key/value pairs that build the configuration. Java properties are encoded using ISO 8859-1 character
encoding. Therefore, Unicode characters that cannot be directly represented in this encoding must be
escaped.
Table 32: Template Configuration

Parameter Mandatory Comment
template x The file name of the HTML mail tem

plate.
subject x The subject of the mail. You can use

the same placeholders as in the mail
template.
sender The mail address of the sender. If no

sender address is specified, the user
who creates the invitation is the
sender.
charset The charset of the template. If no char

set is specified, the value defaults to
"text/html;
charset=windows-1250".
2. To configure additional MIME resources, for example, inline images or attachments, use the key
resource.<index>.<parameter>.
The index starts with zero and every resource has the same three mandatory parameters.
Table 33:
Resource Parameter Mandatory Comment
cid x The content ID according to RFC-2392

that is used to refer to the resource file
in the mail template.
name x The file name of the resource file.
contentType x The content type of the resource file

according to RFC-2046.
disposition Content disposition type according to

RFC-2183.
Possible values are inline (default) and

attachment.

Example
This example template is for sending share invitations including an inline logo to share members. The
uploaded assets are as follows:
invitation.properties
invitation.html
logo.jpg
The configuration file is called invitation.properties:
template=invitation.html
subject=${sender.displayname} has invited you to the Mobile Documents share "$
{name}"
resource.0.cid=logo
resource.0.name=logo.jpg
resource.0.contentType=image/jpeg
3. To use variables in HTML mail templates as placeholders, use the ${variablename} pattern for variables.
Table 34: All Possible Variables of the Invitation Template

Variable Comment
repositoryId The ID of the sharing repositoryId.
objectId The object ID of the share.
name The name of the share.
description The description of the share.
url The URL that opens the share directly.
sender.displayname The display name (first name plus last name) of the inviting
user.
sender.email The mail address of the inviting user.
sender.firstName The first name of the inviting user.
sender.lastName The last name of the inviting user.
recipient.displayname The display name (first name plus last name) of the invited
user.
recipient.email The mail address of the invited user.
recipient.firstName The first name of the invited user.
recipient.lastName The last name of the invited user.
Example
To use the first name of the invited user in the salutation of the mail template: Hello $
{recipient.firstName}.

6.2.11 Using Your Own Icons for File Types (Cloud)
Applications can provide their own icons for the files they expose to SAP Mobile Documents. To use customer-
specific icons, you map the icon to a MIME type and upload the mapping file using the administration user
interface.
Prerequisites
You created an icon.json file as described in Creating an Icon.JSON File [page 72].
Context
To provide a flexible solution, the SAP Mobile Documents server can provide additional mappings of MIME types
to the corresponding icons for all SAP Mobile Documents apps. This is not only possible for MIME types, but also
for object types or even single objects. A mapping can also be restricted to certain repositories.
The naming convention for files ensures that the app-specific icon is used, if available. If none is available, no icon
is displayed.
Only the iOS app has a fallback solution: The server looks for a standard icon. If this is also not defined, then the
fallback icon is used, which is displayed for all unkown file types. This icon is also displayed in the following
situation: If you create a mapping to an already known MIME type, for which no icon can be found on the server,
the first fallback solution is to use the default icon for this MIME type. But if this icon does not exist, that is, the
MIME type is not known, the icon for unknown file types is used.
Procedure
2. Choose SETTINGS Icon Assets .

3. To upload the icon.json file containing the mapping of an icon file to a MIME type, choose Upload.
4. To download or delete a file, select it and choose Download or Delete.
6.2.11.1 Creating an Icon.JSON File
To create an icon mapping, you need to provide an icon file to upload.
You create an icon.json file using the elements, file syntax, and rules listed below.

Icon File Properties
Table 35:
Web App iOS App Android App Mac Desktop Windows Desk Windows Na
App top App tive App
Suffixes @2 @2x -ldpi none none .scale-100

(default)
@3x -mdpi (de
fault) .scale-140
-hdpi .scale-150
-xhdpi .scale-160,
-xxhdpi .scale-180
.scale-240
Required Icon <file <file <file <file <file <file

Files name>.<ext> name>.<ext> name>.<ext> name>.icns name>.ico name>.<ext>
<file <file <file name>- <file

name>@2.<ext> name>@2x.<ext ldpi.<ext> name>.scale
> -140.<ext>
<file name>-
<file hdpi.<ext> <file
name>@3x.<ext name>.scale
> <file name>-
-150.<ext>
xhdpi.<ext>
<file
<file name>-
name><.scal
xxhdpi.<ext
e-160.<ext>
>
<file
name>.scale
-180.<ext>
<file
name>.scale
-240.<ext>
Comment n.a. n.a. The Android n.a. n.a. n.a.

app has to
parse the file
name and put it
as <file
name>.<ext>
under the corre
sponding re
source folder.
The mapping is a rule that consists of one or more of the following key fields:

MIME type
Object type
Object ID
Repository
The key maps to a localized display name and app-specific or generic icon files.
Rules Engine
Rules contain the following elements:
MIME type
Table 36:
Key Values Comment
mimeType An array of technical MIME types The values are case-insensitive, for example,
for which the rule is valid, for ex application/pdf is the same as "application/PDF".
ample, application/pdf. Parameters for mime types are not supported and cut
if existing, for example, text/plain;charset=us-
ascii.
Object type
Table 37:
Key Values Comment
objectType An array of IDs as defined in the The values are matched against the values of the men
CMIS property tioned CMIS properties of the object.
cmis:objectTypeId or
cmis:secondaryObjectTypeId
s, for example, cmis:document.
Object ID
Table 38:
Key Values Comment
objectId An array of IDs of a folder or a file, The option to define specific object IDs is only for use with
if the mapping should only be valid folders not with documents.
for certain objects, for example,
dRnMfRD5TJCCIQ6TU6aFM2jW8H
BrRKtqeWXp5NycGXs.
Repository

Table 39:
Key Values Comment
repository An array of IDs of the repository for If no value is specified, the rule is valid for all repositories.
which the rule should be valid, for
example,
be6348c15c552fc071e04515.
Display Name
Table 40:
Key Values Comment
names A map of localized display names Texts for all supported languages of SAP Mobile
where the key is a two-letter locale Documents should be provided, but the field is op
according to ISO 639-1, for exam tional.
ple, en. If no name for a specific language is defined, the fall

back language is English.
Therefore, if the field is specified, at least the display
name for English must be provided.
The display name of a specified language must not be
null.
File Name
Table 41:
Key Values Comment
fileName A list of icon file names for the spe Possible keys: iOS, android, web, desktop, windows,
cific apps or a default icon if no standard
specific icon is specified for a app, The specified icon files, including the ones for the dif
for example, iOS : ferent resolutions, have to exist in the Settings reposi
iconInvoice.png. tory under the folder icons.
Mandatory field that must contain at least one key with
a value.
JSON File Syntax
File Format
Code Syntax
{ "icons" :
[{ "mimeType" : ["...","..."],
"objectType" : ["...","..."],
"objectId" : ["...","..."],
"repository" : ["...","..."],
"names" : { "<locale>" : "...", ... },

"fileName" : { "<app>" : "...", "standard" : "...", ... }
},
{
...
}]
}
Sample Code
{ "icons" :
[{ "mimeType" : ["application/invoice","application/order"],
"objectType" : null,
"objectId" : null,
"repository" : ["be6348c15c552fc071e04515"],
"names" : {"en":"Invoice", "de":"Rechnung"},
"fileName" : {"iOS":"invoice-iOS.png", "standard":"invoice.png"}
}]
}
Rule Evaluation Examples
Example 1
Rule 1: MIME type = application/invoice, file name = invoice.png
Rule 2: Object type = cmis:document, file name = document.png
Object: Object type = cmis:document, MIME type = application/invoice
Result: The invoice.png icon is used, because the MIME type is more specific than the object type.
Example 2
Rule 1: MIME type = application/invoice, file name = invoice.png
Rule 2: Object type = cmis:document, repository = 12345, file name = document.png
Object: Object type = cmis:document, MIME type = application/invoice, repository = 12345
Result: The invoice.png icon is used, because the MIME type is more specific than the object type and
repository restriction together.
Example 3
Rule 1: Object ID = abcd1234, file name = demo.png
Rule 2: Object type = cmis:document, MIME type = application/invoice, repository = 12345, file name =
invoice.png
Object: Object type = cmis:document, MIME type = application/invoice, repository = 12345, object ID =
abcd1234
Result: The demo.png icon is used, because the object ID is the most specific key element.
Example 4
Rule 1: Object ID = abcd1234, file name = demo.png
Rule 2: Object ID = abcd1234, file name = invoice.png
Object: Object ID = abcd1234
Result: Invalid state! Should have been prevented before the configuration became active. The app should use
neither of the icons, but display the default fallback icon of the app and log an error.

6.3 Displaying User Information
The administrator can, for example, delete users or recalculate how much of their quota they have used on the
SAP Mobile Documents server.
Procedure
2. Choose USER DATA.
3. Select a search criterion from the dropdown list, for example, the logon ID, and enter the user's details.
Note
You can use asterisks (*) as wildcards.
The search is case sensitive.
4. To view a user's details, click any of the links underlying the user's logon ID, last name, first name, or e-mail
address.
The popup that appears shows the User Details, including the user's quota. To ensure that the quota value is
definitely up to date, choose Recalculate Usage. The second half of the popup shows the Repository Details for
this user.
Table 42:
ID Description
Home Repository ID ID of the My Documents repository of the SAP Mobile Documents instance.
Home Folder ID ID of the user's personal folder used for his or her My Documents.
Sharing Repository ID ID of the Shared Documents repository of the SAP Mobile Documents instance.
Sharing Folder ID ID of the user's personal folder used for his or her Shared Documents.
Settings Repository ID ID of the settings, which administrators can configure for the SAP Mobile Documents clients.

ID Description
Settings Folder ID ID of the settings folder used for this user. There is, for example, a settings repository that enfor
ces app passcodes for mobile clients.
Administrators can use this field to assign a specific settings repository to a user.
Caution
Be very careful and only change these fields if you are very sure of what to do.
5. To delete a user, select the row with this user's data, then choose Delete.
Users are automatically added when they first log on to SAP Mobile Documents. Administrators can delete
users, for example, if a user has left the organization. This user's license is freed up and can be reassigned to
another user.
Note
To prevent the user from accessing any files, remove the User. To delete a user, select the row with this
user's role from his or her user profile in your identity management tool.
a. To delete the deleted user's documents from the repositories, select the Also delete user's documents
checkbox in the confirmation dialog.
b. Confirm the deletion with OK.
6.4 Configuring Corporate Content Using Custom

Repositories (Cloud)
SAP Mobile Documents enables you to leverage further use cases by enabling the consumption of corporate
content by your on-premise data management systems.
Procedure
1. Set up the SAP HANA Cloud Platform connectivity service.

2. Upload a destination pointing to the CMIS server on the on-premise document management system (DMS)
using the SAP HANA Cloud Platform SDK.
a. Set up the SAP HANA Cloud Platform console client.
b. Configure the HTTP destination for a subscribed application to your DMS from the console client.
3. On the administration UI, configure the connections as described in Configuring Connections (Cloud).
4. On the administration UI, configure the corporate content as described in Configuring Corporate Content
Repositories (Cloud).

Related Information
Connectivity Service
SAP HANA Cloud Platform Console Client
Setting Up SAP HANA Cloud Platform Console Client
Configuring Destinations from the Console Client
Configuring Connections [page 79]
6.4.1 Configuring Connections
Some repository configurations require you to configure a connection as a preliminary step.
Prerequisites
Read the parameter list below and define the connections required for your SAP Mobile Documents scenario.
Procedure
2. Choose REPOSITORIES Connections .

3. To create a new connection, choose Create.
4. On the Manage Connections screen, enter the parameters that are appropriate for your back-end system and
its repositories:
Table 43: Connection Details
Display Name <DISPLAY-NAME> Arbitrary display name for the repository connection table to identify
the connection in the repository configuration.
Destination <DESTINATION- Destination name. See To upload a destination for a subscribed applica
NAME> tion... in the Uploading Destinations section of the SAP Mobile
Documents documentation.

Options Key1=Value1 The connection options are key-value pairs. You can use them to define
additional parameters or to override default values. For a detailed table
Key2=Value2 with all possible values, see below.
Table 44: Connection Options
Option Default Value Description
org.apache.chemistry.opencmis.binding.spi.typ browser Defines the binding type that is

e used to connect to the remote re
pository. SAP Mobile Documents
supports the following bindings:
browser
atompub
local
The browser binding is used as a

default within the SAP Mobile
Documents server. If connecting a
repository that only offers a CMIS
AtomPub interface, configure
org.apache.chemistry.openc
mis.binding.spi.type=atomp
ub in the connection options (for
example, for Microsoft Share
Point).
org.apache.chemistry.opencmis.binding.clientc false If the remote repository supports

ompression gzip compression of requests, you
can activate the compression of
requests sent by the server by set
ting this parameter to true.
org.apache.chemistry.opencmis.binding.connect 60000 Defines the HTTP connect timeout

timeout in milliseconds.
org.apache.chemistry.opencmis.binding.readtim 300000 Defines the HTTP read timeout in

eout milliseconds.
com.sap.mcm.restrictedQuery false The mobile clients send queries to

the repositories using the
cmis:objectId when documents
are marked as synced. Some re
positories (for example, Microsoft
SharePoint) do not support query
ing of documents by object ID. If
com.sap.mcm.restrictedQuer
y=true is set, then the SAP Mobile
Documents server simulates the
query and returns the necessary
results even though the query itself
is not supported by the back-end
repository.

Option Default Value Description
com.sap.mcm.userIdHeaderName not applicable If the Header Connection con

nection type is used to connect to
repository servers that accept ex
ternal authentication, the addi
tional
com.sap.mcm.userIdHeaderNa
me parameter is used to specify the
name of the HTTP header where
the SAP Mobile Documents server
injects the logon ID of the current
user.
org.apache.chemistry.opencmis.workaround.incl true Only relevant for SharePoint 2010.

udeObjectIdOnCheckout
org.apache.chemistry.opencmis.workaround.incl true Only relevant for SharePoint 2010.

udeObjectIdOnMove
org.apache.chemistry.opencmis.workaround.omit true Relevant for SharePoint 2010 and

ChangeTokens 2013.
org.apache.chemistry.opencmis.workaround.addN true Relevant for SharePoint 2010 and

ameOnCheckIn 2013.
com.sap.mcm.contentHttpDestination not applicable Only relevant for RFC connections.
Defines the destination that is to

be used for content uploads and
downloads if the content is trans
ferred using HTTP.

6. Repeat the steps for all systems that you want to connect to SAP Mobile Documents.
Related Information

Uploading Destinations

6.4.2 Configuring Corporate Documents Repositories
SAP Mobile Documents enables you to set up one or more corporate repositories for your company, containing
company documents that are not owned by the app users.
Prerequisites
Ensure that the required connection for the Corporate Documents repository is available (see Configuring
Connections).
To connect to an on-premise SAP Knowledge Management system, the SAP Mobile Documents KM
Connector must be installed on the remote server. For more information, see SAP Mobile Documents KM
Connector.
If you are using SAP HANA Cloud Platform services and want to connect to an on-premise server that is not
already available over the Internet, you must configure the SAP HANA Cloud Platform Connector.
For more information, see the SAP HANA Cloud Platform documentation.
For the Pushed Content option, the following assumptions apply:
The administrator informs the content managers about the repositories that are pushed (including this
information in the repository description).
Content managers have at least write authorization for these repositories so that they can create, delete,
or update the content there.
Context
The corporate repositories are only displayed in the mobile apps or in a custom app built with the Software
Development Kit (SDK) that enables the function explicitly. In addition, you have the option to push content to a
corporate repository. That is, you can synchronize content on a user's device independently of the user's sync
settings for the respective content.
Procedure
2. Choose REPOSITORIES Corporate Content .

3. To create a new repository connection, choose Create.
4. On the Manage Repository screen, enter the following parameters as appropriate:

Table 45: Details
Connection <CONNECTION NAME> The dropdown box lists all available connections
defined in Configuring Connections plus the Local
Repository Connection used for SAP HANA Cloud
Platform document service repositories.
Note
Due to the tenant isolation in SAP HANA Cloud
Platform, the document service cockpit cannot
access or view repositories you create in SAP
Mobile Documents or vice versa.
Repository <REPOSITORY NAME> The dropdown box lists all available repositories for
the connection parameter.
Display Name <DISPLAY NAME> Predefines the name of the repository displayed in
the mobile app. To display a custom name for the
repository, adjust the setting.
Description <DESCRIPTION> Predefines the description of the repository. Is not

displayed in the mobile app.
Pushed Unselected checkbox (default) Defines whether the corporate repository contains
Content Selected checkbox pushed content.
For examples of the possible combinations of the

pushed content options, see the next table.
Restricted To <role or a semicolon-separated Defines that only those users who have at least one
list of roles> of these roles can see the pushed content. For
other users the repository is not visible at all.
The roles are maintained in the SAP HANA Cloud

Platform cockpit.
Show as Unselected checkbox (default) Defines that users who are not assigned any of the
corporate Selected checkbox UME roles that are specified in the Restricted To
content for field can see the repository.
other users
This checkbox is only displayed after the corporate
repository has been marked as Pushed Content, a
role has been specified in the Restricted To field,
and you have clicked into another field.
Root URI <REPOSITORY-PATH> Defines a specific folder within the repository to be

the root folder displayed in the mobile app.
Format: /<section1>/<section2>
Document Public Defines the classification level of the repository.

Classification Customer This classification is inherited by all documents
Internal that the repository contains.
Confidential For more information, see Document Classifica
Strictly confidential tion.

Hide Unselected checkbox (default)

Repository Selected checkbox
Enable Recycle Unselected checkbox Only available for Local Repository Connection.
Bin Default
Only if you enable the recycle bin for the repository
Selected checkbox
can the users restore deleted files and folders of
this repository.
Retention Time
If you leave this field blank, it will be displayed with Defines a time period in days after which the repo
(Days)
sitory will be emptied by a cleanup job. The maxi
a value of 0 the next time you open the Manage
mum retention time is 999 days. If you set the
Repository dialog for this repository.
number of days to 0, then the recycle bin will not
be emptied.
Managed By <userID1>,<userID2>,<userID3> Only available for the Local Repository Connection

type.
Enter the user IDs (separated by commas) of the

user administrators of the root-level folder in the
SAP HANA Cloud Platform document service repo
sitory. These administrators have the CMIS_ALL
permission and manage the access (permissions)
of other users to the subfolders that are created in
this repository.
Table 46: Samples of Combinations of the Pushed Content Options
Settings Effect
The Pushed Content checkbox is not selected. Pushed content is not used. The repository is visible to all
The Restricted To field is empty. users as a corporate repository.
The Pushed Content checkbox is not selected. Pushed content is not used. The corporate repository is only
The Restricted To field contains the Reviewer role. visible to users who are assigned at least one of the roles listed
in the Restricted To field, in our example the Reviewer role.
The Pushed Content checkbox is selected. All users see the repository as pushed content.
The Restricted To field is empty.
The Pushed Content checkbox is selected. Users who are assigned the Reviewer role see the repository
The Restricted To field contains the Reviewer role. as pushed content. No other users can see the repository.
The Show as corporate content for other users
checkbox is not selected.
The Pushed Content checkbox is selected. Users who are assigned the Reviewer role see the repository
The Restricted To field contains the Reviewer role. as pushed content. All other users see the repository as a nor
The Show as corporate content for other users mal corporate repository.
checkbox is selected.

6. Repeat the steps for all systems that you want to connect to SAP Mobile Documents.

Results
The apps use the repository information to determine which of the corporate repositories the current user can
view and which of these repositories are marked as pushed content:
Repositories that the current user cannot view are not included in the repository information.
Repositories that are marked as pushed content for the current user have the extension pushedContent:
"true" in the repository information. (Remarks: The value true has type string, not boolean. If a repository
is not marked as pushed content, the pushedContent extension is skipped. There is no such extension as
pushedContent: "false".)
Related Information
Configuring Connections [page 79]

Document Classification [page 89]
SAP HANA Cloud Platform Connector
6.4.2.1 Managing Folders in Document Service Repositories
Root folder administrators can create subfolders and assign permissions to other users for accessing these
subfolders.
Prerequisites
Your SAP Mobile Documents administrator has set up an SAP HANA Cloud Platform document service
repository.
Your SAP Mobile Documents administrator has assigned the CMIS_ALL (All) permission for the respective
document service repository to you, that is, your user ID is listed in the Managed By field of the repository.
Context
Note
Due to the tenant isolation in SAP HANA Cloud Platform, the document service cockpit cannot access or view
repostories you create in SAP Mobile Documents or vice versa.
If you are a root folder administrator, you can do the following:

Create a subfolder in the repository.
Change the properties of the subfolder.
Create an ACL for the subfolder, that is, add users to the subfolder and assign a document service repository
permission to each of them.
The users are then listed in this order: the folder owner, the Everyone user/role, users whose email addresses
cannot be resolved, known users in alphabetical order.
You can assign the following permissions, listed from the weakest to the most powerful permission:
Read: Permission to access files and folders and to read their properties, content, and ACLs.
File: Includes the Read permission and in addition the permission to change the children of the folder as well
as the parent of the node.
Write: Includes the File permission and in addition the permission to change the properties and the content of
the children as well as the parent of the node.
Delete: Includes the Write permission and in addition the permission to delete a file or folder.
All: Includes the Delete permission and in addition the permission to change the ACL.
Procedure
1. Log on to the Web app and open Corporate Documents.
2. To create a subfolder in the document service repository, choose Create New Folder .
3. Enter the folder name and confirm with OK.
4. Select the subfolder and choose the Properties icon ( ) to view its properties.
5. Choose the Permissions icon ( ).
6. Choose Edit ( ).
7. Enter the e-mail addresses or the IDs of the users separated by semicolons.
8. Select the permission to assign to these users, and choose Add.
9. In the users list, you can change the permission for each user using the dropdown box.
10. To save your changes, choose Save.
11. To delete a user, choose the Remove icon ( ) in edit mode.
Related Information
SAP HANA Cloud Platform Document Service

6.5 Allowing iOS Users to Access Files from Outside of SAP
Mobile Documents
On iOS devices, users can open files that are stored in SAP Mobile Documents in other applications. For example,
if a user works in Microsoft Office 365, he or she can open a word file that is stored in SAP Mobile Documents.
As an administrator, you have to allow users to access such files using the following settings:
Users must be allowed to disable their passcodes for SAP Mobile Documents.
To make files accessible in the extension, you have to set the security policy for the document provider in the
administration UI.
Related Information
Configuring the Security Settings and Security Policies for iOS [page 52]
6.6 Activating the Repository Recycle Bin

With the cloud edition of SAP Mobile Documents 1.0 you can activate the recycle bin for a repository to enable
users to restore files or folders that were deleted by mistake.
Recycle bins are repository-specific. Your administrator can activate bins for one or more repositories. A recycle
bin contains only the files and folders that were deleted in a specific repository. If you do not restore the objects,
they will be cleaned up automatically after a period of time defined by your administrator. In addition, you can also
permanently delete selected files and folders or all content from a repository recycle bin.
The following rules apply to deleted files and folders:
You cannot update a deleted file or create a new version for it unless you restore it first.
Files and folders in the recycle bin must be restored before you can edit or download them.
You can only restore a complete folder with all its content, not parts of it.
If file name conflicts occur, the restore operation fails with a name constraint violation. You have to ensure
manually that no file with the same name exists in the original location. Folders with the same name will be
merged if they do not contain files or folders with the same name.
You find restored files and folders in their former location, that is, the repository that you deleted them from.
The content of the recycle bin is not added to your user quota, but is automatically deleted after a specified
period of time.
The recycle bin contains entries for the following repository types:
My Documents
Deleted files and folders can only be accessed by their owner. You can restore files and folders until the
recycle bin is automatically cleaned up, for example, for a 30-day period.
Shared Documents
Deleted shares, files, and folders can only be restored by their owner. If a share is deleted, it loses all its
properties. Even if you restore it, it remains a plain share without members or public link settings. The share

owner has to add the members again. If a share administrator deletes a share, it is moved to the owner's
recycle bin. Only the owner can then restore the share. If you restore files, not shares, the restored files inherit
the current access right settings of the share.
Corporate Documents
Only users who are configured as administrators for a repository can restore or permanently delete objects
from the recycle bin. All access rights are inherited from the original parent folder. Original ACLs (if specific to
the deleted object) are not preserved. If you restore a folder of a repository with a local repository connection,
you have to create a new list of users who have permission to access the folder. See Managing Folders in
Document Service Repositories in the cloud admin guide.
To activate the recycle bin and set the retention time for the files and folders, see the relevant sections for the
respective repositories:
My Documents Repository: Configuring the General Settings [page 46]

Shared Documents Repository: Configuring the Shared Documents Settings [page 65]
Corporate Content Repositories:

7 Document Classification
Administrators can use document classification to control which actions are available to users in the different SAP
Mobile Document apps, based on the document confidentiality level.
The SAP Mobile Documents solution enables users to access corporate documents from a variety of apps,
including a desktop app, a Web app, an iPhone or iPad app, and an Android app. As mobile devices often leave the
company premises and the Web app might be accessed from outside the corporate network, you want to restrict
the possible actions that can be performed on corporate documents based on their document classification.
Therefore, SAP Mobile Documents supports enforcing a secure container for confidential documents.
Security policies based on document classification determine the allowed actions. Therefore, administrators can
control the available actions in the apps, for example, whether a document can be printed, e-mailed, or opened
using a specific program. The policies only apply to documents and repositories, not to folders.
Note
SAP Mobile Documents can only guide the users by providing a security-compliant solution. It cannot prevent
the intentional violation of security policies by users, for example, by taking screenshots.
Currently, document classification supports a fixed set of security classifications for repositories only. The
administrator classifies the confidentiality level for one or all repositories by choosing one of the predefined
confidentiality levels in the app settings of the administration UI:
Strictly Confidential
Confidential
Internal
Customer
Public
The SAP Mobile Documents server adds the confidentiality level as a property to each document. In combination
with the security policies, the effect for the users is that they can still see the disabled action, but it is grayed out
and cannot be executed for the selected document.
7.1 Security Policies
In SAP Mobile Documents, administrators use a combination of security policies and the document classification
level of the repositories to define which actions are available to users in the mobile apps.
The security policies are defined for mobile apps in the administration UI. The following policies are available for
the iOS app and the Android app:
Disable Open
Disable Sync
Disable Print

Document Classification 2016 SAP SE or an SAP affiliate company. All rights reserved. 89
Disable Clipboard
Disable Send
Disable Sharing
Disable Open In
Disable Document Provider
Each of these policies can be disabled for certain document classification levels with the following choice of
settings:
Table 47: Security Policy Settings

Setting Description
No Restriction This function is available in all repositories irrespective of the

document classification level.
Strictly Confidential This function is disabled in repositories classified as strictly

confidential.
Confidential - Strictly Confidential This function is disabled in repositories classified as confiden

tial or strictly confidential.
Internal - Strictly Confidential This function is disabled in repositories classified as internal,

confidential, or strictly confidential.
Customer - Strictly Confidential This function is disabled in repositories classified as cus

tomer, internal, confidential, or strictly confidential.
Public - Strictly Confidential This function is disabled in all repositories.

90 2016 SAP SE or an SAP affiliate company. All rights reserved. Document Classification
8 Monitoring with Usage Statistics
The analyst UI provides an impression of how the users and the user apps use the system. Analysts either use the
dashboard to get an overview of the system usage or they export the raw data file in XML format to carry out
further evaluations of the data.
Prerequisites
To enable data collection, a user with the Administrator role must have activated logging by selecting the
Statistics Data checkbox under SETTINGS General Logging .
You are assigned the Analyst role.
Procedure
2. On the STATISTICS page, choose either General Statistics or Usage Statistics.
The General Statistics page displays the same information as the HOME page.
3. On the Usage Statistics page, choose a time interval and a repository from the respective dropdown lists.
4. To display the usage statistics, choose Show Dashboards.
5. To export the data to a file, choose the file format Export Raw Data (xml), Export Raw Data (json), or Export
Raw Data (csv).
The download evaluates the entries in the dropdown boxes and exports a file accordingly.
Results
The XML file contains entries that are created per day, per user agent (usually apps), and per repository. An entry
contains the following data:
Number of times a app has logged on

Number of read or downloaded documents
Number of new documents
Number of changed documents (this only reflects changes to the content and not formal changes, for
example, renaming a document)

Monitoring with Usage Statistics 2016 SAP SE or an SAP affiliate company. All rights reserved. 91
Size of all documents read
Size of all updated or newly created documents
The dashboard displays the same data, but the data for newly created and updated documents is shown in a
single graph.
Related Information

92 2016 SAP SE or an SAP affiliate company. All rights reserved. Monitoring with Usage Statistics
9 Developer's Guide (Cloud)
You can develop your own clients or servers for SAP Mobile Documents using the respective developer's guide.
Related Information
Developing Clients (Cloud) [page 93]

Connecting Your ABAP Back End as a Content Source (Cloud) [page 121]
CMIS Extension for Search [page 133]
9.1 Developing Clients (Cloud)
To develop your own clients, you need to be familiar with the architecture of SAP Mobile Documents, the CMIS
open standard, and its SAP Mobile Documents extensions.
You can develop your own clients that connect to the SAP Mobile Documents server or you can integrate SAP
Mobile Documents functionality into existing platforms.
Related Information
Architecture [page 93]

CMIS Open Standard [page 94]
CMIS Enhancements for SAP Mobile Documents [page 97]
REST API [page 109]
URLs for App-to-App Integration of SAP Mobile Documents (Cloud) [page 112]
Configuring the Server URL with a URL Scheme [page 121]
9.1.1 Architecture
The main components of the SAP Mobile Documents solution are the clients, the server, and the document
repositories.
To ensure interoperability and extensibility, the OASIS standard CMIS (Content Management Interoperability
Services) is used for all document-related communication between the clients and the server as well as between
the server and the repositories. In the current version of the solution (1.0 SP2), we deliver clients for the desktop
(Windows and OS-X), for mobile devices (iPhone, iPad, and Android phones), and a JavaScript-based Web UI.

Developer's Guide (Cloud) 2016 SAP SE or an SAP affiliate company. All rights reserved. 93
All clients connect to and communicate with a single server, the SAP Mobile Documents server, using the CMIS
protocol. The SAP Mobile Documents server is offered as a cloud-based solution (subscription model) and as an
on-premise installation (SAP NetWeaver Application Server for Java). On the server, you can configure settings,
users, and connectivity configurations for integrating CMIS-compliant document management systems.
As well as connecting additional (corporate) repositories to the server, SAP Mobile Documents offers dedicated
repositories to the clients:
The My Documents repository

The repository where every SAP Mobile Documents user can store their personal files and then synchronize
the repository content with all connected clients. Every user has a folder that is marked as their "home" folder.
All folders and files in this home folder are only visible and accessible to the user.
The Shared Documents repository
The repository where SAP Mobile Documents users can share files with each other as well as with external
users. If Shared Documents is enabled on the server, every user can create shares, invite members to
collaborate, and manage the access rights of these members. To share files with external parties, users must
create public links to shares with security settings such as expiration date or password. A public link is
accessible through a dedicated non-guessable URL, which you can additionally protect with a password. If you
enable the write option for a share, anonymous users can also upload or delete documents in this share.
9.1.2 CMIS Open Standard
CMIS (Content Management Interoperability Services) is an open standard that defines a common interface for
various operations offered by content management systems. CMIS defines a domain model and operations for
different binding types.
CMIS is language-independent, which gives it a significant advantage over other specifications, and many vendors
offer (or are going to offer) CMIS interfaces to their systems. In addition, CMIS client libraries already exist in
different programming languages. Many of them are available as Open Source implementations under the

94 2016 SAP SE or an SAP affiliate company. All rights reserved. Developer's Guide (Cloud)
umbrella project Apache Chemistry. SAP uses the Chemistry components for both app and server
implementations.
Prerequisites for Developers
To develop an app or to integrate SAP Mobile Documents functions, developers need to familiarize themselves
with CMIS and Apache Chemistry. If you are a Java developer, OpenCMIS is the tool of choice. Many of the
examples in this guide are based on using OpenCMIS to connect to the SAP Mobile Documents server.
Related Information
Apache Chemistry
OpenCMIS Client API Developer's Guide
CMIS 1.1 Specification on OASIS Web page
9.1.2.1 Object Model
SAP Mobile Documents uses document and folder objects.
CMIS 1.1 defines the following primary base types:
Document objects
Folder objects
Relationship objects
Policy objects
Item objects
Currently, SAP Mobile Documents supports only document and folder objects.
A document object is an item of content. The document can have a content stream, which is the actual file
associated with the document. A content stream exists only as part of its containing document object. A content
stream has a mime type associated with it. A document object may contain one or more renditions, which are
alternative views of the content. Document objects are the only objects that are versionable. Each version of a
document has its own object ID. All the versions of a document make up a version series and share a version
series ID. You can create, read, update, and delete documents using OpenCMIS methods.
A folder object is a container used to organize the document objects. A repository has one root folder. All other
folder objects have one parent folder. A folder has a folder path representing its place in the repository's folder
hierarchy. A folder object can have renditions. For example, a folder can have a thumbnail as a rendition
representing the contents of the folder.

9.1.2.2 Bindings
SAP Mobile Documents supports two of the three binding types defined in CMIS 1.1: the AtomPub and the JSON-
based browser binding.
This means that you can connect apps with both bindings. It also means that you can connect repositories to the
server that offer one of the two binding types. If you are developing a new app or an extension, opt for the new
browser binding if it is technically feasible, since it has better performance.
For more information about the bindings, see the CMIS 1.1 specifications for AtomPub Binding and Browser
Binding.
The following service URLs are available for these bindings:
<protocol>://<server>:<port>/mcm/json
<protocol>://<server>:<port>/mcm/atom
The following additional endpoints exist for the cloud version:
<protocol>://<server>:<port>/mcm/b/json
<protocol>://<server>:<port>/mcm/b/atom
The "/b" after the context root "/mcm" means that the server requests BASIC authentication.
Related Information
AtomPubBinding on OASIS Web page

Browser Binding on OASIS Web page
9.1.2.3 Repository Information
SAP Mobile Documents apps can use the repository information to connect to a repository.
For each repository, the server provides repository information (RepositoryInfo) that describes a repository's
general information and its capabilities. When a app calls a binding service URL without parameters, it gets a list of
RepositoryInfo objects, one for every repository that is connected to SAP Mobile Documents. Apps can then
use the repository ID and the provided navigation information to connect to one of the repositories.
For more information, see the OASIS Web page for getRepositoryInfo.
If you send a GET request to the service URL for AtomPub (/mcm/atom), you get the service document XML,
which contains service definitions and a list of repositories. If you send a GET request to the service URL of the
browser binding (/mcm/json), the server responds with a JSON representation of a list of RepositoryInfo
objects.
Example
Getting the list of RepositoryInfo objects with OpenCMIS
SessionFactory sessionFactory = SessionFactoryImpl.newInstance();

Map parameter = new HashMap();
parameter.put(SessionParameter.USER, "admin");
parameter.put(SessionParameter.PASSWORD, "admin");
parameter.put(SessionParameter.BROWSER_URL, server+"/mcm/json/");
parameter.put(SessionParameter.BINDING_TYPE, BindingType.BROWSER.value());
List<Repository> repositories = sessionFactory.getRepositories(parameters);
For examples of basic operations such as reading, creating, updating, and deleting objects and folder navigation
with OpenCMIS, see the OpenCMIS Client API Developer's Guide.
Related Information
getRepositoryInfo on OASIS Web page

9.1.3 CMIS Enhancements for SAP Mobile Documents
SAP Mobile Documents comes with CMIS enhancements to enable secure and smooth document management.
The following enhancements are available and are described in the following topics:
Token-based protection mechanism against cross-site request forgery attacks

My Documents repository
Public Documents repository
Exceptions
9.1.3.1 Opening a Session
The following CMIS enhancement is used to connect to the SAP Mobile Documents server.
To open a session with exactly one repository in an OpenCMIS client, specify a set of session parameters. Then,
connect to the SAP Mobile Documents server.
Example
SessionFactory sessionFactory = SessionFactoryImpl.newInstance();

Map parameter = new HashMap();
parameter.put(SessionParameter.USER, "admin");
parameter.put(SessionParameter.PASSWORD, "admin");
parameter.put(SessionParameter.BROWSER_URL, server+ "/mcm/b/json/");
parameter.put(SessionParameter.BINDING_TYPE, BindingType.BROWSER.value());
parameter.put(SessionParameter.REPOSITORY_ID, mydocumentsId);
parameters.put(SessionParameter.COOKIES, "true");
Session session = sessionFactory.createSession(parameter);
For examples of basic operations such as reading, creating, updating, and deleting objects, and folder navigation
with OpenCMIS, see the OpenCMIS Client API Developer's Guide.

Custom Authentication Provider
Let's take a closer look at the AUTHENTICATION_PROVIDER_CLASS session parameter as specified in the
example above. This parameter tells the session to use your custom authentication provider instead of the default
one. In SAP Mobile Documents, using a custom authentication provider is mandatory for the following reasons:
To use SAP Mobile Documents, the app must set cookies in the HTTP header. As the OpenCMIS Java client
hides specifics to bindings and HTTP calls, you cannot set an HTTP request header directly, but you can use
additional headers, which the OpenCMIS Java client provides for the HTTP calls it executes.
Specify a Java class (in the example below it is called CustomAuthenticationProvider) that implements
the org.apache.chemistry.opencmis.commons.spi.AuthenticationProvider interface and
overrides the getHTTPHeaders(String url) method. During an HTTP call to the server,
getHTTPHeaders() is invoked and arbitrary headers can be added to the HTTP request.
public class CustomAuthenticationProvider extends StandardAuthenticationProvider

{
@Override
public Map<String, List<String>> getHTTPHeaders(String url) {
....
....
}
}
Related Information
9.1.3.2 Using the CSRF Token
The SAP Mobile Documents server offers a token-based mechanism to protect against cross-site request forgery
attacks.
Note
The CSRF protection was simplified with SP02. The differences are as follows:
The token is no longer repository-specific. It is valid for a session and for any repository that is connected
within that session.
The token can be fetched with HTTP headers. It is no longer necessary to parse RepositoryInfo.
The HTTP header name was changed to harmonize it with other SAP product names.
With the exception of the call to the service URLs, all calls to the SAP Mobile Documents server require a valid
CSRF token. For the call to the service URLs, the token is provided as an HTTP header (as of version 1.0 SP02). All
other requests require the apps to send the token value via the CSRF-token HTTP header. If the app does not
supply a token or if the token has expired, the server sends the HTTP response 403: INVALID_TOKEN_PROVIDED.

Process Flow
1. When the app creates a session and connects to the server, it first calls getRepositoryInfos. To fetch a
CRSF token, the app must send a request header called X-CSRF-Token with the value fetch in this call.
2. The server generates a token, stores it in the user's session table, and sends the value in the X-CSRF-Token
HTTP response header.
3. The app reads the value of the X-CSRF-Token HTTP response header and stores it for later use.
4. For each call in this CMIS session, the app sends the token value it obtained from the X-CSRF-Token HTTP
header.
Example
Extracting the token with HTTP and browser binding
1) Get Repository Info and request a token

Request: GET /mcm/json
Request Header: X-CSRF-Token=fetch
Response: 200 OK
Response Header: X-CSRF-Token=79E85CA37351BBADF02661F64FC21D3C
2) Get the home folder
Request: GET /mcm/json/4caf284f-81f4-4b2a-a77a-3fe7112339c2/root?
cmisSelector=object&objectId=qn913L3f5e7BReuvIPj3UB3KkX2YYePxvIvcQtICiCo
Request Header: X-CSRF-Token=79E85CA37351BBADF02661F64FC21D3C
Response: 200 OK
Example
Token handling in Authentication Provider
public class CustomAuthenticationProvider extends StandardAuthenticationProvider {

private String token = "fetch";
@Override
Map<String, List<String>> httpHeaders = super.getHTTPHeaders(url);
if(httpHeaders==null) {
httpHeaders = new HashMap<String, List<String>>();
}
httpHeaders.put("X-CSRF-Token", Collections.singletonList(token));
return httpHeaders;
}
@Override
public void putResponseHeaders(String url, int statusCode, Map<String,
List<String>> headers) {
super.putResponseHeaders(url, statusCode, headers);
if(headers!=null) {
for(String headerName:headers.keySet()) { // loop for a ignore case check -
> header names are case-insensitive (RFC 2616)
if(headerName!=null && headerName.equalsIgnoreCase("X-CSRF-Token") && !
headers.get(headerName).isEmpty()) {
this.token = headers.get(headerName).get(0);
}
}
}
}
}
Because OpenCMIS executes a call to get the RepositoryInfos when a session is created, this
AuthenticationProvider adds the X-CSRF-Token=fetch HTTP request header. Then the server sends the

response to the AuthenticationProvider. The AuthenticationProvider stores the value returned by the
server for further requests.
Browser Binding Example
In JavaScript-based applications, you first read the repository info by sending a GET request to /mcm/json. Every
other repository contains a token for the communication with this /mcm/json repository. In the following
example, jQuery is used to read the token and set it for all subsequent AJAX requests.
// read repositoryInfos extract token and set it to following requests

jQuery.ajax("/mcm/json",{
type: "GET",
contentType: 'application/json',
dataType: 'json',
beforeSend: function(xhr){
xhr.setRequestHeader('X-CSRF-Token', 'fetch');
},
complete : function(response) {
jQuery.ajaxSetup({
beforeSend: function(xhr) {
xhr.setRequestHeader("X-CSRF-Token",response.getResponseHeader('X-CSRF-
Token'));
}
});
}
});
Static Cookie Manager
Because the repository ID is a parameter when creating a session with an OpenCMIS client, a app would open a
session on the server for each repository. To avoid multiple server sessions for the same app, we highly
recommend using the same server session for multiple CMIS sessions by re-using the cookies that are used for
the state management between the apps and the server.
To do this, use a static CookieManager instead of one cookie per instance. If a app application opens several
sessions for the same user, it must use the same authentication provider with the static CookieManager.
Additionally, it has to override the putResponseHeaders() and getHandleCookies() methods as described in
the following example.
Overriding the getHandleCookies() method has the effect that the COOKIES session parameter is ignored.
Example
public class CustomAuthenticationProvider extends StandardAuthenticationProvider {

// The use of a singleton cookie manager ensures that all created cmis sessions
// use the same session cookies and therefore avoids multiple server session for
each app
private static final CmisCookieManager cookieManager = new
CmisCookieManager();
@Override
Map<String, List<String>> httpHeaders = super.getHTTPHeaders(url);
if (httpHeaders == null) {

httpHeaders = new HashMap<String, List<String>>();
}
Map<String, List<String>> cookies = cookieManager.get(url,
httpHeaders);
if (!cookies.isEmpty()) {
httpHeaders.putAll(cookies);
}
return httpHeaders;
}
@Override
public void putResponseHeaders(String url, int statusCode, Map<String,
List<String>> headers) {
super.putResponseHeaders(url, statusCode, headers);
cookieManager.put(url, headers);
}
@Override
protected boolean getHandleCookies() {
// deactivate standard opencmis session handling
// cmis session parameter "COOKIES" will be ignored
return false;
}
}
9.1.3.3 My Documents
Every SAP Mobile Documents user has their own home folder in the My Documents repository.
To enable clients to easily get the home folder, the repository used to store the My Documents repository contains
a CMIS extension called myDocuments (namespace: http://www.sap.com/mcm; name: myDocuments). The
value of this extension contains the ID of the home folder of the currently logged-on user. A repository with this
extension is easily identifiable as the My Documents repository.
Example
Getting the My Documents repository
Repository myDocumentsRepository = getRepository(repositories, "myDocuments"); //

use the repositories list of chapter Repository Information
public static Repository getRepository(List<Repository> repositories, String
extension) {
for (Repository rep : repositories) {
if(getExtensionValue(rep.getExtensions(), extension)!=null) {
return rep;
}
}
return null;
}
Example
Getting the user's home folder
String homeFolderId = null;

List<CmisExtensionElement> extensions = myDocumentsRepositoryInfo.getExtensions();
if (extensions != null) {
for (CmisExtensionElement extension : extensions) {
if ("myDocuments".equals(extension.getName())) {

homeFolderId = extension.getValue();
}
}
}
if (homeFolderId != null) {
// Obtain a session see chapter Working with the CSRF token
Session session = sessionFactory.createSession(parameter);
Folder userHomeFolder = (Folder) session.getObject(homeFolderId);
}
Example
Getting the user's home folder with browser binding and jQuery
// read repositoryInfos
jQuery.getJSON("/mcm/json").done(function(data){
for(id in data) { // loop repositories and find myDocuments
if(data[id].myDocuments) {
$.ajaxSetup({ // set token for following calls
beforeSend: function(xhr) {
xhr.setRequestHeader("x-token",data["4caf284f-81f4-4b2a-
a77a-3fe7112339c2"].token);
}
});
// read the home folder and alert its displayname
var homeFolderId = data[id].myDocuments;
jQuery.getJSON("/mcm/json/4caf284f-81f4-4b2a-a77a-3fe7112339c2/root?
cmisSelector=object&objectId="+homeFolderId).done(function(data)
{
alert(data.properties["cmis:name"].value);
});
}
}
});
9.1.3.4 Shared Documents

SAP Mobile Documents provides a repository called Shared Documents for collaborating on documents with other
users.
The following table clarifies the terms used to implement Shared Documents.
Table 48: Terms Relevant for Shared Documents

Term Definition
share The root folder that is used for collaboration with other users. It can contain folders and files. Users
can create any number of shares (until their quota is used up).
owner The user who creates the share automatically becomes its owner. The share's size is billed to the
owner's quota.
public link A link that can be applied to a share, to folders, or to files residing in the share. The link makes the
share, the folder, or the file available to anonymous users.
member Any user that has one of the defined roles for the share and can access it.
For each share, the following roles are available. The table below maps these roles to the respective CMIS
permissions.

Table 49: Share Roles
Role Description CMIS Permission
owner Permission to create a share. cmis:all
administrator Permission to delete a share, to manage user rights, and to allow public cmis:all
links.
contributor Permission to create, to update, and to delete files and folders. This per sap:delete
mission also enables the user to create and to delete public links.
reader Permission to read documents. cmis:read
Similar to the My Documents repository, every user has their own personal sharing home folder. Beneath this
home folder are the shares of the user. The ID of the sharing home folder is specified in the RepositoryInfo with
the sharing extension.
If public links are enabled, there are some general settings with which every public link must comply. These
general settings are transported as CMIS extensions in the RepositoryInfo of the sharing repository. In
addition to the general settings, every public link has its own set of properties, where a user can define validity and
security for this public link. In any case, a user is only allowed to define values that are stricter than the general
ones defined by an administrator. If, for example, an administrator defines a minimum password length of four
characters, the user can only choose to use a password with more characters. The user cannot choose to use less
than four characters or even no password at all.
Table 50: CMIS Extensions (on RepositoryInfo Level, Valid for All Public Links)
Name Description Type
sharing Similar to the mydocuments extension, this extension contains the ID of String
the user's Shared Documents home folder.
sharing.uploadAllo Indicates whether the administrator allows uploads by anonymous users or Boolean
wed not.
sharing.baseURL Contains the base URL of the public sharing Web link. The app can use this String
information to create a public link by appending the object ID of the public
link to this base URL.
sharing.maxEpirati The administrator can define the maximum period in days for which anony int
onDays mous users can access a shared folder. This extension contains the num
ber of days.
When a public link is created, the expiration date must not be later than the
current date plus the number of days specified. If the value is 0, no expira
tion date is predefined.
sharing.minPasswor For values greater than 0, the user must set a password for the public links int
dLength of this share. This password must be longer than or of the same length as
the value of this extension.
Table 51: CMIS Extensions (on Folder Level, Valid for All Shares)
Name Description Type
owner.isOutOfSpace Indicates whether the share owner has enough quota left to upload files to Boolean
the share.
True: No content upload allowed.

False: Content upload allowed, as far as the quota is concerned.

9.1.3.4.1 App Operations for Sharing
You can use app operations for shared documents in SAP Mobile Documents.
Getting All Shares of a User
To list all shares that a user can access (with any of the roles specified for share access), the app sends a query to
the server. Since shares have the specific mcm:share CMIS type the query is simply: select * from
mcm:share. The result is a list of all shares where the calling user has an entry in the share's access control list
(ACL).
Creating a Share
Shares must be created under a user's sharing home folder. They have the specific mcm:share type with the
cmis:folder base type.
Managing Share Members
Members are entries in a share's access control list (ACL). An ACL is a list of ACEs (access control entries) that
consist of a principal ID and a list of permissions. The permissions are listed in the roles table in Shared
Documents.
For on-premise installations, the principal ID is a user's unique ID, for SAP HANA Cloud Platform it is the user's
logon ID. You can pass the ACL as an input parameter while creating a share or modify the ACL by calling the
applyAcl CMIS service on an existing share.
When adding a new member to a share, the share administrator wants to use known user attributes, for example,
the name or the e-mail address, but not the user ID. To help apps to search for users and to assemble an ACL with
the correct IDs, SAP Mobile Documents offers a REST API (see REST API).
In the members overview for a share, apps should display user names rather than IDs. To prevent extra server
roundtrips or extra non-CMIS APIs, OpenCMIS offers the possibility to add generic extensions to various objects.
When a app reads the members of a share, technically this is a getObject operation (with ACLs included) on the
folder representing the share. The ACL is a list of ACEs and each ACE contains a principal object. OpenCMIS only
defines an ID for a principal; additional attributes can be added as extensions. The server extends the principal
object with an extension called principal that has the following children as extensions:
_firstName
lastName
email
displayName
logonId

id
Example
Example response of an ACL with a single contributor.
{
"acl": {
"aces": [
{
"principal": {
"principalId": "USER.PRIVATE_DATASOURCE.un:testuser",
"principal": {
"firstName": "Manfred",
"lastName": "Mustermann",
"email": "Manfred.Mustermann@sap.com",
"logonId": "testuser",
"id": "USER.PRIVATE_DATASOURCE.un:testuser",
"displayName": "Manfred Mustermann"
}
},
"permissions": [
"sap:delete"
],
"isDirect": true
}
]
},
"exactACL": true
}
Managing Public Links
To make a share accessible to external users using a public link, it must be given a CMIS secondary type called
mcm:publicLink. CMIS defines the standard multi-value cmis:secondaryObjectTypeIds property that can
contain 0..n secondary type IDs. To make a share public, the mcm:publicLink ID must be added to the
cmis:secondaryObjectTypeIds.
Secondary types contain a set of properties that can be attached or detached from an object. Public links have
properties, for example, a password or an expiration date.
These are the properties:
Table 52:
Name Description ID Namespace Type
Valid to Defines the date after which the shared documents in this folder mcm:validTo com.sap.mcm DATE
Date are no longer accessible for anonymous users. The creator of the Date TIME
share can still access it.

Share Can be used to protect the access to the shared file with a pass mcm:share com.sap.mcm String
Password word. Administrators can enforce the setting of a password. Password
Note
Because the server never exposes the hashed password to the
apps, the server returns "null" as a value if no password has
been set for an existing folder. If a password has been set the
value is an empty string.
Public Controls whether anonymous users have write access to shared mcm:enableUp com.sap.mcm Boolean
write ac documents. If set to Yes, anonymous users are allowed to create, load
cess update, or delete documents within the share.
Table 53:
Valid to If users enter the wrong password, they are not allowed to ac mcm:validFrom com.sap.mcm DATE
Date cess the share until the time set in the value of this property. Date TIME
The administrators can configure a default for this setting.
Share Indicates the owner of the share. If quota is enabled, everything mcm:shareOwner com.sap.mcm String
Owner within this share is counted in the owner's quota.
Example
Code Samples: OpenCMIS
// Getting the sharing home folder

String sharingHomeFolderId = null;
for (CmisExtensionElement extension : sharingRepositoryInfo.getExtensions()) {
if ("sharing".equals(extension.getName()))
{ sharingHomeFolderId = extension.getValue(); }
}
Folder sharingHomeFolder = session.getObject(sharingHomeFolderId);
// Getting all shares for a user
ItemIterable<QueryResult> result = session.query("select * from mcm:share",true);
for(QueryResult result:results) {
String shareName = result.getPropertyValueById("cmis:name");
}
// Create share "Share 1" with administrator "User01"
Map<String, Object> properties = new HashMap<String, Object>();
properties.put("cmis:name", "Share 1");
properties.put("cmis:description", "A description");
properties.put("cmis:objectTypeId", "mcm:share");
List<Ace> aces = new ArrayList<Ace>();
aces.add(session.getObjectFactory().createAce("User01",
Collections.singletonList("cmis:all")));
ObjectId shareId = session.createFolder(properties, sharingHomeFolder, null,
aces, null);
// adding contributor "User02"
List<Ace> addAces = new ArrayList<Ace>();
addAces.add(session.getObjectFactory().createAce("User02",
Collections.singletonList("sap:delete")));
session.applyAcl(shareId, addAces, null, AclPropagation.PROPAGATE);
// Creating a public link
Folder share = session.getObject(shareId);
properties = new HashMap<String, Object>();

properties.put("cmis:secondaryObjectTypeIds",
Collections.singletonList("mcm:publicLink"));
properties.put("mcm:sharePassword", "secret");
properties.put("mcm:enableUpload",true);
GregorianCalendar cal = new GregorianCalendar();
cal.setTime(new Date());
cal.add(Calendar.DAY_OF_MONTH, 7); // one week
properties.put("mcm:validToDate", cal);
share.updateProperties(properties);
Example
Code Samples: JavaScript / jQuery
// Getting all shares for a user var repositoryId = sharingRepositoryInfo.id;

var queryUrl = "/mcm/json/"+repositoryId+ "?cmisSelector=query&q=select+*+from
+mcm%3Ashare&maxItems=1000&skipCount=0";
jQuery.getJSON(queryUrl).done(function(data){
for( var i=0;i<data.results.length;i++) { // loop results
var shareName = data.results[i].properties[ "cmis:name"].value;
// do something }
});
//
Create share "Share 1" var sharingHomeFolderId =
sharingRepositoryInfo.sharing;
jQuery.ajax( "/mcm/json/"+repositoryId+ "/root", {
type : 'POST',
async : false,
data : {
objectId : sharingHomeFolderId,
cmisaction : "createFolder",
"propertyId[0]" : "cmis:name",
"propertyValue[0]" : "Share
1",
"propertyId[1]" : "cmis:objectTypeId",
"propertyValue[1]" : "mcm:share",
"propertyId[2]" : "cmis:description",
"propertyValue[2]" : "A
description"
}
}).done(function(data){
shareId = data.properties[ "cmis:objectId"].value;
});
//
adding contributor "User02"jQuery.ajax( "/mcm/json/"+repositoryId+ "/
root", {
type : 'POST',
async : false,
data : {
objectId : shareId,
cmisaction : "applyACL",
ACLPropagation : "propagate",
"addACEPrincipal[0]" : "User02",
"addACEPermission[0][0]" : "sap:delete"
}
});
// Creating a public link var currentTime = new Date();
var expirationDate = currentTime.setDate(currentTime.getDate()+7);
jQuery.ajax( "/mcm/json/"+repositoryId+ "/root", {
type : 'POST',
async : false,
data : {
objectId : shareId,
cmisaction : "update",
"propertyId[0]" : "cmis:secondaryObjectTypeIds",
"propertyValue[0]" : "mcm:publicLink",

"propertyId[1]" : "mcm:sharePassword",
"propertyValue[1]" : "secret",
"propertyId[2]" : "mcm:enableUpload",
"propertyValue[2]" : "true ",
"propertyId[3]" : "mcm:validToDate",
"propertyValue[3]" : expirationDate
}
});
Determine Whether Upload to a Share Possible (Quota Handling)
Apps can only determine the quota and the used disc space of their own logged-on user. However, in the context
of sharing, apps typically also upload files to shares of other users. In this situation, the user who wants to upload
files is not the share owner. It is not possible to get the quota information of another user, but it is possible to
determine if the share owner has enough quota left to upload more files. apps can and should use this information
to inform the user that no more uploads are allowed and to avoid triggering uploads to this share. For all shares
that are folders of type mcm:share the server provides a CMIS extension named owner.isOutOfSpace.
9.1.3.5 Corporate Repositories
Corporate repositories can have a configured root URI that clients use as a start folder in a repository.
For more information on the root URI, see Configuring Corporate Documents Repositories.
To set the root URI, you configure a path, for example, /folder1/folder2; clients should initially display the
folder structure beneath this path instead of displaying the contents of the root folder. If you configure a root URI,
it is transported to the clients similarly to the user's home folder of My Documents as an extension containing the
ID of the configured path. The extension's name is corporate, so you can apply the same example code as in the
My Documents example. You only need to replace the extension name myDocuments with the extension name
corporate.
Related Information
My Documents [page 101]

Configuring Corporate Documents Repositories [page 82]

9.1.3.6 Exceptions
To notify users that they have made incorrect user entries, SAP Mobile Documents uses specific messages in
exception texts.
In general, SAP Mobile Documents adheres to the exception behavior described in the CMIS specification. If the
exception is used to express incorrect user entries, SAP Mobile Documents uses specific messages in the
exception text.
Table 54: Specific Messages in Exception Text

Exception Name Message Description
CmisPermissionDeni INVALID_TOKEN_PR The app must provide a token in every operation except
edException OVIDED getRepositoryInfos. If no token or the wrong token is provided, this ex
ception is thrown.
CmisInvalidArgumen PASSWORD_NOT_SET Thrown when creating a public link without a password if the administrative
tException settings require a password.
CmisInvalidArgumen PASSWORD_TOO_SHO Thrown when creating a public link if the provided password does not meet
tException RT the requirements specified in the administrative settings.
CmisInvalidArgumen PASSWORD_INVALID Thrown when a password-protected public link is anonymously accessed

tException with a wrong password.
CmisInvalidArgumen PASSWORD_REQUIRE Thrown when a password-protected public link is anonymously accessed

tException D without a password.
CmisInvalidArgumen SHARE_LOCKED<unl Thrown when a password-protected public link is currently locked because
tException ock_date_in_ms> it was accessed with a wrong password. The exception key is followed by
the date when the public link is accessible again (in milliseconds from
1970/1/1).
CmisInvalidArgumen EXPIRATION_DATE_ Thrown when creating a share. The expiration date for the share is a link
tException IN_PAST with a validToDate in the past.
CmisConstraintExce QUOTA_EXCEEDED The quota for the currently logged-on user is used up. No write operations
ption are allowed until the user frees up some space.
CmisConstraintExce Virus When uploading a document, the repository can reject the document if a
ption virus is detected. If the app tries again to upload this document to the
VIRUS
server, the same exception is thrown. Therefore, the app should not retry
virus uploading the document.
9.1.4 REST API

In some cases the apps need server calls that cannot be mapped to CMIS services. For these calls, the SAP Mobile
Documents server offers a proprietary REST API that apps can use.
User Validation
With this API, apps can validate the existence of principals using attributes. A principal is a user management
object, for example, a user, a group, or a role. The response contains JSON representations of the found principal

objects as well as a list of terms for which no principals can be found. In SAP Mobile Documents, this API is used in
the context of the Shared Documents repository when adding members to a share. Wildcards are not supported,
because this API is meant for validating, not for searching.
Note
For on-premise installations of SAP NetWeaver, principal search uses the user management engine (UME) and
supports the logon ID and the e-mail attributes. For SAP HANA Cloud Platform, principal search currently only
supports the logon ID attribute.
Table 55:
Title Validate Users
URL /mcm/rest/v1/users/validate
Method GET
URL Params term=[URL Encoded]
1...n term parameters are possible. Note that a URL including parameters must not exceed
2000 characters.
Example to validate 3 users at a time: .../mcm/rest/v1/users/validate?

term=d123456&term=c654321&term=i123456

Success Response Code: 200
Content sample for single entry response:
{
"foundPrincipals": {
"displayName": "Horst
Sapbox",
"email": "admin@mobidocs.de",
"firstName": "Horst",
"id": "admin",
"lastName": "Sapbox",
"type": "USER"
},
"nothingFoundFor": "d736367"
}
Content sample for multiple entry response:
{
"foundPrincipals": [
{
"displayName": "Horst
Sapbox",
"email": "admin@mobidocs.de",
"firstName": "Horst",
"id": "admin",
"lastName": "Sapbox",
"type": "USER"
},
{
"displayName": "Heinz
Ketchup",
"email": "user1@mobidocs.de",
"firstName": "Heinz",
"id": "user1",
"lastName": "Ketchup",
"type": "USER"
}
],
"nothingFoundFor": [
"d736367",
"admin1"
]
}
Error Response Code 400 for bad requests, for example, parameters contain invalid characters.
Code 403 for unauthorized requests, for example, user has no permission to call this
URL.

Sample Call Validate users within a JavaScript-based app using jQuery
var restURLStart = "/mcm/rest/v1/users/validate?";

var restURL = restURLStart + 'term=d012345&term=i012345';
$.ajax(encodeURI(url), {
type: 'GET',
async: false
}).
done(function (data) {
// Handle successful call
// data = JSON response from server as described above
}).
fail(function (cause) {
// Handle Server Exception
});
9.1.5 URLs for App-to-App Integration of SAP Mobile

Documents (Cloud)
You can build URLs that perform actions in the SAP Mobile Documents app and that can be used for app-to-app
integration or as links in e-mails.
These URLs are either custom URLs (mobiledocs://) or HTTP URLs. Not all apps support both types. In
addition, there is a distinction between URLs for links for share members and URLs for public links, which can be
accessed by anyone who receives the link (and the password, if any).
App Support
Table 56: URL Types
URL Type Web App iOS App Android App Windows Desk Mac Desktop Windows Na
top App App tive App
Custom URL x x x
HTTP URL x x

Table 57: Available Actions
Action Comment Web App iOS App Android App Windows Mac Desktop Windows Na
Desktop App App tive App
select The folder Supported as Supported as Supported as Supported as

containing of Web app of iOS SP2 of Android of Windows
the object SP3 (1.3.x). (1.2.x). SP3 (1.3.x). desktop app
identified with SP4 (1.4.x).
the parame
ter obj is
opened and
the object it
self is se
lected in the
documents
list.
mobiled
ocs://v
1/
select?
rep=123
4567890
&obj=09
8765432
1
https:
//
myhost:
8080/mc
m/
browser
/v1/
select?
rep=123
4567890
&obj=09
8765432
1

open If the pa Supported as Supported as Supported as Supported as

rameter of Web app of iOS SP2 of Android of Windows
obj is SP3 (1.3.x). (1.2.x). SP3 (1.3.x). desktop app
the ID of SP4 (1.4.x).
a folder,
the
folder is
opened
and its
content
is dis
played.
If the pa
rameter
obj is
the ID of
a file, the
folder is
opened
and the
file is
down
loaded.
mobiled
ocs://v
1/open?
rep=123
4567890
&obj=09
8765432
1
https:
//
myhost:
8080/mc
m/
browser
/v1/
open?
rep=123
4567890
&obj=09
8765432
1

present Only for PDF Supported as

files. Opens a of iOS SP2
PDF file in (1.2.x).
presentation
mode.
mobiled
ocs://v
1/
present
?
rep=123
4567890
&obj=09
8765432
1
configure Server config Supported as

uration URL, of iOS SP4
together with (1.4.x).
the
server.url
=http(s):
//
<host>(:<p
ort>) pa
rameter
mobiled
ocs://v
1/
configu
re?
server.
url=htt
ps://
myhost:
8080

create Link to create Supported as

share page: of Web app
Only in com SP5 (1.5.x).
bination with
rep=share
https:
//
myhost:
8080/mc
m/
browser
/v1/
create?
rep=sha
re
Available URL Parameters
has the following values:

<repository ID>
mydocuments
share
corporate
has the following values:
<object ID>
has the following case-sensitive values:
</folder1/folder2>
<server.url> has the following values:
http(s)://<host>(:<port>)
, iOS-only
, iOS-only
Note
You cannot use the obj and the path parameters in the same URL.
Custom URL Syntax
The custom URL syntax is:
mobiledocs://<version>/<action>?parameters

Example
mobiledocs://v1/open?obj=1234&rep=abcdef
This URL opens the document with the CMIS object ID 1234 from the SAP Mobile Documents repository with
ID abcdef, using version v1 of the SAP Mobile Documents URL scheme and the open action.
The syntax contains the following elements:
version string, required

Denotes the scheme version of SAP Mobile Documents; the current version is v1.
action string, required: Is an action that the app performs on the provided parameters. Available actions are
listed in the table above.
The syntax contains the following URL parameters:
rep string (URL-encoded), required

SAP Mobile Documents repository ID. mydocuments, share, and corporate are reserved keywords.
mydocuments and share can be used instead of the corresponding repository ID. If no path or object ID is
provided or found, the repository root is selected. rep=corporate can be used to address the list of all
corporate repositories. For rep=corporate, the parameters obj and path are ignored.
obj string (URL-encoded), optional
CMIS object ID of a file or folder. If provided, the path is ignored.
path string (URL-encoded), optional
The absolute path inside the specified repository. The start URI is not considered here. The path is URL
encoded before it is passed to SAP Mobile Documents. If the repository is share, the path parameter is not
considered, as a link to a document or folder within a share would have the logon ID as part of the URL.
Supported as of iOS SP3 (1.3.x), Android SP3 (1.3.x), Web app SP3 (1.3.x), and Windows desktop app SP4
(1.4.x).
page string, optional
If the object is a PDF document, this parameter can display a given page on opening the document. If the
object is not a PDF document or the given page is outside the range of the document, this parameter is
ignored.
Example: mobiledocs://v1/open?rep=abcdef&obj=1234&page=27
chapter string, optional
If the object is a PDF document that has a table of contents (ToC), this parameter can display the given
chapter on opening the document. The chapter must be specified using the URL-encoding (percent
representation) of the exact chapter name in the table of contents of the PDF document. If the object is not a
PDF document or the given chapter is not part of its table of contents in that sense, this parameter is ignored.
Examples:
mobiledocs://v1/open?rep=abcdef&obj=1234&chapter=ExampleChapterName (for ToC entry
"ExampleChapterName")
mobiledocs://v1/open?rep=abcdef&obj=1234&chapter=Example%20Chapter%20Name (for ToC
entry "Example Chapter Name")

HTTP URL Syntax for All Non-Public Links
The HTTP URL syntax is:
http(s)://<server>:<port>/mcm/browser/<version>/<action>?parameters
Example
https://myhost:8080/mcm/browser/v1/select?rep=1234567890&obj=0987654321
This URL starts the Web app and triggers navigation to the repository 1234567890. The URL then opens all
possible subfolders until object 0987654321 is found. The URL selects this object. The select action does not
differentiate between folders or documents. The respective object is selected in the documents list of SAP Mobile
Documents.

rep string (URL-encoded), required

SAP Mobile Documents repository ID. mydocuments, share, and corporate are reserved keywords.
mydocuments and share can be used instead of the corresponding repository ID. If no path or object ID is
provided or found, the repository root is selected. rep=corporate can be used to address the list of all
corporate repositories. For rep=corporate, the parameters obj and path are ignored.
CMIS object ID of a file or folder. If provided, the path is ignored.
path string (URL-encoded), optional
The absolute path inside the specified repository. The start URI is not considered here. The path is URL
encoded before it is passed to SAP Mobile Documents. If the repository is share, the path parameter is not
considered, as a link to a document or folder within a share would have the logon ID as part of the URL.
Supported as of iOS SP3 (1.3.x), Android SP3 (1.3.x), Web app SP3 (1.3.x), and Windows desktop app SP4
(1.4.x).
HTTP URL Syntax for Public Links
The public HTTP URL syntax is:
http(s)://<server>:<port>/mcm/public/<version>/<action>?parameters
Example
https://myhost:8080/mcm/browser/v1/select?rep=1234567890&obj=0987654321

shr string (URL-encoded), required

Provides the ID of the share to display.
Specifies the object on which the provided action should be executed. If the obj parameter is not present, the
share is opened in the sharing UI and the action is ignored.
For shares with a public link, the share properties only show the URL for share members because the public link is
already available using the link icon ( ).
For an object (folder or file) in a share with a public link, the object properties show the Public URL of the Folder or
Public URL of the Document, as this link is currently not available elsewhere.
Path Handling for HTTP URLs
Path handling for shares is explicitly switched off, as the user ID would have to be a visible part of the URL, which
is not wanted. In addition, the caller (who is creating the URL and calling it) cannot determine the ID of the user
who owns the share that is addressed.
For objects under My Documents, the user ID must also be part of the URL as stated in the CMIS specification.
However, apps parsing the URL know which ID must be used in the path: the ID of the logged-on user. Therefore,
the path does not need to contain the user ID. When the apps parse the URL, they add the user ID to the beginning
of the path. With this adjusted path, getObjectByPath() works.
Example
The apps receive the following URL:
http://myhost:8080/mcm/browser/v1/select?rep=mydocuments&path=/folder1/folder2
The apps use the following URL to send the getObjectByPath() request:
http://myhost:8080/mcm/browser/v1/select?rep=mydocuments&path=/UserID/folder1/
folder2
Related Information
Configuring the Server URL with a URL Scheme [page 121]

9.1.5.1 Integrating Fiori Launchpad and an SAP Mobile
Documents Folder
You can display an SAP Mobile Documents folder in the SAP Fiori launchpad as an embedded element.
Prerequisites
In the SAP HANA Cloud Platform cockpit, the administrator who will perform the below settings is assigned
the Admin role for SAP Mobile Documents.
In the SAP HANA Cloud Platform cockpit, all users who are allowed to access the SAP Mobile Documents
folder are assigned the User role in the mobiledocs app.
In the SAP HANA Cloud Platform cockpit, the SAP Fiori launchpad app is subscribed to the mobiledocs app
and vice versa.
In the SAP HANA Cloud Platform cockpit, users are maintained for the subscriptions. For more information,
see Mapping Users or Groups to Roles (Subscriptions).
Procedure
1. On the SAP Mobile Documents administration UI at https://<host>:<port>/mcm/admin, log on with an

administrative SAP Mobile Documents user.
2. Choose SETTINGS Web App .

3. In the Allowed Parent Domains for Integration text field, enter the domains that should integrate SAP Mobile
Documents using iFrame. You can list several domains separated by commas.
4. Log on as a content administrator to the Web app at https://<server>:<port>/mcm/browser/
index.jsp.
5. Navigate to the folder you want to display in the iFrame. This is usually a Corporate Documents folder because
typically all employees can access these.
6. Select the folder and choose the properties icon ( ).

7. On the folder details tab, copy the URL displayed for the Web link for members. Both its parameters (rep and
obj) are used to build the URL needed for the integration.
8. Build the URL that you can reference from the SAP Fiori launchpad tile as follows: https://
<server>:<port>/mcm/browser/embedded/index.jsp?rep=<REPOSITORY_ID>&obj=<OBJECT_ID>.

9.1.6 Configuring the Server URL with a URL Scheme
If your company does not use the automatic server URL configuration available with a Mobile Device Management
(MDM) solution, you can supply the server URL for the SAP Mobile Documents app using a URL scheme and
provide this URL scheme to your users.
The URL scheme syntax for configuring the server URL is:
mobiledocs://v1/configure?server.url=<http(s)>://<host>(:<port>)
Example
mobiledocs://v1/configure?server.url=https://mobiledocs.example.com
This URL configures the server URL https://mobiledocs.example.com of the SAP Mobile Documents app.

configure action that the app performs. Supported as of iOS SP4 (1.4.x) and Android SP4 (1.4.x).
server.url string, required. Server URL parameter to connect to the SAP Mobile Documents server.
Supported as of iOS SP4 (1.4.x) and Android SP4 (1.4.x).
9.2 Connecting Your ABAP Back End as a Content Source

(Cloud)
You can use your ABAP system as a content source for SAP Mobile Documents.
With an ABAP system as a content source, you can easily access documents stored, for example, in SAP ERP
system repositories. These documents are then available like any other repository file and can be downloaded to a
mobile device for offline access.
Related Information
SAP Mobile Documents ABAP Connector [page 122]

Implementing the SAP Mobile Documents ABAP Connector [page 123]

9.2.1 SAP Mobile Documents ABAP Connector
The SAP Mobile Documents ABAP connector enables ABAP applications to expose a CMIS interface to SAP
Mobile Documents.
Content stored and/or managed in an ABAP system can be retrieved using the SAP Mobile Documents runtime
by any CMIS client. The ABAP CMIS server can provide any kind of folder hierarchy and any kind of metadata.
Both can be mapped to an existing back end or can be virtual and assembled at runtime. The current connector
version only allows reading of data.
The SAP Mobile Documents ABAP connector consists of two parts. The connector provides an ABAP interface
and helper classes to build a CMIS 1.1-compliant server. The data is provided by RFC to the SAP Mobile
Documents server. The other part resides in the SAP Mobile Documents server. It accepts calls from a CMIS
client, converts the data, calls the appropriate RFC, converts the response, and sends it back to the client.
The SAP Mobile Documents ABAP connector connects the SAP Mobile Documents runtime to the SAP ERP
system.
Whenever possible, document content is not routed through SAP NetWeaver AS for ABAP. If content is stored in
an external document store and if that store provides an HTTP interface, the content can be directly pulled from
that store. In this case, the SAP Mobile Documents ABAP connector implementation must provide a URL to the
document instead of sending the content. This allows content streaming and handling of large documents.

This document explains how to implement the SAP Mobile Documents ABAP connector and how to attach it to
SAP Mobile Documents.
9.2.2 Implementing the SAP Mobile Documents ABAP

Connector
To provide documents, content, folder hierarchies, and metadata to SAP Mobile Documents, you must implement
the SAP Mobile Documents ABAP connector.
This interface adheres closely to the CMIS 1.1 specification, that is, there is a method for each CMIS operation.
Each method takes the same parameters and returns data structures similar to those described in the CMIS
specification. There are only a few instances where the input and output deviate from the specification, either to
avoid technical restrictions or to enable optimizations.
The connector allows you to use the full fidelity of the CMIS standard. This freedom increases complexity in some
areas, specifically to the data structures. To mitigate the complexity, the SAP Mobile Documents ABAP connector
also provides an abstract class that implements the interface. It provides convenience code for several methods.
That is, for most scenarios you only have to implement a small set of methods; the abstract class covers
everything else, but can be overridden where necessary.
Tip
We strongly recommend that you extend this abstract class instead of implementing the interface directly.
Additionally, helper and factory classes are provided. These help fill the data structures. Among other things, the
factory provides CMIS-compliant type definitions for documents and folders and provides repository info data
structures for the most common use cases. There is also a simple query parser for the CMIS query language.
9.2.2.1 Enhancements to the CMIS Specification
To provide a full-featured CMIS interface, some enhancements to the CMIS specification were necessary.
9.2.2.1.1 Tree Handling
CMIS specifies some recursive structures that cannot be directly mapped to ABAP.
If you are dealing with treelike structures, for example, the extensions, then the corresponding structure contains
two additional fields named TRANSPORT_ID and TRANSPORT_PARENT_ID. With these two fields, you can create
the tree as a flat structure. The transport ID can be any string-like value. You must not set a transport parent ID
for the root element. If you set a transport parent ID it must exist, otherwise the element is discarded as it cannot
be mapped to a parent.

9.2.2.1.2 Properties
The property structure in CMIS defines only a table of value objects, which can be of any type.
The ABAP implementation of the property structure is different; there is a table containing not single values but
value structures.
Each value structure contains fields for the following data types:
string value
boolean value
int value
decimal value
date time value
Depending on the property type, the corresponding value must be supplied:
Table 58:
Property Type Value Field
boolean BOOLEAN_VALUE
string STRING_VALUE
id STRING_VALUE
integer INT_VALUE
datetime DATE_TIME_VALUE
decimal DECIMAL_VALUE
html STRING_VALUE
uri STRING_VALUE
9.2.2.1.3 Repository Info (Cloud)
The repository info has an additional field that contains information about the implementation capabilities.
Currently, the structure that is used in this field contains two values. These contain information about the content
delivery abilities of the repository. The content delivery behavior is determined by what the repository returns for
these values. See the table below for more information.
DEFAULT_CONTENT_DELIVERY
Table 59:
Value Comment
full Content is always delivered as a complete xstring.
chunked Content is delivered in chunks.

Value Comment
document_specific Content is delivered as stated in the export parameter of the create_document method. To deliver
the content using a URL, use this option.
DEFAULT_CHUNK_SIZE
If the content is delivered in chunks, set the default chunk size for this parameter. The chuck size should not
exceed 1 MB. Chuck sizes over 16 MB are not supported.
9.2.2.2 Constants and Enum Values
The CL_CMIS_PROPERTY_IDS class contains constants for all property IDs that are defined in the CMIS 1.1
specification.
All other constants and enum values used in the specification can be found in the CL_CMIS_CONSTANTS class.
Example
Using Constants
ls_property = cl_cmis_object_factory=>create_string_prop_single
( iv_property_id = cl_cmis_property_ids=>created_by
iv_value = 'Joe'
).
9.2.2.3 Exceptions
The CMIS exceptions defined in the standard are assigned to specific ABAP exceptions. These exceptions are
passed on to the respective app.
Table 60:
CMIS Exception ABAP Exception
invalidArgument CX_CMIS_INVALID_ARGUMENT
notSupported CX_CMIS_NOT_SUPPORTED
objectNotFound CX_CMIS_OBJECT_NOT_FOUND
permissionDenied CX_CMIS_PERMISSION_DENIED
runtime CX_CMIS_RUNTIME
constraint CX_CMIS_CONSTRAINT
contentAlreadyExists CX_CMIS_CONTENT_ALREADY_EXISTS

CMIS Exception ABAP Exception
filterNotValid CX_CMIS_FILTER_NOT_VALID
nameConstraintViolation CX_CMIS_NAME_CONSTRAINT_VIOLATION
storage CX_CMIS_STORAGE
streamNotSupported CX_CMIS_STREAM_NOT_SUPPORTED
updateConflict CX_CMIS_UPDATE_CONFLICT
versioning CX_CMIS_VERSIONING
To throw a CMIS exception, use the following code snippet:
RAISE EXCEPTION TYPE cx_cmis_invalid_argument

EXPORTING
message_text = 'Invalid object ID.'.
9.2.2.4 Content Handling (Cloud)
Read
The GET_CONTENT method can deliver document content in different ways. It can either provide an HTTP URL to
the content or provide the content itself as one or more xstrings.
If a URL is provided, the SAP Mobile Documents server tries to retrieve the content directly from that URL. Keep in
mind that the server must be able to reach the URL and must be authorized to retrieve the content.
If no URL is provided, the SAP Mobile Documents server forwards the content sent in the STREAM export
parameter. If the parameter contains the full content, set the HAS_MORE export parameter to false.
We recommend that you only transfer content of up to 1 MB in this way. The maximum size is 15 MB. Transfer
larger content in chunks. In this way, the GET_CONTENT method only returns the first few bytes in the STREAM
parameter and sets the HAS_MORE parameter to true. The SAP Mobile Documents server then calls the
GET_CONTENT method again with an offset pointing to the next byte after this chunk. The server repeats the call
until the entire content is transferred and HAS_MORE is set to false. To the clients, this looks like one continuous
stream.
Note
The size of a chunk should not exceed 1 MB and must not exceed 15 MB.
The GET_CONTENT method must supply a MIME type for the content. If no MIME type is provided and the content
is pulled from an external store using HTTP, the MIME type provided by the external store is used (HTTP header
Content-Type). If the content source does not provide a MIME type, application/octet-stream is used.

Write
Similarly to the GET_CONTENT method, there are also different ways to create content. The content can be
delivered as one xstring, it can be directly pushed to an HTTP URL, or it can be delivered in chunks. The method
that the repository supports can be expressed with the repository info (see Repository Info (Cloud) [page 124]).
The flow differs depending on the chosen method:
full
In this case, CREATE_CONTENT receives the full content as an xstring within the IS_CONTENT structure and
the HAS_MORE parameter is set to false. The implementation only needs to return the new object ID using the
EV_OBJECT_ID parameter. Use this method if you expect small content (<1 MB, max 15 MB).
chunked
In this case the content is delivered in chunks, the CREATE_DOCUMENT method is called, and the first chunk is
transported using the IS_CONTENT structure. If there is only one chunk, the HAS_MORE parameter is set to
false. If the HAS_MORE parameter is set to true, the CREATE_CONTENT method is then called. The same logic
as for the CREATE_DOCUMENT method applies to the CREATE_CONTENT method: If the HAS_MORE parameter is
set to true, it is called again until the complete content is transferred, as indicated by the HAS_MORE
parameter. In this case it is sufficient for the CREATE_DOCUMENT method to return the object ID using the
EV_OBJECT_ID parameter. Use this method if you expect medium-size content (<100 MB).
document_specific
In this case the CREATE_DOCUMENT method is called with only the document metadata and without content.
The repository must also ensure that the properties are saved and an empty document is created. In addition,
the repository has to send back the ES_CONTENT_DELIVERY_INFO structure that contains the information
on how to deliver the content. If you choose to deliver the content using a URL, then the repository must
provide an HTTP URL and the method (POST/PUT) to use. The content is then directly pushed to that URL.
After the content upload and regardless of whether the upload succeeded or failed, the
ON_CONTENT_UPLOADED method is called. The parameter IV_UPLOAD_RESULT is set to "OK" if the upload
was successful. Any other value indicates an upload failure. If you choose a chunked or a full delivery, the
CREATE_CONTENT method is called either with the complete content or the first chunk of it.
9.2.2.5 Query
The SAP Mobile Documents ABAP connector contains a simple query parser. It splits CMIS queries into the four
main parts of a query: SELECT, FROM, WHERE, and ORDER BY.
It also parses the SELECT, FROM, and ORDER BY parts and provides the results in appropriate data structures.
The WHERE clause is not parsed, but is provided as a single string.
Example
Using the Query Parser
DATA: iv_query_statement TYPE cmis_string,

rs_simple_parse_result TYPE cl_cmis_simple_query_parser=>parse_result,
select TYPE STANDARD TABLE OF
cl_cmis_simple_query_parser=>name_alias WITH DEFAULT KEY,
from TYPE cl_cmis_simple_query_parser=>name_alias,
where TYPE cmis_string,
orderBy TYPE cl_cmis_simple_query_parser=>sort_order_tab.

iv_query_statement = 'SELECT cmis:name AS name, cmis:contentStreamLength FROM
cmis:document WHERE cmis:contentStreamLength < 1024 ORDER BY cmis:name'.
rs_simple_parse_result = cl_cmis_simple_query_parser=>parse( iv_query_statement ).
select = rs_simple_parse_result-property-query_names.
from = rs_simple_parse_result-property-type_query_name.
where = rs_simple_parse_result-property-where_clause.
orderBy = rs_simple_parse_result-property-sort_order.
9.2.2.6 Building a CMIS Server for SAP Mobile Documents
The SAP Mobile Documents end-user clients require the following set of methods to work properly. Other CMIS
clients may require more.
Table 61: Methods

Service CMIS Method ABAP Method Convenience Imple Required (ro = read-
mentation in Abstract only, rw = read-write)
Class
Repository Service
getRepositorie X ro / rw
s
getRepositoryI REP_INFO - ro / rw
nfo
getTypeChildre GET_TYPE_CHILDREN - ro / rw
n
getTypeDecenda GET_TYPE_DESCENDAN X ro / rw
nts TS
getTypeDefinit GET_ - ro / rw
ion TYPE_DEFINITION
createType - -
updateType - -
deleteType - -
Navigation Service
getChildren GET_CHILDREN - ro / rw
getDecendants X -
getFolderTree X -
getFolderParen - ro / rw
t
getObjectParen GET_OBJECT_PARENTS - ro / rw
ts
getCheckedOutD - -
ocs
Object Service

Class
createDocument - rw
createDocument - rw
FromSource
createFolder - rw
createRelation - -
ship
createPolicy - -
createItem - -
getObject GET_OBJECT - ro / rw
getAllowableAc X ro / rw
tions
getProperties X ro / rw
getObjectByPat - ro / rw
h
getContentStre GET_CONTENT - ro / rw
am
getRenditions X -
updateProperti - rw
es
bulkUpdateProp X -
erties
moveObject - ro / rw
deleteObject - ro / rw
deleteTree - ro / rw
setContentStre - ro / rw
am
appendContentS - -
tream
deleteContentS - ro / rw
tream
Versioning Service
checkOut - rw
cancelCheckOut - rw
checkIn - rw
getObjectOfLat - ro / rw
estVersion
getPropertiesO X -
fLatestVersion

Class
getAllVersions - rw
Discovery Service
query QUERY - ro / rw
(metadata query is re
quired, fulltext query is
optional)
getContentChan - -
ges
(used if available)
ACL Service
getACL - -
applyACL - -
Relationship Service
getObjectRelat - -
ionships
Policy Service - -
applyPolicy - -
removePolicy - -
getAppliedPoli
cies
Multifiling Service
addObjectToFol - -
der
removeObjectFr - -
omFolder
Queries
The following queries must be supported:
SELECT * from cmis:folder WHERE cmis:name LIKE '%@'

SELECT * from cmis:document WHERE cmis:name LIKE '%@'
SELECT * FROM cmis:folder WHERE cmis:name LIKE '%@' AND LIKE '%@' ... AND
IN_TREE('%@')
SELECT * FROM cmis:document WHERE cmis:name LIKE '%@' AND LIKE '%@' ... AND
IN_TREE('%@')
SELECT * FROM cmis:folder WHERE cmis:objectId = '%@'
SELECT * FROM cmis:document WHERE cmis:objectId = '%@'

SELECT * FROM cmis:folder WHERE cmis:objectId IN (%@)
SELECT * FROM cmis:document WHERE cmis:objectId IN (%@)
9.2.2.7 Building a CMIS Repository in an ABAP System
These first steps allow you to create a read-only implementation of the ABAP repository.
Procedure
1. Create a class that extends the CL_CMIS_ABSTRACT_SERVICE class.

2. Define a repository ID for your new repository implementation.
A repository ID must be unique within the system and can be any case-insensitive string up to 100 characters.
Note
Avoid special characters. The ID will be part of URLs and debugging is easier if the ID does not need to be
encoded or decoded.
3. Add the repository ID and the name of your class to the CMISD_SERVICE table.
4. Implement the GET_REPOSITORY_INFO method in your class.
Make sure that you use the same repository ID that you entered in the CMISD_SERVICE table.
Note
The CL_CMIS_OBJECT_FACTORY class provides a CREATE_REPOSITORY_INFO_READ method that creates
a stub of a repository info structure. The returned structure is sufficient for most read-only repositories.
Repositories that support create and update operations have to modify this structure depending on their
capabilities.
Example
Using the Object Factory to Create a Repository Info Object
es_repository_info = cl_cmis_object_factory=>create_repository_info_read(
iv_name = 'My Repository'
iv_description = 'This is my first repository'
iv_id = 'MY_REPOSITORY_ID'
iv_vendor = 'Example Inc'
iv_product_name = 'Document Store'
iv_product_version = '1.0'
iv_root_folder_id = '783245-837234-23490823'
iv_acl_supported = abap_false
).
5. Implement the GET_OBJECT, the GET_OBJECT_BY_PATH, and the GET_OBJECT_LATEST_VERSION methods.
These methods are all quite similar. Focus on the properties. Everything else can be added later.

Note
GET_OBJECT returns a structure of type CMIS_S_OBJECT. This structure is used in many places. Consider
using a central method that can be reused by other methods and that fills a CMIS_S_OBJECT structure.
Note
The CL_CMIS_OBJECT_FACTORY class provides methods to fill CMIS_S_PROPERTY structures. These
structures hold property values and you need one for every property value that you have to return.
There are three methods for each data type:

CREATE_<XXX>_PROP_SINGLE
CREATE_<XXX>_PROP_MULTI
CREATE_<XXX>_PROP_NOTSET
<XXX> is a placeholder for one of the CMIS data types: ID, String, Integer, Decimal, Boolean, DateTime,
URI, and HTML.
The CREATE_XXX_PROP_SINGLE methods return a structure for a single-value property. The

CREATE_XXX_PROP_MULTI methods return a structure for a multivalue property. If the property (single-
value or multivalue) has no value, use the CREATE_XXX_PROP_NOTSET method.
Example
Using the Object Factory to Create a Property Value
ls_name_property = cl_cmis_object_factory=>create_string_prop_single(
iv_property_id = cl_cmis_property_ids=>name
iv_value = 'test.txt'
).
6. Implement the GET_CHILDREN, the GET_FOLDER_PARENT, and the GET_OBJECT_PARENTS methods.
You can reuse a lot of the code from the GET_OBJECT method.
At this point, you can browse through your repository, but the SAP Mobile Documents clients do not allow you
to do anything else.
7. Go back to the GET_OBJECT method and add support for Allowable Actions. If your repository supports ACLs,
also add ACL support.
The SAP Mobile Documents clients use the Allowable Actions to determine which buttons are active and
which buttons are deactivated. Once you have added support for Allowable Actions, the SAP Mobile
Documents clients provide you with more options.
8. Implement the GET_CONTENT method.
Note
It is preferable to send a URL to the content rather than sending the content as an xstring. The
performance is better and the content size is not limited.
You should now be able to use most features of the SAP Mobile Documents clients, except syncing and
querying. These depend on the QUERY method.

9. Implement the QUERY method.
This is the most complex task. If you just want to support SAP Mobile Documents clients, only add support for
the queries mentioned above.
The simple query parser that is included in the SAP Mobile Documents ABAP connector helps you identify the
queries and return the correct result set.
Once the query is implemented, this server supports all read-only operations that SAP Mobile Documents
requires.
9.3 CMIS Extension for Search
This specification defines a new predicate function PREVIEW() in the CMIS Query Language that returns a
content snippet with the found match in the searched CMIS objects.
When displaying search results, CMIS clients can display a content snippet with the matched content.
Specification
BNF grammar structure: PREVIEW ()
Usage
This is a predicate function that encapsulates the full-text search capability that may be provided by a
repository. It offers a string content snippet for the matched content in a CMIS object.
Inputs
No inputs must be provided for this predicate function.
Return Value
The PREVIEW () predicate function returns a string with HTML formatting such as <b>matched term</
b>.
Constraints
The PREVIEW () function must only be used in queries that also include a CONTAINS() predicate
function.
The PREVIEW () function must only be used in the SELECT clause of a query. It must not be used in the
WHERE clause or in the ORDER BY clause.
If PREVIEW() is included in the SELECT clause and an alias column name is not provided, then a query
name of SEARCH_PREVIEW is used for the query output, and the property definition id is repository-
specific.
Extension Definition (CMIS 1.1)
The repository MUST provide the following feature extension in the repository info.

Table 62:
Feature Extension Attribute Value
ID http://sap.com/cmis/extension/fulltextsearchpreview
URL n.a.
Common Name Full Text Search Content Preview
Version Label 1.0
Description Allows the CMIS query language to support the PREVIEW() function which returns a
content snippet of the matching text in the selected resources.

10 Supported CMIS 1.1 Features (Cloud)
SAP Mobile Documents supports the following CMIS methods in browser and AtomPub bindings.
Note
For performance reasons, we recommend using the browser binding.
Table 63: CMIS 1.0 Features

Service Method Supported
Repository Service
getRepositories Yes
getRepositoryInfo Yes
getTypeChildren Yes
getTypeDecendants Yes
getTypeDefinition Yes
Navigation Service
getChildren Yes
getDecendants Yes
getFolderTree Yes
getFolderParent Yes
getObjectParents Yes
getCheckedOutDocs Yes
Object Service
createDocument Yes
createDocumentFromSource Yes
createFolder Yes
createRelationship No
createPolicy No
getAllowableActions Yes
getObject Yes
getProperties Yes
getObjectByPath Yes
getContentStream Yes
getRenditions No
updateProperties Yes

Supported CMIS 1.1 Features (Cloud) 2016 SAP SE or an SAP affiliate company. All rights reserved. 135
Service Method Supported
moveObject Yes
deleteObject Yes
deleteTree Yes
setContentStream Yes
deleteContentStream Yes
Versioning Service
checkOut Yes
cancelCheckOut Yes
checkIn Yes
getObjectOfLatestVersion Yes
getPropertiesOfLatestVersion Yes
getAllVersions Yes
Discovery Service
query Yes
getContentChanges No
ACL Service
getACL Yes
applyACL Yes
Relationship Service
getObjectRelationships No
Policy Service
applyPolicy No
removePolicy No
getAppliedPolicies No
Multifiling Service
addObjectToFolder No
removeObjectFromFolder No

136 2016 SAP SE or an SAP affiliate company. All rights reserved. Supported CMIS 1.1 Features (Cloud)
11 Open Source Licenses
This document contains licensing information relating to SAP's use of free and open-source software with or
within the product identified above (collectively, "FOSS").
Any terms, conditions, and restrictions governing the use or distribution of FOSS that are not contained within the
license(s) governing use and distribution of the FOSS (the "FOSS Licenses") are offered and imposed by SAP
alone. The authors, licensors, and distributors of the FOSS have disclaimed all warranties relating to any liability
arising from the use and distribution of the FOSS.
This document identifies the FOSS components used and the FOSS Licenses that SAP believes govern those
FOSS components. While SAP has sought to provide complete and accurate licensing information for each FOSS
component, SAP does not represent or warrant that the licensing information provided herein is correct or error-
free. Recipients of this product should investigate the identified FOSS components to confirm the accuracy of the
licensing information provided herein. Recipients are also encouraged to notify SAP of any inaccurate information
or errors found in this document.
Certain FOSS Licenses require that SAP make available to recipients the source code corresponding to FOSS
binaries distributed under those licenses. Recipients who would like to receive a copy of such source code should
submit a request to SAP by e-mail to opensource@sap.com.
Please provide the following information in submitted requests: the FOSS components for which you are
requesting source code; the SAP product and version number with which the requested FOSS component is
distributed; an e-mail address at which SAP may contact you regarding the request (if available); and the postal
address for delivery of the requested source code.
If you have any questions or concerns, contact opensource@sap.com.
Table 64: Licenses for FOSS Components

FOSS Component License
Android Beacon Library Apache License v 2.0
Apache Active MQ Apache v.2.0 License
Apache Chemistry ObjectiveCMIS Apache License v 2.0
Apache Chemistry OpenCMIS Apache License v 2.0
Apache CXF Apache License v 2.0
Apache-Jakarta BeanUtils Apache License v 2.0
Apache Jakarta Log4j Apache License v 2.0
Apache log4net Apache v.2.0 License
Apache Regexp - Reuse from Portal KM (bc.util.public_api-1.0.jar). Approved Apache License v 2.0
from code center
Base64 adp Rene Nyffenegger License
ELCImagePickerController MIT License V2
Illegal Argument Exception Blog - Java: synchronizing on an ID MIT License V2

Open Source Licenses 2016 SAP SE or an SAP affiliate company. All rights reserved. 137
FOSS Component License
iOS Developer Library - AdvancedURLConnections Apple Disclaimer
CocoaHTTPServer BSD 2.0 License
Eclipse SWT Eclipse Foundation Software User Agreement
Google GSON Apache v.2.0 License
HSQLDB (HyperSQL) Hypersonic SQL License
Jettison Apache License v 2.0
JQuery MIT License V2
Json.NET MIT License V2
LiquiBase Apache v.2.0 License
MGSwipeTableCell MIT License V2
Mozilla Rhino: JavaScript for Java Basic Mozilla Style License
NanoHttpd BSD 2.0 License
Objective-Zip BSD 2.0 License
pdf.js Apache License v 2.0
Proxy Vole BSD 2.0 License
Quartz Apache v.2.0 License
Sardine Apache License v 2.0
SharpShell MIT License
Simple Logging Facade for Java (SLF4J) The MIT License (MIT)
Some SecureRandom Thoughts Some SecureRandom Thoughts License
11.1 Apache License, Version 2.0
Apache License
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1
through 9 of this document.

138 2016 SAP SE or an SAP affiliate company. All rights reserved. Open Source Licenses
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the
License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or
are under common control with that entity. For the purposes of this definition, "control" means (i) the power,
direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or
(ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such
entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software
source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form,
including but not limited to compiled object code, generated documentation, and conversions to other media
types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the
License, as indicated by a copyright notice that is included in or attached to the work (an example is provided
in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from)
the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as
a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include
works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and
Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any
modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor
for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on
behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic,
verbal, or written communication sent to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems, and issue tracking systems that are
managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise designated in writing by the copyright
owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has
been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare
Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such
Derivative Works in Source or Object form.
3. Grant of Patent License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license
to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license
applies only to those patent claims licensable by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s)
was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a
lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or
contributory patent infringement, then any patent licenses granted to You under this License for that Work
shall terminate as of the date such litigation is filed.
4. Redistribution.

You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or
without modifications, and in Source or Object form, provided that You meet the following conditions:
1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
2. You must cause any modified files to carry prominent notices stating that You changed the files; and
3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work, excluding those notices that do not
pertain to any part of the Derivative Works; and
4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You
distribute must include a readable copy of the attribution notices contained within such NOTICE file,
excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following
places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative
Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for
informational purposes only and do not modify the License. You may add Your own attribution notices within
Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work,
provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different
license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such
Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise
complies with the conditions stated in this License.
5. Submission of Contributions.
Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by
You to the Licensor shall be under the terms and conditions of this License, without any additional terms or
conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate
license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks.
This License does not grant permission to use the trade names, trademarks, service marks, or product names
of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and
reproducing the content of the NOTICE file.
7. Disclaimer of Warranty.
Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor
provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-
INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible
for determining the appropriateness of using or redistributing the Work and assume any risks associated with
Your exercise of permissions under this License.
8. Limitation of Liability.
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless
required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any
Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential
damages of any character arising as a result of this License or out of the use or inability to use the Work
(including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or
any and all other commercial damages or losses), even if such Contributor has been advised of the possibility
of such damages.
9. Accepting Warranty or Additional Liability.
While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for,
acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole
responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold

each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by
brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be
enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and
description of purpose be included on the same "printed page" as the copyright notice for easier identification
within third-party archives.
Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed
under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations
under the License.
11.2 Creative Commons License
LEGAL CODE
Attribution 2.5
CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE LEGAL SERVICES.
DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN ATTORNEY-CLIENT RELATIONSHIP. CREATIVE
COMMONS PROVIDES THIS INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO
WARRANTIES REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR DAMAGES
RESULTING FROM ITS USE.
License
THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC
LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE
LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS
PROHIBITED.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE
TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION
OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
1. Definitions
a. "Collective Work" means a work, such as a periodical issue, anthology or encyclopedia, in which the Work in its
entirety in unmodified form, along with a number of other contributions, constituting separate and independent

works in themselves, are assembled into a collective whole. A work that constitutes a Collective Work will not be
considered a Derivative Work (as defined below) for the purposes of this License.
b. "Derivative Work" means a work based upon the Work or upon the Work and other pre-existing works, such as a
translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art
reproduction, abridgment, condensation, or any other form in which the Work may be recast, transformed, or
adapted, except that a work that constitutes a Collective Work will not be considered a Derivative Work for the
purpose of this License. For the avoidance of doubt, where the Work is a musical composition or sound recording,
the synchronization of the Work in timed-relation with a moving image ("synching") will be considered a Derivative
Work for the purpose of this License.
c. "Licensor" means the individual or entity that offers the Work under the terms of this License.
d. "Original Author" means the individual or entity who created the Work.
e. "Work" means the copyrightable work of authorship offered under the terms of this License.
f. "You" means an individual or entity exercising rights under this License who has not previously violated the
terms of this License with respect to the Work, or who has received express permission from the Licensor to
exercise rights under this License despite a previous violation.
2. Fair Use Rights. Nothing in this license is intended to reduce, limit, or restrict any rights arising from fair use,
first sale or other limitations on the exclusive rights of the copyright owner under copyright law or other applicable
laws.
3. License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide,
royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in
the Work as stated below:
a. to reproduce the Work, to incorporate the Work into one or more Collective Works, and to reproduce the Work
as incorporated in the Collective Works;
b. to create and reproduce Derivative Works;
c. to distribute copies or phonorecords of, display publicly, perform publicly, and perform publicly by means of a
digital audio transmission the Work including as incorporated in Collective Works;
d. to distribute copies or phonorecords of, display publicly, perform publicly, and perform publicly by means of a
digital audio transmission Derivative Works.
e. For the avoidance of doubt, where the work is a musical composition:
i. Performance Royalties Under Blanket Licenses. Licensor waives the exclusive right to collect, whether
individually or via a performance rights society (e.g. ASCAP, BMI, SESAC), royalties for the public performance or
public digital performance (e.g. webcast) of the Work.
ii. Mechanical Rights and Statutory Royalties. Licensor waives the exclusive right to collect, whether individually or
via a music rights agency or designated agent (e.g. Harry Fox Agency), royalties for any phonorecord You create
from the Work ("cover version") and distribute, subject to the compulsory license created by 17 USC Section 115
of the US Copyright Act (or the equivalent in other jurisdictions).
f. Webcasting Rights and Statutory Royalties. For the avoidance of doubt, where the Work is a sound recording,
Licensor waives the exclusive right to collect, whether individually or via a performance-rights society (e.g.
SoundExchange), royalties for the public digital performance (e.g. webcast) of the Work, subject to the
compulsory license created by 17 USC Section 114 of the US Copyright Act (or the equivalent in other
jurisdictions).

The above rights may be exercised in all media and formats whether now known or hereafter devised. The above
rights include the right to make such modifications as are technically necessary to exercise the rights in other
media and formats. All rights not expressly granted by Licensor are hereby reserved.
4. Restrictions.The license granted in Section 3 above is expressly made subject to and limited by the following
restrictions:
a. You may distribute, publicly display, publicly perform, or publicly digitally perform the Work only under the
terms of this License, and You must include a copy of, or the Uniform Resource Identifier for, this License with
every copy or phonorecord of the Work You distribute, publicly display, publicly perform, or publicly digitally
perform. You may not offer or impose any terms on the Work that alter or restrict the terms of this License or the
recipients' exercise of the rights granted hereunder. You may not sublicense the Work. You must keep intact all
notices that refer to this License and to the disclaimer of warranties. You may not distribute, publicly display,
publicly perform, or publicly digitally perform the Work with any technological measures that control access or
use of the Work in a manner inconsistent with the terms of this License Agreement. The above applies to the Work
as incorporated in a Collective Work, but this does not require the Collective Work apart from the Work itself to be
made subject to the terms of this License. If You create a Collective Work, upon notice from any Licensor You
must, to the extent practicable, remove from the Collective Work any credit as required by clause 4(b), as
requested. If You create a Derivative Work, upon notice from any Licensor You must, to the extent practicable,
remove from the Derivative Work any credit as required by clause 4(b), as requested.
b. If you distribute, publicly display, publicly perform, or publicly digitally perform the Work or any Derivative
Works or Collective Works, You must keep intact all copyright notices for the Work and provide, reasonable to the
medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, if applicable) if supplied,
and/or (ii) if the Original Author and/or Licensor designate another party or parties (e.g. a sponsor institute,
publishing entity, journal) for attribution in Licensor's copyright notice, terms of service or by other reasonable
means, the name of such party or parties; the title of the Work if supplied; to the extent reasonably practicable,
the Uniform Resource Identifier, if any, that Licensor specifies to be associated with the Work, unless such URI
does not refer to the copyright notice or licensing information for the Work; and in the case of a Derivative Work, a
credit identifying the use of the Work in the Derivative Work (e.g., "French translation of the Work by Original
Author," or "Screenplay based on original Work by Original Author"). Such credit may be implemented in any
reasonable manner; provided, however, that in the case of a Derivative Work or Collective Work, at a minimum
such credit will appear where any other comparable authorship credit appears and in a manner at least as
prominent as such other comparable authorship credit.
5. Representations, Warranties and Disclaimer
UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-
IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS,
IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE,
MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF
LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT
DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH
EXCLUSION MAY NOT APPLY TO YOU.
6. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL
LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL,
PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF
LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
7. Termination
a. This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms
of this License. Individuals or entities who have received Derivative Works or Collective Works from You under this

License, however, will not have their licenses terminated provided such individuals or entities remain in full
compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.
b. Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the
applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work
under different license terms or to stop distributing the Work at any time; provided, however that any such
election will not serve to withdraw this License (or any other license that has been, or is required to be, granted
under the terms of this License), and this License will continue in full force and effect unless terminated as stated
above.
8. Miscellaneous
a. Each time You distribute or publicly digitally perform the Work or a Collective Work, the Licensor offers to the
recipient a license to the Work on the same terms and conditions as the license granted to You under this License.
b. Each time You distribute or publicly digitally perform a Derivative Work, Licensor offers to the recipient a license
to the original Work on the same terms and conditions as the license granted to You under this License.
c. If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or
enforceability of the remainder of the terms of this License, and without further action by the parties to this
agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and
enforceable.
d. No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or
consent shall be in writing and signed by the party to be charged with such waiver or consent.
e. This License constitutes the entire agreement between the parties with respect to the Work licensed here.
There are no understandings, agreements or representations with respect to the Work not specified here.
Licensor shall not be bound by any additional provisions that may appear in any communication from You. This
License may not be modified without the mutual written agreement of the Licensor and You.
Creative Commons is not a party to this License, and makes no warranty whatsoever in connection with the Work.
Creative Commons will not be liable to You or any party on any legal theory for any damages whatsoever,
including without limitation any general, special, incidental or consequential damages arising in connection to this
license. Notwithstanding the foregoing two (2) sentences, if Creative Commons has expressly identified itself as
the Licensor hereunder, it shall have all rights and obligations of Licensor.
Except for the limited purpose of indicating to the public that the Work is licensed under the CCPL, neither party
will use the trademark "Creative Commons" or any related trademark or logo of Creative Commons without the
prior written consent of Creative Commons. Any permitted use will be in compliance with Creative Commons'
then-current trademark usage guidelines, as may be published on its website or otherwise made available upon
request from time to time.
Creative Commons may be contacted at http://creativecommons.org/.
11.3 Eclipse License
Eclipse Foundation Software User Agreement
April 9, 2014
Usage Of Content

THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR
OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS
GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS
OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU
AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND
CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW.
IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW,
THEN YOU MAY NOT USE THE CONTENT.
Applicable Licenses
Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the
terms and conditions of the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is provided with this
Content and is also available at http://www.eclipse.org/legal/epl-v10.html. For purposes of the EPL, "Program"
will mean the Content.
Content includes, but is not limited to, source code, object code, documentation and other files maintained in the
Eclipse Foundation source code repository ("Repository") in software modules ("Modules") and made available as
downloadable archives ("Downloads").
Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the
Content. Typical modules may include plug-ins ("Plug-ins"), plug-in fragments ("Fragments"), and features
("Features").
Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java ARchive) in a directory named
"plugins".
A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may
be packaged as a sub-directory in a directory named "features". Within a Feature, files named "feature.xml"
may contain a list of the names and version numbers of the Plug-ins and/or Fragments associated with that
Feature.
Features may also include other Features ("Included Features"). Within a Feature, files named "feature.xml"
may contain a list of the names and version numbers of Included Features.
The terms and conditions governing Plug-ins and Fragments should be contained in files named "about.html"
("Abouts"). The terms and conditions governing Features and Included Features should be contained in files
named "license.html" ("Feature Licenses"). Abouts and Feature Licenses may be located in any directory of a
Download or Module including, but not limited to the following locations:
The top-level (root) directory

Plug-in and Fragment directories
Inside Plug-ins and Fragments packaged as JARs
Sub-directories of the directory named "src" of certain Plug-ins
Feature directories
Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as
defined below), you must agree to a license ("Feature Update License") during the installation process. If the
Feature contains Included Features, the Feature Update License should either provide you with the terms and
conditions governing the Included Features or inform you where you can locate them. Feature Update Licenses
may be found in the "license" property of files named "feature.properties" found within a Feature. Such Abouts,
Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms
and conditions) that govern your use of the associated Content in that directory.

THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER
LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE OTHER LICENSE
AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):
Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html)

Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)
Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)
Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)
Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)
IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE
CONTENT. If no About, Feature License, or Feature Update License is provided, please contact the Eclipse
Foundation to determine what terms and conditions govern that particular Content.
Use of Provisioning Technology
The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to,
p2 and the Eclipse Update Manager ("Provisioning Technology") for the purpose of allowing users to install
software, documentation, information and/or other materials (collectively "Installable Software"). This capability
is provided with the intent of allowing such users to install, extend and update Eclipse-based products.
Information about packaging Installable Software is available at http://eclipse.org/equinox/p2/
repository_packaging.html ("Specification").
You may use Provisioning Technology to allow other parties to install Installable Software. You shall be
responsible for enabling the applicable license agreements relating to the Installable Software to be presented to,
and accepted by, the users of the Provisioning Technology in accordance with the Specification. By using
Provisioning Technology in such a manner and making it available in accordance with the Specification, you
further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:
1. A series of actions may occur ("Provisioning Process") in which a user may execute the Provisioning
Technology on a machine ("Target Machine") with the intent of installing, extending or updating the
functionality of an Eclipse-based product.
2. During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a
portion thereof to be accessed and copied to the Target Machine.
3. Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the
Installable Software ("Installable Software Agreement") and such Installable Software Agreement shall be
accessed from the Target Machine in accordance with the Specification. Such Installable Software Agreement
must inform the user of the terms and conditions that govern the Installable Software and must solicit
acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
indication of agreement by the user, the provisioning Technology will complete installation of the Installable
Software.
Cryptography
Content may contain encryption software. The country in which you are currently may have restrictions on the
import, possession, and use, and/or re-export to another country, of encryption software. BEFORE using any
encryption software, please check the country's laws, regulations and policies concerning the import, possession,
or use, and re-export of encryption software, to see if this is permitted.
Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or
both.

11.4 Hypersonic SQL License
Copyright (c) 1995-2000 by the Hypersonic SQL Group. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display the following acknowledgment:
"This product includes Hypersonic SQL."
Products derived from this software may not be called "Hypersonic SQL" nor may "Hypersonic SQL" appear in
their names without prior written permission of the Hypersonic SQL Group.
Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes
Hypersonic SQL."
This software is provided "as is" and any expressed or implied warranties, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose are disclaimed.
In no event shall the Hypersonic SQL Group or its contributors be liable for any direct, indirect, incidental, special,
exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services;
loss of use, data, or profits; or business interruption). However caused any on any theory of liability, whether in
contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this
software, even if advised of the possibility of such damage.
This software consists of voluntary contributions made by many individuals on behalf of the Hypersonic SQL
Group.
11.5 Mozilla Public License Version 2.0
http://www.mozilla.org/MPL/2.0/
Mozilla Public License Version 2.0
1. Definitions
1. "Contributor"
means each individual or legal entity that creates, contributes to the creation of, or owns Covered
Software.
2. Contributor Version

means the combination of the Contributions of others (if any) used by a Contributor and that particular
Contributors Contribution.
3. Contribution
means Covered Software of a particular Contributor.
4. Covered Software
means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the
Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case
including portions thereof.
5. Incompatible With Secondary Licenses
means
a. that the initial Contributor has attached the notice described in Exhibit B to the Covered Software; or
b. that the Covered Software was made available under the terms of version 1.1 or earlier of the License,
but not also under the terms of a Secondary License.
6. Executable Form
means any form of the work other than Source Code Form.
7. Larger Work
means a work that combines Covered Software with other material, in a separate file or files, that is not
Covered Software.
8. License
means this document.
9. Licensable
means having the right to grant, to the maximum extent possible, whether at the time of the initial grant
or subsequently, any and all of the rights conveyed by this License.
10. Modifications
means any of the following:
a. any file in Source Code Form that results from an addition to, deletion from, or modification of the
contents of Covered Software; or
b. any new file in Source Code Form that contains any Covered Software.
11. Patent Claims of a Contributor
means any patent claim(s), including without limitation, method, process, and apparatus claims, in any
patent Licensable by such Contributor that would be infringed, but for the grant of the License, by the
making, using, selling, offering for sale, having made, import, or transfer of either its Contributions or its
Contributor Version.
12. Secondary License
means either the GNU General Public License, Version 2.0, the GNU Lesser General Public License,
Version 2.1, the GNU Affero General Public License, Version 3.0, or any later versions of those licenses.
13. Source Code Form
means the form of the work preferred for making modifications.
14. You (or Your)
means an individual or a legal entity exercising rights under this License. For legal entities, You includes
any entity that controls, is controlled by, or is under common control with You. For purposes of this
definition, control means (a) the power, direct or indirect, to cause the direction or management of
such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the
outstanding shares or beneficial ownership of such entity.
2. License Grants and Conditions
1. Grants

Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:
a. under intellectual property rights (other than patent or trademark) Licensable by such Contributor to
use, reproduce, make available, modify, display, perform, distribute, and otherwise exploit its
Contributions, either on an unmodified basis, with Modifications, or as part of a Larger Work; and
b. under Patent Claims of such Contributor to make, use, sell, offer for sale, have made, import, and
otherwise transfer either its Contributions or its Contributor Version.
2. Effective Date
The licenses granted in Section 2.1 with respect to any Contribution become effective for each
Contribution on the date the Contributor first distributes such Contribution.
3. Limitations on Grant Scope
The licenses granted in this Section 2 are the only rights granted under this License. No additional rights
or licenses will be implied from the distribution or licensing of Covered Software under this License.
Notwithstanding Section 2.1(b) above, no patent license is granted by a Contributor:
a. for any code that a Contributor has removed from Covered Software; or
b. for infringements caused by: (i) Your and any other third partys modifications of Covered Software, or
(ii) the combination of its Contributions with other software (except as part of its Contributor Version); or
c. under Patent Claims infringed by Covered Software in the absence of its Contributions.
This License does not grant any rights in the trademarks, service marks, or logos of any Contributor
(except as may be necessary to comply with the notice requirements in Section 3.4).
4. Subsequent Licenses
No Contributor makes additional grants as a result of Your choice to distribute the Covered Software
under a subsequent version of this License (see Section 10.2) or under the terms of a Secondary License
(if permitted under the terms of Section 3.3).
5. Representation
Each Contributor represents that the Contributor believes its Contributions are its original creation(s) or
it has sufficient rights to grant the rights to its Contributions conveyed by this License.
6. Fair Use
This License is not intended to limit any rights You have under applicable copyright doctrines of fair use,
fair dealing, or other equivalents.
7. Conditions
Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in Section 2.1.
3. Responsibilities
1. Distribution of Source Form
All distribution of Covered Software in Source Code Form, including any Modifications that You create or
to which You contribute, must be under the terms of this License. You must inform recipients that the
Source Code Form of the Covered Software is governed by the terms of this License, and how they can
obtain a copy of this License. You may not attempt to alter or restrict the recipients rights in the Source
Code Form.
2. Distribution of Executable Form
If You distribute Covered Software in Executable Form then:
a. such Covered Software must also be made available in Source Code Form, as described in Section 3.1,
and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code
Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the
recipient; and
b. You may distribute such Executable Form under the terms of this License, or sublicense it under
different terms, provided that the license for the Executable Form does not attempt to limit or alter the
recipients rights in the Source Code Form under this License.
3. Distribution of a Larger Work

You may create and distribute a Larger Work under terms of Your choice, provided that You also comply
with the requirements of this License for the Covered Software. If the Larger Work is a combination of
Covered Software with a work governed by one or more Secondary Licenses, and the Covered Software is
not Incompatible With Secondary Licenses, this License permits You to additionally distribute such
Covered Software under the terms of such Secondary License(s), so that the recipient of the Larger Work
may, at their option, further distribute the Covered Software under the terms of either this License or
such Secondary License(s).
4. Notices
You may not remove or alter the substance of any license notices (including copyright notices, patent
notices, disclaimers of warranty, or limitations of liability) contained within the Source Code Form of the
Covered Software, except that You may alter any license notices to the extent required to remedy known
factual inaccuracies.
5. Application of Additional Terms
You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to
one or more recipients of Covered Software. However, You may do so only on Your own behalf, and not on
behalf of any Contributor. You must make it absolutely clear that any such warranty, support, indemnity,
or liability obligation is offered by You alone, and You hereby agree to indemnify every Contributor for any
liability incurred by such Contributor as a result of warranty, support, indemnity or liability terms You
offer. You may include additional disclaimers of warranty and limitations of liability specific to any
jurisdiction.
4. Inability to Comply Due to Statute or Regulation
If it is impossible for You to comply with any of the terms of this License with respect to some or all of the
Covered Software due to statute, judicial order, or regulation then You must: (a) comply with the terms of this
License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such
description must be placed in a text file included with all distributions of the Covered Software under this
License. Except to the extent prohibited by statute or regulation, such description must be sufficiently
detailed for a recipient of ordinary skill to be able to understand it.
5. Termination
1. The rights granted under this License will terminate automatically if You fail to comply with any of its
terms. However, if You become compliant, then the rights granted under this License from a particular
Contributor are reinstated (a) provisionally, unless and until such Contributor explicitly and finally
terminates Your grants, and (b) on an ongoing basis, if such Contributor fails to notify You of the non-
compliance by some reasonable means prior to 60 days after You have come back into compliance.
Moreover, Your grants from a particular Contributor are reinstated on an ongoing basis if such
Contributor notifies You of the non-compliance by some reasonable means, this is the first time You have
received notice of non-compliance with this License from such Contributor, and You become compliant
prior to 30 days after Your receipt of the notice.
2. If You initiate litigation against any entity by asserting a patent infringement claim (excluding declaratory
judgment actions, counter-claims, and cross-claims) alleging that a Contributor Version directly or
indirectly infringes any patent, then the rights granted to You by any and all Contributors for the Covered
Software under Section 2.1 of this License shall terminate.
3. In the event of termination under Sections 5.1 or 5.2 above, all end user license agreements (excluding
distributors and resellers) which have been validly granted by You or Your distributors under this License
prior to termination shall survive termination.
6. Disclaimer of Warranty
Covered Software is provided under this License on an as is basis, without warranty of any kind, either
expressed, implied, or statutory, including, without limitation, warranties that the Covered Software is free of
defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and
performance of the Covered Software is with You. Should any Covered Software prove defective in any

respect, You (not any Contributor) assume the cost of any necessary servicing, repair, or correction. This
disclaimer of warranty constitutes an essential part of this License. No use of any Covered Software is
authorized under this License except under this disclaimer.
7. Limitation of Liability
Under no circumstances and under no legal theory, whether tort (including negligence), contract, or
otherwise, shall any Contributor, or anyone who distributes Covered Software as permitted above, be liable to
You for any direct, indirect, special, incidental, or consequential damages of any character including, without
limitation, damages for lost profits, loss of goodwill, work stoppage, computer failure or malfunction, or any
and all other commercial damages or losses, even if such party shall have been informed of the possibility of
such damages. This limitation of liability shall not apply to liability for death or personal injury resulting from
such partys negligence to the extent applicable law prohibits such limitation. Some jurisdictions do not allow
the exclusion or limitation of incidental or consequential damages, so this exclusion and limitation may not
apply to You.
8. Litigation
Any litigation relating to this License may be brought only in the courts of a jurisdiction where the defendant
maintains its principal place of business and such litigation shall be governed by laws of that jurisdiction,
without reference to its conflict-of-law provisions. Nothing in this Section shall prevent a partys ability to
bring cross-claims or counter-claims.
9. Miscellaneous
This License represents the complete agreement concerning the subject matter hereof. If any provision of this
License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it
enforceable. Any law or regulation which provides that the language of a contract shall be construed against
the drafter shall not be used to construe this License against a Contributor.
10. Versions of the License
1. New Versions
Mozilla Foundation is the license steward. Except as provided in Section 10.3, no one other than the
license steward has the right to modify or publish new versions of this License. Each version will be given
a distinguishing version number.
2. Effect of New Versions
You may distribute the Covered Software under the terms of the version of the License under which You
originally received the Covered Software, or under the terms of any subsequent version published by the
license steward.
3. Modified Versions
If you create software not governed by this License, and you want to create a new license for such
software, you may create and use a modified version of this License if you rename the license and remove
any references to the name of the license steward (except to note that such modified license differs from
this License).
4. Distributing Source Code Form that is Incompatible With Secondary Licenses
If You choose to distribute Source Code Form that is Incompatible With Secondary Licenses under the
terms of this version of the License, the notice described in Exhibit B of this License must be attached.
Exhibit A - Source Code Form License Notice
This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0.
If a copy of the MPL was not distributed with this file, You can obtain one at http://
mozilla.org/MPL/2.0/.

If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location
(such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice.
You may add additional accurate notices of copyright ownership.
Exhibit B - Incompatible With Secondary Licenses Notice
This Source Code Form is Incompatible With Secondary Licenses, as defined by the
Mozilla Public License, v. 2.0.
11.6 The BSD 3-Clause License
http://opensource.org/licenses/BSD-3-Clause
The BSD 3-Clause License
The following is a BSD 3-Clause ("BSD New" or "BSD Simplified") license template. To generate your own license,
change the values of OWNER and YEAR from their original values as given here, and substitute your own.
Note: You may omit clause 3 and still be OSD-conformant. Despite its colloquial name "BSD New", this is not
the newest version of the BSD license; it was followed by the even newer BSD-2-Clause version, sometimes known
as the "Simplified BSD License". On January 9th, 2008 the OSI Board approved BSD-2-Clause, which is used by
FreeBSD and others. It omits the final "no-endorsement" clause and is thus roughly equivalent to the MIT License.
Historical Background: The original license used on BSD Unix had four clauses. The advertising clause (the third of
four clauses) required you to acknowledge use of U.C. Berkeley code in your advertising of any product using that
code. It was officially rescinded by the Director of the Office of Technology Licensing of the University of California
on July 22nd, 1999. He states that clause 3 is "hereby deleted in its entirety." The four clause license has not been
approved by OSI. The license below does not contain the advertising clause.
This prelude is not part of the license.
<OWNER> = Regents of the University of California
<ORGANIZATION> = University of California, Berkeley
<YEAR> = 1998
In the original BSD license, both occurrences of the phrase "COPYRIGHT HOLDERS AND CONTRIBUTORS" in the
disclaimer read "REGENTS AND CONTRIBUTORS".
Here is the license template:
Copyright (c) <YEAR>, <OWNER>
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the <ORGANIZATION> nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
11.7 The MIT License (MIT)
Copyright (c) <year> <copyright holders>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).

154 2016 SAP SE or an SAP affiliate company. All rights reserved. Important Disclaimers and Legal Information
Important Disclaimers and Legal Information 2016 SAP SE or an SAP affiliate company. All rights reserved. 155
go.sap.com/registration/
contact.html
2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

Mobile Docs Cloud Version en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mobile Docs Cloud Version en

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP Mobile Documents 1.0 SP05

SAP Mobile Documents (Cloud Version)

1 SAP Mobile Documents (Cloud Version). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PUBLIC SAP Mobile Documents (Cloud Version)

8 Monitoring with Usage Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

9 Developer's Guide (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

10 Supported CMIS 1.1 Features (Cloud). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

11 Open Source Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

SAP Mobile Documents (Cloud Version) PUBLIC

PUBLIC SAP Mobile Documents (Cloud Version)

You have a subscription to the cloud version of SAP Mobile Documents.

SAP Mobile Documents (Cloud Version) PUBLIC

Support Package 00, Patch 01 (Cloud) [page 7]

Support Package 01 (Cloud) [page 7]

Support Package 02 (Cloud) [page 9]

Support Package 03 (Cloud) [page 11]

Support Package 04 (Cloud) [page 14]

Support Package 05 (Cloud) [page 17]

PUBLIC SAP Mobile Documents (Cloud Version)

Rebranding New SAP NetWeaver Cloud is now part of

Self-registration URL Changed Adjusted the URL for accessing the ac

2.2 Support Package 01 (Cloud)

New Features that Affect All Apps

New wizards guide the users through the publishing workflow.

SAP Mobile Documents (Cloud Version) PUBLIC

SAP Mobile Documents Web User Interface

SAP Mobile Documents Mobile Apps

2.2.1 Support Package 01 - Documentation Corrections (Cloud)

The documentation was updated and enhanced.

Updated Added table of supported CMIS features.

PUBLIC SAP Mobile Documents (Cloud Version)

New Features Affecting All Apps

New Sharing Concept

SAP Mobile Documents Web App

SAP Mobile Documents Desktop App

Notification on Failed Upload Due to Virus Infection

SAP Mobile Documents (Cloud Version) PUBLIC

SAP Mobile Documents Mobile Apps

New Icons to Indicate Synchronization Status:

PUBLIC SAP Mobile Documents (Cloud Version)

2.3.1 Support Package 02 - Documentation Corrections

Updated Restructured the opening topics.

Added the Glossary [page 23].

2.4 Support Package 03 (Cloud)

New Features Affecting All Apps

SAP Mobile Documents (Cloud Version) PUBLIC

SAP Mobile Documents Desktop App

PUBLIC SAP Mobile Documents (Cloud Version)

SAP Mobile Documents Mobile Apps

Enhanced sorting criteria for the mobile apps.

SAP Mobile Documents (Cloud Version) PUBLIC

2.4.2 Support Package 03 - Patch 01

For more information, see Modern UI How-Tos in the User Guide.

2.5 Support Package 04 (Cloud)

New Features Affecting All Apps

PUBLIC SAP Mobile Documents (Cloud Version)

Table 5: Terminology Changes

anonymous user guest

Edit Offline, Create Version Check Out, Check In

SAP Mobile Documents Desktop App

SAP Mobile Documents Web App

SAP Mobile Documents (Cloud Version) PUBLIC