Increasing the 240 minute timeout of Assure's runcp script

Within Assure 9.3, or Assure 9.2 with the IA-9.2-335489-0 fix pack, it is possible to customize the default 240 minute timeout of the runcp script. Note that the timeout only applies to asynchronous control point executions, which is the new default for Assure 9.3 or Assure 9.2 with the latest fix pack. 

The 240 minute timeout can be overridden for both Assure server or Assure Client. The location to override this setting would depend on whether you execute the runcp script from the Assure server's server-util directory and/or from Assure Client's bin directory. The change should be made in any combination of locations where you use the runcp script. 

The two properties below were added to control whether asynchronous executions should be used, and if so, the length of the timeout. 

ASYNC_EXEC_CP_CLIENT_ENABLED=true
ASYNC_CLIENT_POLL_MAXIMUM_TIME_MINS=240

Setting ASYNC_EXEC_CP_CLIENT_ENABLED to false will stop using the asynchronous control point execution and use the legacy method (prior to Assure 9.2, or Assure 9.2 without the latest fix pack). Note that this legacy method may cause different timeouts due to a long-running http connection that may get terminated via intermediary servers. 

The ASYNC_CLIENT_POLL_MAXIMUM_TIME_MINS setting only applies to the new asynchronous model. It has no effect when ASYNC_EXEC_CP_CLIENT_ENABLED is set to false.

To increase the timeout, adjust the value of ASYNC_EXEC_CP_CLIENT_ENABLED by utilizing override.properties.