Engine Server Configurations - Administrator Guide - 6.9 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Product
Cortex XSOAR
Version
6.9
Creation date
2022-09-29
Last date published
2024-04-08
End_of_Life
EoL
Category
Administrator Guide
Abstract

Server configurations for engines.

Key

Description

Default

condition.ask.external.link

The address (including the HTTPS prefix) of the engine used for external user communication in a conditional task. For more information, see Configure Access to Communication Tasks through an Engine.

N/a

data.collection.external.link

The address (including the HTTPS prefix) of the engine used for external user communication in a data collection task. For more information, see Configure Access to Communication Tasks through an Engine.

N/a

engine.test.command.timeout<brand-name>

Increases the timeout, in seconds, for a specific integration when using an engine. For example, change it to 300 seconds. Type in this format adding the brand name: engine.test.command.timeoutTanium.

60

engine.to.server.proxy

Whether the engine connects the server without using a proxy. For more information, see Configure the Engine to Call the Server Without Using a Proxy.

true

engines.notification.users

Specifies which users receive an email notification when an engine disconnects. A comma-separated list of Cortex XSOAR users. For example, user1,user2,user3. For more information, see Notify Users When an Engine Disconnects.

N/a

workers.count.tasks

Configures the number of workers for the server. Useful if experiencing performance issues.

4 workers per CPU core