Data Refresh Triggers

Define data refresh through mobile business object (MBO) settings, programmatically through the data change notification (DCN) interface, or through Unwired Server settings.

Data refresh methods and triggers
Method Description
DCN (development) | Push Listener (administration) The enterprise information system (EIS) developer implements DCN using HTTP or HTTPS GET or POST methods. Depending on which is implemented, the administrator needs to configure the push listener synchronization gateway for the correct encrypted or unencrypted protocol chosen. The DCN can be initiated by a database trigger, stored procedure, or some other event to:
  • Notify Unwired Server that a particular MBO in the CDB needs to be refreshed.
  • Allow the EIS to invoke a particular MBO operation with a set of specified parameters.
Cache group The MBO developer defines any number of cache groups to which one or more MBOs are added based on data refresh requirements. An update policy applies to all MBOs within a cache group.
Cache update policies The MBO developer can add a cache update policy to create, update, or delete operations to control how any EIS affecting operation is applied to the CDB.
Load parameters The MBO developer can create an MBO that uses load parameters to:
  • Control data refresh for individual MBOs
  • Create CDB partitions for individual users based on parameter values.
  • Control synchronization if paired with a synchronization parameter.