Application Configuration Profile (ACP) – the package that holds extensibility-related and other metadata, and
additional resources.
admin user – a user with a defined admin security profile.
administrators – SAP Mobile Platform
users to which an administration role has been assigned.
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 Platform Server, the
runtime entity that can be directly correlated to a native or hybrid
application. The application definition on the server establishes the
relationship among packages used in the application, the user activation
method for the application, and other application-specific settings.
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 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:
- Copying the application to the device.
- Installing the application on the device.
- Configuring the application on the device.
- 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 Platform Server.
application user – the distinct set of identities (identified or anonymous)
that have ever been in contact with the system by utilizing the application.
In Management Cockpit, 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.
back end – a system that provides a datasource, such as a database of Web service.
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.
binding – represents the datasource associated with the given tile.
certificate – a digital security mechanism attached to an electronic message and used to
verify the identity of a specific user.
certificate provisioning – placing digital certificates on a device for user authentication.
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 resources – also known as resource bundles. Containers used by
applications to download dynamic configurations, styles, or content from
SAP Mobile Platform Server.
command line interface (CLI) – the standard term for a command line tool or utility.
connection – configuration details and credentials required to connect to
a database, Web service, or other back end.
connection pool – a cache of back-end system connections maintained by
SAP Mobile Platform Server, so that the
connections can be reused when SAP Mobile Platform Server receives future requests for data. Or a
collection of proxy connections pooled for their respective back ends, such
as SAP Gateway
Consumer Portal – a reference Web application. The Consumer Portal allows consumers to manage
their mobile-banking accounts, with multiple payment instruments, such as
bank accounts, credit cards, stored value accounts (SVA) and Offline SVAs.
They can pay bills, send money to family or friends, and add to
airtime.
custom control – a special type of UIControl subclass defined in the extensibility metadata.
Manage custom controls within the client code.
data manipulation language (DML) – a group of computer languages used to retrieve, insert,
delete, and update data in a database.
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 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 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 Platform Server instance. SAP Mobile Platform Server can then make these units
accessible to users via a client application that is installed on a mobile
device.
device application – a software application that runs on a mobile device. See
mobile application.
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.
end-to-end tracing (E2E tracing) – supportability feature that allows developers to add
specified libraries and code to applications to enable tracing during
runtime.
export – the SAP Mobile Platform administrator can export mobile objects,
then import them to another server on the network.
features – groups of individual bundles (also known as Eclipse plugins) and static
resources that together form an installable function or set of
functions.
generic business object – a data entity that is independent of the underlying model.
Google Cloud Messaging (GCM) – a free service for sending messages to Android devices.
GCM requires an API Key to allow SAP Mobile Platform Server to send push notifications over GCM.
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.
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.
JCA – J2EE Connector Architecture. A Java-based solution for connecting an
application server with a back end.
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 Platform Server runtime components. See truststore.
layout configuration file – an XML file that holds the extensibility descriptors (or metadata).
Lightweight Directory Access Protocol (LDAP) – an application protocol for accessing, querying, and
modifying data in distributed directory services.
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 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, as well as overall system health. It
can be used for system diagnostics or for troubleshooting.
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.
offline demo data – collection of XML files used for demonstration purposes, without online
connection. The files are created based on real data feeds and must adhere
to naming rules.
onboarding – the enterprise-level activation of an authentic device, a
user, and an application entity as a combination, in SAP Mobile Platform Server.
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.
Partner Portal – a reference Web application. Agents who sell to consumers on behalf of a
system provider can use the Partner Portal to manage existing consumers, add
to airtime, validate pending consumer registrations, settle commissions, and
run reports.
personalization key – allows a mobile device user to specify attribute values
that are used as parameters for selecting data from a data source and to
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.
persistent identifier (PID) – a unique identity for a dictionary that contains configuration properties
for a managed service in the Open Services Gateway initiative (OSGi) modular
architecture.
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 Platform 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 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.
push synchronization – the server-initiated process of downloading data from
SAP Mobile Platform 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).
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.
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.
SAP – one of the back-end 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.
Management Cockpit – in SAP Mobile Platform, a Web-based interface that allows you to
administer your installed SAP products.
SAP Messaging Service – the synchronization service that facilitates communication
with device client applications.
SAP Mobile Platform Server – the application server included with the SAP Mobile Platform product that manages mobile
applications, back-end 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.
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.
security profile – part of the application user and administration user
security. A security profile determines the scope of user identity,
authentication and authorization checks, and can be assigned by the platform
administrator in SAP Mobile Platform. A
security profile contains a set of configured security providers (for
example, LDAP) to which authentication, authorization, and attribution are
delegated. It also can include 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 Platform SDK and a back-end EIS.
Simple Object Access Protocol (SOAP) – an XML-based protocol that enables applications to exchange
information over HTTP. SOAP is used when SAP Mobile Platform Server communicates with a Web service.
single sign-on (SSO) – a credential-based authentication mechanism.
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.
subscription – defines how data is transferred between a user's mobile
device and SAP Mobile Platform 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.
synchronize – the process by which data consistency and population is
achieved between remote disconnected clients and SAP Mobile Platform Server.
tile – UI elements or screens, which can be primitive or can embed further tiles.
In theory, you can nest tiles to an unlimited level.
tile container – the container view controller in iOS terms. Container view controllers group
tiles that work together.
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.
user –
SAP Mobile Platform displays the
mobile-device users who are registered with the server.
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.
workspace – in Eclipse, the directory on your local machine where
Eclipse stores the projects that you create.