Relationship between Web UI and Kepler Web Service

We implemented a Kepler Web service which may be useful for the WebUI group. You can access the Web service at https://code.kepler-project.org/code/kepler/modules/webservice/trunk. The Web service includes two sets of operations:

The first set of operations can execute Kepler workflows and get results from the outputs of the operations. It is suitable for short-term execution.

• executeByAttach

• executeByAttachWithPara

• executeByURI

• executeByURIWithPara

• executeByContent

• executeByContentWithPara

The second set of operations can firstly start workflow execution, monitor its status, steer its execution, and get results at last. It is suitable for long-term execution.

• startExeByURI

• startExeByURIWithPara

• startExeByAttach

• startExeByAttachWithPara

• startExeByContent

• startExeByContentWithPara

• getResults

• getResultsByAttach

• getExecutionStatus

• resumeExecution

• stopExecution

• pauseExecution

These operations are similar to the message to "job manager" of the document "Requirements for Kepler web client support". So I think the Web service is useful for WebUI group.

One thing I don't get is the 'input/output data manager'. Are they used to prepare input data and distribute output data, or just specify the resource of input data and the target of output data? The Web service can be executed with parameter configuration, which means the data resource and target can be specified in this way.

G'Day Jianwu...this looks very intersting.

Are you still active with this code? (the link above is dead)

What's the current status? Are there any live examples to share?

Thanks indeed,
JB

Hi, John:

We moved the code to https://code.kepler-project.org/code/kepler/trunk/modules/kepler-run-engine

We are going to release the product soon.

Thanks,

Jing

where can i find the kepler-run-engine.war ?