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 [-?] [-d <domain name>] [-f <file>] [-j <jar-file>]
       [-p <password>] -u <user name> [-url <ior url>] [-v]

available options:

 -?,--help                   Print usage information and quit.
 -d,--domain <domain name>   domain for login (default=<builtin>)
 -f,--definition <file>      file name for the workflow definition to
                             download (default=processdefinition-<id>.xml)
 -j,--jar <jar-file>         file name for the workflow jar to download
                             (default=processdefinition-<id>.jar)
 -p,--password <password>    password for login; you will be prompted for
                             password if not given
 -u,--user <user name>       user for login (required)
 -url,--url <ior url>        url to connect to
 -v,--verbose                enables verbose output

The options have the following meaning:

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

The output will tell you about the process definition identified from input (such as its name and ID) as well as the files written.

The written file(s) can be found by default in the directory of the download tool. To change the download location, consider providing a different path via --definition parameter and possibly --jar parameter, for additional process definition classes download.