Glossary: SAP Mobile Platform

Defines terms for all SAP® Mobile Platform components.

4GL – Short for 4th generation language, this is a term generally applied to development methods and tools that provide graphical interfaces for software development, reducing or eliminating the need to work directly with source code to implement business logic.
activation code – a method of identifying the user in the runtime via code, rather than by authenticated identity. This is considered a manual connection registration method. During the connection registration a connection might be activated when using an activation code.
administration perspective – or administration console. The SAP Mobile Platform administrative perspective is the Flash-based Web application for managing SAP Mobile Server. See SAP Mobile Platform.
administrators – SAP Mobile Platform users to which an administration role has been assigned. A user with the "SAP Mobile Platform Administrator" role is called a "platform administrator" and a user with the "SAP Mobile Platform Domain Administrator" role is called a "domain administrator." These administration roles must also be assigned SAP Control Center administration roles to avoid having to authenticate to SAP Mobile Platform in addition to SAP Mobile Server:
  • a domain administrator requires only the "sccUserRole" role.
  • a platform administrator requires both the "sccAdminRole" and "sccUserRole" roles.
Adobe Flash Player – a third party software tool required to run SAP Control Center.
Afaria® – an enterprise-grade, highly scalable device management solution with advanced capabilities to ensure that mobile data and devices are up-to-date, reliable, and secure. Afaria is a separately licensed product that can extend the SAP Mobile Platform in a mobile enterprise. Afaria includes a server (Afaria Server), a database (Afaria Database), an administration tool (Afaria Administrator), and other runtime components, depending on the license you purchase.
Agentry application hierarchy – The order and structure of, and the relationship between, the various definition types that comprise any Agentry application project.
Agentry application project – The definitions and references to synchronization logic that comprise the encapsulated business logic of an Agentry mobile application.
Agentry Client – The executable client software within the Agentry paradigm that consumes and processes the business logic defined in the Agentry application project, and presents that business logic and behavior to the mobile user.
Agentry Client Branding SDK – A toolset provided to allow partners and customers developing Agentry applications to brand those applications for packaging and delivery.
Agentry Editor – The primary development tool for an Agentry application project, built as a plug-in to the Eclipse IDE and presenting a 4GL development interface to define and modify business logic and rules within the application project.
Agentry Server – The component of the Agentry paradigm that interfaces between the Agentry Clients and the back end system or systems with which the mobile application synchronizes data. The Agentry Server is also responsible for serving up the business logic of the mobile application to the Agentry Clients during the initial implementation and in subsequent updates to the application logic.
Agentry Test Environment (ATE) – An Agentry Client wrapped in numerous testing, debugging and monitoring tools, used primarily by developers to mimic various client device platforms during the development life cycle of a mobile application.
anonymous user – a user type who can access the system without identification.
Apple Push Notification Service (APNS) – service provided by Apple for devices running the iOS operating system. The APNS acts as a mediary to push notifications from the provider to the device rather than have the application operate as an active listener for those notifications.
application – in SAP Mobile Server, the runtime entity that can be directly correlated to a native or Hybrid App. The application definition on the server establishes the relationship among packages used in the application, the domain to which the application is deployed, the user activation method for the application, and other application-specific settings. See client application and mobile application.
application activation – from the SAP Mobile Platform standpoint, all activities that allow an identified or anonymous user to be paired with an application and its connections and customizations. Or, all activities that allow an application to be activated. An activated application creates an instance that is known by SAP Mobile Platform.

From the application user standpoint, application activation is the automated series of events by which a user, without administrative intervention, can start consuming services.

application connection – a unique connection to the application on a device.
application connection template – a template for application connections that includes application settings, security configuration, domain details, and so forth.
Application Data – The data that is the business logic served up by the Agentry Server to the Agentry Client during a transmit; term used to distinguish between this data and Production Data.
application ID – the unique ID that identifies an application (automatic or manual)
application instance – represents a client application on a single device.
application node – in SAP Mobile Platform, a registered application with a unique ID. The main entity that defines the behavior of device and back end interactions.
application provisioning – placing a client application on a device which includes:
  1. Copying the application to the device.
  2. Installing the application on the device.
  3. Configuring the application on the device.
  4. Securing the device.
