The central design time cache is usually updated automatically using the management
connections after each design time change in a back-end system. It is also one of the health
checks that you usually perform regularly in the background or start directly from SOA Manager. If, for example after a transport, a design time object from a managed
system is not available for configuration in your central system, you can use this procedure
to update it manually.
Context
The design time cache is used in the central system to store the service interfaces,
consumer proxies, and service groups that exist in the back-end systems. This is necessary
since in the central system not all the design time objects might be present. For example,
a central system might only be
SAP NetWeaver, without any of the business applications of
the domain systems installed on it. The design time cache also checks the compatibility
between service interfaces and consumer proxies, and between service interfaces and service
groups.
Procedure
-
Log on to the managed system
-
In transaction SE38, execute the
SRT_WSP_CDTC_BUILD report.
-
Select the objects to update. To build the design time cache for all design time
objects, check all checkboxes.
After the report has been executed successfully, the cache information is
automatically sent to the central system using the management connection. Data in the
design time cache for objects that are not selected in this report are not updated or
deleted.
-
In the central system, start SOA Manager (transaction code
SOAMANAGER).
Results
The design time cache is now up-to-date. All design time entities are available during
the central integration scenario configuration.
