You enable URL rewriting on the SAP Gateway server to help create a secure connection to
SAP Jam.
Context
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. You must therefore maintain
entries in table HTTPURLLOC in the same
system that has a connection to SAP Jam.
Procedure
-
On the SAP Gateway server, run transaction SE16.
-
In table HTTPURLLOC, enter the
following values:
| Field |
Value |
| PROTOCOL |
Enter the protocol that the external communication source
uses. For SAP Jam, this is HTTPS.
Use SSL whenever
possible.
|
| APPLICATN |
Leave this field empty. |
| FOR_DOMAIN |
Enter the external representation of the URL that points back to the SAP Gateway server.
Example www.<a_location>.com
|
| HOST and
PORT |
Enter the SAP Gateway hub
internal information.
Example
HOST:
lcfsg2hd
PORT:
8080
You have to enter each application server of the
SAP Gateway server system separately.
|
-
Save your entries.
Note 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).
Results
You have defined the mapping for the protocol, host, and port so that SAP Jam can access
the external OData service.
