Author |
Message
|
RocknRambo |
Posted: Wed Aug 17, 2005 12:50 pm Post subject: WMWF 3.5 & WBISF |
|
|
Partisan
Joined: 24 Sep 2003 Posts: 355
|
do we have doucument where in it specifies the differences between the V3.5 and Server Foundation (Process Choreographer)
Are there any major differences... which cannot be done in v3.5.
any thoughts are appeciated
-RR |
|
Back to top |
|
 |
vennela |
Posted: Wed Aug 17, 2005 1:17 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
They are entirely different products and except that the concept is same. |
|
Back to top |
|
 |
guest123a |
Posted: Wed Aug 17, 2005 1:40 pm Post subject: |
|
|
Newbie
Joined: 16 Aug 2005 Posts: 8
|
|
Back to top |
|
 |
RocknRambo |
Posted: Wed Aug 17, 2005 7:36 pm Post subject: |
|
|
Partisan
Joined: 24 Sep 2003 Posts: 355
|
Agreeing they are differnet products... I'm looking any which cannot be done using V3.5 and WAS as a seperate instance...
or lemme put this way.. currently we have MQWKFL V3.5 & WAS 5.0.. our business team has come up proposal of a project where in workflow has to be used, IBM has come with using WBISF... our team has very less exposure to workflow.. so trying to understand.. Is there any scenario where V3.5 cannot handle and SF can...
any thoughts are appreciated
-RR |
|
Back to top |
|
 |
JLRowe |
Posted: Wed Aug 17, 2005 11:44 pm Post subject: |
|
|
 Yatiri
Joined: 25 May 2002 Posts: 664 Location: South East London
|
Here's a short list but I would suggest you prototype a project on both products so you can see for yourself:
* Staffing support is better in WF out of the box
* WF invokes services with a fixed format MQ message, if you need to invoke an existing service then you need to transform the message. WBISF can invoke different types of heterogeneous service
* WBISF is J2EE based, WF is native code
* WF is a more mature product (previous name was flowmark), has been around much much longer
* WBISF supports compensation and correlation of request/reply using business data
etc etc
If you have a more specific question then ask away... |
|
Back to top |
|
 |
jmac |
Posted: Thu Aug 18, 2005 5:32 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
RocknRambo wrote: |
currently we have MQWKFL V3.5 & WAS 5.0.. our business team has come up proposal of a project where in workflow has to be used, IBM has come with using WBISF... our team has very less exposure to workflow.. so trying to understand.. Is there any scenario where V3.5 cannot handle and SF can... |
As stated above the biggest difference you are looking at is MQWF is a proprietary system, where ProcessServer is based on J2EE. MQWF is an older, therefore, more mature product.
There are many little subtle differences in the modeling for the two products, and, it is my opinion that your MQWF models would definitely require some modification were you to move them to ProcessServer at a future time.
It is my opinion that Workflow technology is here to stay, your decision is really whether to use the more mature MQWF which will eventually go away, or to start in on ProcessServer, the latest Workflow engine avaialble from IBM (which in my opinion will have a longer shelf life than MQWF). _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
RocknRambo |
Posted: Thu Aug 18, 2005 5:49 am Post subject: |
|
|
Partisan
Joined: 24 Sep 2003 Posts: 355
|
Great.. this helps.
thanks for ur comments and suggestions.
-RR |
|
Back to top |
|
 |
|