Cluster Administration

The goal of cluster administration is to ensure that clusters and servers work smoothly, and scale over time. By default, the SAP Mobile Platform is installed as a one-node cluster. The one-node cluster is supported in development or test environments. Production deployments of SAP Mobile Platform are likely to require multiple nodes. Cluster administration is mostly a nonroutine administration task.

See Designing the Landscape in Landscape Design and Integration.

Cluster administration tasks
Task	Frequency	Accomplished by
Installing the cluster	One-time installation per cluster	SAP Mobile Platform installer
Setting up Relay Servers	One-time initial installation and configuration; occasionally adding servers to the cluster	Manual installation; manual setup using configuration files.
Suspending and resuming server nodes	On demand, as required	SAP Control Center
Setting cluster properties, including cache database settings, monitoring database setup, and so on	Once, or as cluster changes require	Manual configuration using files and .BAT scripts.
Tuning the server performance.	Post installation with infrequent tuning as required	SAP Control Center. See SAP Control Center for SAP Mobile Platform>Administer> SAP Mobile Server
Configuring the cluster to: Set the configuration cache properties Set the solution manager URL Set the replication ports and properties Set the messaging synchronization ports Set the amount of data that can be downloaded through an HTTP connection using the BlackBerry MDS Set the management ports for communication requests from SAP Control Center Configure the client dispatcher Set how applications handle DCN requests sent though an HTTP GET operation Create security profiles for secure communication Set up secure synchronization Tune server performance	Post installation configuration with infrequent tuning as required	See SAP Control Center for SAP Mobile Platform>Administer> Clusters
Setting cluster log file settings for SAP Mobile Server system components	Once, unless log data requirements change	See SAP Control Center for SAP Mobile Platform>Administer>Clusters
Administering the runtime databases	Routine to ensure that the database server is monitored and backed up, that there is sufficient space for SAP Mobile Platform metadata and cached data tables, and that performance is within acceptable limits (performance tuning)	Established processes and command line utilities. Consult with your database administrator.
Reviewing licensing information, including currently used licenses count	Occasional, or as device user registration and deregistration occurs	SAP Control Center.

Configuring Cluster Performance Properties
To optimize SAP Mobile Server performance across the cluster, configure performance properties.
Replication
Replication synchronization involves synchronization between SAP Mobile Server and a replication-based mobile device application. Synchronization keeps multiple variations of the data set used by a device application in coherence with one another by reconciling differences in each. Reconciling differences before writing updates back to the enterprise information server (EIS) maintains data integrity.
Messaging
Messaging is a synchronization method used to maintain data integrity on device client applications. It uses a JMS service to upload and download data changes to and from the SAP Mobile Server cache database. Messaging-based synchronization ports implement a strongly encrypted HTTP-based protocol using a proprietary method.
Cluster License Coordination
In a cluster, each server deployed to the environment must be licensed. Multiple servers cannot share a single license. However, all server nodes in the cluster can share device connection licenses.