Skip to end of metadata
Go to start of metadata


Contents



How to Configure a System as Central System

This article describes how to configure an ABAP system (client) as central system.

Concept

In order to enable central Web service configuration tools and processes, one ABAP system (per landscape) has to be configured as a central system. The systems to be managed can then establish a [ Management Connection to a central system|How to create a Management Connection to a central system].

The management connection is used for multiple purposes in the ABAP Web service configuration environment. It is used to gather information from managed systems or to execute tasks on managed systems for the following central applications:

  • Web service configuration log
  • Web service health checks
  • Automatic Web service configuration supporting change management
  • Web service design time compatibility cache

The configuration of a central system also enables the Services Registry functionality of that system.

Prerequisites

None

Constraints

  • The central system cannot be a managed system (although the central system always has a management connection to itself)

Procedure

  1. Open SOA Manager in the system to be the central system.
  2. Go to the "Management Connections" tab and choose the same-named link.
    Now zero or one established Management Connections are shown.
  3. Go to the "Configuration" tab.
  4. Choose "Edit" in the "Settings" section.
  5. Check the box "Central System".
  6. Choose "Save".
  7. If connectivity service is not enabled, enable it by choosing "Enable" in the "Connectivity Service" section. This configures the Web service endpoint needed for the management connection and the Services Registry endpoint.
  8. Afterwards, refresh SOA Manager (e. g. by pressing F5 in your browser).

In a central system the title is changed to "Central SOA Management" to indicate that central Web service configuration features have been enabled.

Result

The system is configured to act as a central system for Web service configuration.

Now the systems to be managed can establish their management connections to the central system.

For this purpose the following service definitions have been configured:

Internal Name

External Name

Namespace

Access URL

SOAMANAGERCONNECTIVITY

SOAManagerConnectivity

http://www.sap.com/netweaver/712/soap/changemanagement

http(s)://<host>:<port>/sap/bc/srt/scs/sap/soamanagerconnectivity?sap-client=<client>

SERVICESREGISTRYFLATSI

ServicesRegistryFlatSi

http://sap.com/esi/uddi/sr/api/ws/

http(s)://<host>:<port>/sap/bc/srt/scs/sap/servicesregistryflatsi?sap-client=<client>

SERVICESREGISTRYSI

ServicesRegistrySi

http://sap.com/esi/uddi/sr/api/ws/

http(s)://<host>:<port>/sap/bc/srt/scs/sap/servicesregistrysi?sap-client=<client>

If the endpoints were not configured before the endpoints are configured allowing the following three transport level authentication methods:

  • Basic authentication (Username/Password)
  • X.509 authentication
  • Single Sign-On.

More Information

Add links to the following:

  • Web Service Configuration Log
  • Web Service Health Check
  • Central Configuration

1 Comment

  1. Unknown User (101ebsydu)

    Hello Florian,

    For what version is this applicable ? 7.0.2 ?

    Thanks 

    Jan