Choosing Installation Scenarios to Implement Your Landscape Design

Each SAP Mobile Platform installation scenario outlines a specific way to install and configure an SAP Mobile Platform system. Your landscape design determines the installation scenario you will implement.

• Single-Server Installation
  Single-server installations set up a complete SAP Mobile Platform system on a single server. This configuration is suitable for a low-volume production system where continuous uptime is not critical. With SAP Mobile SDK installed on the same system, a single-server installation provides a self-contained developer workstation.
• Simple Load-Balancing Cluster
  A simple load-balancing cluster installs SAP Mobile Platform Runtime components onto multiple servers that are configured to share the workload, with additional (optional) SAP Mobile Server nodes installed as scale-out nodes. With two SAP Mobile Server application server nodes, the system continues to operate if either application server node fails.
• Standard Microsoft Failover Cluster
  Installing two data tier nodes in a Microsoft Failover Cluster ensures that the system can continue to operate if the active data tier node fails. Adding this capability to the load-balancing cluster for SAP Mobile Server nodes ensures there is no single point of failure in the system.
• Microsoft Failover Cluster with Shared Hosts
  Placing one data tier and one SAP Mobile Server node, installed as an application server, on each of two physical servers, is a modification of the standard Microsoft Failover Cluster. This is the minimum hardware configuration that ensures there is no single point of failure in the system.