Connection Retry Interval - ironstream_for_elastic - ironstream_for_kafka - ironstream_for_splunk - 7.4

Ironstream for Splunk®/Kafka®/Elastic® for IBM i Ironstream Integration Components Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Elastic®
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream for Splunk®
Version
7.4
Language
English
Product name
Ironstream Splunk®/Kafka®/Elastic®
Title
Ironstream for Splunk®/Kafka®/Elastic® for IBM i Ironstream Integration Components Administration
Copyright
2022
First publish date
2007
Last updated
2023-08-25
Published on
2023-08-28T08:26:48.055356

If the Proxy Server is unable to connect to an IBM i Agent, it attempts to reconnect based on a retry interval. Common scenarios that cause the connection to fail are:

  • The Agent is stopped

  • The specified port on the IBM i LPAR is not enabled for listening

  • The network connection is unavailable

In the 7.4 GA release the default value of this retry interval for each LPAR is 0 seconds. This means that the Proxy Server will continuously attempt to reconnect to the Agent if it is inaccessible for any reason. There is a patch available for the 7.4 Proxy Server which sets the default to 30 seconds, please contact Support for details. However, to update this value manually (if you do not have the patch, or want to use a value other than the current default), follow the instructions below (currently it cannot be set in the Configuration Tool):

  1. On the Proxy Server, go to the conf folder:

On Windows: \EView Technology\EView400i\conf\

On Linux: /etc/opt/OV/share/conf/

  1. Open each System config file, named ev400_config_systemname. For example: if the System is called test then the file will be called ev400_config_test.

  2. Add this line to the bottom of the file, or if the line is already present, edit the existing value. This example sets the interval to 30 seconds:

RETRY_TIME 30

  1. Save the changes to the file.

  2. Stop and restart the Systems affected, to ensure that the new value is used.

Note: This value will persist even if you modify the System configuration in the Configuration Tool.