[kepler-users] How to run kepler Command Line tool to generate provenance data

[Madhavi Tikhe]

Thanks for the reply.

I guess only way to pass on the parameters with kar file is to run the workflow from web services.
What do you think?

Madhavi

-----Original Message-----
From: Daniel Crawl [mailto:crawl at sdsc.edu] 
Sent: Friday, January 28, 2011 2:55 AM
To: Madhavi Tikhe
Cc: kepler-users at kepler-project.org
Subject: Re: [kepler-users] How to run kepler Command Line tool to generate provenance data


Hi Madhavi,

You can run a KAR from the command line:

kepler.sh -runwf -nogui workflow.kar.

None of the other options currently work for KARs.

You can set parameters:

kepler -runwf workflow.xml -x 4 -y "hello"

but only for xml workflows, not KARs.

   --dan


On 1/27/11 3:57 AM, Madhavi Tikhe wrote:
> Thanks Daneil.
> So this is possible to run the workflows from commandline. But I can use .kar file to run the workflows from command line? How can I pass on the parameters required by the workflow to run from command line?
>
> Thanks again,
> Madhavi
>
> -----Original Message-----
> From: Daniel Crawl [mailto:crawl at sdsc.edu]
> Sent: Thursday, January 27, 2011 12:32 AM
> To: Madhavi Tikhe
> Cc: kepler-users at kepler-project.org
> Subject: Re: [kepler-users] How to run kepler Command Line tool to generate provenance data
>
>
> Hi Madhavi,
>
> After some investigation, I found that it is possible to run multiple
> workflows from the command line:
>
> kepler.sh -runwf workflow1.xml workflow2.xml ...
>
> This appears to work for all command-line options except
> "-nogui -nocache".
>
>     --dan
>
>
> On 1/25/11 11:27 AM, Derik Barseghian wrote:
>> Hi Madhavi,
>>
>> I'm not aware of a way to have 1 kepler process launch and run 2 or more workflows in a row before quitting. You could simply run a series from command line like:
>> ant run-w...; ant run-w...; etc.
>> or write a script to loop through workflow files in a directory, and/or a cron job.
>>
>> On a somewhat related note, Jing has added a scheduler module to kepler, which allows you to schedule a workflow to run periodically on a remote kepler server. Any resulting run-kars from these executions are written into a kepler repository (currently MetaCat). This module is not yet released, but will probably be available in the near future.
>>
>> Derik
>>
>> On Jan 24, 2011, at 9:39 PM, Madhavi Tikhe wrote:
>>
>>> Thanks a lot for your reply Derik. It helped.
>>>
>>> When we talk about workflow execution from command line, it is possible to execute the two or more workflows in a batch (batch processing of the workflows)?
>>> Thanks again,
>>> Madhavi
>>>
>>> -----Original Message-----
>>> From: Derik Barseghian [mailto:barseghian at nceas.ucsb.edu]
>>> Sent: Tuesday, January 25, 2011 1:02 AM
>>> To: Madhavi Tikhe
>>> Cc: kepler-users at kepler-project.org
>>> Subject: Re: [kepler-users] How to run kepler Command Line tool to generate provenance data
>>>
>>> Hi Madhavi,
>>>
>>> Yes. The workflow must contain a ProvenanceRecorder, i.e. it must be saved from the GUI while using the provenance suite. Executions of this workflow will then write provenance data.
>>>
>>> Additionally, if you would like your execution to generate a "run-kar" containing some metadata about the execution and a report pdf upon completion, from within the reporting suite you should create a report design from the Reporting view and save to a kar, set keepResultantRunKars true in reporting/resources/configurations/configuration.xml, and then execute from the command line.
>>>
>>> There are a few ways to execute from command line. One is:
>>> ant run-workflow-no-gui-server -Dworkflow=/Users/derik/KeplerData/workflows/MyWorkflows/yourWorkflow.kar
>>>
>>> The resultant run-kar will be created in KeplerData/workflow-runs
>>>
>>> Derik
>>>
>>> On Jan 23, 2011, at 10:37 PM, Madhavi Tikhe wrote:
>>>
>>>> Hello,
>>>> I would like to run the Kepler from command line to execute a workflow. In this case is it possible to generate provenance data?
>>>> Regards,
>>>> Madhavi
>>>> DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
>>>>
>>>> _______________________________________________
>>>> Kepler-users mailing list
>>>> Kepler-users at kepler-project.org
>>>> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>>>
>>>
>>> DISCLAIMER
>>> ==========
>>> This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
>>
>> _______________________________________________
>> Kepler-users mailing list
>> Kepler-users at kepler-project.org
>> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>>
>
>
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
>


DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.