Setting a Cache Update Policy

A Cache Update Policy establishes criteria for updating the Unwired Server cache (also called the consolidate database, or CDB) for a given mobile business object (MBO) operation at a finer granularity than the primary read operation.

1. Access the Cache Update Policy tab from an existing operation by either double-clicking the operation or right-clicking and selecting Edit.
2. From the Properties view for the operation, or from the Cache Policy tab in the Operation edit dialog, select the cache update policy:

   Cache Update Policy	Description
   Apply operation result policy	Updates the CDB based on the returned result set of the called MBO operation.
   Apply operation parameters policy	Updates the CDB based on the operation’s parameters.
   Invalidate cache policy	Invalidates the CDB after the client calls the MBO operation, and requires a primary read operation to fetch all data again from the EIS. This is the default cache update policy.
   No invalidate cache policy	The CDB remains unchanged after the client calls the MBO operation.
   Chained read policy	Chain an alternate read operation to the MBO operation. The CDB is updated with the results returned by the alternate read operation. Choose an existing alternate read operation or create a new one by selecting Create. The alternate read operation is no different from an operation with an apply operation result cache update policy. Specifying an alternate read type operation enables chaining it to the MBO operations to get the desired result. The difference is that they are used only in conjunction with an MBO CUD operation.

• Apply Operation Result Policy
  Use the apply operation result policy to update the consolidated database (CDB) based on the returned result set of the called MBO operation.
• Apply Operation Parameters Policy
  Use the apply operation parameters policy to apply the values of an operation's parameters directly to the cache (CDB).
• Invalidate Cache Policy
  Use the invalidate cache policy only when other policies cannot be implemented or performance is not an important consideration.
• 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).
• Chained Read Policy
  Use the chained read policy to chain an alternate read operation to a create, update, or delete (CUD) operation. This updates the consolidated database (CDB) at a finer granularity than could be achieved with just the CUD operation.
• Alternate Read and Cache Update Policy Validation Rules
  Validation rules are enforced when you define an alternate read operation, set a cache update policy, and, in some cases, when you deploy the mobile business object (MBO) to Unwired Server.