Prerequisites
Before using SAProuter, you should test whether there are any network problems.
To test the basic functions of the SAProuter, you require the programs saprouter and niping as well as three open windows (shells) on one or more hosts.
Procedure
The following table shows the test scenario when using niping:
SAProuter runs in window 1, the server in window 2, and the client in window 3.
| Window 2 (host2) | Window 1 (host1) | Window 3 (host3) |
---|---|---|---|
Without SAProuter | niping -s |
| niping -c -H host2 |
With SAProuter | niping -s | saprouter -r | niping -c -H /H/host1/H/host2 |
| Window 2 (host2) | Window 1 (host1) | Window 3 (host3) |
---|---|---|---|
Without SAProuter | call niping '-s' |
| call niping '-c' '-H' 'host2' |
With SAProuter | call niping '-s' | saprouter '-r' | call niping '-c' '-H' '/H/host1/H/host2' |
Follow the procedure below:
Start SAProuter in window 1 (on host1). To do this, enter the following command:
UNIX/Windows: saprouter -r (IBM i: 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.
In window 2 (host2), start the test program niping to simulate a test server. Enter the command
UNIX/Windows: niping -s
IBM i call niping '-s'
For a complete list of the niping commands, see the online help. To call the online help, enter niping.
In window 3 (host3), start the test program niping to simulate a client. Enter the command
UNIX/Windows: niping -c -H host2
IBM i call niping '-c' '-H' 'host2'
This command tests the connection without the SAProuter, that is directly between host2 and host3.
In window 3, start the test program niping again with the following command:
UNIX/Windows: niping -c -H /H/host1/H/host2
IBM i 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.
For more information, 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 (IBM i: call niping '-t').
A list with function names, parameters, and return codes is displayed. If the self test is successful, the following message appears:
*** SELFTEST O.K. ***
Note
To get an idea of the options provided by niping, enter niping without any parameters.
SAP Note 500235 contains comprehensive documentation about the nipingtool.
2 comments:
For a Excellent Online Resource for SAP EP and SAP Web Dynpro ABAP, Visit Learn SAP Online
For a Excellent Online Resource for SAP EP and SAP Web Dynpro ABAP, Visit Learn SAP Online
SAP EP - Standard Portal Services
Portal Eventing and Navigation
Portal Look and Feel - Branding the Portal
How to Develop Portal Applications
SAP EP-Developing portal content and assigning permissions
SAP EP-Role maintenance
SAP EP-How to make Enterprise Portal highly available
Implement Single Sign On
SAP EP-J2EE architechture
What is SAP Enterprise Portal
And Many More...
Basics of Web Dynpro ABAP
ABAP Data Types and Objects
ABAP Statements
WD4A - Introduction WDA - SAP Logon Procedures
WD4A-Format the Values appearing on value Axis of Business Graphic
WD4A-Navigate from one view to another and back to previous view
WD4A - How to Calculate next 12 months from current month in web dynpro ABAP
WD4A - Validate Inputs in a web dynpro ABAP Application
And Many More...
Post a Comment