Show TOC

Process documentationConfiguring Multiple Service Providers Locate this document in the navigation structure

 

You can apply runtime configuration settings to multiple service definitions at once.

Process

Configuration Profiles

To configure multiple service providers, runtime configuration settings are defined in configuration profiles.

A configuration profile comprises a set of technical settings for endpoints, taking into account the specific interdependencies between providers and consumers in a particular system landscape.

When you assign a configuration profile to one or more service definitions, an endpoint is created for each service definition in the provider system. By assigning different configuration profiles, you can create more than one endpoint for the same service definition. In this way, you can provide the same service with several different runtime configurations.

This graphic is explained in the accompanying text.

Configuration of Single and Multiple Service Providers

The graphic shows a service definition A assigned to configuration profile 1 and configuration profile 2. Since two configuration profiles are assigned to service definition A, two endpoints are created for service definition A:

  • Endpoint A1 – based on configuration profile 1

  • Endpoint A2 – based on configuration profile 1

In the graphic, service definition B is only assigned to configuration profile 2. This results in one endpoint B2 being created.

When a single service provider is configured, configuration settings are assigned directly to one endpoint. Using configuration profiles, more than one endpoint can be created for the same service definition.

Configuration Scenarios

A configuration profile can be applied to one or more service definitions in a configuration scenario.

A configuration scenario consists of multiple service definitions, to which you can assign a configuration profile. You can create multiple configuration scenarios for your system infrastructure.

The same service definition can be active within multiple configuration scenarios. If a service definition is not active in any configuration scenario, the corresponding endpoint is deleted.