火烧径-make life easier

As you've probably seen, the Shark has an admin and worklist handler applications that use Shark API to access it.
The clients access Shark server through the CORBA interface, which is defined in idl files that can be found within modules/SharkCORBA/idl.
These idl files are used to generate java classes that are put into shakcorba.jar. This jar is used by the server (to really implement  the methods for importing XPDL, starting processes, ...), and by Java clients to call these methods to perform wanted operations on server.
If you like to write the custom Java application, you have to include library sharkcorba.jar in your project, and use its interfaces to access Shark server.
First thing you have to do is to get the Shark server main object registered at the CORBA name server - you have to know the name server host name and port, as well as the name that Shark server uses to register itself (default settings are  host=localhost, port=10123, workflowServerName=SharkServer) -
look at the findWorkflowServer() method in the file SharkClient.java.
This WorkflowServer object is the one defined in the idl interface WorkflowService.idl.
The only method you can call on this object is
getWorkflowClientServiceObject() - so you should call it and retrieve this object.
Then you have to call the connect method of the WorlfowClientService object, and pass it login and password parameters, and if it is OK, you will be
connected to the Shark server, and be able to use all of the methods defined in WorkflowClientService interface (the methods for uploading and loading
XPDLs, getting all process definitions and the instantiated processes, ...).
This interface is the "key to the shark server". To load the package, you can use _openPackage() method, when you do that, you can get all process definitions by calling get_iterator_processmgr() method, and then you can select some process definition object and call its method createProcess(),etc...

The Shark API is not well documented, but you should look at the classes SharkServer, SharkClientService, SharkEngineManager and all WfXXXImpl classes. Also, read the OMG document http://www.omg.org/docs/formal/00-05-02.pdf - this file describes the interface implemented by Shark server (plus Shark server upgrades it, the
upgrades are defined in the WorkflowService.idl file).
Also, look at the way of how the Shark clients are written.

Greetings,
Sasa.