Limit the Number of Jobs Per User Session and Per User Account

If your users' job requests place a heavy burden on the system, you can limit the number of open jobs within Intelligence Server, including element requests, autoprompts, and reports for a user.

• To help control the number of jobs that can run in a project and thus reduce their impact on system resources, you can limit the number of concurrent jobs that a user can execute in a user session. For example, if the Jobs per user session limit is set to four and a user has one session open for the project, that user can only execute four jobs at a time. However, the user can bypass this limit by logging in to the project multiple times. (To prevent this, see the next setting, Jobs per user account limit.)

  To specify this setting, in the Project Configuration Editor for the project, select the Governing Rules: Jobs category, and type the number in the Jobs per user session field. A value of -1 indicates that the number of jobs that can be executed has no limit

• You can set a limit on the number of concurrent jobs that a user can execute for each project regardless of the number of user sessions that user has at the time. For example, if the user has two user sessions and the Jobs per user session limit is set to four, the user can run eight jobs. But if this Jobs per user account limit is set to five, that user can execute only five jobs, regardless of the number of times the user logs in to the system. Therefore, this limit can prevent users from circumventing the Jobs per user session limit by logging in multiple times.

  To specify this setting, in the Project Configuration Editor for the project, select the Governing Rules: Jobs category, and type the number of jobs per user account that you want to allow in the Jobs per user account field. A value of -1 indicates that the number of jobs that can be executed has no limit.

These two limits count the number of report, element, and autoprompt job requests that are executing or waiting to execute. Jobs that have finished, cached jobs, or jobs that returned in error are not counted toward these limits. If either limit is reached, any jobs the user submits do not execute and the user sees an error message.