In the in-memory deployment after starting and finishing workflows,
the Workflow Server sends the collected data for pending and finished processes to
the Studio server, where it is persisted in Studio's
in-memory persistence layer.
In order to connect to Studio, the Workflow Server
needs an authorized user. Therefore, configure the Workflow Server
to use the following properties. Additionally, disable CapLists for the
Workflow Server.
studio.url=http://<host>:<port>/<context> studio.user=<username> studio.password=<userpassword> workflow.usecaplist=false
You also have to exclude all Elastic dependencies from the Workflow Server, in order to prevent that MongoDB is used and not available. The following dependency has to be available in the Workflow Server web application.
<dependency> <groupId>com.coremedia.cms</groupId> <artifactId>cap-workflow-archive-memory</artifactId> <scope>runtime</scope> </dependency>
 |  |  |
 |