application registration – configuring an application to work with SAP Mobile Platform. Registration requires a unique identity that defines the properties for the device and back-end interaction with SAP Mobile Server.
application server node – an SAP Mobile Server configuration that can process all of the application types that are supported by SAP Mobile Platform. An application server node includes the installation of SAP Control Center to allow administration of the complete cluster. See scale-out node.
application user – the distinct set of identities (identified or anonymous) that have ever been in contact with the system by utilizing the application. In SAP Control Center, an application user is the distinct list of names under which a user has been identified to the system. An application user may also be a user (identified or anonymous) that has been associated with an application ID.
artifacts – client-side or automatically generated files; for example: .xml, .cs, .java, .cab files.
availability – indicates that a resource is accessible and responsive.
binary large object (BLOB) – a collection of binary data stored as a single entity in a database management system. A BLOB may be text, images, audio, or video.
Business Application Programming Interface (BAPI) – a set of interfaces to object-oriented programming methods that enable a programmer to integrate third-party software into the proprietary R/3 product from SAP®. For specific business tasks such as uploading transactional data, BAPIs are implemented and stored in the R/3 system as remote function call (RFC) modules.

(DOE) refers to a BAPI "wrapper" that contains the parameters required to synchronize the device data and the SAP back-end data.

cache database (CDB) – stores runtime metadata (for SAP Mobile Platform components) and cache data (for MBOs). The CDB is also referred to as the SAP Mobile Server cache, or just cache.See data tier.
cache group – defined in SAP Mobile WorkSpace, a group of MBOs to which the same cache refresh policy is applied to their virtual tables (cache) in the cache database
cache partitions – partitioning the cache divides it into segments that can be refreshed individually, which gives better system performance than refreshing the entire cache. Define cache partitions in SAP Mobile WorkSpace by defining a partition key, which is a load argument used by the operation to load data into the cache from the enterprise information system (EIS).
Change and Transport System (CTS) – SAP Change and Transport System for Advanced Business Application Programming (ABAP). CTS enables administrators to distribute artifacts and automate deployment to different target systems that are connected through transport routes. The enhanced version of this product (CTS+) can be used for transporting non-ABAP objects such as SAP Mobile Platform development artifacts.
client application – in SAP Mobile Platform, the software that runs on a smart phone, tablet computer, or other mobile device. See mobile application.
client device – General term used to describe the device upon which the Agentry Client is installed and running; can apply to any of the devices to which the Agentry Client can be installed, including PCs, laptops, tablets, and smart phones.
client object API – described in Developer Guide: BlackBerry Object API Applications,Developer Guide: iOS Object API Applications, and Developer Guide: Windows and Windows Mobile Object API Applications.
cluster – also known as a server farm. Typically, clusters are set up as either runtime server clusters or database clusters (also known as a data tier). Clustering is a method of setting up redundant SAP Mobile Platform components on your network to design a highly scalable and available system architecture.
cluster database – a data tier component that holds information pertaining to all SAP Mobile Platform server nodes. Other databases in the SAP Mobile Platform data tier includes the cache, messaging, and monitoring databases.
command line interface (CLI) – the standard term for a command line tool or utility.
configuration cache – distributed memory configuration used by all cluster members.
connection – configuration details and credentials required to connect to a database, Web service, or other EIS.
connection pool – a cache of enterprise information system (EIS) connections maintained by SAP Mobile Server, so that the connections can be reused when SAP Mobile Server receives future requests for data. Or a collection of proxy connections pooled for their respective back ends, such as SAP Gateway
connection profile – in SAP Mobile WorkSpace, the configuration details and credentials required to connect to an EIS.
consolidated data store (CDS) – the SAP Data Orchestration Engine (DOE) middleware component where data is consolidated by the DOE.
context variable – in the SAP Mobile WorkSpace Hybrid App Designer, context variables are automatically created when a developer adds references to an MBO in a mobile application. One table context variable is created for each MBO attribute. These variables allow mobile application developers to specify form fields or operation arguments to use the dynamic value of a selected record of an MBO during runtime.
data change notification (DCN) – allows an EIS to synchronize its data with the cache database through a push event.
data manipulation language (DML) – a group of computer languages used to retrieve, insert, delete, and update data in a database.
Data Orchestration Engine (DOE) – the SAP component that supports data exchange between SAP back-end systems and mobile devices.
Data Orchestration Engine Connector (DOE-C) – a component that connects applications running on SAP Mobile Platform with the DOE.
data points – using performance harnesses and measuring KPIs, specific points defined to take and report measurements. Data points are required to implement end-to-end tracing features.
data refresh – synchronizes data between the cache database and a back-end EIS so that data in the cache is updated. See scheduled data refresh.
datasource – in SAP Mobile WorkSpace, the persistent-storage location for the data that a mobile business object (MBO) can access.
data synchronization – the process of establishing consistency among data from a source to a target data storage and vice versa, and the continuous harmonization of the data over time.
data tier – includes SAP Mobile Server data such as the cache database (CDB), cluster, monitoring, and messaging databases.
data vault – a secure store across the platform that is provided by an SAP Mobile Platform client.
Definition – A finite component of an Agentry application project, encapsulating a general functional type within an application, and that exists within the Agentry application hierarchy and may have both a parent definition and one or more child definition types, as well as attributes that comprise its makeup.
demilitarized zone (DMZ) – also known as a perimeter network. The DMZ adds a layer of security to the local area network (LAN), where computers run behind a firewall. Hosts running in the DMZ cannot send requests directly to hosts running in the LAN.
deploy – uploading a deployment archive or deployment unit to an SAP Mobile Server instance. SAP Mobile Server can then make these units accessible to users via a client application that is installed on a mobile device.

