Data Cache: Difference between revisions
Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. == Data Cache Page == ''Understanding the "Data Cache" page in the SEM development Interfa..." |
(No difference)
|
Revision as of 11:32, 23 February 2011
'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.
Data Cache Page
Understanding the "Data Cache" page in the SEM development Interface
This section describes the features available to the SEM Developer for editing the 'Data Cache' page in a display contained in a SEM library.
Checkbox: Enable the data cache
Select this checkbox to enable data caching. Data caching will then take place automatically so that when the SEM display window is started, the data cached from the previous use of the window will automatically be loaded before the agent responds with the latest up to date information.
This can be useful for displays that require a lot of data to be returned from the agent and makes the display window feel more responsive.
Days to keep data in cache
If the display window is infrequently used by a particular user, the cached data can become so out of date that it should not be used. This field sets the number of days in which the data will be used. Older than this and the data will be discarded.
Startup fields which define the return data
The fields shown in this pane are dependent on the definition of the startup window for this display. The above example is taken from the SAcM Enterprise Accounts display.
When the startup window is used to filter information that is being returned from the target agent, then the information returned and therefore the data that is cached is also dependent on these fields. For each combination of filter fields a different data cache is retained for the different values entered in those fields. Therefore, when the data cache is displayed, the correct information relative to the filter fields is also used.
Selecting the checkboxes for these Startup fields determines which fields are filter arguments passed to the agent, and therefore which fields have a bearing on the data to be shown from the cache.
