1.Executing only "niping" will show online help as below:
2.Performing niping self test:
3. Starting niping server on the host by cmd "niping -s"
4.Starting niping client from the front end by cmd " niping -c"
5.Connection test:
Connect / Ping OS Level
Check if the server is reachable, no data are written to the partner (Linux): niping -c -X9 -H <host> -s 3298
Connect / Ping Application Level
To check whether a NI base application can be reached, use the extra option –X1 which sends a NI_PONG
and expects a NI_PONG message (Linux): "niping -c -X1 -H <host>
Connect to Dispatcher
Sometimes the connection test with the Ping/Pong message is not sufficient, because it is not clear if the
dispatcher is running on the other side or another program. With the option –X6 a invalid message is sent to
the partner, the response will be checked against the expected error message from the dispatcher
(Linux): niping -c -X6 -H <host>
6.Other Tests
Hostname Lookup : niping -v -H <Host>
Service Name Lookup
Same as for Hostname Lookups (Linux): niping -v -H <host> -S sapmsEMR ;sapgw00 ;sapdp00
7.Local Interfaces
Print all interfaces which are handled as local by NI. This list of IP addresses is e.g. important for the
Gateway program (Linux):