There is a one-to-one mapping between an SAP Mobile WorkSpace project and a server package. Therefore, all MBOs that you deploy from one project to the same server are deployed to the same server package.

deployment archive – in SAP Mobile WorkSpace, created when a developer creates a package profile and executes the build operation. Building creates an archive that contains both a deployment unit and a corresponding descriptor file. A deployment archive can be delivered to an administrator for deployment to a production version of SAP Mobile Server.
deployment descriptor – an XML file that contains role-mapping and domain-connection information, and describes how to deploy a deployment unit to SAP Mobile Server. You can deliver a deployment descriptor and a deployment unit—jointly called a deployment archive—to an administrator for deployment to a production version of SAP Mobile Server.
deployment mode – the mode in which a mobile application project or mobile deployment package is deployed to the target SAP Mobile Server.
deployment profile – a named instance of predefined server connections and role mappings that allows developers to automate deployment of multiple packages from SAP Mobile WorkSpace to SAP Mobile Server. Role mappings and connection mappings are transferred from the deployment profile to the deployment unit and the deployment descriptor.
deployment unit – the output generated by the SAP Mobile WorkSpace build process. It enables a mobile application to be installed and used in a preproduction or production environment. A deployment unit allows deployment of all required objects, logical roles, personalization keys, and server connection information together, without access to the development project. You can deliver a deployment unit and a deployment descriptor—jointly called a deployment archive—to an administrator for deployment.
development package – a collection of MBOs that you create in SAP Mobile WorkSpace. You can deploy the contents of a development package on an instance of SAP Mobile Server.
device application – a software application that runs on a mobile device. See mobile application.
device notification – received by replication synchronization clients when a data change is detected for any of the MBOs in the synchronization group to which they are subscribed. Both the change detection interval of the synchronization group and the notification threshold of the subscription determine how often replication clients receive device notifications. Administrators can use subscription templates to specify the notification threshold for a particular synchronization group.
device provisioning – making an out-of-the box corporate device or bring your own device (BYOD) secure and ready for synchronization.
device user – the user identity tied to a device.
domain administrator – a user to which the platform administrator assigns domain administration privileges for one or more domain partitions. The domain administrator has a restricted view in SAP Mobile Platform; only features and domains they can manage are visible.
domains – provide a logical partitioning of a hosting organization's environment, so that the organization achieves increased flexibility and granularity of control in multi tenant environments. By default, the SAP Mobile Platform installer creates a single domain named "default." However, the platform administrator can also add more domains as required.
enterprise information system (EIS) – a back-end system, such as a database.
end-to-end tracing (E2E tracing) – supportability feature that allows developers to add specified libraries and code to applications to enable tracing during runtime.
Enterprise Explorer – in SAP Mobile WorkSpace, allows you to define data sources and view their metadata (schema objects in case of database, BAPIs for SAP, and so on).
entity set definition for mobile applications (ESDMA) – contains the external metadata definition of a software component version (SWCV) you can use to construct a client that can interact with the DOE.
ESDMA converter – the SAP Mobile Platform utility that converts an ESDMA bundle into an SAP Mobile Platform package that can be deployed to one or more instances of SAP Mobile Platform.
export – the SAP Mobile Platform administrator can export mobile objects, then import them to another server on the network.
Gateway for NetWeaver Mobile – add-on that is installed on top of DOE to provide integration with SAP Mobile Platform.
Google Cloud Messaging (GCM) – a free service for sending messages to Android devices. GCM requires an API Key to allow SAP Mobile Server to send push notifications over GCM.
hostabilitySee multitenancy.
Hybrid App packages – deployed to SAP Mobile Server, and can be deployed to mobile devices, via the SAP Mobile Platform administrative perspective in SAP Mobile Platform. Hybrid App packages use the messaging synchronization model.
Initial Transmit – The term applied to the first transmit performed by an Agentry Client which, at the onset of the transmit, contains no business logic.
integrated development environment (IDE) – a set of programs that provide comprehensive facilities for software development. An IDE is typically associated with a specific programming language and provides features for authoring, modifying, compiling, deploying and debugging software from a single user interface.
Introscope – a third-party tool that can be integrated into a system landscape to quickly isolate and resolve performance issues wherever they arise in each stage of the application life cycle.
Java development environment (JDE) – IDE specific to the Java programming language that is used in SAP Mobile Platform to create and test BlackBerry Java applications.
key performance indicator (KPI) – used by SAP Mobile Platform monitoring. KPIs are monitoring metrics that are made up for an object, using counters, activities, and time which jointly for the parameters that show the health of the system. KPIs can use current data or historical data.
keystore – the location in which encryption keys, digital certificates, and other credentials in either encrypted or unencrypted keystore file types are stored for SAP Mobile Server runtime components. See truststore.
Lightweight Directory Access Protocol (LDAP) – an application protocol for accessing, querying, and modifying data in distributed directory services.
load group – a set of MBOs that load into the SAP Mobile Server cache from the EIS from the same shared read operation.
LoadRunner – a performance testing tool developed by Hewlett Packard (HP). SAP Mobile Platform provides an extension which integrates with LoadRunner to perform load testing for Hybrid Web Container and Open Data Protocol client applications.
local business object – defined in SAP Mobile WorkSpace, objects that are used as local a data store on a device. Local business objects are not bound to EIS data sources, so cannot be synchronized.
logical role – defined in MBOs, and mapped to physical roles when the deployment unit that contains the MBOs are deployed to SAP Mobile Server.
matching rule – a rule in a Hybrid App that specifies a part of a DCN or e-mail message and an expression to evaluate the text. A match triggers a server-initiated screen flow with an instance of the associated MBO. The SAP Mobile Server can be used for further processing (for example, to send a message to devices). You can configure matching rules both during Hybrid App development in SAP Mobile WorkSpace, and during administration in SAP Control Center.

