| Author |
Message
|
| workflowdude |
 Posted: Mon Nov 17, 2003 10:10 am Post subject: workflowclient API vs workflow API |
 |
|
Novice
Joined: 17 Nov 2003
Posts: 24
Location: US
|
Hi everybody,
I am new to workflow, been working on it since last 3 weeks. I have a question regarding accessing workflow from JSP's or servlets's.
From my findings I have found that there are 2 ways to access workflow. One is to customize the webclient that is provided by IBM and another one is to write your own componenet from scratch implementing workflow API's.
Can anybody please list down the advantages/limitations of each of the above approaches? and in which scenarios they could be used.
Thanks
WFDude |
|
| Back to top |
|
 |
| dsim |
| Posted: Mon Nov 17, 2003 7:23 pm Post subject: |
|
|
Acolyte
Joined: 11 Aug 2003
Posts: 67
Location: Toronto
|
I would suggest starting with the out of the box WebClient: playing with it, reading the its documentation.
Advantages:
- already done
- easy to customize (see docs and the related SupportPacs)
- supported by IBM
- community (as this forum) ready to help you from previous experience
Limitations:
- cannot satisfy all possible requirements
After that, you can look at the programming guide to get familiar with the workflow APIs and also estimate the effort required to write a new WebClient from scratch.
Advantages:
- the new WebClient will satisfy (hopefully) all the requirements
Disadvatages:
- time/resources to design/implement/test such a new application |
|
| Back to top |
|
|
| workflowdude |
| Posted: Wed Nov 19, 2003 10:09 am Post subject: |
|
|
Novice
Joined: 17 Nov 2003
Posts: 24
Location: US
|
| I presume all the workflow API's will be wrapped under the workflow client API. What kind of requirements are you talking about? |
|
| Back to top |
|
|
| dsim |
| Posted: Wed Nov 19, 2003 11:18 am Post subject: |
|
|
Acolyte
Joined: 11 Aug 2003
Posts: 67
Location: Toronto
|
| I was talking about customer requirements |
|
| Back to top |
|
|
| workflowdude |
| Posted: Tue Dec 02, 2003 7:38 am Post subject: workflowclient API vs workflow API |
|
|
Novice
Joined: 17 Nov 2003
Posts: 24
Location: US
|
Are there any specific things that you can do using Workflow API and not do using Workflow client API? I thought workflow client API encapsulates all the possible things you require from workflow
Thanks |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Dec 04, 2003 4:08 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
The Workflow Html Client api, does not wrap the entire MQWF API, so there are many things that can be done with the MQWF API that are not done directly by the HTML Client API. However, I do not think this is a problem ans the intent of the Html Client api is to show you how a client can be written, and it can be easily extended to add any MQWF API functionality that you need.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| workflowdude |
| Posted: Thu Dec 04, 2003 4:39 pm Post subject: |
|
|
Novice
Joined: 17 Nov 2003
Posts: 24
Location: US
|
| you are right. but using the webclient would mean you always have to go through the "main" servlet provided. and i guess that servlet cannot be customized... |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Dec 04, 2003 5:12 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I agree, you could always write your own main servlet 
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| dsim |
| Posted: Sat Dec 06, 2003 8:11 pm Post subject: |
|
|
Acolyte
Joined: 11 Aug 2003
Posts: 67
Location: Toronto
|
| Quote: |
| ... but using the webclient would mean you always have to go through the "main" servlet provided. |
this is right
| Quote: |
| ... and i guess that servlet cannot be customized... |
"Main" servlet can be customized: plugins like command handler, on logon, viewer or WA84 SupportPac |
|
| Back to top |
|
|
|
|
