|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
SystemGrp and Systems Design approach |
« View previous topic :: View next topic » |
Author |
Message
|
satboppana |
Posted: Tue Jan 27, 2004 8:30 am Post subject: SystemGrp and Systems Design approach |
|
|
Acolyte
Joined: 20 Dec 2001 Posts: 64
|
Hi All,
Our topology is as follows:
One Domain
One SystemGRP
One System
Two Process Models for locations A & B.
One Database.
Users are authorized by category (One for each location A & B)
Virtual User Design is implemented.
Now I want to add a third process model for a third location C.
What is the best way to go with?
Before i do that is it optimal to create a second system for the
B process model and Category and then proceed with a third
system which may comprise the C process model and C Category.
I need to share only one database.
As i create new systems i know that i can have their own EXEC &
ADMIN servers which can improve performance.
But apart from that does the user resolution also get improved by
selecting local users in the Staff Assignment.
But by implementing the virtual user concept are we not acheiving
that.
We are on WF3.4 , MQ 5.3 and DB2 7.2 .
ANy inputs and suggestios appreciated!! _________________ Sb |
|
Back to top |
|
 |
vennela |
Posted: Tue Jan 27, 2004 9:10 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
B process model and Category and then proceed with a third
system which may comprise the C process model and C Category.
|
Usually you shouldn't need a new system for every category. Process models are available at the GROUP level and you CANNOT assign (or attach) one process to always run on the same system or execution server every time (I believe you can assign a flow to one or more execution groups in WMQI and I am trying to correlate that concept here).
Quote: |
But apart from that does the user resolution also get improved by
selecting local users in the Staff Assignment.
|
Again, there is no concept of local user. If a user exists in workflow he can lgon to to workflow by specifying any SYSTEM.
Hope this answers most of your questions. |
|
Back to top |
|
 |
satboppana |
Posted: Tue Jan 27, 2004 9:40 am Post subject: Sytems Design |
|
|
Acolyte
Joined: 20 Dec 2001 Posts: 64
|
Hi Venny,
So from your answers it mean that all the process models are available
to all the SystemGroups but can be narrowed down by category.
So do you think that the current design should be fine with adding a new
process model using the same system.
Any plan of publishing your original picture instead of a fake one
Just Kidding.
Thanks
Satya _________________ Sb |
|
Back to top |
|
 |
vennela |
Posted: Tue Jan 27, 2004 10:15 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
to all the SystemGroups |
To all the SYSTEMs in a SYSTEM GROUP.
You should be fine by adding new process models. If you find the "Concepts and Architecture" manual, you should give that a quick reading
Quote: |
Any plan of publishing your original picture instead of a fake one |
NO, that will make the number of private messages I get to ZERO. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|