These additional terms are associated with matching rules:

extraction rule – processes the value returned by a matching rule on a notification message, and constructs a message to be delivered to devices.
distribution rule – specifies devices to send extracted Hybrid App messages to. Configure distribution rules for notification mailboxes in SAP Control Center. DCN Hybrid App messages indicate their target users, so do not require distribution rules.
multiplexer – used by the SAP Mobile Server to retrieve Hybrid App notification messages from an inbox in a specified e-mail server. See notification mailbox.
notification mailbox – uses a listener to scan incoming e-mail messages delivered to an inbox in a specified e-mail server. When the listener identifies an e-mail message that matches the rules specified by the administrator, it sends the message as a Hybrid App to the device that matches the rule. Configure notification mailboxes in SAP Control Center.
MBO attribute – a field that can hold data. You can map an MBO attribute to a result field in a back-end data source; for example, a result field in a database table.
MBO binding – links MBO attributes and operations to a physical data source through a connection profile.
MBO composite object graph – (composite graph) refers to a group of entities (MBOs) in a composite relationship. Entities in a composite relationship are owned by their composite parents such that each entity in a graph has at most one composite parent. Entities that are not part of a composite relationship are treated by SAP Mobile Server as a graph consisting of a single root node.
MBO composite operation – (composite operation) refers to a create, update, or delete operation defined on the root MBO of a composite graph that accepts the entire composite graph as input.
MBO operation – can be invoked from a client application to perform a task; for example, create, delete, or update data in the EIS.
MBO relationship – analogous to links created by foreign keys in a relational database. For example, the account MBO has a field called owner_ID that maps to the ID field in the owner MBO.
Define MBO relationships to facilitate:
  • Data synchronization
  • EIS data-refresh policy
