ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » workflowclient API vs workflow API

Post new topic  Reply to topic
 workflowclient API vs workflow API « View previous topic :: View next topic » 
Author Message
workflowdude
PostPosted: Mon Nov 17, 2003 10:10 am    Post subject: workflowclient API vs workflow API Reply with quote

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
View user's profile Send private message
dsim
PostPosted: Mon Nov 17, 2003 7:23 pm    Post subject: Reply with quote

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
View user's profile Send private message
workflowdude
PostPosted: Wed Nov 19, 2003 10:09 am    Post subject: Reply with quote

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
View user's profile Send private message
dsim
PostPosted: Wed Nov 19, 2003 11:18 am    Post subject: Reply with quote

Acolyte

Joined: 11 Aug 2003
Posts: 67
Location: Toronto

I was talking about customer requirements
Back to top
View user's profile Send private message
workflowdude
PostPosted: Tue Dec 02, 2003 7:38 am    Post subject: workflowclient API vs workflow API Reply with quote

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
View user's profile Send private message
jmac
PostPosted: Thu Dec 04, 2003 4:08 pm    Post subject: Reply with quote

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
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
workflowdude
PostPosted: Thu Dec 04, 2003 4:39 pm    Post subject: Reply with quote

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
View user's profile Send private message
jmac
PostPosted: Thu Dec 04, 2003 5:12 pm    Post subject: Reply with quote

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
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
dsim
PostPosted: Sat Dec 06, 2003 8:11 pm    Post subject: Reply with quote

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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » workflowclient API vs workflow API
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.