The configuration table HTTPURLLOC is provided to handle any URL generation problems. In this table you can configure how a URL is to be generated. Note that this table simply contains configuration information.
The HTTPURLLOC table contains the following fields:
|Field||Data Type and Length||Value Range|
|MANDT||CHAR 3||000 – 999|
|SORT_KEY||CHAR 4||0000 – 9999 (recommended)|
|PROTOCOL||CHAR 8||HTTP | HTTPS|
The entries should be in upper case so that the string compare algorithm is as quick as possible.
- There is no tool to manage or update this table. So make your settings directly in transaction SE16.
Fields and their meanings:
Client for which the configuration is to be performed. Different clients represent different identities, for which different configuration data is needed. For instance, the host name could be server.abc.com for client 100, whereas it could be www.xyz.de for client 200.
Sort sequence of entries. Entries in this sequence are compared from top to bottom and the first matching entry is used.
Protocol for which a fully specified URL must be generated. It can be HTTP or HTTPS.
This string can be used to filter the entry for special application types. If this is configured, this entry is used as the template to determine how the current application that would like to generate a fully specified URL is used. For BSP the string /BSP/<namespace>/<name> is always used.
Leave this field empty if this configuration is used again and again.
Examples of values:
/BSP/SAP/IT00 assigns access rights only to BSP application IT00.
/BSP/XYZ/* assigns access right to all BSP applications in the XYZ namespace (registered namespace of the organization).
/BSP/* assigns access rights to BSP applications.
An empty string assigns access rights for all applications.
Can be used by an application, an SMTP mail system for instance, to generate URLs in other domains. It is not used in the BSP environment. If a value is specified for this field, it is used to filter the request for which a new URL has to be generated. We recommend to always leave this field empty.
Mandatory field for generating the new URL. If the host is requested from an API, this field is used as a filter for the host header of the inbound request to decide which configuration line is to be used. It is a special case when the exception table is not to be used for an entry. If the field for the host is empty and the other parameters tally, this field is used as an indicator to specify that the local host data is used for generating the URL, and not the exception table.
Port number used in the new, fully-specified generated URL.