message-based synchronization – a synchronization method where data is delivered asynchronously using a secure, reliable messaging protocol. This method provides fine-grained synchronization (synchronization is provided at the data level—each process communicates only with the process it depends on), and it is therefore assumed that the device is always connected and available. See synchronization.
messaging database – allows in-flight messages to be stored until they can be delivered. This database is used in a messaging-based synchronization environment. The messaging database is part of the SAP Mobile Platform data tier, along with the cache, cluster, and monitoring databases.
Messaging framework – the messaging functionality provided by the SAP DOE Connector to connect the SAP DOE with devices.
mobile application – (mobile app) is a software application designed to run on smart phones, tablet computers and other mobile devices. For Agentry, a general term used to refer to the mobile application built in Agentry and generally used to make the fine distinction between the Agentry Client executable itself, and the business logic which it is processing and presenting to the user; in essence this business logic is the mobile application.
Mobile Application Diagram – the graphical interface for creating and editing MBOs. By dragging and dropping a datasource onto the Mobile Application Diagram, you can create a mobile business object and generate its attribute mappings automatically.
Mobile Application Project – a collection of MBOs and client-side, design-time artifacts that make up a mobile application.
mobile business object (MBO) – the fundamental unit of data exchange in SAP Mobile Platform. An MBO roughly corresponds to a data set from a back-end datasource. The data can come from a database query, a Web service operation, or SAP. An MBO contains both concrete implementation-level details and abstract interface-level details. At the implementation level, an MBO contains read-only result fields that contain metadata about the data in the implementation, and parameters that are passed to the back-end data source. At the interface level, an MBO contains attributes that map to result fields, which correspond to client properties. An MBO may have operations, which can also contain parameters that map to arguments, and that determine the manner in which the client passes information to the EIS.

You can define relationships between MBOs, and link attributes and parameters in one MBO to attributes and parameters in another MBO.

