Gateway Server Configuration |
Gateway |
Click Configuration in the expanded menu.
Make your changes to the configuration as necessary.
Item |
Description |
Auto-Start |
Select the Auto-Start check box to automatically restart the Gateway Server if the PROIV Gateway web application is started or restarted. |
Environment Name |
The name of the Gateway Server. |
Listen Port |
The port that the Gateway Server listens on for connections. |
Maximum Kernels |
The maximum number of PROIV Kernels that this Gateway Server allows. This sets a resource limit on the use of this Gateway Server. If another attempt is made to use this Gateway Server after the limit is reached, an error message appears and a message is put in the general log. The value must be greater than 0 and is constrained by your number of Gateway Licences |
Initial Kernels |
The number of PROIV Kernels to start up ready for Gateway Server connections. This creates a pool of kernels that are ready and waiting for Gateway Server connections and this improves the response time at the expense of resources. The value must greater than 0 and must be less than the Maximum Kernels value. |
Kernel Port (Win/Unix) |
For Unix platforms this is the port used by the kernel to connect to the gateway. For Windows platforms this is the port used by the gateway to connect to the kernel service. |
Kernel Host (Win) |
This is only used on Windows platforms and is the name or IP address of the PROIV application server. |
Kernel Path (Unix) |
This is only used on Unix platforms and is the full path to the kernel executable or script. See The Gateway Connection to PROIV for details. |
Kernel Ini Path (Unix) |
This is only used on Unix platforms. It is the full path to the .ini file used by the kernel in addition to pro4v[n].ini file. If there is no additional .ini file, this field should be set to /etc/pro4v[n].ini. See The Gateway Connection to PROIV for further details. |
Kernel Pre Argument String (Unix) |
This is only used on Unix platforms and is any command line text that should be placed before the kernel command. |
Kernel Post Argument String (Unix) |
This is only used on Unix platforms and is any command line text that should be placed after the kernel command. |
Kernel Idle Timeout |
The number of seconds a kernel can remain idle before the connection is closed. This must be greater than 0 and 60 is a good starting value. |
Kernel Maximum Startup Timeout |
For Unix platforms this is the maximum number of seconds to wait for a kernel to start. For Windows platforms this is the maximum number of seconds to wait for a successful connection to be made to a kernel via the kernel service. This must be greater than 0 and 60 is a good starting value. |
Kernel Maximum Response Timeout |
The maximum number of seconds to wait for a response from a kernel before timing out the operation. Note that this needs to be larger than the time taken for the slowest Task in your PROIV application. This must be greater than 0 and 60 is a good starting value. |
Kernel Factory |
The Java class to be used to create kernels. |
Gateway Session Timeout |
The number of seconds a Gateway Server connection remains active. Currently this is not implemented and connections remain active indefinitely. |
Maximum Gateway Sessions |
The maximum number of simultaneous connections that the Gateway Server will allow. This sets a resource limit on the use of this Gateway Server. If another attempt is made to use this Gateway Server after the limit is reached the user will get an error message and a message will be put in the general log. This must be greater than 0 and 20 is a good starting value. |
Login Cache Lifetime |
The number of seconds that an authenticated user name/password will be regarded as valid without retrying the actual authentication. Note that this can be set to 0 to force each authentication request to be carried out. A good starting value is 3600. |
Login Cache Size |
The maximum size of the cache containing authenticated user name/password combinations. Note that this can be set to 0 to force each authentication request to be carried out. A good starting value is 100. |
Kernel Queue Maximum Size |
Set the number of queued session requests waiting for a free kernel. When the number of requests exceeds the number of available kernels, you can try increasing the maximum number of available kernels in the Maximum Kernels field (See above). This number is constrained by the number of Gateway licences that you have. Default is 100. |
Kernel Queue Maximum Wait Time |
Set the time in milliseconds that a request is queued before displaying a 'Kernel not available' error message. When the message displays, the request is removed from the queue and an error message is sent to the requestor. Default is 1000 milliseconds. |
Kernel Read Select Timeout |
Entering a value in this field configures the read_select_timeout parameter, which sets the PROIV Gateway's maximum wait time when it attempts to retrieve (read) data through NIO (Non-blocking I/O) data transfers before timing out and returning a 'Kernel not available' error message. The default setting is sufficient for many java-dependent applications that use NIO buffers. However, if other processes are consuming resources that are resulting in frequent read select timeouts, then increasing the value reduces the CPU load (i.e. fewer read NIO buffer retries). Default value is 10 milliseconds. The maximum value is 1000 milliseconds. |
User Authenticator |
The authentication mechanism used to check user name/password pairs. A value of 'Default User Authentication' will always accept all user name/password pairs as valid (i.e. it does not do any authentication). See Security and Authentication for details. |
Click Save Gateway Server Configuration.
Restart the PROIV Gateway Server service from the Services option in the Windows Control Panel for the read_select_timeout changes take effect.
If you do not click Save Gateway Server Configuration; then your changes are not saved. |
Warning: The PROIV Gateway Server service must be restarted from the Services option in the Windows Control Panel before the read_select_timeout changes take effect. Stopping or re-starting the PROIV Gateway Server from the PROIV Control Panel will not reload the new read_select_timeout parameter value into the Gateway Server. |
Topic ID: 250007