You can set the Control-M/EM Gateway (GTW) parameters to optimize requests and communication between Control-M/EM and Control-M/Server.
Parameters in the Defaults.rsc file that affect timeout values are discussed below. For more information, see Defining a Control-M/EM component.
The following modifications to timeout values can be made:
You can modify the following parameters in the Defaults.rsc file to set timeout values:
download_timeout
upload_timeout
usreq_timeout (affects user requests like hold, free, kill, delete, and save)
inforeq_timeout (affects information requests timeout like output, documentation, and log)
keep_alive_timeout
sync_timeout
You can optimize the SSL synchronization timeout by modifying the SSLSyncTime system parameter.
For more information about modifying the Defaults.rsc file, see System configuration.
Setting a timeout value for a GUI Server affects only requests that the GUI Server invokes as a CORBA client. Examples of such requests are:
updating the GUI with Viewpoint information
sending results of a callback action, such as Upload Folder or Holding an active job
To prevent disconnections from slow clients, set the GSR AddJobsChunkSize system parameter to 100 (the default chunk size is 1000). BMC recommends decreasing the chunk size instead of increasing the timeout value.
