Setting Up Reverse Invoke Connections with SAProuter 
SAProuter can be used as both a client and a server for reverse invoke (RI). Since SAProuter releases are independent of SAP kernel releases (SAP NetWeaver Application Server), reverse invoke can also be used with older releases of SAProuter by interconnecting two SAProuters.
To activate reverse invoke for SAProuter, you start the SAProuter as follows:
saprouter -i <RI config file> other options]
All settings for the SAProuter are made in a configuration file. The options in this file affect the connection setup only, all other SAProuter functions remain the same.
The configuration parameters listed in the configuration file are described below.
The parameters can be divided into client and server parameters. Some appear both as RI clients and RI servers for the SAProuter.
|
Parameter |
Meaning |
Domain |
Default |
|---|---|---|---|
|
client |
Determines use as a client |
Any value |
|
|
client_service |
Determines the registration port (see Reverse Invoke) |
Port number |
|
|
ACE |
Access control entry |
Maximum 32 entries per form P/D <address>/<prefix> |
|
|
max_servers |
Maximum number of servers allowed to register |
Integer |
1 |
|
conn_pool_size |
Number of connections held in the pool |
Integer |
3 |
|
client_hostname |
Local address for registration port if a specific interface is required |
Port number |
|
|
listen_protocol |
Protocol of the registration ports |
IPv4, IPv6, unspec |
Unspec |
|
exclusive |
Specifies whether conventional non-RI connections can be set up |
Logical value [yes, no] |
yes |
|
connect_timeout |
Timeout for the connection setup. |
Milliseconds |
2000 |
|
Parameter |
Meaning |
Domain |
Default |
|---|---|---|---|
|
server |
Determines use as a client |
Any value |
|
|
client_hostname |
Host name/client address (registration port) |
Host name or IP address |
|
|
client_service |
Determines the registration port (see Reverse Invoke) |
Port number |
|
|
reg_hostname |
Host name to be registered; if the parameter is not set, all local interfaces are registered (pseudo port) |
Host name or IP address |
|
|
reg_service |
Service name to be registered (pseudo port) |
Port number |
3299 |
|
connect_timeout |
Timeout for connection to client. The value -1 deactivates the timeout. |
Milliseconds |
-1 |
|
retry_timeout |
Timeout between two attempts to set up the connection to a client |
Seconds |
5 |
|
conn_on_demand |
Specifies whether connections are set up only when they are needed |
Logical value [yes,no] |
yes |
|
reg_protocol |
Protocol of the pseudo port |
IPv4, IPv6, unspec |
Unspec |
|
conn_pool_size |
Number of connections held in the pool On the server side this parameter affects only the size of the internal structures; the actual number of connections is specified by the client (default is 3) |
Integer |
3 |