There is no limitation on the number of users in PGs, it is recommended to keep the number as low as possible and only tests in your environment can give an answer on the number of users in PG that your system can bare.
Usually it is recommened to perform capacity planning, tests and check whether tests results meet SLA on user response, number of concurrent and the like the best practice says to assign Human tasks to fine-graned PGs and to never assign Human tasks to "All users", the reason behind this recommendation is because it is a known fact that assignments to "all users" might lead to performance degradation.
Options to create PGs :
"IBM Business Process Manager Security Concepts and Guidance"
http://www.redbooks.ibm.com/redbooks/pdfs/sg248027.pdf
4.2.5 Mapping roles to groups
Usually it is recommened to perform capacity planning, tests and check whether tests results meet SLA on user response, number of concurrent and the like the best practice says to assign Human tasks to fine-graned PGs and to never assign Human tasks to "All users", the reason behind this recommendation is because it is a known fact that assignments to "all users" might lead to performance degradation.
Options to create PGs :
1. Create a Participant Group and then add users to this group manually via ProcessDesigner
2. Create a Participant Group, create an internal BPM group in ProcessAdmin/Group Management page and include that BPM group into the created PG, then you may add users to the BPM group via ProcessAdmin
The latter is preferred as more flexible and convenient approach.
Refer following red book for more information. "IBM Business Process Manager Security Concepts and Guidance"
http://www.redbooks.ibm.com/redbooks/pdfs/sg248027.pdf
4.2.5 Mapping roles to groups
No comments:
Post a Comment