Application Services (Mobiliser) Administration

SAP® Mobiliser is a fully integrated system with a back-end database, a set of application services as a middle-tier, and a front-end Web application for configuration, management and utilization. It is based on the Open Services Gateway initiative (OSGi) modular architecture.

• Basic Deployment Model
  Each Mobiliser host must meet the requirements for operating system and available disk space. In a development or test environment, you can install the system on a single physical host or virtual machine. In a production environment, deploy the system in a tiered manner to aid in administration, maintenance, and security.
• Standard Reverse Proxy Setup
  Any reverse proxy, such as Apache HTTPD, can accept incoming requests from the Internet in the DMZ and forward them to the Mobiliser core running on the application server tier.
• Mobiliser Setup
  In SAP Mobile Platform, you can enable optional Mobiliser server features. Once you enable these features, you must perform a few other tasks to ensure that Mobiliser functions properly.
• Mobiliser Universal User
  For Mobiliser to function properly, you must configure the universal user, using the required hashed credential, in the MOB_CUSTOMERS-CREDENTIALS table of the database.  The Web portal uses the universal user to authenticate the server. Therefore, you must set the password in hashed format in the database and in encrypted format in the portal configuration.
• Encryption and Keystore Configuration
  Encryption protects data within Mobiliser from unauthorized access using methods and a key or keys to encode plain text into a unreadable ciphertext. A key is required to decrypt the encrypted information and make it human-readable again. Keystores securely store and manage encryption keys.
• On-Device Charging Installation and Configuration
  On-device charging provides the capability to store sensitive data, such as stored-value account (SVA) balances, on a smartphone, which can interact with external systems through near-field communication.
• Performance Considerations
  A standalone SAP Mobile Platform Server includes a default configuration that is appropriate for workloads that do not require high transaction rates. A server that is running with the default settings is generally limited to development and proof-of-concept scenarios.
• Business Logic Configuration
  All configuration options, such as Preferences and ConfigAdmin, handle different scenarios for Mobiliser components.
• Security Fundamentals
  Use the information about each of the various mechanisms to learn about the required configuration that is necessary to harden your application.
• Default Mobiliser Web Portal Accounts
  When you enable Mobiliser in SAP Mobile Platform, Web portals are deployed for both administrative and consumer access. 
• Operations Dashboard Reference
  The Operations Dashboard provides system administrators with a high-level operational view of the enterprise mobility management system. The dashboard aggregates the information to give administrators an overview of the system, which aids in operational support. Administrators can track individual statistics for servers to monitor performance and general operational efficiency.
• Data Archiving, Retention and Deletion
  Currently, SAP Mobile Platform does not support data archiving, data retention, or deletion policies. It is therefore important that you use default database technology to implement any desired procedures and policies.
• Virus Protection
  Antivirus software is one of the most important tools for safeguarding vital information and personal data from the daily onslaught of viruses and worms.
• cron Expression Reference
  A cron expression is a string comprised of six or seven fields separated by white space. Fields can contain any allowed values, including special characters. Expressions can be as simple as * * * * ? * or as complex as 0/5 14,18,3-39,52 * ? JAN,MAR,SEP MON-FRI 2002-2010.