Data Tier Administration

The data tier stores data used by SAP Mobile Server and the management console within the runtime landscape..

Four categories of data are persisted and managed in the data tier:

Cache data is stored only for applications that use synchronization and maintains records of device synchronization activity along with any cached data that may have been retrieved from the back end or pushed from the device.
The application package hosted in SAP Mobile Server communicates to the CDB through JDBC connection pools that are configured from the administration console. The MBO parameters and the relationships between MBOs define the shape of the cache tables. The internal implementation of these tables and the associated queries are not public and may change from release to release.
Cluster data maintains knowledge of and coordination between SAP Mobile Server clusters.
Monitoring and domain log data stores monitoring, tracking, and log messages for application activities.
For applications that employ messaging services, HTML5/JS Hybrid Apps, OData SDK and applications that use notification mechanisms, this data stores in-transit asynchronous messages until they are processed by the mobile application infrastructure layers. Message data is encrypted on the device and in transit.

If you need to change the password for the DBA user, see either Changing DBA Passwords for SQLAnywhere Databases in a Single Node Installation or Changing DBA Passwords for SQLAnywhere Databases in a Cluster Deployment in Security .

Note: All data tier nodes in a cluster must run with the same timezone setting; otherwise, data issues may occur.

Changing Database Ports for SQLAnywhere Databases
By default, ports are configured when you install the data tier. You can change values for any SQLAnywhere database deployed as part of the data tier.
Changing SQLAnywhere Database Server Startup Options
Change the database server startup options (thread counts and user options) to control the performance of a SQLAnywhere database server.
Using a Different Database Log Path
SAP recommends that you always use the default database log path location for SAP Mobile Platform databases. However, the database log path can be changed.
Setting Up an Existing Database for Monitoring
You can use any SQL database provided that the existing version number of that database matches the version required by SAP Mobile Platform.
Isolating the Monitoring and Domain Logging Databases from Cache and Messaging Databases
Install a new data tier node and configure the connection details to it.
Managing Connection Pools for SAP Mobile Server Connections
Connection pools are used by SAP Mobile Server to improve performance between the server and internal databases, which include the cache database, domain log database, messaging database, monitor database and sample database. These values are synchronized among all servers in the cluster when the primary server values change.
Rebuilding Platform Databases
Platform databases need to be rebuilt regularly. Without regular maintenance, the database log can grow to be large (several gigabytes in size), and performance could degrade.
Control Transaction Log Size
Control the size of transaction logs to prevent the log files from growing indefinitely.
Enterprise Data Consistency
MBOs are designed for use with data-intensive applications. Data consistency between the enterprise information system (EIS) and device applications is managed by way of the SAP Mobile Server cache. Managing the SAP Mobile Server cache ensures that enterprise data remains stable, available, and consistent across sources.