No Invalidate Cache Policy

Use the no invalidate cache policy when changes to the enterprise information system (EIS) do not need to be immediately passed to the consolidated database (CDB).

An operation that uses the no invalidate cache policy updates the EIS without invalidating the cache (CDB) for that instance of the MBO. Because cache is not invalidated, it may be different from the EIS. The cache is updated later, for example, based on the Cache Interval set on Unwired Server. The no invalidate cache policy eliminates nonessential CDB refreshes, which improves performance.

Note: Consolidated database, CDB, and cache all refer to the same thing, and the terms are used interchangeably.

This example uses the department table from the sampledb database, which is accessible from the "My Sample Database" connection profile.

To create a mobile business object (MBO), drag and drop the sampledb's "department" table onto the Mobile Application Diagram.
Set the update operation's cache update policy to No Invalidate Cache.
Deploy the MBO.
From Sybase Control Center (SCC) Administration Console, set the MBO's Cache Interval to one hour (or any value long enough to complete this test).

Sync the MBO from a test client or device application. The client, CDB, and EIS all have the same data:

dept_id      dept_name          dept_head_id
 ------- ------------------      ------------
   100           R & D              501
   200           Sales              902
   300           Finance           1293
   400          Marketing          1576
   500          Shipping            703

Call the MBO's update operation from the test client or device application to update this record:

dept_id=100, dept_name="SUPQA", dept_head_id=501

Sync the MBO. The EIS is modified:

dept_id      dept_name          dept_head_id
 ------- ------------------      ------------
   100           SUPQA              501
   200           Sales              902
   300           Finance           1293
   400          Marketing          1576
   500          Shipping            703

Based on the no invalidate policy associated with this operation, the CDB and client remain unchanged because the cache (CDB) remains valid:

dept_id      dept_name          dept_head_id
 ------- ------------------      ------------
   100           R & D              501
   200           Sales              902
   300           Finance           1293
   400          Marketing          1576
   500          Shipping            703