Mobile data model – shows the relationship between back-end enterprise data and the data on a mobile device.
monitoring – an SAP Mobile Platform feature that allows administrators to identify areas of weakness or periods of high activity in a particular area. It can be used for system diagnostic or for troubleshooting. Monitored operations include replication synchronization, messaging synchronization, messaging queue, data change notification, device notification, package, user, and cache activity.
monitoring database – a database that exclusively stores data related to replication and messaging synchronization, queues status, users, data change notifications, and device notifications activities. By default, the monitoring database runs in the same data tier as the cache database, messaging database, and cluster database.
monitoring profiles – specify a monitoring schedule for a particular group of packages. These profiles let administrators collect granular data on which to base domain maintenance and configuration decisions.
multitenancy – the ability to host multiple tenants in one unwired cluster. Also known as hostability. See domains.
node – a host or server computer upon which one or more runtime components have been installed.
object query – defined in SAP Mobile WorkSpace for an MBO and used to filter data that is downloaded to the device.
OData for SAP – provides SAP Extensions to the OData protocol that enables users to build user interfaces for accessing the data published via OData. The interfaces require human-readable, language-dependent labels for all properties and free-text search within collections of similar entities and across (OpenSearch).
OData metadata document – describe the entity data model (EDM) for a given service, which is the underlying abstract data model used by OData services to formalize the description of the resources it exposes.
OData Schema – defines the structure of the XML files in the OData service.
OData Service Document – a document that describes the location and capabilities of one or more collections.
Online Data Proxy (ODP) – a light-weight edition of the SAP Mobile Platform that provides a robust mobile infrastructure for enterprise IT organizations to securely roll out and manage the deployment of light-weight applications in a controlled and monitored approach.
Open Data (OData) Protocol – Web protocol for querying and updating data. It applies and builds upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications.
operation – See MBO operation.
package – a named container for one or more MBOs. On SAP Mobile Server, a package contains MBOs that have been deployed to this instance of the server.
palette – in SAP Mobile WorkSpace, the graphical interface view from which you can add MBOs, local business objects, structures, relationships, attributes, and operations to the Mobile Application Diagram.
parameter/argument – a value that is passed to an operation/method to determine the output. When you create an MBO, you can map MBO parameters/arguments to datasource arguments. For example, if a datasource looks up population based on a state abbreviation, the MBO gets the state from the user, then passes it (as a parameter/argument) to the data source to retrieve the information:
  • Synchronization parameters – synchronize a device application based on the value of the parameter.
  • Load arguments – perform a data refresh based on the value of the argument.
  • operation parameters – MBO operations contain parameter values that map to remote operation arguments and determine how the client passes information to the EIS.
persistence layer – the collection of database files, containing tables, that is available on the device through the Client Object API.
personalization key – allows a mobile device user to specify attribute values that are used as parameters for selecting data from a data source. Personalization keys are set at the package level and also provide operation parameter values. There are three type of personalization keys: transient, client, and server.

Personalization keys are most useful when they are used in multiple places within a mobile application, or in multiple mobile applications on the same server. Personalization keys may include attributes such as name, address, zip code, currency, location, customer list, and so forth.

