Configure shared services

Shared services are software services that are required only when a workflow is published in asynchronous mode.

Shared services are present in the published workflow, but not represented visually in the diagram, they don't have a corresponding hexagon.
Being instantiated as hidden blocks of the workflow, they require computing resources (CPU, RAM) like other processing blocks.

To configure shared services, select Shared services on the editor toolbar. The Shared services pop-up appears. It contains one or more of these tabs, each corresponding to a service with the same name:

• Script Interpreter
• Proxy Legacy
• Output Producer

The Script Interpreter service supports the interpretation of scripts. It is required—and the corresponding tab is displayed—when the workflow contains at least one block of one of the following components:

• Python Interpreter
• JavaScript Interpreter
• Switch
• Map

Proxy Legacy allows using old components that are not compatible with the latest implementation of asynchronous mode. The corresponding tab appears automatically only if such components are used in the workflow.

Output Producer takes care of orchestrating the production of output inside the workflow. It is always needed for asynchronous mode and so the corresponding tab is always displayed.

In the tabs of the Shared services pop-up you set the properties of the shared services that are needed by the workflow. The properties are the same for all the services and are:

• Timeout: execution timeout expressed in minutes (m) or seconds (s).
• Replicas: number of required instances.
• Memory: required memory expressed in mibibytes, gibibytes or other units of choice.
• CPU: thousandths of a CPU required (for example: 1000 = 1 CPU).
• Consumer Number: number of threads of the consumer, the software module of the block that provides input to process by taking it from the block's work queue.