> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/engines/configure-engines/edit-the-engine-configuration/common-properties-when-editing-an-engine-configuration.md).

# Common Properties When Editing an Engine Configuration

Configure common engine properties in Cortex XSOAR 6.12.

The following table describes the common properties when editing an engine configuration using the `d1.conf` file (located by default at **`/usr/local/demisto/`**) or in the **JSON formatted configuration** dialog box in Cortex XSOAR.

| Property                           | Type         | Values                                                                                                                                                                                                                                                                                                                                                                                                                   | Edit                                                                         |
| ---------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
| **`http_proxy`**                   | String       | The IP address of the HTTP proxy through which the engine communicates. For an example, see [Configure the Engine to Use a Web Proxy](/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/engines/configure-engines/edit-the-engine-configuration/common-properties-when-editing-an-engine-configuration/configure-the-engine-to-use-a-web-proxy.md).                                                                 | The engine `d1.conf` file.                                                   |
| **`https_proxy`**                  | String       | The IP address of the HTTP/s proxy through which the engine communicates. For an example, see [Configure the Engine to Use a Web Proxy](/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/engines/configure-engines/edit-the-engine-configuration/common-properties-when-editing-an-engine-configuration/configure-the-engine-to-use-a-web-proxy.md)                                                                | The engine `d1.conf` file.                                                   |
| **`LogLevel`**                     | String       | <ul><li><strong><code>debug</code></strong></li><li><strong><code>info</code></strong></li><li><strong><code>warning</code></strong></li></ul>                                                                                                                                                                                                                                                                           | The engine `d1.conf` file or in the JSON formatted configuration dialog box. |
| **`BindAddress`**                  | String       | The port on which the engine listens for agent connection requests and communication task responses.                                                                                                                                                                                                                                                                                                                     | The engine `d1.conf` file.                                                   |
| **`EngineURLs`**                   | String array | An array of Server addresses to which the engine tries to connect. If you change the server URL, you need to update this parameter.                                                                                                                                                                                                                                                                                      | The engine `d1.conf` file.                                                   |
| **`LogFile`**                      | String       | Path to the **`d1.log`** file. If you change the name or location of the **`d1.log`** file, you need to update this parameter.                                                                                                                                                                                                                                                                                           | The engine `d1.conf` file.                                                   |
| **`log.rolling.maxfilesize`**      | String       | The maximum size in MB to retain log files based. Default is 20 MB.                                                                                                                                                                                                                                                                                                                                                      |                                                                              |
| **`log.rolling.backups`**          | String       | The maximum number of log files to retain. Default is 3.                                                                                                                                                                                                                                                                                                                                                                 |                                                                              |
| **`log.rolling.maxage`**           | String       | <p>The maximum number of days to retain old log files based on the time stamp encoded in the file name. Default is 0 (not to retain old log files based on age).</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>A day is defined as 24 hours and may not exactly correspond to calendar days due to daylight savings, leap seconds, etc.</p></div> |                                                                              |
| **`engine.allow.data.collection`** | String       | <p>Disables the option to send communication task forms through the engine.</p><ul><li>false</li></ul>                                                                                                                                                                                                                                                                                                                   | The engine `d1.conf` file.                                                   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/engines/configure-engines/edit-the-engine-configuration/common-properties-when-editing-an-engine-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.