URL could not be mapped to its external representation

Message type: E = Error

Message class: CLB - SAIL: Common messages

Message number: 456

Message text: URL could not be mapped to its external representation



What causes this issue?

The mapping of a URL from internal to external representation failed.


System Response

The URL mapper was called, but could not find any mapping information in
table HTTPURLLOC for the given combination of host and port. The mapper
was informed that this situation had to be logged.
Depending on the context, this defect is the result of an exception
that interrupted the application. Especially, during the distribution of
business object notifications, the Customizing parameter determines
whether the processing is interrupted.


How to fix this error?

For the notification scenario<(>,<)> see instructions in the next
section.


Procedure for System Administrators

For the URL mapping, table HTTPURLLOC is used as described in the
notification guide.
A new Customizing indicator, <LS>Mapping Exception</>, is available for
Customizing activity<DS:SIMG.S_JAM_SERVER>Server Settings
</>(transaction CLB_PLATF). It controls error handling when mapping URL
links:
If the checkbox is selected, an exception is raised when URL mapping is
not successful. The exception results in erroneous entries in the bgRFC
queue of the Gateway hub.
To prevent an exposure of your internal server IDs to the internet, you
must select this checkbox and maintain table HTTPURLLOC. To do so, run
transaction SE16 and call up table HTTPURLLOC.
Maintain table HTTPURLLOC as follows:
In the <LS>PROTOCOL </>field, enter the protocol that the external
communication uses (HTTPS in the case of SAP Jam ? use SSL whenever
possible).
In the <LS>FOR_DOMAIN </>field, enter the external representation of the
URL, for example, <LB>www.saptest.com</>.
In the <LS>APPLICATN</> field, specify the same application ID as used
in Customizing activity
<DS:SIMG.S_CLB_APPLI>Application-Specific Server Assignment</>.
In the <LS>HOST </>and <LS>PORT </>fields, enter the internal proxy
information, for example, <LB>lcfsg2hd </>and <LB>8080</>.
<ZH>Notes:</>
The HTTPURLLOC entries represent an inside->out mapping that corresponds
to the outside->in mapping at your reverse proxy or web dispatcher.
You can also specify a default entry, with host and port set to *, if it
is not possible to specify all application servers at design time (for
example, due to virtualization).

Error message extract from SAP system. Copyright SAP SE.