Deploying to Unwired Server in a Cluster Fails

Problem: Deployment fails when you deploy a mobile business object (MBO) to Unwired Server in a cluster.

Explanation: When you deploy a package into a Sybase Unwired Platform cluster, you must be connected to the Unwired 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: On Non primary servers, you could not execute
createDsyncDataZip()
        at com.sybase.sup.server.cluster.ClusterUtils.createDsyncDataZip
(ClusterUtils.java:816)
        at com.sybase.sup.server.SUPDomain.incrementDomainVersion
(SUPDomain.java:779)
        at com.sybase.sup.admin.server.DomainAdminImpl.deployJar
(DomainAdminImpl.java:291)

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