| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| sharing workflow configurations |
View previous topic :: View next topic |
| Author |
Message
|
| naresh |
 Posted: Thu Mar 03, 2005 9:01 am Post subject: sharing workflow configurations |
 |
|
Newbie
Joined: 03 Mar 2005
Posts: 3
|
We plan on sharing an existing workflow environment between multiple applications. Each application has a different process template using programs such as FMCNSHOW,FMCINTERNALNOOP etc. Each template uses a different data container.
Does anyone know of any issues/pitfalls that we need to look out for such as overwriting object definitions?”
Also are there concerns with volumes of messages going across the same set of queues? Combined total of 11000 process instances being created per day; possibly cleaned up once a week. |
|
| Back to top |
|
 |
| Ratan |
| Posted: Thu Mar 03, 2005 9:56 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Your scenario doesnot really require multiple Workflow Environments. You can just add multiple WF Systems to the same group to gain performance.
_________________
-Ratan |
|
| Back to top |
|
|
| naresh |
| Posted: Thu Mar 03, 2005 10:24 am Post subject: |
|
|
Newbie
Joined: 03 Mar 2005
Posts: 3
|
| yes, we plan on using a single environement which will be shared for multiple WF Systems, i was just wondering whether there were any conflict issues associated with programs/data structures that have the same name but different definitions. |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Mar 03, 2005 11:14 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| naresh wrote: |
| i was just wondering whether there were any conflict issues associated with programs/data structures that have the same name but different definitions. |
Well there are only 2 possible conflicts I can see, neither of which should cause a problem
FMCINTERNALNOOP, but the definition of this Program Object should be the same on all systems anyway.
Default Data Structure, unless you modified this structure to contain user defined members, this should be empty on all systems
You mention FMCNSHOW, there is no object that must have this name, so I can not see how there could be a conflict.
As to other "user defined" names, I would suggest that you use Process Categories, and be sure to have a rigid naming standard that uses some process model related identifier in front of each object.
To calculate load use the Performance spreadheet in support pac WP01
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| naresh |
| Posted: Thu Mar 03, 2005 7:28 pm Post subject: |
|
|
Newbie
Joined: 03 Mar 2005
Posts: 3
|
|
| 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
|
|
|
|
