Show TOC

Procedure documentationThe Central Design Time Cache Locate this document in the navigation structure

 

The central 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 be a plain SAP NetWeaver, and thus no business applications of the domain systems are installed on it. Furthermore, the central design time cache checks the compatibility between service interfaces and consumer proxies and also between service interfaces and service groups. The central design time cache is updated automatically in the central system after each design time change in the back-end system.

Procedure

The central design time cache can also be updated manually by a program in the back-end system and transferred to the central system:

Note Note

The central design time cache is usually updated automatically using the management connection. If a design time object from a managed system is not available for configuration in your central system, you can proceed as described below:

  1. Log on to the managed system in question.

  2. In transaction SE38, execute the report SRT_WSP_CDTC_BUILD.

  3. 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.

  4. In the central system, start SOA Manager (transaction code SOAMANAGER).

    The design time cache is now up-to-date. All design time entities are available during the central business configuration.

End of the note.