Enhancement spot /IWFND/ES_MGW_DEST_FINDER is provided to help you in dynamically calculating which system alias should be used. You can therefore use this enhancement spot to overwrite or enhance the standard routing for a service. Alternatively, you can use this enhancement spot to control the traffic from the SAP Gateway system to a backend system, so as to limit the load on that backend system.
This has to be defined with the standard implementation guide activity for system aliases.
This field is filled according to the standard routing in the implementation guide which has the role as an optional “filer”. Note that this field can be empty.
Technical Service Name: | /IWBEP/TEA_TEST_APPLICATION |
External Service Name: | TEA_TEST_APPLICATION |
Version: | 0001 |
The service registered on the SAP Gateway system is as follows:
Namespace: | /IWBEP/ |
External Service Name: | TEA_TEST_APPLICATION |
Version: | 0001 |
Technical Service Name: | ZTEA_TEST_APPLICATION (provided during registration) |
Service Document Identifier: | ZTEA_TEST_APPLICATION_0001 (technical service name plus version) |
URI = /sap/opu/odata/iwbep/TEA_TEST_APPLICATION/TeamCollection
IV_USER | =MRMEYER |
IV_SERVICE_ID | = ZTEA_TEST_APPLICATION_0001 |
Table of system aliases containing the result of the standard routing |
The BAdI output would then be a table of system aliases which were changed by the BADI (or not changed) as a result of the standard routing,
… RAISE EXCEPTION TYPE /iwfnd/cx_mgw_dest_finder EXPORTING textid = /iwfnd/cx_mgw_dest_finder=>backend_load_too_high http_status_code = /iwfnd/cx_mgw_dest_finder=>gc_status_service_unavailable system_alias = lv_system_alias.