|
a/README.md |
|
b/README.md |
1 |
# Taverna2Archi OSGi Bundle
|
1 |
# Taverna-Provenance-Extractor v1.0
|
2 |
|
2 |
|
3 |
Link to the official website: http://www.ifs.tuwien.ac.at/dp/process/projects/tavernaExtractor.html
|
3 |
Link to the official website: ``http://www.ifs.tuwien.ac.at/dp/process/projects/tavernaExtractor.html``
|
4 |
|
4 |
|
5 |
This OSGi bundle encapsulates following feature: Converts a Taverna 2.4/2.5 worfklow to an Archimate model regarding specification 2.1.
|
5 |
Link to the repository ``https://opensourceprojects.eu/p/timbus/context-population/extractors/taverna-extractor``
|
6 |
|
6 |
|
7 |
## RUNTIME DEPENDENCIES
|
7 |
This program comes in two flavors:
|
|
|
8 |
|
|
|
9 |
* Standalone CLI
|
|
|
10 |
* OSGi Bundle
|
|
|
11 |
|
|
|
12 |
## USING THE STANDALONE CLI
|
|
|
13 |
|
|
|
14 |
The standalone CLI version encapsulates two different features:
|
|
|
15 |
|
|
|
16 |
* Feature A: Converts a Taverna 2.4 worfklow to an Archimate model.
|
|
|
17 |
* Feature B: Accesses provenance data captured during a Taverna 2.4 workflow run,
|
|
|
18 |
applies DROID on that capturing (to identify used file formats in the workflow) and generates
|
|
|
19 |
a CSV report (including e.g., file formats). Extends an existing Domain Specific Ontology (DSO)
|
|
|
20 |
with file format information identified by DROID.
|
|
|
21 |
|
|
|
22 |
### Interacting with the standalone CLI version
|
|
|
23 |
|
|
|
24 |
A => -i,--inputFile <arg> ...specifies the taverna t2flow (input) file. \path\to\taverna\input.t2flow
|
|
|
25 |
-o,--outputFile <arg> ...specifies the archimate (output) file. \path\to\archimate\output.archimate
|
|
|
26 |
|
|
|
27 |
|
|
|
28 |
B1 => -d,--droid <arg> ...\path\where\to\save\droidOutputFile
|
|
|
29 |
|
|
|
30 |
B2 => -cr,--report <arg> ...\path\where\droidOutputFile\is\located
|
|
|
31 |
|
|
|
32 |
B3 => -ont,--ontology-file <arg> ...ontology to extend. \path\to\ontology
|
|
|
33 |
-r,--reportFile <arg> ...generated DROID CSV report.
|
|
|
34 |
|
|
|
35 |
(general) -v, verbose ...enable verbose mode
|
|
|
36 |
|
|
|
37 |
### Sample usage
|
|
|
38 |
|
|
|
39 |
[A] Convert a Taverna Workflow to an Archimate Model:
|
|
|
40 |
|
|
|
41 |
java -jar TavernaExtractor.jar -i \path\to\TavernvaWorkflowInputFile.t2flow -o \path\to\ArchimateOutputFile.archimate
|
|
|
42 |
|
|
|
43 |
[B] Extract including file formats from Workflow and identify them with DROID. In the following the 3 necessray steps are presented:
|
|
|
44 |
ATTENTION: Due to its DROID dependencies, make sure you are executing the TavernaExtractor.jar in the respective directory!!
|
|
|
45 |
|
|
|
46 |
[B1] Running DROID identififaction on collected Taverna Workflow Run data:
|
|
|
47 |
INPUT: path to file which gets created.
|
|
|
48 |
OUTPUT: file containing DROID identification information in a none readable form.
|
|
|
49 |
|
|
|
50 |
java -jar TavernaExtractor.jar -d path\to\myDroidFile.droid
|
|
|
51 |
|
|
|
52 |
Sample Output:
|
|
|
53 |
===== [ID] | [Workflow Name (Timestamp)] ===== | 2 entries found.
|
|
|
54 |
|
|
|
55 |
[1] MusicClassificationExperiment (2013-09-25 13:11:42.488)
|
|
|
56 |
[2] MusicClassificationExperiment (2013-09-23 10:44:43.839)
|
|
|
57 |
Your choice: //Enter an ID to process
|
|
|
58 |
|
|
|
59 |
[B2] Generate a CSV report out of a DROID profile: (CSV report is stored in the same directory as the *.droid input file)
|
|
|
60 |
INPUT: file from step [B1].
|
|
|
61 |
OUTPUT: file in CSV format containing DROID information in a readable form.
|
|
|
62 |
|
|
|
63 |
java -jar TavernaExtractor.jar -cr path\to\myDroidFile.droid
|
|
|
64 |
|
|
|
65 |
[B3] Extend existing ontology with information about the used file formats in the workflow run:
|
|
|
66 |
INPUT1: existing OWL file, which should be extended.
|
|
|
67 |
INPUT2: file from step [B2].
|
|
|
68 |
OUTPUT: updates OWL file from INPUT1.
|
|
|
69 |
|
|
|
70 |
java -jar TavernaExtractor.jar -ont \path\to\myOntology.owl -r \path\to\myDroidCSVreportFile.droid.csv
|
|
|
71 |
|
|
|
72 |
### Build and Execution
|
|
|
73 |
|
|
|
74 |
1. Clone the current project from ``https://opensourceprojects.eu/p/timbus/context-population/extractors/taverna-extractor``.
|
|
|
75 |
2. Change in the checked-out directory.
|
|
|
76 |
3. Adapt the ``TavernaExtractor.properties`` file.
|
|
|
77 |
4. Use maven (``mvn package -DskipTests=true -Pstandalone``) to package the program.
|
|
|
78 |
5. Change to the 'target' directory.
|
|
|
79 |
6. Run the executable with ``'java -jar TavernaExtractor.jar <args>'``.
|
|
|
80 |
|
|
|
81 |
### Runtime Dependencies
|
8 |
|
82 |
|
9 |
* JRE 1.7+
|
83 |
* JRE 1.7+
|
10 |
* Apache Ant 1.9+ for building
|
84 |
* Apache Ant 1.9+ for building
|
11 |
* DOT (comes with Graphviz). Is not mandatory
|
85 |
* DOT (comes with Graphviz)
|
|
|
86 |
|
|
|
87 |
## USING THE OSGi TIMBUS testbed BUNDLE
|
12 |
|
88 |
|
13 |
## MANADATORY PARAMETERS
|
89 |
The OSGi bundle can be accessed at ``http://testbed.timbusproject.net:3001/``
|
14 |
|
90 |
|
15 |
* Path to the Taverna workflow input file (*.t2flow)
|
91 |
It encapsulates following feature: Converts a Taverna 2.4/2.5 worfklow to an Archimate model regarding specification 2.1.
|
16 |
* Path to the generated output file (*.generated.archimate)
|
92 |
|
|
|
93 |
### Mandatory Parameters
|
|
|
94 |
|
|
|
95 |
* fqdn ... IP of the remote address (e.g. ``134.191.240.68``)
|
|
|
96 |
* port ... Port of the remote machine (e.g. ``10026``)
|
|
|
97 |
* user ... Username Credentials (e.g. ``timbus``)
|
|
|
98 |
* password ... Password Credentials (e.g. ``timbus``)
|
|
|
99 |
* inputFileName ... Path to the Taverna workflow input file (e.g. ``/home/timbus/Documents/imagemagick_wf.t2flow``)
|
|
|
100 |
* archimateOutputPath ... Path to the generated output file (e.g. ``/home/timbus/Documents/imagemagick.contextmodel.archimate``)
|
|
|
101 |
* tavernaHome ... Path to Taverna Home directory (e.g. ``/home/timbus/.taverna-2.4.0``)
|
|
|
102 |
|
|
|
103 |
### Build
|
|
|
104 |
|
|
|
105 |
The bundle can also be build using maven ``mvn package -DskipTests=true -POSGi``
|
17 |
|
106 |
|
18 |
## SUPPORTED TAVERNA ACTIVITIES
|
107 |
## SUPPORTED TAVERNA ACTIVITIES
|
19 |
|
108 |
|
20 |
At the moment, the following activitied are supported.
|
109 |
At the moment, the following activitied are supported.
|
21 |
|
110 |
|