SAProuter as Port Forwarder 
If two SAProuters with reverse invoke are used as in the example (RI Configuration of SAProuter: Example), these can also act as port forwarders. In addition to the standard configuration the parameter route must also be set on the client. This route specifies where incoming connections are forwarded.
This profile parameter replaces a call to the SAProuter with a route, so for this reason the first SAProuter must appear in the route string. The route string you specify as the parameter is the one you would specify in SAP GUI or for gateway connections.
Caution
Since this configuration enables all incoming connections to be forwarded, administration requests cannot be identified by the SAProuter. Therefore, the client SAProuter cannot be administered. You can only stop the SAProuter using signals at operating system level.
You could extend the above example to a port forwarder in the following way:
The route parameter must be added to the configuration file of the client as follows:
route = /H/10.18.0.1/S/4001/H/10.18.0.2/S/5002/H/10.18.0.3/S/8080
Since 'raw' connections (pure TCP/IP without NI header) are necessary for HTTP, the route permission table on server 2 (file rt2) must be modified. You must enter the destination port:
P 10.18.0.1 * 8080
With the HTTP browser you can now call the Web server on 10.18.0.3:8080 using the following URL:
http://10.18.0.1:4001
The server SAProuter displays the following connection data:
> saprouter -l -S 4002 ... ID CLIENT | PARTNER service -----------------------------+--------------------------------- 4 localhost | (no partner) 2 10.18.0.1 + 10.18.0.3 8080 ... RI server hdl 1/sock 5 BUFFERED client 10.18.0.1:5001 registered 0.0.0.0:5002 connPool 3 checks 0 selectSet set0 onDemand NO CONN ID S SOCK 0: 0000306404935302 C 9 1: 000040acd61fac53 C 11 2: 000050ba74a8a931 C 6 |