API Gateway 10.7 | Configuring API Gateway | API Gateway Architecture | Reverse Invoke Configuration in API Gateway | Reverse Invoke Connectivity Properties
 
Reverse Invoke Connectivity Properties
This section describes the properties that you can configure to maintain the connectivity in a paired API Gateway deployment.
watt.server.rg.internalregistration.timeout
Specifies the time, in seconds, a connection on the internal server (API Gateway or Integration Server) waits before closing the connection to the API Gateway server.
The default value of watt.server.rg.internalregistration.timeout setting is 0, so that the connection between internal API Gateway and the DMZ API Gateway never times out. This is applicable when the network and connections are reliable.
If the network and connections are unreliable, and some times the connections breakdown, then you can set the watt.server.rg.internalregistration.timeout setting to a non-zero value, so that the connections times out.
When the connectivity between internal API Gateway and DMZ API Gateway is broken after a refresh (disabled and enabled), set the internal ports manually to resolve the issue. If you enable watt.server.rg.internalregistration.timeout setting to XX seconds within which if the internal server does not receive any requests from DMZ API Gateway, then registration internal ports are auto refreshed.
Setting watt.server.rg.internalregistration.timeout to a value that is lower than watt.net.socketpool.sweeperInterval causes the internal server to close the connection to the DMZ API Gateway and re-establish a new connection regularly.
watt.net.socketpool.sweeperInterval
Specifies the frequency, in seconds, at which the socket pool sweeper executes. The socket pool sweeper sends a ping request to all API Gateway connections and HTTP client connections. During a sweep it removes any invalid HTTP client connections. By default, the sweeper executes every 60 seconds.
As a good practice, Software AG recommends enabling the watt.net.socketpool.sweeperInterval setting, if you are using the watt.server.rg.internalregistration.timeout property. Set the value of watt.server.rg.internalregistration.timeout on the internal server to a value greater than the ping values defined by the watt.net.socketpool.sweeperInterval server configuration parameter on the API Gateway.
To prevent a client request from waiting indefinitely, you can configure the watt.server.rg.internalsocket.timeout property. This property allows you to set a time-period until which the Integration Server waits to establish a connection to the internal server. If no connection is established in the set time-period, a HTTP 500-Internal Server error is returned.