What is SAProuter? How to Check SAP Router?

What is SAProuter?

SAProuter is an SAP program that acts as an intermediate station (proxy) in a network connection between SAP Systems, or between SAP Systems and external networks. SAProuter controls the access to your network (application level gateway), and, as such, is a useful enhancement to an existing firewall system (port filter).

Before using SAProuter, you should test whether there are any network problems.

You require the programs saprouter and niping as well as three open windows (shells) on one or more hosts.

UNIX/NT

	Window 2 (host2)	Window 1 (host1)	Window 3 (host3)
WithoutSAProuter	niping -s		niping -c -H host2
With SAProuter	niping -s	saprouter -r	niping -c -H /H/host1/H/host2

Steps to test SAP Router

       1.      Start SAProuter in window 1 (on host1). To do this, enter the following command:

UNIX/Windows: saprouter -r
( iSeries: saprouter '-r')

This command calls SAProuter without any parameters.

For a complete list of the SAProuter commands, refer to the chapter SAProuter Options  or the online help. To call the online help, enter saprouter.

       2.      In window 2 (host2), start the test program niping to emulate a test server. Enter the following command:

UNIX/ Windows: niping -s

 iSeries: call niping '-s'

For a complete list of the niping commands, refer to the online help. To call the online help, enter niping.

       3.      In window 3 (host3), start the test program niping to emulate a client. Enter the following command:

UNIX/ Windows: niping -c -H host2

 iSeries: call niping '-c' '-H' 'host2'

This command tests the connection without SAProuter, that is directly between host2 and host3.

       4.      In window 3, start the test program niping again with the following command:

UNIX/ Windows: niping -c -H /H/host1/H/host2

 iSeries: call niping '-c' '-H' '/H/host1/H/host2'

This command tests the connection with SAProuter. A host name is interpreted as a route (over one or more SAProuters to the server) if /H/ is added as a prefix to the host name (see Route Strings ).

In steps 3 and 4, data packages are sent to the server, and the server sends the data packages back. In step 3, the data packages should be sent to the server more frequently, since more process changes take place.

To perform a self test for the local host:

Enter the command niping -t (iSeries: call niping '-t').