Return-Path: X-Original-To: apmail-oodt-dev-archive@www.apache.org Delivered-To: apmail-oodt-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D0A6E9342 for ; Tue, 12 Mar 2013 17:37:20 +0000 (UTC) Received: (qmail 62766 invoked by uid 500); 12 Mar 2013 17:28:03 -0000 Delivered-To: apmail-oodt-dev-archive@oodt.apache.org Received: (qmail 16894 invoked by uid 500); 12 Mar 2013 17:26:33 -0000 Mailing-List: contact user-help@oodt.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@oodt.apache.org Delivered-To: mailing list user@oodt.apache.org Received: (qmail 28720 invoked by uid 99); 12 Mar 2013 15:32:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 15:32:35 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [128.149.139.109] (HELO mail.jpl.nasa.gov) (128.149.139.109) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 15:32:29 +0000 Received: from mail.jpl.nasa.gov (ap-ehub-sp01.jpl.nasa.gov [128.149.137.148]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r2CFW8uU005295 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO) for ; Tue, 12 Mar 2013 08:32:09 -0700 Received: from AP-EMBX-SP40.RES.AD.JPL ([169.254.7.238]) by ap-ehub-sp01.RES.AD.JPL ([169.254.3.109]) with mapi id 14.02.0342.003; Tue, 12 Mar 2013 08:32:08 -0700 From: "Mattmann, Chris A (388J)" To: "user@oodt.apache.org" Subject: Re: Workflow2 - State Persistence Thread-Topic: Workflow2 - State Persistence Thread-Index: AQHOG0pACbGwNlIYWUi06kg8AnoUaZiiNuwA Date: Tue, 12 Mar 2013 15:32:08 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.1.130117 x-originating-ip: [128.149.137.113] Content-Type: multipart/alternative; boundary="_000_CD649801BCE82chrisamattmannjplnasagov_" MIME-Version: 1.0 X-Source-Sender: chris.a.mattmann@jpl.nasa.gov X-AUTH: Authorized X-Virus-Checked: Checked by ClamAV on apache.org --_000_CD649801BCE82chrisamattmannjplnasagov_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hey Mike, Workflow information (state, etc.) is persisted to the WorkflowInstanceRepo= sitory. In Wengine/Workflow2 support in trunk it makes heavy use of this, b= ut the support is evolving. I think for 0.6 I'll add some functionality and features (and would appreci= ate any help) to allow users to: 1. Specify in workflow.properties whether or not prior not completed (or= not "finished" category state) workflows should be cleared out and/or shou= ld be restarted and run on startup. Maybe a property like org.apache.oodt.c= as.workflow.engine.unfinishedWorkflows.complete=3Dtrue or false 2. Finish support in WorkflowInstanceRepository for persisting all new W= engine state information Those are the 2 items that should be done for 0.6 to support this feature. = It's on the roadmap just not fully done yet. Cheers, Chris From: , "Michael D (388J)" > Reply-To: "user@oodt.apache.org" > Date: Thursday, March 7, 2013 8:41 AM To: "user@oodt.apache.org" > Subject: Workflow2 - State Persistence Hi Chris and/or Brian, I'm currently on a project where PDS and AMMOS are joining forces to create= a pipeline service and we'd like to use the latest Workflow2 to do that. T= hey asked a question at last week's meeting regarding if the latest and gre= atest OODT Workflow will be able to do state persistence. I can let Paul Ra= mirez chime in any further details since he was at the meeting as well, but= can the latest and greatest Workflow do that? And if so, under which engin= e? I'm currently using the following engine: workflow.engine.factory =3D org.apache.oodt.cas.workflow.engine.ThreadPoolW= orkflowEngineFactory Thanks, Mike --_000_CD649801BCE82chrisamattmannjplnasagov_ Content-Type: text/html; charset="us-ascii" Content-ID: <8C9B1EC47C005C4DA837EA4309C61E9C@ad.jpl> Content-Transfer-Encoding: quoted-printable
Hey Mike,

Workflow information (state, etc.) is persisted to the WorkflowInstanc= eRepository. In Wengine/Workflow2 support in trunk it makes heavy use of th= is, but the support is evolving.

I think for 0.6 I'll add some functionality and features (and would ap= preciate any help) to allow users to:
  1. Specify in workflow.properties whether or not prior not completed (or n= ot "finished" category state) workflows should be cleared out and= /or should be restarted and run on startup. Maybe a property like org.apach= e.oodt.cas.workflow.engine.unfinishedWorkflows.complete=3Dtrue or false
  2. Finish support in WorkflowInstanceRepository for persisti= ng all new Wengine state information
Those are the 2 items that should be done for 0.6 to support this feat= ure. It's on the roadmap just not fully done yet.

Cheers,
Chris


From: <Cayanan>, "Michae= l D (388J)" <mich= ael.d.cayanan@jpl.nasa.gov>
Reply-To: "user@oodt.apache.org" <user@oodt.apache.org>
Date: Thursday, March 7, 2013 8:41 = AM
To: "user@oodt.apache.org" <user@oodt.apache.org>
Subject: Workflow2 - State Persiste= nce

Hi Chris and/or Brian,

I'm currently on a project where PDS and AMMOS are joining forces to create= a pipeline service and we'd like to use the latest Workflow2 to do that. T= hey asked a question at last week's meeting regarding if the latest and gre= atest OODT Workflow will be able to do state persistence. I can let Paul Ramirez chime in any further detai= ls since he was at the meeting as well, but can the latest and greatest Wor= kflow do that? And if so, under which engine? I'm currently using the follo= wing engine:

workflow.engin= e.factory =3D org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngineF= actory


Thanks,

Mike



--_000_CD649801BCE82chrisamattmannjplnasagov_--