Analyzing Cache Notifications
Use
To ensure that the relevant Integration Engines have quick access to the contents of the Integration Directory 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:
● Change lists being activated in the Integration Directory
● Change lists that contain runtime-relevant objects being activated in the Enterprise Services Repository
This includes mapping objects, adapter metadata, and integration processes.
The Cache Notifications enable you to display which notification about released changes was transferred to the relevant cache instances. You can also display whether the data was updated successfully or not. If a notification or cache update fails, you can determine the cause of the error.
The following can be cache instances:
● Integration Server
● Adapter Engine
● Business Systems
Procedure
...
1. In the menu bar, choose Environment → Cache Notifications.
The events that triggered a cache update are displayed in the Notifications of Released Change Lists frame.
You can restrict the display to a particular cache instance, notification period, and author.
Cache notifications and cache updates are displayed on multiple tab pages in the Integration Directory. For more information, see the table below.
2.
To update the cache
again, select the corresponding line and choose Repeat
Cache Update for Instance (
).
Cache notifications can fail for a variety of reasons. You can test the cache connectivity in the Runtime Workbench.
More information:
Testing Cache
Connectivity● SAP Note 780747
Content of the Tab Pages
Tab Page |
Description |
Notifications |
Contains a list of the released changes that have resulted in a cache notification and cache update. The system displays the following information for each event: ● The cache instance that is affected by the change ● Status and time of the cache update ● Status and time of the cache notification ● Underlying change The Type field shows the type of change. Depending on the type of change, the Identifier (GUID) column displays the identifier of the change list or the imported software component version. |
Problems |
Contains information about the cause of the error when notifications or cache updates fail. In the Problems That Occurred During Cache Update frame, the changes that resulted in the notification or cache update failing are listed in a table. You can find the following information about each problem. ● The type of problem is specified in the Problem column. The Context can have the following values: ○ Notification: This is a notification error. ○ Part Update: Collect Data: This is an error in the Integration Directory.
An Integration Directory object has been deleted and therefore cannot be read. ○ Data Evaluation: This is a cache-instance error. ● The Object Affected column displays information about the object that caused the error. The Detailed Problem Description frame displays a description of the selected problem. |
Object views |
Shows the cache status for each individual object. This tab page displays the cache status for each individual object in the cache. If, for example, objects from a change list were not updates in the cache, you can use this view to determine which objects are affected and to find the cause of the error.
You can also display which cache a particular object was distributed to and analyze the status. To do this, open the object and in the main menu bar of the object editor choose <Object Type> → Display Cache Status. |
