Deploying to SAP Mobile Server in a Cluster Fails

Explanation: When you deploy a package into a SAP Mobile Platform cluster, you must be connected to the SAP Mobile Server designated as the primary server in the cluster. If not, deployment fails and you see a message similar to following in the server logs:

YYYY-MM-DD HH:MM:SS.SSS WARN    MMS          Thread-466
[com.sybase.sup.server.SUPDomain] On Non primary servers, you could not
execute createDsyncDataZip()
java.lang.Exception: Current server is not primary, request rejected.

Solution: Set up a connection profile to the server that has become the primary, and deploy using that connection. See Creating a SAP Mobile Server Connection Profile in SAP Mobile WorkSpace - Mobile Business Object Development for how to create a new SAP Mobile Server connection profile.