In Chapter 6, “Managing Integrated Products,” include the following additional push-synchronization information.
Push synchronization is not supported on Java ME (Symbian/J2ME) devices, so ignore any references in the chapter.
[CR #431722] It is the nature of mobile computing, especially of offline applications, that client data gets out of sync with server data over time. The push sync feature attempts to close the gap, but cannot do so completely because of unreliable connectivity to the devices. Users should be aware of this, and sync regularly when they are online to ensure their data is updated.
On page 88, in the section “Working with push agents,” the documentation correctly states that as soon as a user subscribes to an application and syncs from the client, an agent is created for the application. However, this is new information:
If the Content Cache Interval is set to a value (such as minutes, hours, or days), the value is set in Agent Scheduling, and the agent will be in a Started state.
If the Content Cache Interval is left as “Real Time,” the agent will be in a Stopped state. The administrator must configure Agent Scheduling and then enable it.
For an example, see the “Setting up employeeSales for automated push” section in the Mobile Application Development Tutorial.
Table 5 provides additional information about push-sync operations on the BlackBerry offline client and the Mobile Web Studio Push Admin GUI.
BB offline client/ Push Admin GUI |
Function |
Operations |
Remarks |
---|---|---|---|
BlackBerry offline client |
AutoRefresh |
|
BlackBerry offline client retrieves applications that have been assigned to a profile. (In this case, the user does not want to see all mobile-enabled applications, only those assigned to the profile.) |
RefreshApps |
Overwrites push parameters from the BlackBerry UA client to the UA server |
The BlackBerry offline client value overwrites the UA server value, unless the Admin=Y flag is set on the subscription. |
|
Push Admin GUI |
Device | Synchronize |
Push-sync notification is sent to the device for a particular application, and for a particular profile (whether push is enabled or disabled, and whether there are any changes). Synchronization creates agents if the push is set to “Y” for the first time. |
To push data changes, or a newly created application, to a profile, the administrator can use the Device | Synchronize function in Mobile Web Studio. |
Execute |
When the application is push- enabled and if there are changes, then the sync process is initiated. No notification is generated if changes are not detected. |