Service Group Publishing
Service groups are published in transaction /IWFND/V4_ADMIN on the SAP Gateway Foundation hub.
Publishing of service groups is a pure configuration task and does not create ABAP repository objects, hence does not entail artifacts with lifecycle for new services on the hub.
Only services of published service groups can be addressed by a consumer.
During publishing service groups can be retrieved from SAP backend systems for which a system alias has been maintained in the routing configuration of the transaction /IWFND/V4_ADMIN. When a service group is published, the currently used system alias is automatically assigned to this service group.
You can also assign other system aliases to this service group to access different backend systems based on user roles or by specifying a system alias in the request URL.
Services assigned in the backend system to an existing and already published service group are automatically addressable by consumers. No further configuration is needed for these services and service groups on the hub.
The routing configuration defines the way how a SAP Gateway Foundation hub system can communicate with a connected backend system. You use transaction /IWFND/V4_ADMIN for the routing configuration.
-
Manage system alias
-
Create system alias
-
Update system alias
-
Delete system alias
-
- Check RFC connections
- Display all services using OData V2 and also V4, using the same system alias
- Navigate to transaction /IWFND/MAINT_SERVICE to maintain OData V2 services or /IWFND/V4_ADMIN to administrate OData V4 services on the hub system
You can also use this routing configuration to manage system aliases for OData V2 services.
If the SAP Gateway Foundation hub system and the backend system are separate systems, you have to use transaction SM59 to configure a trusted RFC destination for the communications between the hub and backend system.
Note that the language in this destination has to be empty. Otherwise, all text elements use in the backend system during an OData request processing will be in the language configured in this destination. Moreover, the language used by the OData consumer must be installed in the SAP Gateway Foundation hub system and the backend system.
At least one system alias must be assigned to a service group to define the communication between the SAP Gateway Foundation hub system and the backend system.
-
System Alias ID – CHAR 16
-
RFC Destination: SM59 destination or blank (co-deployed system)
-
Local GW: Once this flag is set, the framework will use the RFC bypass to locally call the OData service provider.
-
For Local App: Some specific OData services such as Task Workflow use the RFC destinations to configure the communications between the co-deployed system and the Workflow backend systems. In this case you have to set this flag.
-
Use Micro Hub: Set this flag if the backend system is a separate system and is at least on SAP NetWeaver 7.50 SP04 to speed up the processing performance.
-
BEP System Information: Depending on the RFC destination defined in the system alias, the backend system information consists of the following information for communication between the hub system and the backend system:
-
<System name>/<SAP client>,
-
Rel.<SAP NetWeaver release>,
-
BEP version,
-
The backend system information is only available once the system alias is used for processing an OData service request. If not, it will be shown as "not yet available". Once the backend system has been upgraded or the system alias configuration has been changed and the system alias is used again, this information will also be updated.
The BEP version of the SAP Gateway Foundation component in the backend system is independent of the SAP NetWeaver release or support package stack. It helps the SAP Gateway Foundation framework to synchronize the supported features between the hub system and the backend system.