Push Synchronization Applications

BlackBerry devices support sending push requests through HTTP. Sybase Unwired Platform supports push configuration and notification handling APIs for BlackBerry HTTP push. Clients receive device notifications when a data change is detected for any of the MBOs in the synchronization group to which they are subscribed.

Sybase Unwired Platform uses a messaging channel to send change notifications from the server to the client device. By default, change notification is disabled. You can enable the change notification of a synchronization group:

SynchronizationGroup sg = SUP101DB.getSynchronizationGroup("TCNEnabled");

if (!sg.getEnableSIS())
{
  sg.setEnableSIS(true);
  sg.setInterval(2); // 2 minutes
  sg.save();
  SUP101DB.synchronize("TCNEnabled");
}

When the server detects changes in an MBO affecting a client device, and the synchronization group of the MBO has change detection enabled, the server will send a notification to client device through messaging channel. By default, a background synchronization downloads the changes for that synchronization group. The application can implement the onSynchronize callback method to monitor this condition, and either allow or disallow background synchronization.

public int onSynchronize(ObjectList groups, SynchronizationContext context)
{
  int status = context.getStatus();
  if (status == SynchronizationStatus.STARTING_ON_NOTIFICATION)
  {
    // There is changes on the synchronization group
    if (busy)
    {
      return SynchronizationAction.CANCEL;
    }
    else
    {
      return SynchronizationAction.CONTINUE;
    }
  }

  // return CONTINUE for all other status
  return SynchronizationAction.CONTINUE;
}

HTTP Push Gateway
BlackBerry has an HTTP push feature for sending messages to occasionally connected devices. For Blackberry devices paired with BlackBerry Enterprise Server (BES), the HTTP push gateway contains an address that points to the HTTP listener of the BES server. The POST to the BES server has a query parameter that contains the device ID of the target devices (for example, 2100000a for an emulator). The BES server holds the message for a configurable amount of time, and delivers it to the device when the device becomes reachable.

Parent topic: Synchronization APIs