Workflow Manual / Version 2512.0
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:
Options Description
-d, --domain <domain name> domain for login
(default=<builtin>)
-f, --definition <definition> file name of the workflow
definition to upload
-g, --grpc-endpoint <gRPC endpoint> gRPC endpoint to connect to
--grpc-wfs-endpoint <WFS gRPC endpoint> gRPC endpoint of Workflow
Server to connect to
--http-base-uri <HTTP base URI> HTTP base URI of Content
Server where HTTP servlets
are provided (e.g. blob
servlet)
-j, --jar <jar> file name of the workflow jar
to upload (deprecated)
-n, --names <names> filenames of the built-in
workflows to upload
-p, --password <password> password for login; you will
be prompted for password if
not given
-u, --user <user name> user for login (required)
--url <ior url> url to connect to
-v, --verbose enables verbose output
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. |
-j
|
Deprecated:
Specify an optional JAR file which contains custom resources for your workflow.
Required classes should be added to the classpath of the Workflow Server
instead. This option cannot be used with the default configuration of the
Workflow Server, which disables JAR uploads
(see property workflow.server.use-uploaded-jar).
Also, it is only useful in combination with the -f option
for custom workflows. The standard workflows don't need additional resources.
|
Table 3.5. 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 classpath of the Workflow Server. Only
if a class with a given name is not found there, then it will be read from an uploaded JAR file,
if not disabled with configuration property workflow.server.use-uploaded-jar.
See also Section 6.7, “Managing Process Definitions” in Unified API Developer Manual.