perspective – an Eclipse term applied as a named tab that groups commonly used resources (such as servers) and UI views associated with those resources. In SAP Mobile Platform the Mobile Development perspective facilitates mobile application development.
physical role – a security provider group or role that is controls access to SAP Mobile Server resources.
Problems view – displays errors and warnings for the Mobile Application Project in Eclipse. This is a valuable source for collecting troubleshooting information and resolving issues during the MBO development phase, and avoiding device application problems later, for example, device application synchronization or data refresh errors.
Production Data – The data stored either in the back end system or on the client device that is synchronized between those two components during a transmit; term used to distinguish between this data and the Application Data.
provisioning – See application provisioning and device provisioning.
Publish – The term that describes the deployment and transformation of the business logic built and/or modified within the Agentry Editor to the Agentry Server with the intent of serving that business logic to Agentry Clients when they next synchronize.
pull synchronization – initiated by a remote client to synchronize the local database with the cache database. On Windows Mobile, pull synchronization is supported only in replication applications.
push synchronization – the server-initiated process of downloading data from SAP Mobile Server to a remote client, at defined intervals, or based upon the occurrence of an event.
queue – a list of pending activities, made up of in-flight messages for a messaging application. The server sends messages to specific destinations based on message order in the queue. The depth of the queue indicates how many messages are waiting to be delivered.
recovery – performing the activities required to bring a system to a usable/functional state after a failure (populating CDB, initializing client, and so on).
relationship – See MBO relationship.
Relay Server – See SAP Hosted Relay Server.
Relay Server Outbound Enabler (RSOE) – an application that manages communication between SAP Mobile Server and a relay server.
remote function call (RFC) – used to write applications that communicate with SAP R/3 applications and databases. An RFC is a standalone function. Developers use SAP tools to write the Advanced Business Application Programming (ABAP) code that implements the logic of a function, and then mark it as "remotely callable," which turns an ABAP function into an RFC.
replication-based synchronization – a synchronization method where a device pulls data from the SAP Mobile Server cache (the database where data from the EIS is replicated by SAP Mobile Server and cached to be sent to the device).
Representational State Transfer (REST) web services – a style of software architecture for distributed hypermedia systems, such as the World Wide Web.
resource – a unique SAP product component (such as a server) or a subcomponent.
restoration – returning a system to its prefailure state using one or more methods of recovery. Restoration does not guarantee a return to a usable state.
role – controls access to SAP Mobile Platform resources. See logical role mapping and physical role mapping
role mapping – maps a physical (server role) to a logical (SAP Mobile Platform role). Role mappings can be defined by developers, when they deploy an MBO package to a development SAP Mobile Server, or by platform or domain administrators when they assign a security configuration to a domain or deploy a package to a production SAP Mobile Server (and thereby override the domain-wide settings in the security configuration).
runtime server – an instance of SAP Mobile Server that is running. Typically, a reference to the runtime server implies a connection to it.
SAP – one of the EIS types that SAP Mobile Platform supports. SAP Business Suite applications (such as ERP, CRM, SRM, SCM, Industry Solutions and so on) consist of many technologies and components. Unless stated otherwise, the term “SAP” means a backend business application that is based on the SAP NetWeaver ABAP application server, for example ECC 6.0.
SAP Control Center – in SAP Mobile Platform, a Web-based interface that allows you to administer your installed SAP products.
SAP Hosted Relay Service – a Web-hosted Relay Server that enables you to test your SAP Mobile Platform development system.
SAP License Audit – a system measurement tool that analyzes usage data from SAP Mobile Platform and SAP applications deployed to the SAP Mobile Platform server.
SAP Messaging Service – the synchronization service that facilitates communication with device client applications.
SAP Mobile Platform – a development and administrative platform that enables you to mobilize your enterprise. With SAP Mobile Platform, you can develop MBOs in the SAP Mobile WorkSpace development environment, connect to structured and unstructured data sources, develop mobile applications, and deploy mobile business objects and applications to SAP Mobile Server, which manages messaging and data services between your data sources and your mobile devices.
SAP Mobile Platform X.X Service – provides runtime services to manage, monitor, and control distributed SAP resources. The service must be running for SAP Mobile Platform to run. Previously called Sybase® Unified Agent.
SAP Mobile WorkSpace – SAP Mobile Platform includes SAP Mobile WorkSpace, which is a development tool for creating mobile business objects and mobile applications.
SAP Mobile Server – the application server included with the SAP Mobile Platform product that manages mobile applications, back-end EIS synchronization, communication, security, transactions, and scheduling.
SAP NetWeaver Gateway – enables people-centric applications to consume SAP Business Suite data through popular devices and platforms in an easy and standards-based fashion.
SAP Passport – medium for transporting technical data in a request from the client to the server. Used for collecting trace and reporting information for chains of requests (RFC, HTTP) across system borders.
SAP Solution Manager – SAP standard platform for Application Life Cycle Management (ALM). SAP Solution Manager is a centralized, robust solution management toolset that facilitates technical support for distributed systems - with functionality that covers all key aspects of solution deployment, operation, and continuous improvement.
scale-out node – an SAP Mobile Server configuration that is specifically designed to allow the stateless request/response HTTP and synchronous message services over an open HTTP channel to be scaled horizontally, by adding more server nodes. See application server node.
schedule – the definition of a task (such as the collection of a set of statistics) and the time interval at which the task must execute in SAP Mobile Platform.
scheduled data refresh – data is updated in the cache database from a back-end EIS, based on a scheduled data refresh. Typically, data is retrieved from an EIS (for example, SAP) when a device user synchronizes. However, if an administrator wants the data to be preloaded for an MBO, he or she can schedule a data refresh so that data is saved locally in a cache. By preloading data with a scheduled refresh, the data is available in the information server when a user synchronizes data from a device. Scheduled data refresh requires an administrator to define a cache group as "scheduled" (as opposed to "on-demand").
security configuration – part of the application user and administration user security. A security configuration determines the scope of user identity, authentication and authorization checks, and can be assigned to one or more domains by the platform administrator in SAP Mobile Platform. A security configuration contains:
  • A set of configured security providers (for example, LDAP) to which authentication, authorization, and attribution are delegated.
  • Role mappings which can be specified at the domain or package level.
