Workflow Manual / Version 2301
Table Of Contents
With the upload tool you can add new process definitions to the workflow
server.
usage: cm upload -u <user> [other options]
[-f <definition path> [-j <jar path>] |
-n <name1> <name2> ...]
available options:
-n,--names <names> names of built-in workflows to upload
-d,--domain <domain name> domain for login (default=<builtin>)
-f,--definition <def> file name of the workflow definition to
upload
-j,--jar <jar> file name of the workflow jar to upload
-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 |
|---|---|
-n
|
Specify workflows by filename (such as
studio-two-step-publication.xml). This works only for the
standard workflows which are delivered with the
CoreMedia CMS.
|
-f
| Specify the XML file which contains the process definition. This option is available only if your CoreMedia CMS license includes the usage of custom workflows. |
-j
|
Specify a JAR file which contains all resources (esp. custom actions) your workflow
needs. You need this option only in combination with the -f option for
custom workflows. The standard workflows don't need additional resources.
|
Table 3.4. Options of upload
If a process definition with the name of the uploaded process definition exists already, that definition is superseded by the uploaded definition. Process instances of the old definition run to completion, but additional instances are built using the new definition.
If your process definition references custom Java classes, such classes are preferentially
loaded from the JAR files located in the Workflow Server's lib directory. Only
if a class with a given name is not found there, the server will read the uploaded JAR.
If you upload all custom classes with the process definition and refrain from deploying jars
at the Workflow Server, it becomes easier to use updated versions of the classes. In this
case the new classes will only be used with the new definition, while the existing
definitions and instances use the original versions. Therefore, it is not necessary to run
the tool cm workflowconverter to resolve possible serialization issues.
