Bulk Loading Cache Strategy

Bulk loads transfer large quantities of data into the Unwired Server cache database (CDB). Because of the demands this places on resources, special consideration needs to be given when using this strategy.

When Used

Bulk loads are typically used when:

Creating an initial data set of reference data for the device application. Bulk loads are ideal for data that does not change often.
The structure of EIS data changes and the application data structure needs to be normalized on the device.
Repairing a complete data set when corrupted on the device or on the CDB.

How Used

For each MBO, the developer selects the largest set of data that is applicable to most mobile users and designs the MBO to load data into the Unwired Server cache all at once. The developer then needs to define synchronization criteria for the MBO, so that synchronization parameters index into the cache to retrieve device-relevant data subsets. Good for data where the device is primarily driving change (work orders) or reference data that does not change often

Considerations

Preloads the cache up front and isolates specific device invocations from the enterprise application.
Large up-front cost of data that may never be used. Bulk loads are best performed when minimal amount of users are connected to the EIS server.