User Access to iProcess Engine Work Queues

The total number of work queues a single iProcess user can have access to is 32,767.

If the number of work queues a user has access to exceeds 32,767, the user is not able to log in to the TIBCO iProcess Engine and the following error message is displayed:

Sal Queues Interface 'sal_queues_count()' returned fatal error -n. Called by wqsess_lcreat_folder.

Abort WorkQs?

where n is the total number of work queues.

This only affects the single user who has access to too many work queues. All other iProcess users will be able to log in to the iProcess Engine without any problems.

As an iProcess user, you can access the following work queues:

Your Personal Queue which is only accessible to you
Any Group Queues that you are a member of
Any Test User Queues or Test Group Queues, if you are authorized to define procedures.

An iProcess user can also be given access to work queues as the:

Supervisor of a work queue.
Participant of a work queue.

For example, the following table illustrates the total number of work queues a user (swusr001) can access:

Work Queues that swusr001 has access to:

Personal Queue

swusr001

Group Queue

group1

Test User Queue

swusr001

Test Group Queue

group1

Supervisor of

swusr002, swusr003

Participant of

swusr002

Total number of work queues that swusr001 has access to:

7

From the previous example, you can see that the number of work queues a user can have access to can quickly increase if that user is a member of several groups and is a supervisor or participant of several queues.

This means it is important to plan in advance the number of work queues you want to create and how many supervisors and participants you are going to need. For example, if you create 17,000 work queues on TIBCO iProcess Engine, a single user cannot be a supervisor and a participant of all the work queues. This is because that user would then have access to 34,000 work queues which would exceed the limit.

If you do want to create a large number of work queues and if you want to assign supervisors and participants to the work queues, you would have to split them between more than one user. For example, if you had 17,000 work queues you could make:

swusr001 a participant of all 17,000 work queues
swusr002 a supervisor of all 17,000 work queues.