APAC SD Team
Category
Administration
How do I configure the Background Execution tasks?
Answered
How can I tell Yellowfin to only run 10 reports at once?
The same question
Hi David,
There are precise controls available for limiting the amount of reports that can be run simultaneously by Yellowfin. We call this the Execution Queue. However, to access these control features you will have to edit one of Yellowfin's configuration XML files. Please follow the steps below to do this:
1) In your OS, navigate to <YourYellowfinInstallDirectory>/appserver/webapps/ROOT/WEB-INF and make a backup copy of the file called web.XML. Put this in a safe place.
2) Use your favorite text editor to open web.XML.
3) Locate the Execution Queue section. On standard configurations, this will be around line 200. You will have to remove the lower comment marker in order to make Yellowfin recognize your changes.
The breakdown of each parameter is as follows:
ExecutionQueueConcurrentTasks: The number of reports that can be run concurrently. The default value is 5 times the number of CPU cores available on the server. EX, a server with 2 cores with default to 10 concurrent tasks, whereas a server with 4 cores will run 20 tasks at the same time.
ExecutionQueueInitialWaitTime: How long the server will wait (in seconds) to finish a report before the client shows the delivery popup and starts polling. The dafault value here is 5 seconds.
ExecutionQueueMaximumExecutionTime: The maximum time (in minutes) the reports can be running in the execution queue before they are killed. The default value is 240 minutes (4 hours)
4) Edit the configuration options as desired. This is done by changing the value between the <param-value> tags. For example, if I wanted to boost the wait time before seeing the 'long running report" prompt from 3 to 5 seconds, I would change <param-value>3</param-value> to <param-value>5</param-value> under the <param-name>ExecutionQueueInitialWaitTime</param-name> parameter.
5) Save your changes.
6) Restart Yellowfin. If Yellowfin is installed as a Windows service, this will need to be restarted.
7) Test and verify that the desired changes are now implemented and functioning.
Hi David,
There are precise controls available for limiting the amount of reports that can be run simultaneously by Yellowfin. We call this the Execution Queue. However, to access these control features you will have to edit one of Yellowfin's configuration XML files. Please follow the steps below to do this:
1) In your OS, navigate to <YourYellowfinInstallDirectory>/appserver/webapps/ROOT/WEB-INF and make a backup copy of the file called web.XML. Put this in a safe place.
2) Use your favorite text editor to open web.XML.
3) Locate the Execution Queue section. On standard configurations, this will be around line 200. You will have to remove the lower comment marker in order to make Yellowfin recognize your changes.
The breakdown of each parameter is as follows:
ExecutionQueueConcurrentTasks: The number of reports that can be run concurrently. The default value is 5 times the number of CPU cores available on the server. EX, a server with 2 cores with default to 10 concurrent tasks, whereas a server with 4 cores will run 20 tasks at the same time.
ExecutionQueueInitialWaitTime: How long the server will wait (in seconds) to finish a report before the client shows the delivery popup and starts polling. The dafault value here is 5 seconds.
ExecutionQueueMaximumExecutionTime: The maximum time (in minutes) the reports can be running in the execution queue before they are killed. The default value is 240 minutes (4 hours)
4) Edit the configuration options as desired. This is done by changing the value between the <param-value> tags. For example, if I wanted to boost the wait time before seeing the 'long running report" prompt from 3 to 5 seconds, I would change <param-value>3</param-value> to <param-value>5</param-value> under the <param-name>ExecutionQueueInitialWaitTime</param-name> parameter.
5) Save your changes.
6) Restart Yellowfin. If Yellowfin is installed as a Windows service, this will need to be restarted.
7) Test and verify that the desired changes are now implemented and functioning.
Hi David,
There are precise controls available for limiting the amount of reports that can be run simultaneously by Yellowfin. We call this the Execution Queue. However, to access these control features you will have to edit one of Yellowfin's configuration XML files. Please follow the steps below to do this:
1) In your OS, navigate to <YourYellowfinInstallDirectory>/appserver/webapps/ROOT/WEB-INF and make a backup copy of the file called web.XML. Put this in a safe place.
2) Use your favorite text editor to open web.XML.
3) Locate the Execution Queue section. On standard configurations, this will be around line 200. You will have to remove the lower comment marker in order to make Yellowfin recognize your changes.
The breakdown of each parameter is as follows:
ExecutionQueueConcurrentTasks: The number of reports that can be run concurrently. The default value is 5 times the number of CPU cores available on the server. EX, a server with 2 cores with default to 10 concurrent tasks, whereas a server with 4 cores will run 20 tasks at the same time.
ExecutionQueueInitialWaitTime: How long the server will wait (in seconds) to finish a report before the client shows the delivery popup and starts polling. The dafault value here is 5 seconds.
ExecutionQueueMaximumExecutionTime: The maximum time (in minutes) the reports can be running in the execution queue before they are killed. The default value is 240 minutes (4 hours)
4) Edit the configuration options as desired. This is done by changing the value between the <param-value> tags. For example, if I wanted to boost the wait time before seeing the 'long running report" prompt from 3 to 5 seconds, I would change <param-value>3</param-value> to <param-value>5</param-value> under the <param-name>ExecutionQueueInitialWaitTime</param-name> parameter.
5) Save your changes.
6) Restart Yellowfin. If Yellowfin is installed as a Windows service, this will need to be restarted.
7) Test and verify that the desired changes are now implemented and functioning.
Hi David,
There are precise controls available for limiting the amount of reports that can be run simultaneously by Yellowfin. We call this the Execution Queue. However, to access these control features you will have to edit one of Yellowfin's configuration XML files. Please follow the steps below to do this:
1) In your OS, navigate to <YourYellowfinInstallDirectory>/appserver/webapps/ROOT/WEB-INF and make a backup copy of the file called web.XML. Put this in a safe place.
2) Use your favorite text editor to open web.XML.
3) Locate the Execution Queue section. On standard configurations, this will be around line 200. You will have to remove the lower comment marker in order to make Yellowfin recognize your changes.
The breakdown of each parameter is as follows:
ExecutionQueueConcurrentTasks: The number of reports that can be run concurrently. The default value is 5 times the number of CPU cores available on the server. EX, a server with 2 cores with default to 10 concurrent tasks, whereas a server with 4 cores will run 20 tasks at the same time.
ExecutionQueueInitialWaitTime: How long the server will wait (in seconds) to finish a report before the client shows the delivery popup and starts polling. The dafault value here is 5 seconds.
ExecutionQueueMaximumExecutionTime: The maximum time (in minutes) the reports can be running in the execution queue before they are killed. The default value is 240 minutes (4 hours)
4) Edit the configuration options as desired. This is done by changing the value between the <param-value> tags. For example, if I wanted to boost the wait time before seeing the 'long running report" prompt from 3 to 5 seconds, I would change <param-value>3</param-value> to <param-value>5</param-value> under the <param-name>ExecutionQueueInitialWaitTime</param-name> parameter.
5) Save your changes.
6) Restart Yellowfin. If Yellowfin is installed as a Windows service, this will need to be restarted.
7) Test and verify that the desired changes are now implemented and functioning.
Replies have been locked on this page!