| Author |
Message
|
| vennela |
 Posted: Thu Apr 14, 2005 1:44 pm Post subject: WBISF Process Choreographer: Staff |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
With PC, how should we deal with organizational structure. What I mean is, in workflow, we create users in buildtime and import them into runtime database and the users can be assigned work items. How do we achieve the same using process choreographer? I have found a sample on how to assign a work item to a particular user. But, I couldn't find anything about how users will be added to the PC runtime DB and all.
Can somebody point me to the documentation on where this is mentioned. |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu Apr 14, 2005 2:18 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Vennela:
I send you some PDFs that I found on the web a while back on Staffing in WPC to your email address. I am pretty sure one of them will have the answer.
Good Luck
WELL I tried to email them to you anyway... it got rejected cause the email address associated with your mqseries.net id is "disabled" or "discontinued"
Send me a PM with a good email address and Iwill send you the PDFs
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Apr 14, 2005 3:02 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I already sent you an alternate e-mail address.
Have you heard of any scalability issues on the number of users that we can have in PC. Workflow is not recommended for people not more than 10,000. Is this still the case with PC??? |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Apr 14, 2005 3:40 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Vennela:
I don't know enough about WPC to make any statment about performance. I have not seen anything written about number of users supported in WPC.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| JLRowe |
| Posted: Thu Apr 14, 2005 4:12 pm Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
It works on queries against a naming service (usually LDAP or active directory), the queries are expressed as XSL templates deployed on the server. The templates are compiled on deployment and the results are also cached so performance should be good.
Setting up a staffing model as rich as the mq workflow one would take quite a bit of work and managing the directory, although their are plenty of examples to work from. For me, this has turned out to be the greatest disadvantage of working with WPC against previous experience with MQ workflow.
Hope this helps. |
|
| Back to top |
|
|
| stubie |
| Posted: Mon Apr 18, 2005 6:10 am Post subject: Staff size recommendations |
|
|
Novice
Joined: 05 Nov 2001
Posts: 14
Location: Charlotte, NC
|
| Vennela -- where did you find the recommendation about MQWF not being good for user bases above 10000? I've looked for that for a while, and never could find anything nor get a commitment from IBM. We have a system with over 50000 defined users, although not more than 3000 are active at any particular time. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Apr 18, 2005 6:36 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| That is what we got when we asked IBM. IBM said that it is not a good idea to have that many users in runtime. 50,000 is acceptable but even 50,000 was not enough for us. Other than that, maintaining the runtime DB is not an easy task. Synchronizing the Active Directory and the runtime database for such number of users would then be a night mare. This is one of the things that Process Choreographer can claim to handle better than workflow. But, the ORG structure in PC may not be that rich as it can be i workflow. I am yet to explore the staff resolution capabilities of PC. |
|
| Back to top |
|
|
|
|
