In this step, you define the mapping for the URLs that are sent as part of the notifications.
It is necessary to expose all UI and OData links in their external representation, and not to expose the internal proxy host or port name. To achieve this, an implicit URL must be rewritten for any given OData resource based on SAP table HTTPURLLOC.
The entries in the table HTTPURLLOC must reflect the proxy server settings (SAP Web Dispatcher or other).
These steps must be executed in your application back-end system, unless you are using the ABAP SMI hub. If you want to use the ABAP SMI hub, the definition must be made on the SAP Gateway server.
|Enter the protocol that the external communication source
For SAP Jam, this is HTTPS. Use SSL whenever possible.
|Specify the same application ID as used in Defining Application Settings.
|Enter the external representation of the URL that points back to the SAP Gateway server, for example, the address of your web dispatcher
or reverse proxy that can forward requests to the SAP Gateway server.
|HOST and PORT
|Enter the internal server information for the SAP Gateway server.
Only links to OData resources that are explicitly passed are converted. ABAP SMI does not convert UI links nor parse the text segment (summary) of the notification.