Mail Archive Home | shark List | September 2003 Index
| <-- Date Index --> | <-- Thread Index --> |
Hi, 1. Using shark you can overcame various business problems. For every particular business process, you can write an XPDL process that represent it (of course there are some rules when creating xpdl presentations of real business process, you have to read the XPDL specification, and learn more about Workflows). 2. The advantage of using Shark is that you do not need to write new servlet/jsp when you need to model new Business process - you just write an XPDL file describing this process (look at JaWE, our graphical XPDL editor used in Shark admin application at http://jawe.enhydra.org). Also, I don't know if you can distribute the workitems using servlet/jsp technology. Shark server distributes the work to the proper users that are logged on server. When some user finishes its work, he sets some process variables that determines the further process flow. The Shark server based on these variables determines who are the next users that should get the work. Also, you can run many processes in Shark server concurrently, i.e. you can run 5 instances of the main business_example process (Each instance for the new order), and at the same time you can instantiate some of processes from test.xpdl. 3. Currently the Shark does not have much documentation (all Shark documents you can find under doc directory - I think that sharkclientinfo.txt is the most useful), and you can go to the http://www.wfmc.org to read more about WfMC workflow specifications, particularly the documents http://www.wfmc.org/standards/docs/tc003v11.pdf - Workflow Referenc Model (it gives the big picture of WfMC workflow specifications and workflow technology at all), http://www.wfmc.org/standards/docs/TC-1025_10_xpdl_102502.pdf - XPDL specification (it defines how the xpdls should be created, the JaWE implements this specification), http://www.wfmc.org/standards/docs/if2v20.pdf - the client API (the description of what an engine should implement), http://www.omg.org/docs/formal/00-05-02.pdf - OMG specification for engine implementation in Object Oriented languages. 4. Maybe the business example is to complicated, but it shows the pretty real example of some business process flow. If you have some real business process, you can describe it, and we could try to implement it in XPDL, and then let you execute in Shark server. Hope I helped a little! Regards, Sasa. ----- Original Message ----- From: "arijit debbarman" <arijitdb@xxxxxxxxx> To: <Shark@xxxxxxxxxxx> Sent: Tuesday, September 30, 2003 11:08 AM Subject: Shark: Why should I use shark/xpdml > Hello, > we are at present using Jsp/servlet environment for development process.Now after coming to know about the Sahrk project I had seen it.Till now it clear how to use shark in our roject but I would like to clarify some points regarding shark and xpdl. > > 1. what type of business problems can be overcome with using shark and xpdl. > 2.If they can be solved using servlet/jsp then what are the advantages of using shark/xpdl over them. > 3.where to find help regarding shark/xpdml. > 4.I think the present example regrding business_example.xpdl is bit complicated and vast can anybody point out the key features upon which should I focus right now to have clear understanding of shark and xpdl. > > bye > -- > ______________________________________________ > http://www.india.com > Now with POP3/SMTP access for only US$14.95/yr > > Powered by Outblaze > _______________________________________________ > Shark mailing list > Shark@xxxxxxxxxxx > http://support.enhydra.org/mailman/listinfo.cgi/shark >
| <-- Date Index --> | <-- Thread Index --> |
Powered by MHonArc.
Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.