Show TOC

Service RegistrationLocate this document in the navigation structure

Services are developed in the SAP backend system. Services are registered in the transaction /IWBEP/V4_ADMIN in the SAP backend. This section explains the prerequisites and the steps necessary for the registration of services.

Service Repositories

A service repository is identified by a CHAR 10 repository ID (without an ABAP namespace). With SAP NetWeaver 7.50 SP04 only the SAP Gateway Foundation repository DEFAULT is available.

There is no generic registration for repositories because there will be only very few service repositories. The supported repositories are hard-coded in the SAP Gateway Foundation framework sources.

Service Repository, Service and Service Group

A service is always a member of exactly one service repository.

A service group simply collects several services and allows to administrate (for example publishing, routing and authorization maintenance) all services in this group at once. A service can only be consumed using OData V4 in the context of a service group and only after this service group has been published in the hub component.

Service Identifier
Service identifier is a development object with the two key fields:

  • Service ID – CHAR 36 containing a namespace and a service name (for example /IWBEP/TEA_BUSI)

  • Service Version – NUMC 4, starting with 0001

Service Group Identifier
Service group identifier is a development object with the key field:

  • Service Group ID – CHAR 36, and contains a namespace and a service group name (for example /IWBEP/TEA)

Registration of Service Group and Service

Hand-crafted services are registered in transaction /IWBEP/V4_ADMIN. For registration of a service a service group and the service implementation - model provider class (MPC) and data provider class (DPC) - have to be specified.

A service becomes a member of a service group after it has been assigned to a service group. This is available for services of different service repositories.

A service can contain primitive properties that are linked to an F4 help service. Each of these F4 help services will be added automatically to the service group this service is assigned to. These F4 help services will then be directly addressable in the context of the service group.

Service Group /IWBEP/ALL

During prototyping and development it might be inconvenient that a service needs to be assigned to a published service group before it can be tested. For this use case, SAP Gateway Foundation supports the service group /IWBEP/ALL that virtually contains all registered services of different repositories. This service group still needs to be published once, but after that any service that has been and also will be registered in the affected backend can be accessed in the context of this service group.

The service group /IWBEP/ALL can only be published in a backend system that is configured as a development, customizing, training or sandbox/demo system, but not in test or production systems.

You can display all services of the service group /IWBEP/ALL within transaction /IWBEP/V4_ADMIN.

Manage Services
The SAP Gateway Foundation administration tool supports the following actions for services of different service repositories:

  • Assign a service to a service group

  • Assign a service of a service group to another service group

  • Unassign a service from a service group

The SAP Gateway Foundation administration tool supports the following actions for services of the repository DEFAULT:

  • Update service

  • Delete service