close

Filter

loading table of contents...

Blueprint Developer Manual / Version 2107

Table Of Contents

4.2.4.2 In-Memory configuration for the Workflow Server

In the in-memory deployment the Workflow Server sends pending and finished processes to Studio, where they are persisted in the Studio's in-memory persistence layer. In order to connect to Studio, the Workflow Server needs a Studio connection and an authorized user.

The recommended way to enable the in-memory configuration for Workflow Server, is to create a Spring application configuration file, like application-inmemory.properties, add the necessary configuration properties and start the Workflow Server web app with the corresponding Spring profile name (in this case with the profile name inmemory).

The configuration file has to contain these settings:

elastic.core.persistence=memory

studio.host=localhost
studio.http.port=41080
studio.context=studio

studio.user=admin
studio.password=admin

repository.caplist.connect=false

Alternatively, the properties above also can be set using corresponding environment variables (written in upper case, appropriate for Spring relaxed binding). This approach may come in handy in a container environment like docker. The blueprint workspace contains a docker-compose YAML file, which may serve as a starting point: global/deployment/docker/compose/in-memory.yml

Please note, that you may need to adapt the values for studio.host, studio.http.port and studio.context.

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.