Workflow Manual / Version 2301
Table Of Contents
The download tool fetches a process definition and, when existing, an associated JAR
from the Workflow Server and writes them into files.
usage: cm download -u <user> [other options]
[-f <definition path>]
[-j <jar path>] <process definition id or name>
available options:
-j,--jar <jar> file name for the workflow jar to
download
(default=processdefinition-<id>.jar)
-f,--definition <definition> file name for the
workflow definition to download
(default=processdefinition-<id>.xml)
-d,--domain <domain name> domain for login (default=<builtin>)
-p,--password <password> password for login
-u,--user <user name> user for login (required)
-url <ior url> url to connect to
The options have the following meaning:
| Parameters | Description |
|---|---|
-j
|
The name of the file into which the JAR file should be written. Default is processdefinition-<id>.jar.
If there is no custom JAR file associated with the process definition, this option is irrelevant.
|
-f
|
The name of the file into which the process definition should be written. Default is processdefinition-<id>.xml.
|
Table 3.2. Options of download
The downloaded process definition corresponds to the coremedia-workflow.dtd.
Example
You can use the Section 3.5.6, “Processdefinitions” tool to get the IDs of all workflow definitions that are uploaded to the Workflow Server. Then use, for example, the following call, where "1" is the ID of one of the uploaded workflow definitions:
./cm download -u admin -p admin 1
This will give you some output like:
Downloading '1' Wrote 'processdefinition-1.xml' (5112 bytes) Successfully downloaded 'coremedia:///cap/processdefinition/1' to 'processdefinition-1.xml'
The written file(s) can be found in the directory of the download tool.
