Administrator

Glossary: MBO Runtime

Defines terms for all SAP Mobile Platform components.

  • 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 Platform Server.
  • 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 Management Cockpit administration roles to avoid having to authenticate to SAP Mobile Platform in addition to SAP Mobile Platform 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 Management Cockpit.
  • application activation From the SAP Mobile Platform standpoint, all activities that allow a user, either identified or anonymous, 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 server node An SAP Mobile Platform 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 Management Cockpit to allow administration of the complete cluster. See scale-out node.
  • 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 Platform Server cache, or just cache. See data tier.
  • cache group Defined in Management Cockpit, 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 Management Cockpit by defining a partition key, which is an argument that the operation uses to load data from the enterprise information system (EIS) into the cache.
  • 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. You can use the enhanced version of this product (CTS+) to transport non-ABAP objects, such as SAP Mobile Platform development artifacts.
  • 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.
  • configuration cache Distributed memory configuration used by all cluster members.
  • connection profile In Management Cockpit, the configuration details and credentials required to connect to an EIS.
  • context variable In the Management Cockpit 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.
  • custom control A special type of UIControl subclass that is defined in the extensibility metadata. Manage custom controls within the client code.
  • data change notification (DCN) Allows an EIS to synchronize its data with the cache database through a push event.
  • 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 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 Management Cockpit, the persistent-storage location for the data that a mobile business object (MBO) can access.
  • data tier Includes SAP Mobile Platform Server data such as the cache database (CDB), cluster, monitoring, and messaging databases.
  • 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.

    There is a one-to-one mapping between Management Cockpit 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 Management Cockpit, 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 Platform 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 Platform 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 Platform Server.
  • deployment mode The mode in which a mobile application project or mobile deployment package is deployed to the target SAP Mobile Platform Server.
  • deployment profile A named instance of predefined server connections and role mappings that allows developers to automate deployment of multiple packages in Management Cockpit to SAP Mobile Platform 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 Management Cockpit 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 Management Cockpit. You can deploy the contents of a development package on an instance of SAP Mobile Platform Server.
  • 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.
  • 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.
  • 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 Management Cockpit, 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 Mobile Add-on that is installed on top of DOE to provide integration with SAP Mobile Platform.
  • generic business object A data entity that is independent of the underlying model.
  • hybrid-app packages Deployed to SAP Mobile Platform 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.
  • 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.
  • load group A set of MBOs that load into the SAP Mobile Platform 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 Containers and Open Data Protocol client applications.
  • local business object Defined in Management Cockpit, objects that are used as local a data store on a device. Local business objects are not bound to back-end 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 Platform Server.
  • Management Cockpit In SAP Mobile Platform, a Web-based interface that allows you to administer your installed SAP products.
  • Management Cockpit Service Provides runtime services to manage, monitor, and control distributed SAP Mobile Platform resources. The service must be running for SAP Mobile Platform to run. Previously called Sybase® Unified Agent service.
  • 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. SAP Mobile Platform 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 Management Cockpit, and during administration in Management Cockpit.

    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 Management Cockpit. DCN hybrid-app messages indicate their target users, so do not require distribution rules.
    • multiplexer Used by SAP Mobile Platform 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 Management Cockpit.
  • 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 Platform 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
  • MBO Runtime Allows you to deploy and manage MBO-based applications in SAP Mobile Platform 3.0.
  • MBO Toolkit Allows you to maintain backward compatibility with your SAP Mobile Platform 2.3 MBO applications. To use MBO Toolkit, MBO Runtime must also be installed.
  • 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 on which it depends), 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 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.
  • 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 Management Cockpit for an MBO and used to filter data that is downloaded to the device.
  • 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.
  • operation See MBO operation.
  • package A named container for one or more MBOs. On SAP Mobile Platform Server, a package contains MBOs that have been deployed to this instance of the server.
  • palette In Management Cockpit, 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 A 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 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 MBO development phase, and avoiding device application problems later, for example, device application synchronization or data refresh errors.
  • 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.
  • relationship See MBO relationship.
  • Relay Server See SAP Hosted Relay Server.
  • Relay Server Outbound Enabler (RSOE) An application that manages communication between SAP Mobile Platform 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.
  • 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 Platform 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 Platform Server (and thereby override the domain-wide settings in the security configuration).
  • 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 Mobile Platform A development and administrative platform that enables you to mobilize your enterprise. With SAP Mobile Platform, you can develop mobile applications, connect to structured and unstructured data sources, and deploy mobile applications to SAP Mobile Platform Server, which manages messaging and data services between your data sources and your mobile devices.
  • SAP Mobile Platform Server The application server included with the SAP Mobile Platform product that manages mobile applications, back-end EIS synchronization, communication, security, transactions, and scheduling.
  • scheduled data refresh Data is updated in the cache database from a back end, based on a scheduled data refresh. Typically, data is retrieved from the back end (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").
  • 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.
  • software component version (SWCV) A shipment unit for design-time objects in the DOE repository.
  • synchronization group Defined in Management Cockpit, 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 Platform Server.
  • undeploy Remove a domain package from an SAP Mobile Platform 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
  • 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.