Data Tier and Unwired Server on Separate Hosts

In this scenario, Unwired Server components share no host system resources with data tier components.

This scenario is suitable for a typical production system. It allows support for both:

Load balancing across multiple instances of Unwired Server resources
High availability (i.e., failover) of common data tier resources shared by multiple Unwired Server instances

Note:

This is the only scenario that supports deployment of clustered systems, which are required to provide failover support.

Load balancing can be supported by:

A front-end server application, such as Relay Server
Network hardware, such as a layer 4 switch
A Network Load Balancing cluster

When Unwired Server and data tier components are on separate hosts, they rely on network connections for some inter-process communication. The local network must be configured to allow all communication between Unwired Platform components.

Note:

If the local network is secured by an intrusion detection/prevention appliance (IPS or IDPS), or if the host of any Unwired Platform component is secured by host-based intrusion prevention software (HIPS), the security device must be configured to allow all network communication between Unwired Platform components.

Host system resources must be adequate to support all of the applications and services included in the Unwired Platform component. Disk resources must be adequate to support all of the databases managed by data tier servers.

To complete an installation in this scenario, you must complete the tasks:

Installing the Data Tier on each Unwired Platform data tier host
Installing the Unwired Server on each Unwired Server host

Note:

Unwired Server installation depends on a data tier installation. Data tier components must be installed first, before installing any Unwired Server components.

Shared Hosts in Failover Cluster

Sybase Unwired Platform supports a scenario in which Unwired Server components are colocated with data tier components, on hosts configured with Microsoft Cluster Service (or Failover Clustering).

This scenario is suitable for a production system that supports both load balancing for Unwired Server instances, and high availability of common data tier resources, with minimum hardware requirements — just two host systems. It is a variation of the "separate hosts" scenario described above.

In this scenario, the data tier and Unwired Server components are installed separately, on each host.

Data tier components are configured during installation to use a shared cluster storage resource to house the database files.
After data tier installations, the cluster is configured to define a managed cluster resource for each data tier server.
Unwired Server components are installed on each host, after managed cluster resources are defined.

In essence, data tier servers are managed by the high availability cluster, while colocated Unwired Servers are independent of the cluster.

Unwired Server and data tier components rely on network connections, because the managed cluster resource must be addressed as a distinct host, independent of any host in the cluster. The local network must be configured to allow all communication between Unwired Platform components.

Host system resources must be adequate to support all of the applications and services included in all Unwired Platform components. Disk resources must be adequate to support all of the databases managed by data tier servers.