Defining Systems as Central Systems
Prerequisites
You use SAP NetWeaver 7.0 EHP2, Service Package 08 or higher.
Context
The central system is used to execute tasks on other systems within an ABAP landscape. As soon as a client of an ABAP system is defined as a central system, other systems can pass control to the central system so that different configuration tasks can be carried out in these managed systems from the central system. For example, Web service configuration and Web services health checks can be executed on the managed system from within the central system. The central system can also be used for easy change management. When a system is configured as a central system, it can also be used as a services registry. Note that on the system you select as your central system, you will no longer be able to configure local business scenarios.
Third-party systems can be integrated in your system landscape as Web service provider. To do this, you create a domain system in the central system that represents external Web services. These Web services can then be managed from the central system.
Procedure
Results
Your system is defined as a central system, allowing other systems to be managed by it. For this purpose, the following entities must be maintained in the central system:
-
Domains and domain systems
Domain systems are automatically created in the central system as soon as a system establishes a management connection to the central system. Using this management connection, a system allows the central system to configure it centrally. For third-party systems, you have to create domain systems manually. Domains are created in the central system to group domain systems according to security settings.
-
Central design time cache
-
Change processor to distribute changes from the central system to its domain systems