Analyzing Cache Status

Use

To ensure that the relevant Integration Engines have quick access to the contents of the Enterprise Services Repository at runtime, the information required is loaded into corresponding caches. Caches also contain the runtime-relevant data from the System Landscape Directory (SLD).

The cache is updated by different events:

Software component versions being imported to the Enterprise Services Repository
Objects being imported to the Enterprise Services Repository
Software component versions being updated in the Enterprise Services Repository

All runtime-relevant objects under the updated software component version are refreshed.
Release transfer
Change lists that contain runtime-relevant objects being activated in the Enterprise Services Repository

The runtime-relevant objects includes mapping objects, adapter metadata, and integration processes.

You can check which notification about released changes was transferred to the Integration Directory.

Procedure

In the menu bar, choose Environment Cache Status Overview .

The events that triggered a cache update are displayed in the Notifications of Released Change Lists frame.

Note
You can restrict the display to a particular notification period and author.

For each event, the status relating to the notification and the underlying change are displayed. Depending on the change that caused the cache update, the Identifier (GUID) column displays the identifier of the change list or the imported software component version.
To update the cache again, select the corresponding line and choose Repeat Cache Message .

Cache notifications can fail for a variety of reasons. If you have SAP Process Integration installed in your landscape, you can test the cache connectivity in the Runtime Workbench. For more information, see Testing Cache Connectivity . Also refer to SAP Note 780747.