Workflow Manual / Version 2512.0
Table Of ContentsThere are some tools that help you to work with the Workflow Server.
General usage in a Windows 64-bit environment
The server utilities can be started using the cm64.exe command in a
Windows 64-bit environment with a JVM 64-bit, as described in the
Operations Basics.
General usage
The CoreMedia system supports gRPC and CORBA for internal communication. While servers always offer both protocols for clients to connect, server utilities can be configured to use either gRPC or CORBA. The protocol can be chosen freely on each start of a component. Currently, CORBA is the default protocol.
Note
With release 2512.0 of the CoreMedia system, the Workflow Server does not yet offer gRPC services to its clients. Activating gRPC on server utilities connecting to the Workflow Server won't do any harm as long as these are of release 2512.0, too. Future clients, though, will fail to connect to this Workflow Server if gRPC is active on them.
Keep this in mind when operating a mixed-release CoreMedia system setup. In such scenarios (e.g., during upgrades), it is recommended to leave clients in their default protocol mode which is CORBA.
To activate gRPC on a Workflow Server utility, export environment variable REPOSITORY_USEGRPC
set to true or precede the command with a local variable definition.
You then have to specify the gRPC endpoint of the Content Server to connect to with option -g
and the IOR URL of the Content Management Server with option -url. Example:
> REPOSITORY_USEGRPC=true \ cm start -u admin -p admin \ -url http://content-management-server:40180/ior \ -g content-management-server:40165 \ -pn Synchronization
Alternatively to the command line options -g and -url, you may also use
environment variables. Example:
> REPOSITORY_USEGRPC=true \ REPOSITORY_URL=http://content-management-server:40180/ior \ SPRING_GRPC_CLIENT_CHANNELS_CAP_ADDRESS=content-management-server:40165 \ cm start -u admin -p admin -pn Synchronization
| Parameter | Description |
|---|---|
-u <name>
| The name of the user |
-d <domain>
| The domain of the user (optional, only for LDAP users) |
-g <gRPC endpoint>
| The gRPC endpoint of the Content Server (optional). Using this option is equivalent to
defining Spring Boot property spring.grpc.client.channels.cap.address. The tool option
takes precedence over the Spring Boot property. |
--http-base-uri <HTTP base URI>
| HTTP base URI of Content Server where HTTP servlets are provided (e.g. blob servlet) (optional). This option is irrelevant for Workflow Server utilities. |
--grpc-wfs-endpoint <WFS gRPC endpoint>
| The gRPC endpoint of the Workflow Server (optional). This option is only effective for
releases after 2512.0 as the Workflow Server currently does not offer gRPC services to its
clients. Using this option is equivalent to
defining Spring Boot property spring.grpc.client.channels.wf.address. The tool option
takes precedence over the Spring Boot property. |
-p <password>
| The password of the user (optional). Using this option is equivalent to
defining Spring Boot property repository.password. The tool option
takes precedence over the Spring Boot property. If you don't specify the password at all,
the tool will prompt for it at runtime. |
--url <ior url>
| The IOR URL of the content server (optional). Using this option is equivalent to
defining Spring Boot property repository.url. The tool option
takes precedence over the Spring Boot property. If not specified otherwise, the
URL is taken from file capclient.properties. |
Table 3.1. Common options of server utilities
