Running Workflows using Taverna Server

[Nitish Kundala <ni...@gmail.com>]

Hi,
I have been reading up to work on the Issue - 1033
<https://issues.apache.org/jira/browse/TAVERNA-1033> and have understood
the following. (Any advice or corrections would be appreciated)

I have been through the documentation
<https://docs.google.com/document/d/1G3AmW-zgsOxNg81uOWOUVISfaimp9Ku5k1ntIFm8hvo/edit>
of the Taverna Mobile app and understood the following:
1)The Taverna Player JSON API
<https://github.com/taverna-extras/taverna-player/wiki/JSON-API-Documentation>
is used to run the workflows.
2)Taverna Player is currently capable of running only type two workflows.
3)On clicking the run button we receive a WorkflowRunTask, the user can
enter the required parameters specific for the run.
4)Then the app creates a RunTask which then waits for the result and the
user can download the results.

So as I understand it, the changes that are to be made are:
1) The login that currently goes via the the Taverna Player Portal needs to
go via the Taverna Server.
2) The uploading of the workflow content has to be done to the Taverna
Server to run.
3) Getting of the workflow details of the ones that were run also has to be
rerouted.

So basically the TavernaPlayerService.java
<https://github.com/apache/incubator-taverna-mobile/blob/master/app/src/main/java/org/apache/taverna/mobile/data/remote/TavernaPlayerService.java>
Interface has to be replaced. And there have to be made certain changes in
the API call structure.
I have been going through the Taverna Server
<https://taverna.incubator.apache.org/documentation/server/3.1/usage>
Documentations and trying to map the required calls.


Thanks and Regards,

*Nitish Kundala* .

Re: Running Workflows using Taverna Server

[Sagar <ku...@gmail.com>]

Hi,

On Sat, Mar 3, 2018 at 1:03 PM, Nitish Kundala <ni...@gmail.com> wrote:

> Hi,
> I have been reading up to work on the Issue - 1033
> <https://issues.apache.org/jira/browse/TAVERNA-1033> and have understood
> the following. (Any advice or corrections would be appreciated)
>
> I have been through the documentation
> <https://docs.google.com/document/d/1G3AmW-zgsOxNg81uOWOUVISfaimp9Ku5k1nt
> IFm8hvo/edit>
>

The documentation is outdated. So please don't rely on it.


> of the Taverna Mobile app and understood the following:
> 1)The Taverna Player JSON API
> <https://github.com/taverna-extras/taverna-player/wiki/
> JSON-API-Documentation>
> is used to run the workflows.
> 2)Taverna Player is currently capable of running only type two workflows.
> 3)On clicking the run button we receive a WorkflowRunTask, the user can
> enter the required parameters specific for the run.
> 4)Then the app creates a RunTask which then waits for the result and the
> user can download the results.


Currently app download the workflow from myexperiment and upload it to
taverna player portal and then app show taverna player portal in WebView.
So, Now this project idea is to eleminated the the webview in which we have
to wait for result on the basis on input and also to eleminate the
middleware taverna player portal.





> So as I understand it, the changes that are to be made are:
> 1) The login that currently goes via the the Taverna Player Portal needs to
> go via the Taverna Server.
> 2) The uploading of the workflow content has to be done to the Taverna
> Server to run.
> 3) Getting of the workflow details of the ones that were run also has to be
> rerouted.
>
> So basically the TavernaPlayerService.java
> <https://github.com/apache/incubator-taverna-mobile/blob/
> master/app/src/main/java/org/apache/taverna/mobile/data/
> remote/TavernaPlayerService.java>
> Interface has to be replaced. And there have to be made certain changes in
> the API call structure.
> I have been going through the Taverna Server
> <https://taverna.incubator.apache.org/documentation/server/3.1/usage>
> Documentations and trying to map the required calls.
>
>
> Thanks and Regards,
>
> *Nitish Kundala* .
>

-- 

Warmest regards
Sagar