security profile – part of the SAP Mobile Server runtime component security. A security profile includes encryption metadata to capture certificate alias and the type of authentication used by server components. By using a security profile, the administrator creates a secured port for component communication.
security provider – a security provider and its repository holds information about the users, security roles, security policies, and credentials used to provide security services to SAP Mobile Platform. A security provider is part of a security configuration.
server connection – the connection between SAP Mobile WorkSpace and a back-end EIS.
server farm – the Relay Server designation for a cluster. See cluster.
server-initiated synchronization – also called targeted change notification (TCN). See push synchronization.
shared read operation – an EIS operation that returns data that the mobile application model maps into multiple MBOs. A shared read operation can load or refresh cached data for multiple MBOs.
Simple Object Access Protocol (SOAP) – an XML-based protocol that enables applications to exchange information over HTTP. SOAP is used when SAP Mobile Server communicates with a Web service.
single sign-on (SSO) – a credential-based authentication mechanism.
software component version (SWCV) – a shipment unit for design-time objects in the DOE repository.
solution – in Visual Studio, the high-level local workspace that contains the projects users create.
Solution Explorer – in Visual Studio, the pane that shows the active projects in a tree view.
Start Page – in Visual Studio, the first page that appears when you launch the application.
statistics – in SAP Mobile Platform, the information collected by the monitoring database to determine if your system is running as efficiently as possible. Statistics can be current or historical. Use current or historical data to determine system availability or performance. Performance statistics are known as key performance indicators (KPIs).
structured data – data in a table with columns and labels.
structure object – defined in SAP Mobile WorkSpace, structures hold complex datatypes, for example, a table input to a SAP operation.
subscription – defines how data is transferred between a user's mobile device and SAP Mobile Server. Subscriptions notify a device user of data changes, then these updates are pushed to the user's mobile device.
synchronization – synchronous data delivery using an upload/download pattern. For push-enabled clients, synchronization uses a "poke-pull" model, where a notification is pushed to the device (poke), and the device fetches the content (pull), and is assumed that the device is not always connected to the network and can operate in a disconnected mode and still be productive. For clients that are not push-enabled, the default synchronization model is pull. See messaging-based synchronization.
synchronization group – defined in SAP Mobile WorkSpace, a collection of MBOs that are synchronized simultaneously.
synchronization parameter – an MBO attribute that filters and synchronizes data between a mobile device and SAP Mobile Server.
synchronization phase – for replication-based synchronization packages, an upload event (from device to the SAP Mobile Server cache database) or a download event (from the cache database to the device).
synchronize – the process by which data consistency and population is achieved between remote disconnected clients and SAP Mobile Server. See data refresh
System Landscape Directory (SLD) – a central repository of system landscape information used to manage the software life cycle when SAP Mobile Platform is deployed as part of a larger SAP landscape.
Transmit – The term that describes the initiation of the synchronization process between the Agentry Client and Agentry Server.
truststore – the location in which certificate authority (CA) signing certificates are stored. See keystore.
undeploy – remove a domain package from an SAP Mobile Server.
user – SAP Mobile Platform displays the mobile-device users who are registered with the server.
view – a window in a perspective that displays information about one or more managed resources. Some views also let you interact with managed resources or with SAP Mobile Platform itself. For example, the Perspective Resources view lists all the resources managed by the current perspective. Other views allow you to configure alerts, view the topology of a replication environment, and graph performance statistics
Visual Studio – an integrated development environment product that you can use to develop device applications from generated SAP Mobile WorkSpace code.
Web Service Definition Language (WSDL) file – describes the Web service interface that allows clients to communicate with the Web service. When you create a Web service connection for a mobile business object, you enter the location of a WSDL file in the URL.
Welcome page – in Eclipse, the first set of pages that appear when you launch the application.
workspace – in Eclipse, the directory on your local machine where Eclipse stores the projects that you create.
WorkSpace Navigator – in Eclipse, the tree view that displays your mobile application projects.